Setup 3DS card schemes - Gr4vy

When you set up 3DS, add a scheme profile to your merchant account for each card scheme you want to authenticate. Gr4vy sends these details to the 3DS server when it authenticates a transaction. Most of them come from your acquirer, and can differ per card scheme.

Field	API field	Description
Acquirer BIN	`merchant_acquirer_bin`	The acquirer BIN for the card scheme. Your acquirer provides this value. Up to 11 characters.
Acquirer Merchant ID	`merchant_acquirer_id`	The merchant ID provided by the acquirer used by your payment service. Up to 35 characters.
Merchant Name	`merchant_name`	Your merchant name. This is sent on to the 3DS provider. Up to 40 characters.
Merchant Country Code	`merchant_country_code`	The merchant’s country, as an ISO 3166-1 numeric three-digit code. For example, `840` for the United States.
Merchant Category Code	`merchant_category_code`	The four-digit merchant category code (MCC) for the merchant account. This describes the type of business, product, or service offered.
Merchant URL	`merchant_url`	The URL of the website on which payments are made.

Where to find these detailsMost of these identifiers can be found in the payment service’s dashboard, or requested from your acquirer or payment service. If you use more than one acquirer, see 3DS with multiple connections.

Merchant account-level fields

A merchant account-level configuration has these extra fields. They control which transactions use the configuration, not what’s sent to the 3DS server.

Field	API field	Description
Scheme	`scheme`	The card scheme this configuration applies to.
Currency	`currency`	The ISO 4217 currency this configuration applies to. Select All currencies in the dashboard, or set `null` in the API, to use it for every currency. A configuration for a specific currency is used before one for all currencies.
Metadata	`metadata`	Key-value pairs that a transaction’s `metadata` must contain for this configuration to be used. Leave this empty to use the configuration for every transaction with this scheme and currency.

Metadata on a 3DS configuration is a filter. If you add metadata, the configuration is only used for transactions that send all of the same key-value pairs. If no configuration matches, the transaction is processed without 3DS. See scheme profile resolution for details.