Skip to main content
This page is part of the Payments Library Guides. For how the library handles the 3DS flow itself, see 3D Secure.
3D Secure authentication identifies you, the merchant, to the card networks and to the cardholder during the authentication challenge. Orchestra cannot perform that authentication on your behalf using generic details, so you must supply your own.
3DS merchant details are required whenever Perform 3Ds? is enabled on a CardPay eWallet account. Orchestra has no default or fallback 3DS merchant. An account with 3DS enabled and no merchant details will save successfully, but every 3DS transaction on it will fail.

​
What the details are

The information falls into three groups.

​
Merchant identity

​
Acquirer details, per card brand

For each card brand you process, you need a set of identifiers issued by your acquiring bank: You only need entries for the brands you actually process. If you accept Visa and Mastercard but not Amex, supply two sets.
These identifiers are issued by your acquiring bank, and they are different from the API credentials you already used to configure your PSP account in Orchestra. If your PSP sends you an integration guide or API documentation in response, that is not the right information. Ask specifically for your acquirer BIN, MID and MCC per card scheme, for 3D Secure enrolment.

​
How to obtain them

Request the details from your PSP or directly from your acquiring bank. A request along these lines usually gets the right answer:
We are enabling 3D Secure and need our 3DS merchant enrolment details. For each card scheme we process, please provide the Acquirer BIN, our Merchant ID (MID), and our Merchant Category Code (MCC).
Turnaround varies by acquirer, so start this early. It is a common cause of delay when going live with 3DS.

​
Where to enter them

In the Orchestra Portal, on the CardPay eWallet account:
  1. Go to eWallet Accounts and open or create a CardPay account.
  2. Tick Perform 3Ds?.
  3. Tick I Have 3DS Merchant Details. This reveals the remaining fields.
  4. Fill in Merchant Requestor Id Suffix and Merchant Url.
  5. In the table below, add one row per card brand, entering the Acquirer BIN, brand, MCC and Merchant ID for that brand. Click + Add for each row.
  6. Click Save.
For the full CardPay field reference, see Creating eWallet Accounts.

​
If you skip this step

An account saved with Perform 3Ds? enabled and I Have 3DS Merchant Details left unticked, or with an empty brand table, is accepted by the portal but cannot process 3DS transactions. Attempts fail at transaction time, currently with a generic An unexpected error occurred message rather than a specific one. If you are seeing that error on a 3DS-enabled account, check this configuration first. See also Troubleshooting.

3D Secure

How the library handles the 3DS flow

Creating eWallet Accounts

Full CardPay field reference

PSP Setup

Configure your payment processor

Troubleshooting

Common issues and fixes