Skip to main content
3-D Secure (3DS) can be configured in two ways: for a specific connection or for an entire merchant account. This guide walks through both options. This setup is only required when using Gr4vy’s 3DS solutions, such as Gr4vy Embed or the Hosted 3DS page. No configuration is needed if passing through 3DS data from an external source. The main difference between the two options is that a merchant account-level configuration can be shared across multiple payment service connections. The following table highlights the main differences.
FeaturePer-ConnectionPer-Merchant Account
Shared scheme profilesNoYes
Metadata filtersNoYes
Click to Pay supportNoYes
Native mobile SDK supportNoYes

​
Configuration options

​
Per-connection configuration

To configure 3DS for a specific payment service connection, follow these steps:
  1. Go to the Connections tab in the Gr4vy Admin Panel.
  2. Select an active card connection and navigate to the 3-D Secure tab.
  3. Enable the Enable 3DS toggle.
  4. Add a scheme profile for each card scheme to enable 3DS for.

​
Merchant account-level configuration (Beta)

A new option to configure 3DS at the merchant account level is being rolled out. This simplifies the setup by allowing a single configuration to be shared across multiple connections.
This feature is currently in beta. Please contact the support team to enable it for the account.
Once enabled, 3DS can be configured for a merchant account by following these steps:
  1. Go to Settings in the Gr4vy Admin Panel.
  2. Click Edit merchant and select the 3-D Secure tab.
  3. Add a scheme profile for each card scheme to enable 3DS for.
After setting up the merchant account-level configuration, 3DS still needs to be enabled on each connection to use it with.
  1. Go to the Connections tab.
  2. Select an active card connection and go to the 3-D Secure tab.
  3. Switch the Enable 3DS toggle on.

​
Scheme profile resolution

When a transaction requires 3DS, Gr4vy determines which configuration to use based on the following order:
  1. Connection-level profile: If a 3DS profile is configured for the card’s scheme on the specific connection, that profile is used.
  2. Merchant account-level profile: If no connection-level profile is found, Gr4vy uses the merchant account-level configuration. This resolution takes into account the buyer’s country and any metadata passed in the transaction to select the appropriate profile.