Failed transaction report
This report gives details of the transactions that were declined daily. It contains a list of transactions that Paymentology or the client declined, and sent a declined response code to the card association. With the failed transaction report file, it becomes easier to find the reasons for failures in transactions and improve the process.
The report is also generated monthly and contains the same report details as the daily report.
There are two versions of this report available:
Version 1
Version 1 includes the following details:
- Campaign Name – name of client’s campaign.
- Voucher Number – the customer’s card number.
- Transaction Amount – the value of the transaction.
- Transaction Date – this is the settlement date of the transaction.
- Transaction Method – the API method used in sending the transaction to the client.
- Transaction Error Code – the code indicating the reason for the decline.
- Acceptor Name – the name of the merchant.
- Merchant No – the unique number used to identify the merchant.
- Voucher Value – the voucher value at the point the transaction failed. Voucher Value = Voucher Load Value – (Already settled amount + Authorised amount).
- Wallet Reference – this is a unique customer reference for the card.
- Transaction ID – it’s a unique reference for the transaction.
- In most cases, the provided Transaction ID will be the same Transaction ID as the original authorization. It’s usually 7 to 10 digits.
- In case of refunds, there will be a unique Transaction ID for each of them. The ID does not relate to the original authorization. It’s also longer, up to 23 characters.
- In case of chargebacks, there will be a unique Transaction ID for each of them. The ID does not relate to the original authorization. It’s also longer, up to 23 characters.
- Tracking Number – this is a unique 15-digit tracking identifier for the card.
- MCC – the merchant category code.
- POS Entry mode – indicates how the transaction was captured (Capture Mode). Possible values include: ECOM (Ecommerce), NFC (Near Field Communication), MAG (Magnetic stripe), MAN (Manually), EMV (EMV chip).
- Transaction Internal Code – this is a code that gives you the reason for transaction declines. List of codes can be downloaded here
- Digitized Wallet ID – the 3 digit numeric code that identifies the Xpay App. Find a list of the Wallet IDs here.
If the transaction did not reach Paymentology and was declined, this would not appear on the report.
Version 2
Version 2 includes the following details:
- Campaign Name – name of client’s campaign.
- Voucher Number – the customer’s card number.
- Transaction Amount – the value of the transaction.
- Transaction Date – this is the settlement date of the transaction.
- Transaction Method – the API method used in sending the transaction to the client.
- Transaction Error Code – the code indicating the reason for the decline.
- Acceptor Name – the name of the merchant.
- Merchant No – the unique number used to identify the merchant.
- Voucher Value – the voucher value at the point the transaction failed. Voucher Value = Voucher Load Value – (Already settled amount + Authorised amount).
- Wallet Reference – this is a unique customer reference for the card.
- Transaction ID – it’s a unique reference for the transaction.
- In most cases, the provided Transaction ID will be the same Transaction ID as the original authorization. It’s usually 7 to 10 digits.
- In case of refunds, there will be a unique Transaction ID for each of them. The ID does not relate to the original authorization. It’s also longer, up to 23 characters.
- In case of chargebacks, there will be a unique Transaction ID for each of them. The ID does not relate to the original authorization. It’s also longer, up to 23 characters.
- Tracking Number – this is a unique 15-digit tracking identifier for the card.
- MCC – the merchant category code.
- POS Entry mode – indicates how the transaction was captured (Capture Mode). Possible values include: ECOM (Ecommerce), NFC (Near Field Communication), MAG (Magnetic stripe), MAN (Manually), EMV (EMV chip).
- Transaction Internal Code – this is a code that gives you the reason for transaction declines. List of codes can be downloaded here
- Digitized Wallet ID – the 3 digit numeric code that identifies the Xpay App. Find a list of the Wallet IDs here.
- Payment Initiator – indicates whether a transaction was initiated by the Cardholder (CIT – Cardholder Initiated Transaction) or the Merchant (MIT – Merchant Initiated Transaction)
If the transaction did not reach Paymentology and was declined, this would not appear on the report.
Report format
| FORMAT | FILE NAME | FREQUENCY | ACCESSIBILITY |
|---|---|---|---|
| CSV | DAILY REPORT: [CampaignUUID]/[CampaignName]_DailyAuthFailure_[YYYYMMDD].csv MONTHLY REPORT: [CampaignUUID]/failedtransactions_[CampaignName]_[YYYY-MM-DD-YYYY-MM-DD].csv | Daily & Monthly | HTTP get request or client SFTP folder |
Report time frame
| UTC +2 | UTC +7 | REMARKS |
|---|---|---|
| 06:30 | 11:30 | When the report is generated at 06:30 UTC+2 / 11:30 UTC+7 2020-09-10, the timeframe of all failed transactions captured in this report is from 2020-09-09 00:00:00 to 2020-09-09 11:59:59 in: • System time zone UTC+2 • Asia client time zone UTC+7 • Merchant time zone |
Report sample
Note: file will automatically download upon clicking link