{"title":"Recurring payments","category":"default","creationDate":1754569620,"content":"

Country availability<\/h2>\n

PaySafeCard supports tokenization<\/a> for recurring payments in the following countries:
\nAustria, 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.<\/p>\n

Prepare for tokenization<\/h2>\n

PaySafeCard has no setup requirements. Your existing PaySafeCard account will immediately work for recurring payments.<\/p>\n

\n

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.<\/p>\n<\/div>\n

Set parameters to flag transactions<\/h2>\n

When you make a \/payments<\/a> request to create a token<\/a>, or pay with a token<\/a> you must include:<\/p>\n\n\n\n\n\n\n\n\n
Parameter<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
recurringProcessingModel<\/a><\/td>\nWhen you first create a token, recurringProcessingModel<\/code> 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><\/strong><\/span>: 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><\/strong><\/span>: A transaction that occurs on a non-fixed schedule and\/or have variable amounts.- Subscription<\/a><\/strong><\/span>: 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.<\/td>\n<\/tr>\n
shopperInteraction<\/a><\/td>\nIndicates 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<\/strong><\/span>).<\/td>\n<\/tr>\n
shopperReference<\/a><\/td>\nYour 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.<\/td>\n<\/tr>\n
storePaymentMethod<\/a><\/td>\nWhen you first create a token, set to true to store the shopper's payment details. For subsequent payments, this parameter is not required.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

Even though the recurringProcessingModel<\/code> contains the term card<\/strong>, recurring payments for PaySafeCard is only supported whenever the shopper authorizes with a myPaysafecard account (wallet) and not a PaysafeCard PIN\/card.<\/p>\n<\/div>\n

Create PaySafeCard tokens<\/h2>\n
\n

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.<\/strong> 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.<\/p>\n<\/div>\n

When the preparation<\/a> is completed, creating and using tokens for PaySafeCard payments is the same as described for tokenization in general:<\/p>\n

    \n
  1. \n

    To create a token through a zero-value authorization request, in your initial \/sessions<\/a> or \/payments<\/a> request include:<\/p>\n\n\n\n\n\n\n\n\n
    Parameter<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    value<\/a><\/td>\nSet to 0 when making a zero-value authorization request.For with-purchase tokenization, simply provide the correct amount and include the below parameters.<\/td>\n<\/tr>\n
    recurringProcessingModel<\/a><\/td>\nThe type of transactions you can use the stored details for.<\/td>\n<\/tr>\n
    shopperReference<\/a><\/td>\nYour unique reference for the shopper.<\/td>\n<\/tr>\n
    storePaymentMethod<\/a><\/td>\nThe setting for storing the shopper's payment details.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ol>\n

    Example \/payments<\/a> request (creating token):<\/p>\n

    \n <\/code-sample>\n<\/div>\n
      \n
    1. 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<\/a>.<\/li>\n<\/ol>\n

      Make payment with existing tokens<\/h2>\n

      In subsequent transactions, use storedPaymentMethodId<\/code> to provide the token value obtained from the webhook. This is Adyen's reference to the token \/ myPaysafeCard account.<\/p>\n

      The recurringProcessingModel<\/code> and shopperInteraction<\/code> indicate a type of recurring processing is taking place (shopperInteraction<\/code> = contAuth<\/strong><\/span>) and the type of recurring model that is applicable (for example Subscription<\/strong><\/span>).<\/p>\n

      \n <\/code-sample>\n<\/div>\n

      Customer data exchange<\/h2>\n

      When the shopper confirms the payment and a myPaysafeCard wallet was used, you will be able to retrieve the customer\u2019s data via Customer Data Exchange<\/a>. 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.<\/p>\n

      Testing<\/h2>\n

      Before testing recurring payments, create a myPaysafeCard test account (wallet). To request a test account, contact the Paysafe technical support team<\/a> with the following details:<\/p>\n