Supported operations
After a post-authorization score, the Fraud Check step pauses until Riskified’s decision arrives. Payrails verifies the webhook’s signature with your secret key, then resumes the workflow with the decision.
Decisions
Before you begin
- In the Payrails Portal, go to Settings → Integrations and select Add instance.
- Select the workspaces where Riskified should be available.
- Select Fraud as the integration type, then Riskified as the provider.
- Enter your Riskified credentials and save:
In test mode, Payrails sends requests to the Riskified sandbox.
- Pass the session ID from Riskified’s beacon script in
meta.risk.sessions. - Add a Fraud Check step before your authorize step, and another one after it for the post-authorization review. See Authorization with fraud screening.
Request fields for Riskified
Send these fields in the authorize request, in addition to the standard authorize fields. Required fields must be present for the score to succeed. Payrails sends Optional fields to Riskified when you include them.
For a post-authorization score, Payrails also sends the authorization from the earlier authorize step: the PSP as the gateway, the PSP reference as the authorization ID, the card or wallet details, AVS and CVV results, and the 3D Secure result.
Send order updates
Add a Fraud Update step after each lifecycle action and set itsorderStatus. Payrails picks the Riskified endpoint from the status.
When the authorize step fails, a Fraud Update step on that path sends Riskified a checkout denied update with the declined payment, whatever the order status.
Example authorize request
Authorize request