Card tokenization

Tokenization by Processor

Tokenization by payment processors replaces sensitive payment card data with unique tokens generated by the processor.
The processor uses the tokens to perform transactions securely, without the need to handle confidential card information in the transactional process.
To tokenize your customers' cards:

• Request PSP tokenization functionality from the merchant to DEUNA.
• Implement processor methods that support card tokenization.
• In some cases you must have a prior agreement with the processor for tokenization
  The main characteristics of tokenization are:
• Transparency: Processor tokenization integrates transparently into the transaction flow.
• Flexibility: Use multiple processors for tokenization and make purchases without CVV.
• CVV Update: Update the CVV of cards already existing in the vault-api, in case it is requested by the processor.

  📘

  For more information about cards, go to Create card.

Exclude CVV

Some processors require that the user's tokenized cards re-enter the CVV.

📘

Check the available payment methods.

If the response from a payment processor contains the "exclude_cvv" field with the boolean value "true", it does not require entering the CVV.
For payment methods that already have a tokenized card in the DEUNA network, the CVV should always be requested when processing a transaction for cards used for the first time by a user or that have not been saved.
📘 Go to Create Payment for more information about CVVs. Within the credit_card node it documents how to send a CVV.
Example

{
  "enabled": true,
  "method_type": "credit_card",
  "processor_name": "kuski",
  "exclude_cvv": true, 
}