Tokenization

Using Tokenization technology allows you to securely store one or more payment information for each shopper. This way, you can provide subscription payments, automatic recharge of shopper accounts, and faster checkout experiences by using their stored cards. We support major card brands and some local payment methods. Benefits of tokenization include:

1. Allow shoppers to store their payment information for faster checkout later.
2. Provide shoppers with their stored payment information for subsequent payments.
3. Save payment information for subscriptions or contracts with non-fixed schedules.
4. Submit subsequent payments for subscriptions or automatic recharge of shopper accounts.

To save shoppers' payment information, you only need to pass some additional parameters when making payments. In the first payment, we collect payment information from the shopper and generate a token for them. Then, the token is sent to your server for future use. For subsequent payments, you need to make requests using the token. By default, tokens are stored by merchant accId.

Note

To collect raw credit card data, you need to be fully compliant with PCI DSS (Payment Card Industry Data Security Standard) requirements. If you are already fully compliant with PCI DSS requirements, you can choose to create your own Token Vault, or store raw credit card data to provide faster checkout options.

Note

If you are not yet fully compliant with PCI DSS (Payment Card Industry Data Security Standard) requirements, we recommend using Tokenization technology for payments. By using tokens, you can provide your shoppers with an improved checkout experience.

Documentation Navigation

Tokenization-related capabilities are organized in the documentation as follows:

• NetworkToken: for network-token-based payment scenarios in international card payments.
• Saved Cards / CardOnFile: for international card saved-card scenarios, including the first payment and save-card flow, checkout repeat purchases, server-side token repeat purchases, and CardOnFile transaction rules.
• CodeGrant: for token-based signing or authorization scenarios in some local payment methods.

Note

If you need recurring billing scenarios, please refer to the documents under the Recurring section. That capability is not expanded under the current Tokenization section.

Previous pageRefund

Next pageNetworkToken