Merchant 3DS Authentication
By default, the gateway handles the full 3D Secure (3DS) authentication flow on behalf of the merchant. When Merchant 3DS Authentication is enabled, the gateway will not trigger its own 3DS verification and will instead expect the merchant to provide their own authentication data obtained from an external 3DS MPI (Merchant Plug-In).
Merchant 3DS Authentication must be enabled for your merchant account. Contact your onboarding manager to activate this service. It defaults to disabled.
How It Works
When this service is active:
- The merchant performs 3DS authentication independently using their own MPI.
- The merchant includes the resulting authentication values in the payment request.
- The gateway uses the provided 3DS data to process the transaction directly — no redirect or challenge is triggered.
Required Parameters
When submitting a payment with your own 3DS authentication, include the following parameters in the Payment API request:
| Parameter | Description |
|---|---|
threeds_authentication_value | The 3DS authentication value (CAVV/AAV) obtained from your MPI. |
threeds_directory_server_trans_id | The Directory Server Transaction ID from your 3DS authentication. |
Both parameters must be provided together. When present, the gateway skips its own 3DS flow and returns a direct response.
Integration
For full details on the server-to-server flow with and without merchant 3DS authentication, see the Server-to-Server Processing guide.