Tokenization with Custom UI

Tokenization

Tokenization replaces sensitive payment data such as credit card number with a unique identifier or token. Once you obtain a token for card data or a bank account, you can charge transactions on these tokens without having to store the payment data.

Supported payment methods to store

Currently tokenization of credit card and bank account information is supported.

The following card details can be tokenized:
  • card holder,
  • card number,
  • expiration date.

CVV cannot be stored with a token, you can prompt the shopper to re-enter the CVV code for subsequent transaction, if required.

The following bank account details can be tokenized:
  • bank account holder,
  • IBAN.


Storing payment data

SDK provides two options for storing the payment data:

  • Store the data during a payment: When a shopper is checking out for the first time, he has to fill in his complete payment data. Use this option to automatically store his data during the payment for reuse in later transactions.
  • Store the data as stand-alone: If your site provides shoppers with an administrative area where they can register their payment details independent of a checkout-process, this option is for you.

Store the data during a payment

2. Receive a token along with payment status

Our server will generate token for the passed payment details and return it with the payment status (step 3).
Parameter registrationId is your generated token. Your server is responsible for handling and storing the token.

Here is an example of the Payment Status response:

{
  "registrationId":"8a82944a580a782101581f3a0b4b5ab9",
  "result":{
    "code":"000.100.110",
    "description":"Request successfully processed in 'Merchant in Integrator Test Mode'"
  },
  // ...
}

Store the data as stand-alone

It is also possible to create a just registration separate from any later payment.
A registration-only transaction is basically using the same workflow and parameters as a payment. You just need to use another endpoint when submitting transaction.

Using payment data

Skip 3D-Secure for stored cards

Your server should send one additional parameter recurringType=REGISTRATION_BASED during Prepare the checkout.