Tokenization

With tokenization, the transaction data is replaced by a token, which is a randomly generated code that cannot be mathematically reversed. When a merchant submits a debit or credit card payment, a unique token is generated and returned to the merchant for future use.

Because the token can always be referenced back to the original card number, it can be used to process recurring payments on that card. Tokens can also track customer transactions for marketing purposes.

A Token Zone Name field is available on the Merchant Parameters page, and is initially disabled (NONE). A token zone name can be selected only at the merchant level if the BIN is participating in tokenization. Once the first terminal with tokenization is set up for the merchant, the Token Zone Name field is enabled populated with the value chosen at the terminal level.

Only those custom token zone names that are flagged for display at BIN level are displayed at the merchant level. Should the user attempt to change a Token Zone Name that terminals are currently using, a warning message displays, indicating that changing the Token Zone Name at the merchant level will prevent the use of existing tokens at the terminals. A user cannot de-select tokenization participation at the merchant level if there are still terminals participating in tokenization.

Note: After the first Token Zone Name is selected with the first terminal setup, the subsequent token zone names are selected at the merchant level. the token zone name selected at the merchant level is applied to all terminals.