Transaction Cancel Types Codes & Definitions Table
A reference of Nayax Cancel Type IDs codes showing how each transaction ended. Use this table to interpret records in Nayax Core. Cancel type reflects if a transaction was approved, declined, or cancelled, and drives key transaction logic.
General
Payments & Transactions › Transaction Issues
Transaction Cancel Types: Codes and Definitions
A complete reference of Cancel Type IDs the codes that indicate how a transaction concluded. Use this table to interpret transaction records and reports in Nayax Core.
Jump to section
What Is a Cancel Type?
Every transaction in Nayax Core concludes with a Cancel Type a numeric code that records the outcome. Cancel Types cover all possible endings: approved, declined, cancelled by the user, cancelled by the device, or handled automatically by a system service.
Cancel Type IDs appear in transaction reports and are used in Nayax transaction flow logic. Use the reference table below to identify what happened when a transaction did not complete as expected.
Related article: For guidance on how to respond to cancellations and declines, see Understanding Transaction Cancellations and Declines.
Cancel Type Reference
ConsumerInitiated by the customer
DeviceInitiated by the device or machine
BankingRelates to the payment provider or bank
SystemInternal system or processing event
AutomatedHandled by an automated service
| ID | Cancel Type | Description | Category |
|---|---|---|---|
| 1 | Transaction Timeout | The transaction was not completed within the allowed time and was cancelled automatically by the system. | System |
| 2 | Cancelled by Consumer | The customer actively cancelled the transaction before it was completed. | Consumer |
| 3 | Cancelled by Machine | The device automatically cancelled the transaction due to an internal condition or interruption. | Device |
| 4 | Not Enough Credit | The transaction was cancelled due to insufficient available funds on the customer account, or the device credit setting is configured too low. | Consumer |
| 5 | MDB No Idle | The device MDB interface was not in an idle state when the transaction attempted to start, resulting in cancellation. | Device |
| 6 | Product Could Not Be Dispensed | The device failed to dispense the selected product, triggering an automatic cancellation. | Device |
| 7 | Power Down | The device or reader lost power during the transaction. | Device |
| 8 | Power Down in Dispense Mode | The device lost power while in the process of dispensing a product mid-transaction. | Device |
| 9 | Cancelled by Machine During Authorization | The device cancelled the transaction while awaiting payment authorization. | Device |
| 10 | Automatic Void | Collected by the Auto Void service, which runs hourly and processes transactions assigned Cancel Type 10. | Automated |
| 11 | Cancelled by Purchase Price Data Query | The transaction was cancelled during a purchase price data query. | System |
| 17 | Declined by Card After Issuer Approval | An EMV card declined the transaction after receiving results from the issuer that did not meet its acceptance criteria. | Banking |
| 18 | Declined by Terminal After Issuer Approval | The EMV terminal declined the transaction after receiving results from the issuer that did not meet its acceptance criteria. | Device |
| 19 | Unknown Cancel Type | The cancel type could not be determined. Further investigation is required. Contact Nayax Support with the transaction details. | System |
| 21 | Transaction Declined by Bank | The transaction was declined by the bank or banking provider. | Banking |
| 22 | Bank Server Communication Timeout | Communication with the bank server timed out before authorization could be completed. | Banking |
| 23 | Wrong PIN Code | The PIN was entered incorrectly the maximum number of times, resulting in the card being blocked. | Consumer |
| 32 | Vending Machine Communication Error | Communication between the vending machine and the POS device could not be established. | Device |
| 36 | Failed on Void | A void attempt failed. This is a generic code covering all failed void attempts, both automatic and immediate. | System |
| 44 | Standing Order Registration | A recurring authorization attempt failed. | System |
| 45 | Validate Card Only | The transaction could not be initiated during a card validation attempt. | Banking |
| 50 | Automatic Void (Successful) | Collected by the Auto Void service, which runs hourly. Cancel Type 50 indicates a successful automatic void. | Automated |
| 52 | Automatic Cancel | Collected by the Auto Cancel service, which runs hourly. Cancel Type 52 indicates a successful automatic cancellation. | Automated |
| 53 | Failed Cancel | An automated cancel attempt failed during processing. | Automated |
| 55 | Remote Start Settlement Done but Still Unsettled | A remote start settlement was completed on the device side but confirmation from the banking provider has not been received. | Banking |
| 60 | Timeout Void | A void was triggered due to delayed authorization from the banking provider or a poor internet connection. | Banking |
| 61 | Mobile Payment Provider Void | The mobile payment provider delayed authorization, resulting in a void. | Banking |
| 62 | Refunded | The transaction was refunded. | System |
| 63 | Loyalty Card Validation Only | The transaction could not be initiated during a loyalty card validation attempt. | System |
| 80 | Pending Batch | Relevant to Batch 2.0. The service collects Cancel Type 80 transactions and places them in the processing queue. | Automated |
| 81 | Batch Declined | A transaction failed during a Batch 2.0 processing run. | Automated |
| 84 | Batch Voided | A batch transaction was voided due to delayed authorization from the banking provider or a poor internet connection. | Automated |
| 250 | Declined During Authorization | All third-party declined transactions are assigned this code. The transaction was not authorized during the authorization stage. | Banking |
Did you find this article helpful?