PSP Authorization

Authorization with 3DS Results

To provide the bank with the 3DS results, it is necessary to modify your integration with the Payment Service Provider (PSP). This adjustment usually involves enriching the PSP payment request with the following values from the Forter 3DS result response's verificationMethod.verificationSpecificData.ThreeDS object:

Forter's ThreeDS field	Common Names
authenticationValue	Authentication Value / CAVV / AAV / Cryptogram
ECIValue	ECI / ECIFlag / ECIValue / Electronic Commerce Indicator
version	3DS Version
dsTransID	dsTransID / Directory Server Transaction ID / Transaction ID (formerly xid)

Examples for common PSPs

Map the previously mentioned Forter fields to the corresponding fields within the Adyen authorize request:

Adyen's mpiData.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
cavv	authenticationValue
eci	ECIValue
threeDSVersion	version
dsTransID	dsTransID

Map the previously mentioned Forter fields to the corresponding fields within the Braintree Transaction: Sale request:

Braintree's three_d_secure_pass_thru.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
cavv	authenticationValue
eciFlag	ECIValue
threeDSecureVersion	version
dsTransactionId	dsTransID

Contact your Account Manager at Stripe and ask to enable “3DS Import”.

In the paymentintent object, please include the following child attributes inside the payment_method_options.card attribute and map them to the corresponding Forter fields as indicated below:

Stripe's payment_method_options.card.three_d_secure.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
cryptogram	authenticationValue
transaction_id	dsTransID
version	version
electronic_commerce_indicator	ECIValue

See also Stripe's 3DSecure import guide

Example:

"payment_method_options": {
   "card": {
     "three_d_secure": {
       "cryptogram":"kAMTKCFOIM134yphDhh4o4QBiURR",
       "transaction_id":"c5b808e7-1de1-4069-a17b-f70d3b3b1645",
       "version":"2.2.0",
       "electronic_commerce_indicator":"05"
     }
 }

Review Worldpay AWP for full details

Add the customer object to the request with Forter's 3DS results

Worldpay's customer.authentication.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS
version	version
type	"3DS"
eci	ECIValue
authenticationValue	authenticationValue
transactionId	dsTransID

   "customer": {
        "authentication": {
            "version": "2.1.0"
            "type": "3DS",
            "eci": "05"
            "authenticationValue": "MTIzNDU2Nzg5MDEyMzQ1Njc4OTA"
            "transactionId": "c5b808e7-1de1-4069-a17b-f70d3b3b1645"
        }
    }

Map the previously mentioned Forter fields to the corresponding fields within Checkout's Authorization Request

Checkout.com's 3ds.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
enabled	true
cryptogram	authenticationValue
eci	ECIValue
version	version
xid	dsTransID

{
  "source": {
    "type": "card",
    "number": "5436031030606378",
    "expiry_month": 12,
    "expiry_year": 2025
  },
  "amount": 257,
  "currency": "USD",
  "3ds": {
    "enabled": true,
    "eci": "06",
    "cryptogram": "MTIzNDU2Nzg5MDEyMzQ1Njc4OTA=",
    "xid": "79f6205c-ff5c-4a4c-8fca-90f67f3a6470",
    "version": "2.0.1"
  }
}

PaymetsOs's three_d_secure_attributes.external.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
three_d_secure_version	version
three_d_secure_authentication_status	transStatus
ds_xid	dsTransID
encoding	"BASE64"
cavv	authenticationValue
eci_flag	ECIValue

Call /payments endpoint and include the 3DS authentication results:

Fiserv's authenticationResult.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
authenticationType	"Secure3DAuthenticationResult"
authenticationResponse	transStatus
cavv	authenticationValue
dsTransactionId	dsTransId

Below is a request payload for example.

  "authenticationResult": {
    "authenticationType": "Secure3DAuthenticationResult",
    "dsTransactionId": "f3371948-5388-43a6-bca4-b49700019437",
    "authenticationResponse": "Y",
    "cavv": "ARTnBCZIhcQAAAABZlyFxAABVCAA"
  }

Call /payments endpoint and include the 3DS authentication results:

Chase's paymentMethodType.card.authentication.<attribute>	Forter's verificationMethod.verificationSpecificData.ThreeDS.<attribute>
electronicCommerceIndicator	eci
threeDS.authenticationValue	authenticationValue
threeDS.authenticationTransactionId	dsTransId
threeDS.threeDSProgramProtocol	version

Authorization with PSD2 Exemption

The following part is relevant only for PSD2 solution

In order to pass the bank a request for exemption from 3DS following Forter's recommendation in the Order Response, you should adjust your integration with the PSP and include in the PSP Authorization request a flag for TRA Exemption or Low Value or Secure Corp Exemption.

Contact your PSP to enable such a call (it is not always activated by default), and get their relevant Authorization API reference which explains how to pass a request for TRA Exemption and Low Value Exemption.

Examples for common PSPs

Review Adyen documentation for passing exemption

Change the default setting in the Customer Area in you Adyen Dasboard. Doing this will override Adyen's choice to apply TRA for a transaction or not. Navigate to Risk > Risk Settings > General > Perform TRA. Choose Enable 3rd party/proprietary risk solution TRA to apply the TRA exemption yourself per transaction.

Pass the relevant exemption type (transactionRiskAnalysis\ lowValue\ secureCorporate) in the scaExemption object, following Forter's recommendation (REQUEST_SCA_EXEMPTION_TRA \ REQUEST_SCA_EXEMPTION_LOW_VALUE \ REQUEST_SCA_EXEMPTION_CORP) . Example:

  additionalData": {
    "scaExemption": "lowValue"
  }

Review Checkout SCA documentation for passing exemption

Pass the relevant exemption type via the 3ds.enabled and 3ds.exemption fields within the 3ds object

{
  "source": {
    "type": "token",
    "token": "tok_f6z4mnoububudpqnvhwa5ff27u"
  },
  "amount": 2000,
  "currency": "USD",
  "3ds": {
    "enabled": false,
    "exemption": "low_value"
  },
  "success_url": "https://example.com/payments/success",
  "failure_url": "https://example.com/payments/failure"
}

{
  "source": {
    "type": "token",
    "token": "tok_f6z4mnoububudpqnvhwa5ff27u"
  },
  "amount": 2000,
  "currency": "USD",
  "3ds": {
    "enabled": true,
    "exemption": "low_value"
  },
  "success_url": "https://example.com/payments/success",
  "failure_url": "https://example.com/payments/failure"
}

Authorization with IDCI results

To provide the bank with the IDCI results, it is necessary to modify your integration with the Payment Service Provider (PSP). This adjustment involves including the verificationMethod.verificationSpecificData.ThreeDS.dsTransID , verificationMethod.verificationSpecificData.ThreeDS.authenticationValue and verificationMethod.verificationSpecificData.ThreeDS.ECIValue values from Forter Order Response in the PSP Authorization request.

PSP Authorization

Authorization with 3DS Results

Examples for common PSPs

Adyen

Braintree

Stripe

Worldpay AWP GW

Checkout.com

PayU / PaymentsOs

Fiserv

Chase

Authorization with PSD2 Exemption

Examples for common PSPs

Adyen

Checkout.com

Authorization with IDCI results

Examples for common PSPs

Adyen

Braintree

Authorization with Network Token & Cryptogram

Braintree

Adyen

Cybersource

Checkout.com