In order to process transactions using Spreedly’s 3DS2 solution and help identify which merchant is requesting authentication, Spreedly has created an entity called a Merchant Profile that allows customers to save merchant information. This also generates an SCA Provider Key, another entity from Spreedly that allows customers to make 3DS2 Authentication transactions and holds the credentials required for Spreedly to interact with a 3DS2 server.

You will need to set up a Merchant Profile after you create your payment gateway with 3DS2 configured. We cover all of this information here, including steps for creating a test Merchant Profile and steps specifically for Stripe users.

Required Fields to Configure a Merchant Profile:

The required fields can be located by contacting your acquirer, or, in some cases, can be located by using your payment processor. Find more details from Spreedly here.

There is a required set of data fields that are needed per card network to generate 3DS credentials per merchant. You will need to gather this information before proceeding with creating the Merchant Profile.

Merchant ID (“MID”)

The Merchant ID is assigned by each payment gateway. Be aware that the field name may vary per gateway (i.e. this field is called “Live Mode Client ID” if using Stripe). Contact your payment gateway provider if needed.

Merchant Name

The Merchant Name is the legal name of your organization.

Merchant Country

The Merchant Country must be listed in ISO 3166-1 Numeric format. The complete list is available here. Some examples include:

  • 826: United Kingdom of Great Britain and Northern Ireland

  • 756: Switzerland

  • 528: Netherlands 

  • 372: Ireland

  • 276: Germany

  • 250: France

  • 208: Denmark

  • 056: Belgium

Merchant MCC

The Merchant Category Code can be set up by your gateway. There is a potential that the MCC has not been set up for your account. Contact your payment gateway provider if you have not submitted an account application yet.

How long does it take to set up an MCC code? Time will vary based on your payment gateway process. It will be helpful to have a code in mind that your organization feels will fit your industry. Find more details from Spreedly here.

Merchant URL

The Merchant URL is your organization’s website. If you have multiple URLs, choose the one that best represents your organization.

Merchant Password (optional field)

The Merchant Password will not be required when configuring your Merchant Profile.

Acquirer BIN per Card Brand

The Bank Identification Number is assigned by your acquirer, i.e. merchant bank. Please contact your banking institution if needed. Currently, Fonteva and Spreedly support the following card networks: Visa, Mastercard, and American Express.

Configuring a Merchant Profile:

When creating a Merchant Profile, there may be up to a one hour delay for the 3DS server to register merchant credentials with all of the card brands. While the SCA Provider key returned here will work immediately in our API, it may result in failures with our 3DS Server. Spreedly advises merchants to wait an hour after creating a production Spreedly SCA Provider before using it on gateway transactions.

Use the information you gather for the required fields above to create your Merchant Profile.

  1. From each Payment Gateway record that is enabled for 3DS2, click Configure Merchant Profile.

  2. Using the information you gathered for the required fields, provide your Merchant ID (“MID”), Merchant Name, Merchant Country, Merchant MCC, and Merchant URL. Note that Merchant Password is optional. Find more details from Spreedly here.

  3. From the Acquirer BIN per Card Brand dropdown, select your card network, click Add New and the system will display an additional field to enter the unique BIN number.

    1. If you use multiple card networks, repeat this step for each.

  4. Click Submit.

  5. The confirmation window will display if the Merchant Profile has been successfully configured and the SCA Provider Key has been generated. Click OK to exit this window.

There may be up to a one hour delay for the 3DS server to register merchant credentials with all of the card brands. While the SCA Provider key returned here will work immediately in our API, it may result in failures with our 3DS Server. Spreedly advises merchants to wait an hour after creating a production Spreedly SCA Provider before using it on gateway transactions.

Configure A Test Merchant Profile For Test Payment Gateways:

Test payment gateways with 3D Secure 2.0 (3DS2) enabled will require a test Merchant Profile. You will enter the following values in the required fields for creating a Merchant Profile.

  • Merchant ID: spreedlys_mid

  • Merchant Name: Spreedly

  • Country Code: 840

  • MCC: 5978

  • Acquirer BIN: 4444444444 for Mastercard, Amex, or Visa. Amex and Visa are optional, but Mastercard is required for test gateways.

  • Merchant URL: https://spreedly.com

  • Merchant Password: optional

Click Submit to complete creating the test Merchant Profile. It will generate immediately.

Next Steps:

If you have created a test payment gateway with a test Merchant Profile, you will want to run some tests. Spreedly has provided a test credit card for you to run tests. Information is available on Test Payment Gateways With 3DS2 Enabled.