Fraud integrations

A fraud integration connects a fraud prevention provider to Payrails. Payrails sends the provider the payment, customer, device and order details, and the provider returns a decision your workflow acts on: authorize, challenge with 3D Secure, hold for review or block. You configure each provider once in the Payrails Portal and add it to your workflow, so you don’t call the provider’s API yourself.

How fraud screening works

You send the customer’s device session in meta.risk.sessions and the order details in meta on the authorize request.
A Fraud Check step in your workflow sends the payment to the fraud provider. Payrails scores it as pre-authorization when no payment exists on the execution yet, and as post-authorization after an authorize step.
The provider returns a decision, and a Condition step routes the payment on it.
As the order moves on, a Fraud Update step tells the provider what happened: cancelled, shipped, delivered, returned or failed.
Payrails notifies you of each fraud result through webhook notifications.

Decisions

Every provider’s answer maps to one of these Payrails decisions. Each provider page lists how its own values map.

Decision	Meaning	Typical next step
`Allow`	The payment is low risk.	Authorize without a challenge, or capture after a post-authorization check.
`Challenge`	The provider recommends authenticating the customer.	Authorize with 3D Secure.
`Review`	The provider holds the order for manual review.	Wait for the review, or apply your own rule.
`Prevent`	The provider recommends blocking the payment.	Stop before authorization, or cancel or refund after it.
`NoDecision`	The provider returned no recommendation.	Apply your own rule, for example authorize with 3D Secure.

Connect your fraud provider

Forter

Fraud prevention

Ravelin

Fraud prevention

Riskified

Fraud prevention

Signifyd

Fraud prevention

Check providers

Operation	Forter	Ravelin	Riskified	Signifyd
Pre-authorization score	✔	✔	✔	✔
Post-authorization score	✔	✔	✔	✔
Order updates	✔	✔	✔	✔
Dispute reporting	✖	✔	✖	✔
Decision delivery	In the response	In the response	In the response before authorization, by webhook after it	In the response

Send the device session

Fraud providers link a payment to the customer’s device through a session ID that their client-side script creates in the customer’s browser or app. The Payrails Web Fraud SDK loads these scripts for you and passes the session to the Payrails Web SDK. If you integrate through the API, send one session per provider in meta.risk.sessions. Payrails gives each provider its own session, so you can run more than one provider in the same workflow.

Risk sessions

{
  "meta": {
    "risk": {
      "sessions": [
        { "provider": "riskified", "sessionId": "c8a1f0e2-7b4d-4c39-9a51-3e2d6f8b1a07" },
        { "provider": "signifyd", "sessionId": "5f2e9b7c-1d84-4a6e-b0c3-9e7a2d4f6c18" }
      ]
    }
  }
}

Build your fraud workflow

Authorization with fraud screening runs a Fraud Check before authorization and branches on the decision.
Capture with fraud update tells the fraud provider what happened after capture.
Full authorization combines fraud screening with 3D Secure for risk-based routing.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

How fraud screening works

Decisions

Connect your fraud provider

Check providers

Send the device session

Build your fraud workflow

​How fraud screening works

​Decisions

​Connect your fraud provider

​Check providers

​Send the device session

​Build your fraud workflow

How fraud screening works

Decisions

Connect your fraud provider

Check providers

Send the device session

Build your fraud workflow