Reported Fraudulent Transactions Report

Last updated: September 10, 2025

The Reported Fraudulent Transactions Report provides an overview of all unique fraudulent transactions that have been reported by cardholders.

The report is generated using reported fraud data provided by issuers in the following sources:

Visa TC40 reports
Mastercard SAFE reports

Issuers may report transactions as fraud without raising a chargeback. For example, if the fraud amount was low value, or the transaction was authenticated with 3D Secure.

The report is available as:

An hourly report, which includes fraud reported against transactions in the last 183 days
A daily report available at 9:00 PM UTC, which brings through all new fraud records received in the last day

See instructions on how to download the report on demand or on a schedule:

The report is provided as a CSV file. By default, the file name uses the following format:

API and SFTP – reported_fraudulent_transactions_{EntityID}_{Start Date: YYYYMMDD}_{End Date:YYYYMMDD}_1.csv
Dashboard scheduled reports – {Start Date:YYYY-MM-DD}-{End Date:YYYY-MM-DD}-Reported Fraudulent TransactionsReport-{Client Name}.csv

For SFTP, the report is uploaded in the following folder structure: {Entity_name} > reports-{Entity_name} > reported_fraudulent_transactions

Download a sample report (CSV file).

Information

If you're using Safari, hold the Option key when you download.

The report includes the following fields in this order:

Field name Description

Field name	Description
Entity ID string	The entity's unique identifier, prefixed with `ent_`.
Action ID string	The financial action's unique identifier, prefixed with `act_`.
Charge ID string	The charge transaction's unique identifier. Example – `1234a1b2-3c45-6de7-890f-g12345h6i789`
Payment ID string	The payment's unique identifier, prefixed with `pay_`.
Acquirer Reference Number string	The unique 23-digit identifier for the payment provided by the acquirer as it moves through the payment flow between the merchant's bank and the customer’s bank.
Source Type string	The payment's source.type. Example – `card`
Fraud Issue Date date-time	The date and time when the fraud was reported, in UTC. Standard – ISO 8601 code Format – `yyyy-mm-ddThh:mm:ss.sss`
Transaction Date Timestamp date-time	The date and time when the transaction took place, in UTC. Standard – ISO 8601 code Format – `yyyy-mm-ddThh:mm:ss.sss`
Issuer Country ISO 2 Code string	The issuer's country. Standard – ISO alpha-2 country code Example – `US`
Issuing Bank string	The issuer's name.
Is 3DS boolean	Indicates whether the transaction was authenticated with 3D Secure.
3DS Version string	The 3DS protocol version used for authentication.
CVV Check string	The result of the card verification value (CVV) check.
AVS Check string	The result of the Address Verification Service (AVS) check.
ECI string	The Electronic Commerce Indicator (ECI) value.
Fraud Type string	The fraud code returned by the card scheme.
Fraud Reason string	The reason the transaction was reported as fraud. Example – `Card Not Present Fraud`
Fraud Amount number	The transaction amount identified as fraudulent. If the issuer generates a TC40 data claim for a transaction that is reported fraudulent over one year after the original transaction date, Visa's Fraud Reporting System (FRS) can no longer include the amount. This value then displays as `0`.
Fraud Amount USD number	The transaction amount reported as fraudulent, converted to US dollars. If the issuer generates a TC40 data claim for a transaction that is reported fraudulent over one year after the original transaction date, Visa's Fraud Reporting System (FRS) can no longer include the amount. This value then displays as `0`.
Currency Symbol string	The payment's currency. Standard – ISO 4217 code Example – `USD`
Currency Name string	The payment's currency. Example – `USD`
Payment Amount number	The full payment amount.
Payment Currency Symbol string	The payment's currency. Example – `USD`
Payment Amount USD number	The full payment amount, converted to US dollars.
Billing Descriptor Name string	The merchant's name as displayed on the billing descriptor.
Acquirer Country ISO 2 Code string	The acquirer's country. Standard – ISO alpha-2 country code Example – `US`
Payment Type string	The type of payment. Example – `Credit Cards`
Customer IP string	The customer's IP address. Example – `198.51.100.2`
IP Country ISO 2 Code string	The country of the IP address. Standard – ISO alpha-2 country code Example – `US`
Merchant Category Code string	The merchant's merchant category code (MCC) for this payment. Standard – ISO 18245 code Merchants can have multiple MCCs.
Merchant Category Code Description string	The MCC's description.
Client Name string	Your name as a Checkout.com client.
Entity Name string	The entity's name.
Sub Entity ID number	The sub-entity's unique identifier, prefixed with `ent_`.
Sub Entity Name string	The sub-entity's name.
Processing Channel ID number	The processing channel's unique identifier, prefixed with `pc_`.
Processing Channel Name string	The processing channel's name.
Payment Method Name string	The name of the payment method used for the transaction. This can be one of: `AMEX` `Mastercard` `Visa`
Card Expiry Month number	The card's expiry month. Format – `M`
Card Expiry Year number	The card's expiry year. Format – `YYYY`
Card Holder Name string	The cardholder's name.
Customer Email string	The customer's email address.
Customer Name string	The customer's name.
BIN string	The card's bank identification number (BIN). Example – `123456`
Billing Address Country ISO 2 Code string	The country of the billing address. Standard – ISO alpha-2 country code Example – `US`
Card Scheme Type string	The type of card, as provided by the card scheme. This can be one of: `CREDIT` `DEBIT`
Card Number string	The card's masked primary account number (PAN). Example – `123456******7890`
Transaction Type string	The type of payment. Example – `Recurring`
Card Network Token Type string	The type of the card network token. This can be one of: `MDES` – Mastercard `VTS` – Visa
Track ID string	The payment's unique tracking identifier. Example – `ORNETJBUX6UPEKH7QN`

Entity ID

string

The entity's unique identifier, prefixed with ent_.

Action ID

string

The financial action's unique identifier, prefixed with act_.

Charge ID

string

The charge transaction's unique identifier.
Example – 1234a1b2-3c45-6de7-890f-g12345h6i789

Payment ID

string

The payment's unique identifier, prefixed with pay_.

Acquirer Reference Number

string

The unique 23-digit identifier for the payment provided by the acquirer as it moves through the payment flow between the merchant's bank and the customer’s bank.

Source Type

string

The payment's source.type.
Example – card

Fraud Issue Date

date-time

The date and time when the fraud was reported, in UTC.
Standard – ISO 8601 code
Format – yyyy-mm-ddThh:mm:ss.sss

Transaction Date Timestamp

date-time

The date and time when the transaction took place, in UTC.
Standard – ISO 8601 code
Format – yyyy-mm-ddThh:mm:ss.sss

Issuer Country ISO 2 Code

string

The issuer's country.
Standard – ISO alpha-2 country code
Example – US

Issuing Bank

string

The issuer's name.

Is 3DS

boolean

Indicates whether the transaction was authenticated with 3D Secure.

3DS Version

string

The 3DS protocol version used for authentication.

CVV Check

string

The result of the card verification value (CVV) check.

AVS Check

string

The result of the Address Verification Service (AVS) check.

ECI

string

The Electronic Commerce Indicator (ECI) value.

Fraud Type

string

The fraud code returned by the card scheme.

Fraud Reason

string

The reason the transaction was reported as fraud.
Example – Card Not Present Fraud

Fraud Amount

number

The transaction amount identified as fraudulent.

If the issuer generates a TC40 data claim for a transaction that is reported fraudulent over one year after the original transaction date, Visa's Fraud Reporting System (FRS) can no longer include the amount. This value then displays as 0.

Fraud Amount USD

number

The transaction amount reported as fraudulent, converted to US dollars.

Currency Symbol

string

The payment's currency.
Standard – ISO 4217 code
Example – USD

Currency Name

string

The payment's currency.
Example – USD

Payment Amount

number

The full payment amount.

Payment Currency Symbol

string

The payment's currency.
Example – USD

Payment Amount USD

number

The full payment amount, converted to US dollars.

Billing Descriptor Name

string

The merchant's name as displayed on the billing descriptor.

Acquirer Country ISO 2 Code

string

The acquirer's country.
Standard – ISO alpha-2 country code
Example – US

Payment Type

string

The type of payment.
Example – Credit Cards

Customer IP

string

The customer's IP address.
Example – 198.51.100.2

IP Country ISO 2 Code

string

The country of the IP address.
Standard – ISO alpha-2 country code
Example – US

Merchant Category Code

string

The merchant's merchant category code (MCC) for this payment.
Standard – ISO 18245 code

Merchants can have multiple MCCs.

Merchant Category Code Description

string

The MCC's description.

Client Name

string

Your name as a Checkout.com client.

Entity Name

string

The entity's name.

Sub Entity ID

number

The sub-entity's unique identifier, prefixed with ent_.

Sub Entity Name

string

The sub-entity's name.

Processing Channel ID

number

The processing channel's unique identifier, prefixed with pc_.

Processing Channel Name

string

The processing channel's name.

Payment Method Name

string

The name of the payment method used for the transaction. This can be one of:

AMEX
Mastercard
Visa

Card Expiry Month

number

The card's expiry month.
Format – M

Card Expiry Year

number

The card's expiry year.
Format – YYYY

Card Holder Name

string

The cardholder's name.

Customer Email

string

The customer's email address.

Customer Name

string

The customer's name.

BIN

string

The card's bank identification number (BIN).
Example – 123456

Billing Address Country ISO 2 Code

string

The country of the billing address.
Standard – ISO alpha-2 country code
Example – US

Card Scheme Type

string

The type of card, as provided by the card scheme.

This can be one of:

CREDIT
DEBIT

Card Number

string

The card's masked primary account number (PAN).
Example – 123456******7890

Transaction Type

string

The type of payment.
Example – Recurring

Card Network Token Type

string

The type of the card network token. This can be one of:

MDES – Mastercard
VTS – Visa

Track ID

string

The payment's unique tracking identifier.
Example – ORNETJBUX6UPEKH7QN

Reported Fraudulent Transactions Report

Report availability

Report format

Sample report

Information

Report fields