Skip to main content
Forter provides accurate, real-time decisions about every digital interaction, powered by the largest network of online retailers. Forter’s anti-fraud decisions can be used in Flow to trigger any action.

​
Credentials

To configure a Forter connection, you need to set the following credentials. Each of these can be found in the Forter dashboard under the settings (gear) icon.
The integration requires your credentials to be compatible with the 2.1 version of the Forter API. To verify that your credentials are compatible with this version of the API, please reach out to Forter support.

​
Merchant information

Additionally, some default merchant information can be configured in case you are running multiple storefronts through one Forter account.

​
Decision mapping

Decisions received from Forter are mapped to the decisions according to the following logic. If any of the data requirements below are not met, the decision is skipped. If there was a technical issue reaching Forter the decision returns as an exception.

​
Data requirements

When using Forter, anti-fraud decisions can only be fetched if the transaction has a minimum set of required fields set. If any of these values are not provided then the call to Forter can not be completed and the anti-fraud decision results in a Skipped decision.

​
Browser requirements

Forter requires the following browser data to be associated with a transaction. Both of these are automatically set when using Embed or one of the e-commerce plugins. Please refer to the IP address forwarding guide for more details on this subject.

​
Buyer requirements

Forter also requires the transaction to be associated with a buyer, and the buyer must have the following fields populated.
  • First name
  • Last name
  • Email address
  • Country

​
Additional data

When any of the following attributes are associated with a transaction they are sent to Forter as well.
  • The buyer’s shipping address
  • Any cart items
    • If set, they must specify the product type

​
Custom options

You can also pass custom merchant-defined data specifically for Forter using connection options.

​
Device fingerprinting

The use of device fingerprinting is highly recommended when using Forter. Please refer to the device fingerprinting guide for more information on the universal solution. If needed, you could load the fingerprint script for Forter directly and pass the token value as the anti_fraud_fingerprint to the new transaction API.