Prior to commencing development, verify that the integration prerequisites are met between the merchant and both Forter and the merchant's PSP.

Forter would be happy to assist you with you, reach out to your Forter contact if you need any help!

Requirements Summary

Requirements are succinctly summarized in 2 tables, read further down for more information

Data Requirements

Data Point	`/v3/orders/:id` field under `payment[0].creditCard`	Required	Definition
Full PAN (Card Number) 🔗	`fullCreditCard`	Yes	The full card number used in the transaction (don't have access to card numbers? See Forter Tokenization)
Acquirer BIN 🔗	`threeDSecure.acquirerData. acquirerBIN`	Yes	This unique number is assigned to the acquiring bank by a payment card network to identify that bank when settling transactions (Contact your acquiring Bank to obtain this value per card network)
Acquirer Merchant ID (MID) 🔗	`threeDSecure.acquirerData. acquirerMerchantId`	Yes	Merchant ID (MID) is a unique code provided to merchants by their acquiring bank (Contact your acquiring Bank to obtain this value per card network)
Merchant Category Code (MCC)	`threeDSecure.acquirerData. merchantCategoryCode`	Yes	A Merchant Category Code (MCC) is a four-digit number listed in ISO 18245 for retail financial services. MCC is used to classify the business by the type of goods or services it provides.
Merchant Country Code	`threeDSecure.acquirerData. merchantCountryCode`	Yes	The country your acquiring account is setup in, in ISO 3166-1 numeric country code format
Acquirer Merchant Name	`threeDSecure.acquirerData .acquirerMerchantName`	Optional	Will be displayed in the 3DS challenge page if there'll be one
Acquirer Name	`threeDSecure.acquirerData .acquirerName`	Optional	Name of Acquiring Bank

Non-Data Requirements

Action	How	Required
Provide Forter all your Acquirer BIN + MID pairings	Share a file with all your acquirer BIN+MIDs pairings with Forter	Yes
Enroll Mastercard MID to MasterCard 3DS2	Contact acquiring bank and request enrollment of Mastercard MID to 3DS2. If your acquirer is EU based it's likely you're already enrolled	If MasterCard is in scope for Forter 3DS Execution
Confirm Liability Shift with processor	Contact processor and request confirmation that transactions with Forter 3DS Execution will have liability shifted to the issuer	Yes
Verify with processor that exemptions from 3DS can be sent on authorization call	Contact processor and confirm if 3DS exemptions for Low Value and Low Risk transactions can be passed as part of the Payment Authorization request	Only for PSD2 scope
Provide Forter your exemption TRA limits	Contact acquiring bank and ask for your TRA limits (should be in the 100-500 EUR range)	Only for PSD2 scope
Include the Forter Payments JS SDK in your checkout page	Forter's Payments JS SDK handles 3DS execution for you, include it in your checkout page and invoke it accordingly	Yes

Full PAN

Verify that you can pass the full card number in the /v3/orders/:id call under payment[0].creditCard.fullCreditCard. This is required in order to successfully execute 3DS with Forter.

If you have vaulted cards and the full card number is not exposed on the checkout page, please check with your Tokenization vendor regarding the availability of a Detokenization Proxy service. Such service enables you to make a request to a 3rd party (such as the Forter API) with a placeholder for the full credit card value included in the request. The request is then routed through the proxy, where the placeholder is replaced with the corresponding card data.

You can also check out our Forter Tokenization solution for a more seamless integration.

Visa Required Data Points

Starting from Aug 2024 Visa requires the following fields in order to execute 3DS:

Browser IP Address
Cardholder Name
Cardholder Email Address OR Cardholder Phone Number (Work / Home / Mobile - At least one of these fields must be provided)

If you collect those fields only for a subset of the transactions that's ok, but the portion without those fields will not have 3DS executed.

Acquirer Data

Contact your PSP Acquiring Bank to request the details in the above table, without the accurate details, 3DS cannot be executed and will fail.

Acquirer BIN/MID pairings usually obey the following patterns:

Card Scheme	Acquirer BIN	Acquirer MID
Visa	6-8 digit numbers starting with `4`	Usually numeric (but not necessarily so)
MasterCard	6-8 digit numbers usually starting with `5` or `2` (rarely `8` or `7`)	Usually shared with Visa (but paired with a MasterCard BIN)
American Express	11 digit numbers starting with `1000`	Usually 10-12 digit numbers
Discover	6-8 digit numbers usually starting with `6` (sometimes `3` or `4`)	Usually 12-15 digit number

Example sane values:

Card Scheme	Acquirer BIN	Acquirer MID
Visa	412345	123456789012345
MasterCard	512345	123456789012345 (same one!)
American Express	10000000123	1234567890
Discober	612345	123456789012

Enroll to 3DS on Mastercard

Please request your acquirer bank to enroll your MIDs to 3DS2 on Mastercard, as it is not done automatically like with Visa. If your acquirer is EU based, that's probably already the case, but still best to verify
Forter, as an external MPI, can execute 3DS only if the MIDs are enrolled with the card scheme to the 3DS service

PSP supports external 3DS MPI

Ensure that your PSP is configured to receive and process the results of the 3DS authentication when using an external MPI like Forter
Get the relevant API reference from your PSP, for calling Authorization with 3DS results, and clarify which additional fields about 3DS results should be populated (e.g CAVV, ECI, 3DS version, XID, TransID).
- See our Authorization for more details

PSP supports PSD2 exemption requests

Relevant only for PSD2 solution

Verify with your PSP that you can request in the Authorization call an exemption from executing 3DS for Low Value and Low Risk transactions.
Get the relevant reference from your PSP, for calling the Authorization API with the Exemption request.