- Integration Guidelines
- Integrating the Merchant Boarding API
- Update Merchant Payment Details
- Enabling Network Tokenization
Enabling Network Tokenization
This page describes how to use the Update Merchant Payment Details or Create or Updaterequest to enable/disable, and configure network tokenization.
The gateway currently supports the following network tokenization, service providers:
- Mastercard Digital Enablement Service (MDES)
- Visa Token Service (VTS)
To enable and configure network tokenization for a scheme, you must have MDES and VTS tokenization privileges. Provide the following fields specific to the network tokenization provider.
For MDES:
merchant.tokenization.mdesSchemeTokenUsage: Provide this field to enable the use of MDES network tokens in transaction requests, for example, Authorize or Pay, from the selected token repository for this merchant. You can choose to enable them for Production and Test merchant profiles, or only Test.- ENABLE_FOR_PRODUCTION_AND_TEST_MERCHANT_PROFILE
- ENABLE_FOR_TEST_MERCHANT_PROFILE_ONLY
merchant.tokenization.tokenRepository.schemeTokenization.mdes.tokenRequestorId: Provide the unique identifier assigned to the merchant by MDES. This identifier is used for all the merchants using the same token repository. Once configured, this value cannot be updated. If you want to use a new identifier, a new token repository must be assigned to the merchant.merchant.tokenization.tokenRepository.schemeTokenization.mdes.merchantTradingName: The trading name of the merchant. If you provide this field and the repository is not yet enabled for the scheme tokenization, that is, the merchant.tokenization.tokenRepository.schemeTokenization.mdes.tokenRequestorId field is not present, then the gateway attempts to enable the scheme tokenization with MDES by registering the merchant with MDES and retrieving a token requestor ID (TRID). If the registration was successful, the Retrieve Merchant response contains the TRID in the field merchant.tokenization.tokenRepository.schemeTokenization.mdes.tokenRequestorId and the repository is enabled for the scheme tokenization for the Mastercard cards.
Once approved, the usage fields are displayed on the Tokenization Configuration page within the Manage Merchants section, in the Merchant Manager. The configuration field, that is, tokenRequestorId is displayed on the Token Repository page in the Merchant Manager.
For VTS:
merchant.tokenization.vtsSchemeTokenUsage: Provide this field to enable the use of VTS network tokens in transaction requests, for example, Authorize or Pay, from the selected token repository for this merchant. You can choose to enable them for Production and Test merchant profiles, or only Test.- ENABLE_FOR_PRODUCTION_AND_TEST_MERCHANT_PROFILE
- ENABLE_FOR_TEST_MERCHANT_PROFILE_ONLY
merchant.tokenization.tokenRepository.SchemeTokenization.vts.tokenRequesterId: Provide the unique identifier assigned to the merchant by VTS. This identifier is used for all the merchants using a particular token repository. Once configured, this value cannot be updated. If you want to use a new identifier, a new token repository must be assigned to the merchant.merchant.tokenization.tokenRepository.SchemeTokenization.vts.relationshipId: Provide the unique identifier assigned to the merchant by VTS. This identifies the merchant, in the request submitted by the gateway to VTS. The same identifier is used for all the merchants using this token repository. Once configured, this value cannot be updated.
Once approved, the usage fields are displayed on the Tokenization Configuration page within the Manage Merchants section, in the Merchant Manager. The configuration fields, that is, tokenRequestorId and relationshipId are displayed on the Token Repository page in the Merchant Manager.
merchant.tokenization.tokenRepository.tokenManagementStrategy to "UNIQUE_TOKEN" when enabled for network tokens. When merchant.tokenization.tokenRepository.tokenGeneration is set to PRESERVE_6_4, note that the gateway token may not represent the actual FPAN if the card is updated by the issuer, for example, expired card, lost or stolen card.