Last Updated: 11 April 2025 | Change Log
Minimize fraud and increase approval rates using the latest in data insights. Use an integrated risk assessment as part of the Payments API or follow the steps below for a separate risk assessment request.
Supported payment methods: American Express / Carte Bancaires / Discover / Diners / EFTPOS / ELO / JCB / Maestro / MasterCard / MasterCard Debit / Visa / Visa Debit / Visa Electron (UK only)
Make yourself familiar with our API Principles to ensure a resilient integration.
Use our API Reference to set your headers.
This step gathers customer browser details and performs a GeoIP lookup. It adds more data points for the risk assessment or manual rule creation.
Web device data
ThreatMetrix JS library for web sites
Android SDK
ThreatMetrix Android SDK (coming soon)
iOS SDK
ThreatMetrix iOS SDK (coming soon)
This is the API request containing payment, customer and order information. Optionally, you can provide a sessionId from the Device Data Collection (DDC).
You can request an SCA exemption assessment as part of the FraudSight request. This is also available as a separate exemption request.
When using our Card Payments API for the payment itself, the outcome of the payment (e.g. authorized) and any subsequent fraud or chargeback information is automatically fed to the fraud data model to improve assessment accuracy. For any other API processing the payment (Worldpay or 3rd Party), the following steps are required:
If you're using other gateways/acquirers for the payment gateway you can still use FraudSight but you must provide additional details so the data model can learn and mature for future risk assessments.
One or both of these should also be provided:
Fraud
Using TC40/Safe data, did fraud occur on any risk assessed payments.
Chargeback
Did any of the payments result in any fraud specific chargebacks.
Next steps