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 Hub.
We've highlighted the features that are available only in the pro version. Contact your Account Manager for more information about our pro offer.
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.
The Hub 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 Hub 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.
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.
3DS authentication failed due to a technical issue, invalid parameters (card doesn't support 3DS), or incorrect parameters.
3DS authentication was not attempted.
Customer failed to pass the 3DS challenge, or the access control server’s response was not valid.
3DS authentication was not completed in the given time, usually because the customer abandoned the process.
Customer passed the 3DS challenge. This status includes cases where the issuer decides not to challenge the customer at all.
The customer’s bank has declined the payment.
The customer’s bank has authorized the payment.
The transaction has been voided.
The transaction has been flagged for manual review. You will be able to review it in the Hub, so you can make a final decision (usually within 7 days).
The transaction has been captured.
Either the risk assessment was not performed or could not be performed. As a result, the default decision of capture has been applied.
The payment has been voided. This is a final status.
The payment has been captured. If the payment later becomes subject to a fraud chargeback, the status will change to Fraud chargeback.
Pending manual review
The payment has been flagged for manual review. Once you’ve chosen to capture or void it, the status will be updated accordingly. If no decision is made within 7 days, the payment will be voided.
The payment has been subject to a chargeback. Cardholders usually have up to 6 months to request a chargeback. This means that transactions previously marked as Captured can change status to Fraud chargeback any time within 6 months of the transaction taking place.
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.