Prerequisites

Prior to commencing development, Verify that both Forter's and your PSP's integration requirements are met. Reach out to your Implementation Engineer if you have any questions about specific requirements.

Requirements Summary

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

Data Requirements

Data Point	Parameter in creditCard object	Required	Definition
Full PAN Full PAN (Card Number)	fullCreditCard	Yes	Full card number used in the transaction (Don't have access to card numbers? See Card Vaulting
Acquirer BIN	threeDSecure.acquirerData. acquirerBIN	Yes	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	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	Four-digit number listed in ISO 18245 for retail financial services, 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 set up in, formatted as a 3-digit ISO 3166-1 numeric code (e.g., 840 for the United States).
Acquirer Merchant Name	threeDSecure.acquirerData .acquirerMerchantName	Optional	Your company name, which will be displayed in the 3DS challenge page.
Acquirer Name	threeDSecure.acquirerData .acquirerName	Optional	Name of the acquiring bank.

Non-Data Requirements

Action	How	Required
Provide Forter allAcquirer BIN + MID pairings	Share a file with Forter that contains your acquirer BIN+MIDs pairings	Yes
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

Additional Detail

Full PAN

Verify that you can pass the full card number in the Order API 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.

Even if the transaction will be processed using a network token, it is required to send the full card number in the Order API call

You can also check out our Forter's Card Vaulting 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 (at least one of: work, home, or mobile)

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

Acquirer Data

Contact your PSP Acquiring Bank to request the details in the table below. Without these accurate details, 3DS cannot be executed and will fail. Acquirer BIN/MID pairings usually follow these 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 6, 7 or 8)	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
Discover	612345	123456789012

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 to request authorization with 3DS results. Clarify which additional fields about 3DS results should be populated (e.g CAVV, ECI, 3DS version, XID, TransID). See PSP Authorization for more details.

PSP supports PSD2 exemption requests

Relevant only for PSD2 solution

Verify with your PSP that you can request an exemption from executing 3DS for Low Value and Low Risk transactions in the authorization call.

Get the relevant API reference from your PSP to request authorization with an exemption request.