ISO response codes

When a transaction reaches the acquiring bank, the bank returns an ISO 8583 response code that explains the outcome. Scan to Pay surfaces this code on webhook payloads and queryRef responses in the bankResponse.bankResponse field. This page maps every code to its meaning and a suggested message to display to your customer.

📘

For platform errors, see Errors. This page covers bank/scheme response codes — the third-party authorisation result. Platform-side errors use a different code range (431–481).

How to use this page

When a transaction completes, the bankResponse object on the webhook payload includes:

{
  "retrievalReferenceNumber": 6321400012,
  "authCode": "123456",
  "bankResponse": "00",
  "bankResponseMessage": "Approved"
}

The bankResponse field is the ISO code. Look it up in the table below to map it to a customer-friendly message. Never show the raw code to end users — translate it to your own copy first.

Code categories at a glance

Full code reference

Notes

• Code 00 is the primary positive value. Codes 10, 11, and 32 are conditional or partial approvals; codes 76, 79, and 80 are administrative approvals. Anything else is a decline or failure.
• The platform may return the same code for different underlying reasons (e.g. 05 covers both "do not honour" and generic refusals). The bankResponseMessage field provides additional context where available.
• For transactions that never reach the bank (validation failures, fraud blocks, limit failures), bankResponse will be absent or null — refer to Errors and Transaction states instead.
• Mastercard T1–T8 codes are transaction-level rejections returned before authorisation. Treat as bank-side failures.

What's next

• Map errors and states together in your handler → Errors, Transaction states
• Webhook payload format including bankResponse → Webhooks
• Customer-friendly retry guidance → Transaction states