Understanding Terminal Response Codes
When an EFTPOS terminal encounters a problem while processing a payment, it generates a specific numerical response code. For a business owner, knowing what these two-digit or three-digit identifiers mean helps you pinpoint exactly why a transaction did not go through—whether the issue originates from the customer's bank account, a temporary network outage, or a configuration error on the device itself.
Having a basic understanding of standard National Australia Bank (NAB) EFTPOS error codes enables you to address payment interruptions smoothly. Recognizing the root cause means you can either guide the cardholder toward an alternative payment method or take the appropriate technical steps to get your terminal communicating with the bank again.
Key Information and Requirements
| Category | Details |
|---|---|
| Error Display Methods | Printed directly on the declined customer receipt or displayed on the terminal's screen. |
| Typical Resolution Time | Often resolved immediately by retrying, or within a few minutes if a network reboot is required. |
| Applicable Devices | Standard NAB standalone terminals, mobile EFTPOS hardware, and integrated point-of-sale setups. |
| Key Requirements | Your Merchant ID, Terminal ID, and the exact error code to help the support team assist you. |
The most popular NAB EFTPOS error codes are:
- 00, 11, 76 - approved
- 01, 31 - declined to see card
- 54 - declined card
- 55 - PIN Incorrect
- 60 - declined call help
- 96 - declined
- A2 - general failure
- N1 - login success
- T1 - operator timeout
- T8, B5 - invalid amount
- TN, TZ, 98 - declined
- TR - system error
- Z3 - line busy
- Z5 - power fail
Troubleshooting Terminal Access
If you cannot clear an error or the terminal behaves unexpectedly, here is how to resolve the most common technical hurdles you might face in a retail environment.
MFA / Login Issues (Terminal Logon Failure)
- Cause: A weak Wi-Fi or 4G cellular signal prevents the terminal from successfully authenticating its daily security credentials with the bank's main servers.
- Simple Fix: Move the terminal closer to your router or a window to improve signal strength, then manually select the 'Logon' option from the merchant menu.
- Fallback Action: Call the merchant helpdesk to verify if there is an active network outage affecting your specific area or telecommunications provider.
Browser or App Errors (POS Integration Failures)
- Cause: Stale software data or an outdated version of the point-of-sale application on your tablet or register is failing to communicate the purchase amount to the connected card reader.
- Simple Fix: Close your point-of-sale application entirely, check your device settings for any pending software updates, and then restart the integration software.
- Fallback Action: Switch to manual entry mode on the standalone terminal if possible, and contact your POS software provider to report the ongoing glitch.
Locked Account / ID / Access Issues (Blocked Terminal Functions)
- Cause: Entering the incorrect merchant manager PIN multiple times when trying to process a refund or alter administrative settings triggers an automated security lock on those functions.
- Simple Fix: Stop attempting to guess the PIN to avoid a permanent hardware lock, and check your original setup documentation for the correct default passcode.
- Fallback Action: Contact the business support team with your Merchant ID and Terminal ID so they can securely reset your administration passcode over the phone.
Pro-Tip: Because many communication errors stem from outdated security certificates, performing a manual software update through the terminal's settings menu at least once a month typically reduces random connection drops and keeps your payment processing smooth.
Frequently Asked Questions
Q: Why did the terminal return a "51 Insufficient Funds" code?
This happens when the cardholder's issuing bank declines the purchase because the account balance is too low to cover the requested amount. The terminal itself is functioning perfectly; the bank's processing logic has simply halted the transaction to prevent an overdraft. One limitation is that privacy laws mean the terminal will never display the customer's actual balance, just the generic decline message. Your practical next step is to discreetly inform the customer that their bank declined the charge and ask if they would like to use an alternative card to complete the purchase.
Q: What should I do if I get a "91 Issuer Unavailable" error?
Typically, this code appears when your EFTPOS machine successfully connects to the NAB network, but the system cannot reach the specific bank that issued the customer's card. This is usually caused by a temporary maintenance window or data outage at the other financial institution. Depending on the situation, the system might automatically switch to an offline electronic fallback mode, allowing small transactions to proceed, but larger amounts will fail outright. Your practical next step is to wait a few minutes and retry the transaction, or suggest the customer use a card from a different bank.
