Payment card fraud losses worldwide exceeded $32 billion in 2021 and will continue to rise. Protect your bottom line by deploying a fraud service, like Riskified, to stop bad actors from making it through your checkout

What is supported?

Actions

• Pre-authorization -> We ask Riskified to "Advise" if 3DS should be used or not, and whether we should proceed with authorization.
• Post-authorization -> We ask Riskified to "Decide", knowing the 3DS result and the authorization outcome, whether to proceed.

Resulting decisions

• Pass
• 3DS (pre-authorization only)
• Reject
• Fail

Payment methods

• Card
• Apple Pay
• Google Pay
• Paypal

Instructions

Set-up Instructions

• Go to your Primer Dashboard.
• Navigate to the "Integrations" section, select "Add Integration" at the top of the page and search for Riskified. Follow the dashboard instructions.
• Follow the rest of the steps to set up Primer Workflows for fraud checks.

Testing

Pre-authorization fraud check

• To trigger a Pass outcome, set customer.emailAddress to start with out_of_scope.
• To trigger a Reject outcome, set customer.emailAddress to start with fraud.
• To trigger a 3DS outcome, set customer.emailAddress to start with sca.
• To trigger a Fail outcome you will need to pass a request that is incorrect. An example of this is to set the currency to something as this field needs to be a recognised currency code.

Post-authorization fraud check

• To trigger a Pass outcome, set customer.emailAddress to equal test@approve.com
• To trigger a Reject outcome, set customer.emailAddress to equal test@decline.com

General Notes

• You must update the Primer orderId for each Riskified test. Reusing the same orderId returns a previous result. You can override the fraud order id by providing a fraudContext.fraudOrderId inside metadata.

Other notifications via Automation

You can use Automation to also notify Riskified for updates that happen after the authorization step:

• when a payment that used either a pre- or post-auth fraud check is declined.
• when a dispute has been opened for a payment. See dispute management for details around processor coverage.

To do so, connect to the Workflow App for Riskified and either update your existing payment flows flows, or just apply the pre-configured Riskified templates.