Forter Integration

PayU supports Forter’s risk assessment, allowing you to easily activate the service within your Authorization and Charge requests. After receiving Forter’s prediction, you can decide whether to authorize or block transactions accordingly. Forter also takes full liability for transactions they approve by implementing a chargeback guarantee policy. The service provides the following benefits:

• An embedded risk assessment call within the Authorization and Charge requests.
• Chargeback guarantee policy – If a Forter-approved transaction is later disputed, Forter commits to cover the transaction amount.
• Can be used for transactions in every geographical location.

Configuring Forter

Start using Forter’s service by following these steps:

1. Add Forter as a Provider to your account.
2. Activate Forter’s risk assessment in the header of your Authorization or Charge request.
3. Ensure PaymentsOS' API requests include all fields required by Forter to perform the risk assessment. Mandatory fields divided by request-type are listed here.
4. Configure Business rules to determine how to proceed with transactions based on the risk assessment result. Note that you will need to devise your own blocking rules via the decision engine to prevent transactions from moving on to Authorization. Forter’s recommendations are not enacted automatically and thus require another step from your end to devise blocking rules. Our blocking recommendations are outlined below.

Step 1: Add Forter as a Provider

Go to Account -> Providers and choose ‘Forter Risk’. Insert the Forter SiteID and SecretKey to finalize the configuration (grab the SiteID and SecretKey from the Forter Portal).

Step 2: Activate Forter Within Requests

To ensure transactions are reviewed by Forter, you must pass the x-risk-provider-config-id in the request header of the Authorization or Charge call, like so:

x-payments-os-env: test 
api-version: 1.3.0 
x-client-ip-address: 216.3.128.12 
x-risk-provider-config-id: 4efe54ff-5956-4df3-a295-b23c17836d21 
private-key: bede7ee5-eaaq-4c9a-bc1f-617ba28256ae 
app-id: com.zooz.docapp 
idempotency-key: AGJ8FJLkGHIpHUTK 

Step 3: Pass all Required Fields for Forter’s Assessment

In addition to passing the x-risk-provider-config-id in the request header, and to ensure Forter reviews transactions, you must pass some Forter-specific fields according to the request-type you intend to send.

PaymentsOS maps Forter’s decision to one of the following statuses: Succeed, Failed, or Unreviewed. Succeed means that the transaction is approved and covered by Forter. PayU can then proceed with the transaction to the authorization/charge request.

Failed indicates that Forter does not approve the transaction, so you are advised not to proceed with the authorization or charge request.

Unreviewed indicates that Forter did not review the transaction according to its policy. This may happen if some Forter-specific parameters were missing from the request.

...
{
  "risk_analysis":{
    "id":"f6b8938f-2f90-4c10-832b-027a8597f1e6",
    "result":{
      "status":"Succeed",
      "score":0
    }
  }
}
...

Step 4: Configure Blocking Rules

Use the decision engine to configure blocking rules according to Forter’s risk assessment.

Our recommendation is to block transactions with a Failed risk status. Note that unless you devise blocking rules, all transactions (whether with a Failed, Succeed or Unreviewed status) will be automatically sent for authorization.

Mandatory Fields Required by Forter

To ensure transactions are reviewed by Forter, you must pass some Forter-specific fields, depending on the request(s) you wish to be sending — Create Token, Create Payment, Create Authorization, or Create Charge.

Create Token Required Fields

The following fields are mandatory and are specific to Forter. Passing these fields is crucial to receive Forter’s risk assessment. Unless all fields are passed, Forter will return an Unreviewed status.

Create Payment Required Fields

The following fields are mandatory and are specific to Forter. Passing these fields is crucial to receive Forter’s risk assessment. Unless all fields are passed, Forter will return an Unreviewed status.

Create Authorization or Create Charge Required Fields

The following fields are mandatory and are specific to Forter. Passing these fields is crucial to receive Forter’s risk assessment. Unless all fields are passed, Forter will return an Unreviewed status.