# Authorization Activity Report The Authorization Activity Report lists all authorization messages within a specified time frame. It provides information about: - The authorization, the related transaction, and their statuses - The card, card verification, and any 3D Secure (3DS) challenge - The conditions at the point of sale (PoS) - Whether the [Authorization Relay](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/relay-authorization-requests.md) passed the authorization to you - Any user-defined fields you specified during setup --- ## Report availability The report data is refreshed twice daily at around 12:30 AM and 10:30 AM, in UTC. See instructions on how to download the report on demand or on a schedule: - [In the Dashboard](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Generate_reports_in_the_Dashboard) - [Using the API](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Retrieve_reports_via_API) - [Using Secure File Transfer Protocol](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Access_reports_via_SFTP) (SFTP) - [Using webhooks](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Receive_reports_using_webhooks) --- ## Report format The report is provided as a CSV file. The file name uses the following formats by default: - API and SFTP – `issuing_authorization_activity_{EntityID}_{Start Date: YYYYMMDD}_{End Date:YYYYMMDD}_1.csv` - Dashboard scheduled reports – `issuing_authorization_activity_{EntityID}_{Start Date: YYYYMMDD}_{End Date:YYYYMMDD}_1.csv` For SFTP, the report is uploaded in the following folder structure:
`{Entity_name} > reports-{Entity_name} > issuing_authorization_activity` --- ## Sample report [Download a sample report](https://www.checkout.com/docs/files/Sample_Authorization_Activity_Report.csv) (CSV file). > **Information** > > If using Safari, hold down the _Option_ key when selecting the link to download the file. --- ## Report fields The report includes the following fields in this order: | Field name | Description | | --- | --- | | Scheme

`string` | The card scheme used for the payment.
This can be one of:

- `Mastercard`
- `Visa` | | Message ID

`string` | The authorization message's unique identifier, prefixed with `msg_`. | | Transaction ID

`string` | The transaction's unique identifier, which links all related authorization, reversal, and clearing messages. This is prefixed with `trx_`. | | Client ID

`string` | Your unique identifier as a Checkout.com client, prefixed with `cli_`. | | Entity ID

`string` | The entity's unique identifier, prefixed with `ent_`. | | Cardholder ID

`string` | The cardholder's unique identifier, prefixed with `crh_`. | | Card ID

`string` | The card's unique identifier, prefixed with `crd_`. | | Client Name

`string` | Your Checkout.com client name. | | Entity Name

`string` | The entity's name. | | Message Type

`string` | The type of authorization message. This can be one of:

- `authorization_advice` – A transaction to modify an authorization – For example, an adjustment, amount change, or card hold
- `authorization` – An authorization request
- `reversal` – A request to undo an authorization before presentment or clearing
- `reversal_advice` – A message from the acquirer reversing an authorization request | | Indicator

`string` | The type of authorization. This can be one of:

- `deferred_authorization` – When the merchant sends you an authorization to indicate transactions that were mainly done during mass transit, from automated fuel dispensers (AFD), or offline mode
- `incremental_pre_authorization` – A request to increase the total authorized amount before the payment is captured
- `final_authorization` – When the final amount is known, unless there is a technical issue between the merchant and the card scheme
- `full_reversal` – A reversal of the full transaction amount
- `normal_authorization` – The transaction was fully processed by the merchant at the point of sale
- `partial_reversal` – A reversal of part of the transaction amount
- `pre_authorization` – A temporary hold on funds on the card to cover the transaction amount
- `unknown` – Any other type of authorization | | Transaction Type

`string` | The type of transaction. This can be one of:

- `cash_advance` – A short-term cash loan you give to a cardholder
- `cashback` – When cash is returned on top of a purchase
- `balance_inquiry` – When the cardholder checks the balance on the card
- `payment` – A payment for goods or service
- `pin_change` – When the cardholder changes their PIN at an ATM
- `pin_unblock` – When the cardholder unblocks their PIN at an ATM
- `purchase` – A purchase of goods or services
- `refund` – A credit to the cardholder's account as a full or partial refund for a purchase
- `remittance_funding` – When funds are added to a remittance account
- `remittance_payment` – When the cardholder transfers funds to another party, often internationally
- `unique transaction` – A quasi-cash payment using, for example, gaming tokens, cryptocurrency, travelers' cheques
- `unknown` – Any other type of transaction
- `withdrawal` – A cash withdrawal from an ATM | | Is Relayed

`boolean` | Indicates whether Authorization Relay passed you the authorization to approve or decline:

- `false` (default) – The authorization was not relayed.
- `true` – The authorization was relayed. | | Status

`string` | The status of the authorization. This can be one of:

- `approved` – You approved the authorization.
- `declined` – You declined the authorization. | | Decline Reason

`string` | The [decline code](https://www.checkout.com/docs/developer-resources/codes/issuing-decline-codes.md) that specifies why the authorization was declined.

If you approved the authorization, this field is empty. | | Verification Result Cryptogram

`string` | Indicates whether the card’s identity was successfully verified. This can be one of:

- `unverified` – The card’s identity was not successfully verified.
- `verified` – The card’s identity was successfully verified. | | Verification Result CVC1

`string` | Indicates whether the card validation code (CVC1) encoded in the magnetic stripe was successfully verified. This can be one of:

- `unverified` – The CVC1 was not successfully verified.
- `verified` – The CVC1 was successfully verified. | | Verification Result CVC2

`string` | Indicates whether the card validation code (CVC2) printed on the card is valid. This can be one of:

- `invalid` – The CVC2 is not valid.
- `valid` – The CVC2 is valid. | | Verification Result Expiry Date

`string` | Indicates whether the card’s expiry date is still valid. This can be one of:

- `invalid` – The card has expired.
- `valid` – The card has not expired. | | Verification Result PIN

`string` | The result of verifying the cardholder's personal identification number (PIN). This can be one of:

- `unverified` – The PIN was not successfully verified.
- `verified` – The PIN was successfully verified. | | Verification Result Service Code

`string` | The result of verifying the three or four-digit number that specifies the card’s acceptance requirements and transaction limitations. This can be one of:

- `unverified` – The service code was not successfully verified.
- `verified` – The service code was successfully verified. | | Transaction Currency

`string` | The acquirer's local currency or the local currency where the transaction took place.
Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Transaction Amount

`decimal` | The amount for the transaction in the [major currency unit](https://www.checkout.com/docs/payments/accept-payments/format-the-amount-value.md).

Format – Fixed-point notation with up to eight decimal places

Example – 500 USD is represented as `500.00` | | Billing Currency

`string` | The currency in which you bill the cardholder.
Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Billing Amount

`decimal` | The amount to bill the cardholder in the major currency unit.

Format – Fixed-point notation with up to eight decimal places

Example – 500 USD is represented as `500.00` | | 3DS Version

`string` | The 3D Secure (3DS) protocol version used for authorization. This can be one of:

- `1` – 3DS version 1
- `2` – 3DS version 2
- Empty – 3DS was not used | | Authentication Status

`string` | The outcome of the authentication.
This can be one of:

- `authenticated` – The authorization was authenticated successfully.
- `authentication_attempted` – Either the issuer or cardholder did not participate in the authentication flow.
- `not_authenticated` – Either the authentication failed or the acquirer did not initiate authentication.
- `not_applicable` – Authentication was not required for this authorization.
- `Unknown` – The authentication status is unknown. | | Requested Exemption Type

`string` | The type of exemption from 3DS requested for the transaction. This can be one of:

- `acquirer_transaction_risk_analysis` – The acquirer performed a risk analysis on the transaction.
- `authentication_outage_exception` – An outage prevented the merchant or acquirer from completing authentication.
- `low_value_payment` – The transaction amount is less than 30 EUR.
- `merchant_initiated_transaction` – The merchant initiated the transaction under a previous agreement with the cardholder.
- `not_applicable` – 3DS is not required for this transaction.
- `not_requested` – 3DS was not requested for this transaction.
- `recurring_payment` – This is a recurring payment under a previous agreement with the cardholder.
- `secure_corporate_payment` – The transaction was initiated by a corporate customer, or from a secure corporate environment.
- `secure_customer_authentication_delegation` – The transaction carries low fraud risk, is with a trusted merchant, or passed a risk analysis. | | SCA Not Required Reason

`string` | The reason why Strong Customer Authentication (SCA) was not required for the transaction. For more information about the following exemption types, see [SCA compliance](https://www.checkout.com/docs/business-operations/ensure-regulatory-compliance/sca-compliance.md).
This can be one of:

- `acceptance_rate_accelerator_exemption`
- `acquirer_transaction_risk_analysis`
- `authentication_outage_exception`
- `issuer_secure_corporate_payment`
- `low_value_payment`
- `merchant_initiated_transaction`
- `mail_order_telephone_order`
- `not_applicable`
- `one_leg_out` – A cross-border payment where only one part of the transaction is regulated under the European Union (EU) payment laws.
- `recurring_payment`
- `secure_corporate_payment`
- `strong_customer_authentication_delegation`
- `unknown_or_not_supported`
- `zero_amount_asi` | | Has ECB Conversion Rate

`boolean` | Indicates whether currency conversion is required at the European Central Bank (ECB) rate:

- `false` (default) – Currency conversion is not required.
- `true` – Currency conversion is required. | | ECB Conversion Rate

`decimal` | The ECB currency conversion rate against the euro applied to the payment.
Example – For `GBP`:`EUR`, the conversion rate is represented as `0.842293` | | Merchant ID

`string` | The merchant's unique identifier.

This may vary per acquirer. | | Merchant Category Code

`number` | The merchant's [merchant category code (MCC)](https://www.checkout.com/docs/developer-resources/testing/codes/merchant-category-codes.md) for this payment.
Standard – ISO 18245 code
Example – `1731`

Merchants can have multiple MCCs. | | Merchant Name

`string` | The merchant's company name. | | Merchant Country Code

`string` | The country where the merchant is registered.
Standard – [ISO alpha-3 country code](https://www.checkout.com/docs/developer-resources/testing/codes/country-codes.md)
Example – `USA` | | Merchant State

`string` | For US merchants, the state of the merchant's address.

For other merchants, the value is `null`. | | Merchant City

`string` | The city where the merchant is registered. | | POS Entry Mode

`string` | The way the payment was captured at the point of sale (PoS). This can be one of:

- `credential_on_file` – The card details were available on file.
- `contact_chip` – The card chip touched the PoS terminal.
- `contactless_chip` – The terminal read the card chip via near-field communication (NFC).
- `contactless_magstripe`– The terminal read the card's magnetic stripe via NFC.
- `ecommerce` – The card details were entered in a website or app.
- `magstripe` – The card's magnetic stripe touched the terminal.
- `manual` - The card details were manually entered into the terminal, or the customer used cash, check, or money order.
- `optical_character_recognition` – The card details were captured using optical character recognition (OCR).
- `optical_code` – The merchant's optical scanner or device read a Quick Response (QR) code.
- `server` – The card details were passed directly from the merchant's server to the payment platform.
- `other` – Any other way of capturing payment. | | Digital Card ID

`string` | The digital card's unique identifier, prefixed with `dcr_`.

For physical cards, this field is empty. | | Verification Result Digital Card Expiry Date

`string` | The result of verifying the digital card. This can be one of:

- `unverified` – The digital card was not successfully verified.
- `verified` – The digital card was successfully verified. | | Xpay Device Type

`string` | The type of device used for an Xpay payment.
This can be one of:

- `Smartphone`
- `Smartwatch` [Check the possible values]

If not relevant, this field is empty. | | Xpay Wallet Type

`string` | The type of digital wallet used for an Xpay payment.
This can be one of:

- `Apple Pay`
- `Google Pay` [Check the possible values]

If not relevant, this field is empty. | | Created On UTC

`date-time` | The date and time when the payment was initiated, in UTC.
Standard – ISO 8601 code
Example – `yyyy-mm-ddThh:mm:ss.sss` | | Transmitted By Scheme On UTC

`date-time` | The date and time when the card scheme transmitted the authorization, in UTC.
Standard – ISO 8601 code
Example – `yyyy-mm-ddThh:mm:ss.sss` | | Card Type

`string` | The type of card. This can be one of:

- `physical` – A physical card
- `virtual` – A non-physical card for card-not-present (CNP) transactions only | | Card Masked PAN

`string` | The card's masked primary account number (PAN).
Example – `1234 56** **** 7890` | | Card Issuing Country

`string` | The country where you issued the card.
Standard – [ISO alpha-3 country code](https://www.checkout.com/docs/developer-resources/testing/codes/country-codes.md)
Example – `USA` | | Card Display Name

`string` | The display name you provided when creating the card. | | Card Reference

`string` | The reference you provided when creating the card. | | Card UDF 1

`string` | A user-defined field (UDF) you specified during setup. | | Card UDF 2

`string` | A UDF you specified during setup. | | Card UDF 3

`string` | A UDF you specified during setup. | | Card UDF 4

`string` | A UDF you specified during setup. | | Card UDF 5

`string` | A UDF you specified during setup. |