# 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 the synchronous response, you will receive the card token immediately. It is used exclusively for card payment operation.
- full card data tokenization (full binding). Includes redirection of the user to the Mandarin payment page to enter the card data, passing the 3-D Secure procedure. Then the control amount is deducted and the payment is cancelled. If the entire process is successful, the token can be used for payments (with or without the user's participation) and for card payments.
# Tokenization of full card data
Tokenization of full card data involves writing off a control amount (usually 1 ruble) followed by cancellation of the payment. In some cases authorization instead of writing off is possible. During debiting the payer enters the code 3-D Secure, which allows confirm that he has access to this card.
After the checksum is debited, you will receive a callback notification including the card token, masked card number, expiration month and year, cardholder name, tokenization status. All card details except CVV/CVC code and dynamic data (code 3-D Secure) have been stored on Mandarin servers. Now you can use the tokenized card.
Full card data tokenization statuses:
Success. Recurring payments, payments with user participation, payments to the card are possible.
Fail (unsuccessful).
Payout-only (card details are correct, but there is no money on the card funds). The card can go to this status both during tokenization (if card has no debit amount), and after (when the limit is exceeded unsuccessful autosignings in a row).
Full card data token in payout-only status can be used in the same way as card number tokenization: for payments to the card, as well as for payments with the participation of the payer (entry of CVV/CVC and passing through the procedure 3-D Secure will be required).