Country availability
PaySafeCard supports tokenization for recurring payments in the following countries:
Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lichtenstein, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United Kingdom.
Prepare for tokenization
PaySafeCard has no setup requirements. Your existing PaySafeCard account will immediately work for recurring payments.
We strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of complaints.
Set parameters to flag transactions
When you make a /payments request to create a token, or pay with a token you must include:
| Parameter | Description |
|---|---|
| recurringProcessingModel | When you first create a token, recurringProcessingModel indicates what type of recurring payment the token is intended for.For subsequent payments, it indicates the type of recurring payment. Possible values: - CardOnFile: A transaction where shopper's myPaysafeCard account details are stored to enable one-click or omnichannel journeys, or to offer a faster checkout later. - UnscheduledCardOnFile: A transaction that occurs on a non-fixed schedule and/or have variable amounts. - Subscription: A transaction for a fixed or variable amount, which follows a fixed schedule. Adyen propagates these parameters to PaysafeCard. Ensure you choose the most fitting model to ensure maximum conversion. |
| shopperInteraction | Indicates the sales channel through which the shopper gives their account details. For online transactions, this is Ecommerce. For subsequent payments, indicates whether the shopper is a returning customer (ContAuth). |
| shopperReference | Your unique reference for the shopper. Minimum length: three characters. Note that the value is case-sensitive. Do not include personally identifiable information (PII), such as name or email address. |
| storePaymentMethod | When you first create a token, set to true to store the shopper's payment details. For subsequent payments, this parameter is not required. |
Even though the recurringProcessingModel contains the term card, recurring payments for PaySafeCard is only supported whenever the shopper authorizes with a myPaysafecard account (wallet) and not a PaysafeCard PIN/card.
Create PaySafeCard tokens
When shoppers pay with PaySafeCard they can use one of two funding sources: Wallet or Voucher/PIN cards. Only Wallet payments are eligible for tokenization. If a tokenization request is made for a Voucher/PIN card payment, the transaction will still be processed, but no token will be generated. Note that you cannot control which funding source shoppers use, and PaySafeCard does not indicate this information in the payment response.
When the preparation is completed, creating and using tokens for PaySafeCard payments is the same as described for tokenization in general:
-
To create a token through a zero-value authorization request, in your initial /sessions or /payments request include:
Parameter Description value Set to 0 when making a zero-value authorization request.
For with-purchase tokenization, simply provide the correct amount and include the below parameters.recurringProcessingModel The type of transactions you can use the stored details for. shopperReference Your unique reference for the shopper. storePaymentMethod The setting for storing the shopper's payment details.
Example /payments request (creating token):
- Proceed as described for tokenization in general: get the shopper reference and the token by listening to webhooks, and use this data in future payments for the shopper. For instructions on obtaining the token and enabling webhooks for recurring payments, see Create tokens.
Make payment with existing tokens
In subsequent transactions, use storedPaymentMethodId to provide the token value obtained from the webhook. This is Adyen's reference to the token / myPaysafeCard account.
The recurringProcessingModel and shopperInteraction indicate a type of recurring processing is taking place (shopperInteraction = contAuth) and the type of recurring model that is applicable (for example Subscription).
Customer data exchange
When the shopper confirms the payment and a myPaysafeCard wallet was used, you will be able to retrieve the customer’s data via Customer Data Exchange. For any zero-amount transactions used to create a recurring relationship, this data will not be returned. For any (subsequent) payments of an amount greater than zero, customer data exchange works as described.
Testing
Before testing recurring payments, create a myPaysafeCard test account (wallet). To request a test account, contact the Paysafe technical support team with the following details:
- The country for the test account
- A date of birth for the test user
When the test account is created, test the following scenarios in your Adyen test environment:
- Initiate a payment to create a token
- Receive the webhook that confirms tokenization
- Process the different recurring models
- Handle errors
Perform the same scenarios in your live environment.
Error handling
For refusals the two main errors are:
| Error message | PaySafeCard error code | How to proceed |
|---|---|---|
| Insufficient funds on customer PaysafeCard account. | 2004 | There is not enough balance on the myPaysafeCard account. You can do either of the following:
|
| Token not valid. | 10033 | The token is no longer valid. This can happen when the token expires if there is more than a year of lack of activity. It is also possible that the token was never (properly) created. Ask the shopper again to approve recurring payments with a new zero-value authorization request. |