Our fraud and risk management 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 Hub.
How it works
Every payment request has an authentication (known as 3DS) and authorization stage that verifies who is making the request and whether the payment can be accepted. Use our fraud solution to control what happens before and after this stage. We call these decision points pre-3DS and post-auth.
The ultimate outcome of the pre-3DS and post-auth decision points are determined by your decline list, decline rules, 3DS rules, void and flag rules. Each transaction passes through these groups, which 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 7 steps in a payment lifecycle. You only configure steps 2 and 6, as the rest is determined by one of: the card issuer, the cardholder, or Checkout.com.
- Incoming transactions – all new transactions start as incoming transactions.
- Pre-3DS – 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.
- Pre-auth – the decision Checkout.com has taken as a result of the 3DS outcome.
- 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 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.
Your customer will have to prove their identity, such as through the use of a one-time pass code. This will reduce fraud, but also may impact your conversion rate.
The 3DS payment has been accepted.
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 and risk management solution
Understand how to use our fraud and risk management solution, so you control what type of payments you accept and reduce the risk of fraud.