Get Started
Hellgate® provides a simple and convenient but also secure way to integrate 3DS2 into your payment flows. Our services are designed to make it easy to authenticate cardholders and reduce fraud across all your acquirers, while still providing a seamless user experience for your customers.
Setup
In order to use 3DS2, you need to ensure that you have the following data available:
- Acquirer Merchant ID (MID)
- Acquirer BIN
- Merchant Category Code (MCC)
Please reach out to our customer support to get the necessary configuration in place.
Integration
The integration of 3DS2 in your experiences is fairly simple. Our SDKs take care of the required coordination and automatically handle the authentication process.
Please reach out to our customer support to activate 3DS2 for your use-cases.
Supported Scenarios
Hellgate® supports 3DS2 in variety of scenarios to ensure that you can provide a seamless experience for your customers.
Account Verification
In some situations, the integrator must verify the identity of a cardholder before proceeding with payment-related processes. A good example of this is the process of adding cardholder data to file and provisioning network tokens. In these systems, an identification and verification (ID&V) process must be carried out beforehand.
Hellgate® supports automatic 3DS2 authentications as part of the tokenization process. If activated, the customer will automatically authenticated before a token is issued.
Please reach out to our customer support to activate 3DS2 for tokenization on your account.
Payment Authentication
This is the standard scenario where the cardholder is authenticated during the payment process. Hellgate® supports 3DS2 authentications as customer interactions in our processes. 3DS2 is automatically triggered based on a defined rule set. If the integration is done via our SDKs, the integration is quite simple.