Mandarin

# Card tokenization

# Types of tokenization

Types of tokenization:

  • card number tokenization (one-side binding). Used to avoid storing the card number in your system. In a synchronous response, you will immediately receive a card token. Used exclusively for card payment transactions.
  • tokenization of full card data (full binding). Includes redirecting the user to the Mandarin payment page to enter card data and completing the 3-D Secure procedure. Then the checksum is written off and the payment is subsequently cancelled. If the entire process was successful, then the token can be used for payments (both with and without user participation) and for payments to cards.

# Tokenization of full card data

Tokenization of full card data involves writing off a checksum (usually 1 ruble) with subsequent cancellation of the payment. In some cases, authorization is possible instead of write-off. During debiting, the payer enters the code 3-D Secure, which allows confirm that he has access to this card.

After the checksum is written off, you will receive a callback notification that includes the card token, masked card number, month and year of expiration, card owner name, tokenization status. All card details were saved on the Mandarin servers, except for the CVV/CVC code and dynamic data (code 3-D Secure). You can now use your tokenized card.

Full card data tokenization statuses:

  • Success (successful). Recurrent payments, payments with user participation, and payments to a card are possible.

  • Fail (unsuccessful).

  • Payout-only (card details are correct, but there are no money on it means). The card can enter this status as during tokenization (if there is no write-off amount on the card) and after (if the limit is exceeded unsuccessful auto write-offs in a row).

Full card data token in the payout-only status (can be used in the same way as in In case of tokenization only the card number. That is, for payments to the card, as well as for payments involving the payer (you will need to enter CVV/CVC and go through the procedure 3-D Secure).

# Saving the card on the payment page

Separate from tokenization: Card details can be stored on the payment page for quick re-entry (without creating a binding token in the API). Briefly - in Payment options; request parameters - in Accepting payments (API).