Our Fraud Detection solution gives you the power to control what happens to the payments you process. Each payment that has the
risk set to
true using our Unified Payments API will be assessed against the risk assessment rules you set in the Dashboard.
We've highlighted the features that are available only in the pro version. Contact your Customer Success Manager for more information about our pro offer.
How it works
Every payment request has an authentication and authorization stage that verifies who is making the request, and whether the payment can be accepted. Use our Fraud Detection solution to control what happens before and after this stage. We call these decision points pre-auth and post-auth.
Your decisions are made using flows in the Dashboard. You have one for pre-auth and another for post-auth. Each flow gathers information about a transaction and directs it to a specific outcome. This is referred to as routing. We go into more detail when we explain how to use the solution.
The fraud dashboard shows the journey of all transactions that went through a risk assessment.
There are 6 steps in a payment lifecycle. Only steps 2 and 5 are configured by you, as the rest is determined by the card issuer, cardholder or Checkout.com.
- Incoming transactions – all new transactions start as incoming transactions.
- Pre-auth – the first decision point you determine when creating your risk strategy.
- 3DS outcome – the outcome of 3DS authentication, including scenarios where it hasn’t been applied.
- Auth outcome – the outcome of the authorization request.
- Post-auth - the second decision point you determine when creating your risk strategy.
- Current status – the last known status of the transaction.
The data displayed on the fraud dashboard is updated every day at midnight (UTC). You can download a report that contains a transaction-by-transaction summary of data points, rules triggered, outcomes at each stage, and whether there were fraudulent transactions.
To download a report:
- Select a date range.
- Select Generate report.
- Select Download.
Each stage in the payment lifecycle has several statuses associated with it.
The transaction has not been processed. It will not continue to 3DS authentication or authorization.
The customer's bank has been asked to challenge the customer, but they can choose not to.
No recommendation has been provided to the card issuer for whether to challenge the customer or not.
The card issuer has been asked to authenticate the transaction without challenging the customer, but they can still choose to do so.
The most permissive decision, resulting in the lowest friction. Where possible, our 3DS routing engine has selected the most appropriate exemption to bypass Strong Customer Authentication (SCA). If the customer's bank accepts the exemption, you will not be covered by the liability shift.
Either risk assessment was not performed or could not be performed. As a result, the default decision of try exemptions has been applied.
Where to next?
Understand the Fraud Detection solution
Understand how to use our Fraud Detection solution, so you control what type of payments you accept and reduce the risk of fraud.