> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Fraud integrations

> Connect a fraud prevention provider to Payrails, screen payments in your workflow and keep the provider updated on each order.

export const ProviderLogo = ({code, alt, bleed = false, mono = false}) => {
  const root = `https://assets.payrails.io/img/logos/${code}`;
  const sources = bleed ? [`${root}/logo-full-bleed.svg`, `${root}/logo.svg`] : [`${root}/logo.svg`];
  const [index, setIndex] = useState(0);
  const ref = useRef(null);
  const fail = i => setIndex(current => current === i ? i + 1 : current);
  useEffect(() => {
    const img = ref.current;
    if (img && img.complete) img.decode().catch(() => fail(index));
  }, [index]);
  if (index >= sources.length) {
    return <span className="provider-card-logo-fallback" role="img" aria-label={alt} />;
  }
  return <img key={sources[index]} ref={ref} src={sources[index]} alt={alt} className={mono ? "provider-logo-mono" : undefined} onError={() => fail(index)} />;
};

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

1. You send the customer's device session in `meta.risk.sessions` and the order details in `meta` on the authorize request.
2. 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.
3. The provider returns a decision, and a **Condition** step routes the payment on it.
4. As the order moves on, a **Fraud Update** step tells the provider what happened: cancelled, shipped, delivered, returned or failed.
5. Payrails notifies you of each fraud result through [webhook notifications](/docs/fraud-management/fraud-score).

## 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

<CardGroup cols="2">
  <Card href="/docs/orchestration/fraud-integrations/forter">
    <div className="provider-card">
      <span className="provider-card-logo">
        <ProviderLogo code="forter" alt="Forter logo" bleed />
      </span>

      <div>
        <p className="provider-card-name">Forter</p>
        <p className="provider-card-type">Fraud prevention</p>
      </div>
    </div>
  </Card>

  <Card href="/docs/orchestration/fraud-integrations/ravelin">
    <div className="provider-card">
      <span className="provider-card-logo">
        <ProviderLogo code="ravelin" alt="Ravelin logo" />
      </span>

      <div>
        <p className="provider-card-name">Ravelin</p>
        <p className="provider-card-type">Fraud prevention</p>
      </div>
    </div>
  </Card>

  <Card href="/docs/orchestration/fraud-integrations/riskified">
    <div className="provider-card">
      <span className="provider-card-logo">
        <ProviderLogo code="riskified" alt="Riskified logo" />
      </span>

      <div>
        <p className="provider-card-name">Riskified</p>
        <p className="provider-card-type">Fraud prevention</p>
      </div>
    </div>
  </Card>

  <Card href="/docs/orchestration/fraud-integrations/signifyd">
    <div className="provider-card">
      <span className="provider-card-logo">
        <ProviderLogo code="signifyd" alt="Signifyd logo" />
      </span>

      <div>
        <p className="provider-card-name">Signifyd</p>
        <p className="provider-card-type">Fraud prevention</p>
      </div>
    </div>
  </Card>
</CardGroup>

## 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](/docs/orchestration/checkout-sdks/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.

```json Risk sessions theme={null}
{
  "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](/docs/orchestration/workflow-studio/examples/authorization-with-fraud) runs a Fraud Check before authorization and branches on the decision.
* [Capture with fraud update](/docs/orchestration/workflow-studio/examples/capture-with-fraud-update) tells the fraud provider what happened after capture.
* [Full authorization](/docs/orchestration/workflow-studio/examples/full-authorization) combines fraud screening with 3D Secure for risk-based routing.


## Related topics

- [Elements](/docs/orchestration/checkout-sdks/web-v5-legacy/elements.md)
- [Capture with Fraud Update](/docs/orchestration/workflow-studio/examples/capture-with-fraud-update.md)
- [Forter](/docs/orchestration/fraud-integrations/forter.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.