Getting Started

Internal Tokenization

Internal tokenization refers to situations in which tokens are provided by the System.

Tokenization logic is as follows:

1. In the first transaction the merchant is conducting with a specific credit card, the merchant activates the tokenization service in the transaction request by passing Tokenization=Internal and the credit card information is sent to the System
2. The System receives the credit card information from the Merchant
3. If the merchant has specified internal tokenization Tokenization=Internal, the System encrypts the credit card information, saves it in its own database in the encrypted mode, and issues a PaymentMethodToken that gets returned to the merchant in the first server response. The PaymentMethodToken is used by the merchant with subsequent transactions on this credit card, instead of credit card information
4. In subsequent transactions on this card, the System checks the PaymentMethodToken against the database and finds the relevant transaction based on the token. It then decrypts the related credit card information and uses it in place of the token
5. With internal tokenization, you may pass your credit card CVV value if required by the bank. Consult with your bank for more details (some banks require CVV just for the first transactions).

External Tokenization

With external tokenization, the external Processor provides the tokens. Internal and external tokenization follow nearly identical tokenization logic.