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 includes the following details:

  • 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 number – the unique number used to identify the merchant.
  • Wallet referencethis column will be empty for Card API reporting.
  • 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.

 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 [CampaignUUID]/[CampaignName]DailyAuthFailure[Date].csv Daily HTTP 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

Are you ready to use our APIs

If you are not yet registered with us.

Still have questions? Contact us.