Tokenization at API level

What is it?

When applied to the payment industry, tokenization is generally used for credit card payments. Now also made available for the debit payment methods, iDEAL and SOFORT Banking. Meaning that for every credit or debit card, a unique Recurring ID is created and subsequently encrypted as a token. The payment token itself is the unique string of numbers. As result, a unique security identifier is created to finalize a payment. Therefore, potential risks are reduced.

How does it work?

The token is a unique number generated by MultiSafepay that refers to the credit or debit card details provided by the customer upon completing the initial transaction. Creating a token allows you to save a customer’s payment method. In return, a token can be used for recurring and subscription payments. It also allows the customer to finalize a payment in one step by selecting the stored payment details in his or her account.

Tokenization gives you the possibility to link the payment details of a customer to a reference ID, allowing you to:

  • Create recurring and/or subscription payments, recommended to any businesses with subscription payments or which generate significant business with repeat customers
  • Due to the tokens that are securely stored, they can be used to enable “one-click” payments for future transactions
  • List multiple tokens to a customer reference
  • Retrieve token information or delete a token.

Available for?

Available for JSON API only.
full API documentation on Tokenization

Tokens processed by the payment method Direct Debit “DIRDEB” are originally received by an iDEAL or SOFORT Banking transaction.

Parameter Type Description
type string Specifies the payment flow for the checkout process. Options: direct, redirect
gateway string The unique gateway_id to immediately direct the customer to the payment method. You retrieve these gateways using a gateway request. Option: AMEX, VISA, MASTERCARD and DIRDEB
reference string Customer reference to link a token