Skip to main content
Version: 1.0


How can I request credentials for the APIs?

To request credentials for the APIs, contact your Fraudio representative or email to schedule an appointment.

What is historical data, and how can I transfer it?

Historical data comprises payment transactions and chargebacks. Fraudio uses this data to enhance fraud detection models. Share files with Fraudio by uploading CSV files to our Amazon S3 storage, which is secure and compliant with privacy regulations. Upon request, we will provide a secure key ID and secret for file uploading to a designated folder. There are various S3 clients available for uploading, such as command-line interfaces, GUIs, and client-side libraries for most programming languages.

For more information on transferring data, refer to the batch transfer manual. If you prefer alternative methods for sending data, please contact us. Remember, more data results in better fraud scores!

What is pre- and post- authorisation data?

A payment transaction is a set of information about money that flows from an entity (the payer) to another entity (the beneficiary) through the payment ecosystem. As the transaction is processed by different entities (e.g., payment gateway, acquirer, issuer), it requires authorisation from the payer's bank.

  • The information a transaction holds before seeking authorisation is called pre-authorisation information.
  • The information obtained after a transaction is authorised by the issuing bank is called post-authorisation information.

Why do I need to send post-authorisation data?

Post-authorisation data is crucial for maximizing the benefits of Fraudio's products. We use this data to provide historical context to transactions.

Can I send data just at the post-authorisation stage?

Generally, you should send pre-authorisation transaction data to Fraudio. Depending on your role in the payment ecosystem, you might want to detect fraud using our Payment Fraud Detection product after transaction authorisation. In both cases, send us both pre- and post-authorisation information to accurately detect fraud.

Score your transaction using pre-authorisation information and submit post-authorisation information as soon as it's available. This is mandatory. To send post-authorisation information, connect to the post-authorisation backfill API endpoint. If you cannot send pre-authorisation data due to your position in the payments ecosystem, score transactions after authorisation by sending all information (pre- and post-authorisation) within the same transaction to the fraud score API endpoint.

Can I integrate with the Merchant-Initiated Fraud detection product without the Payment Fraud Detection product?

Yes, you can integrate with the Merchant-Initiated Fraud detection product without the Payment Fraud Detection product. However, you will still need to follow the steps related to the Payment Fraud Detection product, but you won't need to purchase both products.