Tokenization is a security and compliance feature that mitigates risk and lowers the scope of PCI compliance. In a tokenization workflow, payment data is exchanged with the payment gateway for a token that represents the payment data. This data cannot be decrypted.
Multi-gateway tokenization allows you to tokenize payment data across multiple payment gateways. The payment gateways may be for different Merchant Identifiers (MIDs) at the same payment gateway that may be configured differently based on your financial operations, or they may be for different MIDs across different payment gateways.
Use Cases #
- Multiple MIDs with the same payment gateway. For example, the payment gateway is Cybersource. One MID is configured for Strong Customer Authentication (SCA) mandated transactions by Payment Service Directive 2 (PSD2) for the European Economic Area. Another MID is configured without SCA for the United States of America.
- Multiple MIDs with a different payment gateway. For example, there are two payment gateways: Cybersource and Authorize.net. One gateway is the primary (Cybersource), and the other is the secondary (Authorize.net). In the unlikely event that Cybersource is unavailable as the primary payment gateway, transactions may sent to Authorize.net as the secondary payment gateway.
Prerequisites #
- You must be on the latest version of Chargent to use Multi-Gateway Tokenization, which can be installed or updated using our Package Installation Manager (PIM).
- Multi-Gateway Tokenization is offered as part of Chargent’s Growth or Enterprise Editions. For more information, see our Pricing Page.
- Multi-Gateway Tokenization is a pro-code solution recommended only for experienced Salesforce Developers. See our Developer Documentation for technical guidance.
Before You Begin #
Before starting development related to Multi-Gateway Tokenization, ensure you have an account with at least two gateways that support tokenization or multiple merchant identifiers (MIDs) for the same gateway.
See the Gateway Setup and User Guides to learn how to integrate a gateway using Chargent.
Setting Up Multiple Gateway Tokenization #
Ready to start developing your Multi-Gateway Tokenization solution? Chargent supports a single method for multi-gateway tokenization requests across multiple API types. Developers can implement Multi-Gateway Tokenization using Chargent’s REST API, Apex, or Flow. Learn more about each method by visiting our developer documentation.
See Also
The Benefits of Multi-Gateway Tokenization
Gateway Setup and User Guide
Chargent for Developers
Understanding Tokenization