Primer Docs

Forter is a company that specializes in providing fraud prevention and detection solutions for online businesses. It offers an integrated platform that uses advanced machine learning and behavioral analytics to help businesses identify and prevent fraud in real time.

Primer supports Forter’s Validation API. The Validation API is used to receive Forter’s real-time fraud decision of whether to approve or decline an order when the customer transacts on your site. The request should be sent either prior to calling your payment gateway for authorization of funds (Pre-Authorization) or immediately after receiving the authorization response from your payment gateway, but prior to capturing the funds (Post-Authorization).

See our Fraud Overview for more general information about how we support fraud prevention.

What is supported?

Actions

Pre-authorization
Post-authorization

Resulting decisions

Pass
3DS (pre-authorization only)
Reject
Fail

Payment methods

Card
Apple Pay
Google Pay
Paypal
Klarna
Alipay+
Wechat

Instructions

Pre-requisites

To be able to receive 3DS decisions via the Forter Validation API, ask your account manager to enable the 3DS decision for your account
In order to collect additional device data, Forter JS needs to be installed by you, the merchant, in your checkout application. During the flow, Forter’s JS will generate a token that you have to will need to pass to Primer in the client session under the field name metadata.fraud_context.cookie_token

Set-up Instructions

Go to your Primer Dashboard.
Navigate to the "Integrations" section, select "Add Integration" at the top of the page and search for Forter.
Find your credentials in the Forter Dashboard by following the below steps:
- Log into the Forter dashboard
- Go to the Settings gear icon
- Copy Secret Key and Site ID
Follow the rest of the steps to set up Primer Workflows for fraud checks.

Required fields

For card payments

For card payments, the following fields have to be passed for Forter to accept the request.

Field	Type
`customer.billingAddress.firstName`	string
`customer.billingAddress.lastName`	string
`customer.billingAddress.addressLine1`	string
`customer.billingAddress.countryCode`	string
`customer.billingAddress.city`	string
`order.shipping.amount`	integer
`order.shipping.methodName`	string
`order.lineItems[].name`	string
`order.lineItems[].amount`	integer
`order.lineItems[].productType`	string
`metadata.fraud_context.device_details.user_agent`	string
`metadata.fraud_context.device_details.browser_ip`	string

Field	Type
`customer.billingAddress.firstName`	string
`customer.billingAddress.lastName`	string
`customer.billingAddress.addressLine1`	string
`customer.billingAddress.countryCode`	string
`customer.billingAddress.city`	string
`order.shipping.methodName`	string
`order.lineItems[].name`	string
`order.lineItems[].amount`	integer
`order.lineItems[].productType`	string
`metadata.fraud_context.device_details.user_agent`	string
`metadata.fraud_context.device_details.browser_ip`	string

Notes:

Primer's integration with Klarna currently does not support passing order.shipping.amount.
Passing a customer.billingAddress on your Client Session request that is different from the shopper address that is stored by Klarna, results in a failed payment attempt.

Testing

Pre-authorization fraud check

To trigger a Pass outcome, set customer.emailAddress to approve@forter.com
To trigger a Reject outcome, set customer.emailAddress to decline@forter.com
To trigger a 3DS outcome, set customer.emailAddress to force_3ds_psd2_recommendation@forter.com
To trigger a Fail outcome, set customer.emailAddress to notreviewed@forter.com

Post-authorization fraud check

To trigger a Pass outcome, set customer.emailAddress to approve@forter.com
To trigger a Reject outcome, set customer.emailAddress to decline@forter.com
To trigger a Fail outcome, set customer.emailAddress to notreviewed@forter.com

General Notes

Forter's test document can be found here (need to be logged into your Forter dashboard to access)