Transaction Cancel Types Codes and Definitions
Cancel type indicates how a transaction concluded whether it was approved, declined, or cancelled. We utilize this information as a critical component in our transaction flow logic.
General
Cancel Type is an indication for how the transaction ended, was it Approved, Declined or Canceled?
We utilize this information as a critical component in our transaction flow logic. Additionally, it enables us to provide comprehensive analysis and insightful reports to our customers.
Transaction Cancel Types Definition Table
|
Cancel Type ID
|
Cancel Type Description
|
Explanation
|
|
1
|
Transaction timeout
|
The user didn’t complete the transaction in time, so the system cancelled it automatically.
|
|
2
|
Cancelled by consumer
|
The user actively cancelled the transaction before completion
|
|
3
|
Cancelled by machine
|
The machine automatically cancelled the transaction due to an internal condition or interruption.
|
|
4
|
Not enough credit
|
The transaction was cancelled due to insufficient available funds from the user.
|
|
5
|
MDB no idle
|
The machine's MDB interface wasn’t in an idle state, so the transaction couldn’t start and was cancelled
|
|
6
|
Product could not be dispensed
|
The machine failed to dispense the selected product, leading to an automatic cancellation.
|
|
7
|
Power down
|
Machine/reader got powered off during transaction
|
|
8
|
Power down in dispense mode
|
Power down mid transaction
|
|
9
|
Cancelled by machine during authorization
|
The machine cancelled the transaction while waiting for payment authorization
|
|
10
|
Automatic void
|
Auto Void service runs every hour and collects the cancel type 10 transactions
|
|
11
|
Cancelled by Purchase Price data query
|
Cancelled by Purchase Price data query |
|
17
|
Declined by card after issuer approval
|
EMV Card declined the transaction since it's not please with the results it received
|
|
18
|
Declined by terminal after issuer approval
|
EMV Terminal (Nayax device) declines the transactions since it's not please with the results it got
|
|
19
|
Unknown Cancel Type
|
Need further investigation since the CT is unknown
|
|
21
|
Transaction declined by bank
|
Transaction declined by bank |
|
22
|
Bank’s server communication Timeout
|
Bank’s server communication Timeout |
|
23
|
Wrong PIN code (after X retries)
|
PIN Blocked |
|
32
|
Vending Machine communication error
|
No communication between vending machine and POS |
|
36
|
Failed on Void
|
Generic CT for all void failed attempts (Auto void and Immediate void)
|
|
44
|
Standing order registration
|
Recurring authorizing failed |
|
45
|
Validate card only
|
Transaction was not able to initiate |
|
50
|
Automatic void
|
Automatic Void service runs every hour and collects specific transactions, when successful the CT will be 50
|
|
52
|
Automatic Cancel
|
Auto Cancel service runs every hour and collect specific transactions, when successful the CT will be 52
|
|
53
|
Failed Cancel
|
Failed during Auto Cancel attempt
|
|
55
|
Remote start settlement done but still unsettled
|
Remote start settlement done but still unsettled in Nayax - No confirmation from banking provider |
|
60
|
Timeout void
|
Banking provider delayed authorization or internet connection poor
|
|
61
|
Mobile payment provider void
|
Mobile payment provider delayed authorisation |
|
62
|
Refunded
|
Refunded transaction
|
|
63
|
Loyalty Card Validation Only
|
Transaction was not able to initiate
|
|
80
|
Pending Batch
|
Relevant to Batch 2.0, the service collects CT 80 transactions and sends them on queue
|
|
81
|
Batch Declined
|
If something occurred during the batch 2.0 run, the transaction will fail and CT will be 81
|
|
84
|
Batch Voided
|
Banking provider delayed authorization or internet connection poor
|
|
250
|
Declined During Authorization
|
All 3rd party declined transactions will get CT 250
|
Did you find this article helpful?