Supported operations
Ravelin returns its decision in the response, so the Fraud Check step completes straight away. Payrails adds the Ravelin risk score to the result details.
Decisions
Before you begin
- In the Payrails Portal, go to Settings → Integrations and select Add instance.
- Select the workspaces where Ravelin should be available.
- Select Fraud as the integration type, then Ravelin as the provider.
- Enter your Ravelin credentials and save:
- Load the Ravelin provider in the Payrails Web Fraud SDK with your publishable key, or pass the device ID from your own Ravelin integration in
meta.risk.sessions. - Add a Fraud Check step with your Ravelin integration to your workflow. See Authorization with fraud screening.
Request fields for Ravelin
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 Ravelin when you include them.
Payrails sends the payment method from the instrument: card BIN, last four digits and expiry for cards, the wallet for Apple Pay and Google Pay, and the PayPal email for PayPal. Before authorization, Payrails sends the payment method for card payments. After authorization, it sends it for every payment method, together with the authorization result and 3D Secure data.
Send order updates
Add a Fraud Update step after each lifecycle action and set itsorderStatus. Payrails sends Ravelin the matching order stage. Order updates also need the Ravelin session in meta.risk.sessions.
Report disputes
Payrails reports each dispute on an order to Ravelin, with its amount, reason code and stage, from early fraud warnings and retrievals through to chargebacks and arbitration. Ravelin links the dispute to the order throughmeta.order.reference.
Example authorize request
Authorize request