Error Codes
Common Response Codes
| Response Code | Explanation | Required Action |
| S8 (Cancelled by PINpad) | The transaction was cancelled by the operator or donator by pressing the Cancel button on the terminal. | Retry the transaction, if required. |
| S3 (Inactivity Timeout) | The terminal has timed out waiting for the donator to present their card or digital wallet. | Retry the transaction, if required. |
| 51 (Insufficient Funds) | The card holder's bank has declined the transaction due to insufficient funds. | Ask the card holder to use a different card. |
| C5 (No Network) | The terminal does not currently have a network connection. | Check that the terminal has a working network connection by following the instructions outlined here. |
Response Types
| Response Type | Description | How to Identify | Required Action | Links |
| Host Response Codes | The codes are returned by the terminal's merchant facility host or from the card holder's bank. | These response codes are typically numeric; some examples include 12, 51, 55, etc. | If the response pertains to the merchant facility, please contact your merchant facility provider. Otherwise, please prompt the card holder to contact their issuing bank. | Error List |
| Terminal Response Codes | The codes are returned by the terminal, which may indicate an issue with the terminal or the attempted transaction. | These response codes are alphabetical and alphanumeric; some examples include FD, S3, H5, etc. | Some errors do not result from a terminal fault, so please find the response code in the Terminal response codes table below and follow the troubleshooting steps. | Error List |
| Communication Response Codes | The codes indicate an issue with network connectivity between the terminal and any server endpoints. | These response codes begin with C and are alphabetical & alphanumeric. Some examples are C5, CA, C9, etc. | Please find the response code in the Communication response codes table below and follow the troubleshooting steps. | |
| Cloud EFTPOS Middleware (Wedge) Response Codes | The codes indicate an issue with the terminal middleware's interactions with other terminal software and the Cloud EFTPOS Web Portal. | These response codes begin with E and contain 3-4 numbers. Some examples are E253, E2100, E2003, etc. | Please find the response code in the Wedge response codes table below and follow the troubleshooting steps. |
Response Code Lists
Host (NAB) Error Codes
Please contact NAB's merchant services team or ask the card holder to contact their issuing bank. The errors are outlined below.
| Error Code | Error Text | Explanation |
| 00 | APPROVED | The transaction has been approved. No further action is required. |
| 01 | REFER TO CARD ISSUER | The card holder’s Bank (issuer) has not allowed the transaction. Refer card holder to issuer. Ask customer for alternative method of payment. |
| 04 | CALL AUTH CENTRE | The transaction has been unsuccessful. Retain the card. Ask the customer for an alternative method of payment and contact your Merchant Help Desk. |
| 08 | APPROVED (with Signature) | The transaction has been approved. No further action is required. |
| 12 | INVALID TRANSACTION | The card holder’s Bank has not allowed the transaction. Refer the card holder to the card issuer. Ask customer for an alternative method of payment. |
| 13 | INVALID AMOUNT | The transaction amount has been rejected by the Bank. Ask the customer for an alternative method of payment. |
| 21 | AUTH NOT FOUND | The transaction has been rejected by the Bank. The Authorisation ID provided cannot be verified by the Bank. Contact the Merchant Help Desk. |
| 22 | SYSTEM ERROR 022 | An error occurred downloading the CPAT during a Logon. Retry the Logon. If the problem persists, contact your EFTPOS supplier. |
| 30 | SYSTEM ERROR 030 | An error occurred during the Logon processing. Retry the Logon. If the problem persists, contact your EFTPOS supplier. |
| 31 | SEE CARD ISSUER | The card holder’s Bank (issuer) is not able to process the transaction. Ask customer for alternative method of payment. |
| 37 | SYSTEM ERROR 037 | An error occurred during the RSA Key initialisation processing. Retry the Key Initialisation or contact your EFTPOS supplier. |
| 39 | NO CREDIT ACCOUNT | The card does not have a credit account linked to it. Ask the customer to select another account type. |
| 51 | CHECK ACCOUNT | There are insufficient funds available in the customer’s account. Ask the customer to select another account type. |
| 52 | NO CHEQUE ACCOUNT | The card does not have a cheque account linked to it. Ask the customer to select another account type. |
| 53 | NO SAVINGS ACCOUNT | The card does not have a savings account linked to it. Ask the customer to select another account type. |
| 54 | CARD EXPIRED | The transaction has been rejected by the issuing Bank. Refer the card holder to the card issuer. Ask the customer for an alternative method of payment. |
| 55 | PIN INCORRECT | The customer has entered an incorrect PIN number. They should attempt to enter it again. |
| 60 | DECLINED - CALL HELP | The Bank has declined the transaction for this card. Ask the customer for an alternative method of payment or contact the Merchant Help Desk. |
| 61 | OVER CARD LIMIT | The card holder has already exceeded the withdrawal limit for this card for the day. Ask the customer for an alternative method of payment. |
| 63 | SECURITY FAILURE 081 | The Bank has detected a Message Authentication error on the message from the PINpad. Re-tender the transaction. If the problem persists contact the Merchant Help Desk. |
| 75 | EXCEED PIN TRIES | The card holder has entered the wrong PIN three times. The card cannot be used for the remainder of the day. Refer card holder to the card issuer. Ask the customer for an alternative method of payment. |
| 91 | ISSUER NOT AVAILABLE | The card holder’s Bank is unable to be contacted to authorize the transaction. Raise a manual voucher for the amount of the EFT transaction. |
| 93 | ALREADY SETTLED | The PINpad has already been settled. No further action is required. |
| 94 | DUPLICATE TRANSACTION | The Bank has rejected the transaction as the Bank has received this as a duplicate. The transaction details at the Bank match a previously processed transaction. |
| 96 | SYSTEM ERROR | The card holder’s Bank has not allowed the transaction. Refer the customer to the card issuer and seek another method of payment. |
| 97 | SETTLEMENT TAKEN | The settlement has been approved. No further action required. |
| 98 | MAC ERROR | The Bank has detected a Message Authentication error on the message from the PINpad. Re-tender the transaction. If the problem persists contact the Merchant Help Desk. |
| N0 | CANCELLED | The Bank has Declined the logon message. Please try again and if the problem persists contact the Merchant Help Desk. |
| N1 | APPROVED | The Bank has Approved the logon message. |
| N2 | INVALID PINPAD | The Bank has Declined the logon message, please contact the Merchant Help Desk. |
| N3 | CANCELLED | The Bank has Declined the logon message, please contact the Merchant Help Desk. |
| ND | DECLINED | The Bank has Declined the logon message. Please try again and if the problem persists contact the Merchant Help Desk. |
| NE | CANCELLED | The Bank has Declined the logon message. Please try again and if the problem persists contact the Merchant Help Desk. |
| NF | RECONNECTING | The Bank has Declined the logon message. Please try again and if the problem persists contact the Merchant Help Desk. |
| NG | RECEIVED FILE | The Bank has Declined the logon message. Please try again and if the problem persists contact the Merchant Help Desk. |
| NH | SECURITY FAILURE 081 | The Terminal ID and Merchant ID is invalid or unknown by the Host. Contact the NAB Merchant Help Desk to confirm the Terminal and Merchant IDs. |
Terminal Response Codes
Below is a list of response codes the terminal may return.
| Response Code | Error Text | Error Explanation | Troubleshooting Steps |
E0 |
Generic EMV application error |
Generic EMV error |
|
E1 |
Card error |
EMV level 1 error, refer to EMV response codes tab for meaning of nnn |
|
E2 |
Processing error |
EMV level 2 error, refer to EMV response codes tab for meaning of nnn |
|
EB |
TLV / EMV library error |
EMV TLV library error |
|
EJ |
Card not accpeted |
Card prefix is flagged in the MAST as not accepted |
Request customer use a different card. |
ER |
EMV level 1 reset error, model C / D |
EMV level 1 error returned by emvReset() |
|
ES |
EMV level 1 command error, model C / D |
EMV level 1 error returned by emvCommand() |
|
ET |
EMV level 1 reset error, model X |
EMV level 1 error returned by emvReset() |
|
EU |
EMV level 1 command error, model X |
EMV level 1 error returned by emvCommand() |
|
Z1 |
EMV trans declined offline |
Declined by the terminal or the card without an online attempt |
As the transaction was declined offline. you should first determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, request the customer try a different card which may be capable of being accepted whilst offline. |
Z3 |
EMV trans declined offline after online failure |
Declined by the terminal or the card following a failed attempt to go online |
As the transaction was declined offline. you should first determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, request the customer try a different card which may be capable of being accepted whilst offline. |
Z4 |
Use another card |
Offline specific error which occurs when blocking a card not configured for use in EFB / Offline mode. |
Advise the customer to try another card. |
Z5 |
Use Physical Card |
Offline specific error which occurs when blocking a mobile phone or device whilst in EFB / Offline mode. |
Advise the customer to use a physical card, not a mobile phone or wearable. |
F0 |
Generic contactless application error |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F1 |
Bad contactless protocol |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F2 |
Contactless Manufacturer Init Requried |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F3 |
Contactless reader key init required |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F4 |
Contactless reader response timeount |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F5 |
Invalid contactless reader response format |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F6 |
Invalid contactless reader response code |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F7 |
Contactless reader initialisation error |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F8 |
Tap error |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
F9 |
Try another entry mode |
A contactless read error has occurred. |
Retry the transaction. If problems persist on more than one card, Contact Support. |
FA |
Try another card |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FB |
No contactless AID record found |
A contactless read error has occurred. |
|
FC |
Contactless AID lookup error |
A contactless read error has occurred. |
|
FD |
Declined by contactless reader |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FE |
Offline data authentication failure |
A contactless read error has occurred. |
Check that you are not using a test card in a production environment, or visa versa. If the correct card is being used, Contact Support. |
FF |
Contactless disabled |
A contactless read error has occurred. |
Retry the transaction. If problems persist, Contact Support. |
FK |
Ctls Tags file access error |
A contactless read error has occurred. |
Retry the transaction. If problems persist, try a different card and then contact support regardless on if the different card works or fails. Doing the additional test will help support diagnose and fix your terminal’s configuration. |
FO |
ODA error in Reader |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FP |
CVM Error |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FQ |
Card Action Analysis Error |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FR |
terminal Does not have contact EMV |
A contactless read error has occurred. |
Retry the transaction on a different card. If problems persist, Contact Support. |
FS |
Unsupported Card |
Caused when a card with an unsupported scheme is tapped. |
If you believe you should be able to accept the card scheme receiving this error, Contact Support. Otherwise, ask the customer to use a different card. |
FV |
Expired Card |
Card is expired. |
Retry the transaction on a different card. If problems persist, Contact Support. |
H0 |
Manufacturer initialisation required |
The payment terminal has not been loaded correctly. |
The payment terminal has not been loaded correctly. Call support to arrange repair / replacement. |
H1 |
MAST access error |
The payment terminal has not been loaded correctly. |
The payment terminal has not been loaded correctly. Call support to arrange repair / replacement. |
H2 |
MAST lookup error |
Card prefix not configured. |
Check if card should be accepted. If you believe it should, Contact Support. |
H3 |
AIIC application not loaded |
The payment terminal has not been loaded correctly. |
The payment terminal has not been loaded correctly. Call support to arrange repair / replacement. |
H4 |
Error reading the CPT |
Error accessing internal terminal resources. |
|
H5 |
Card not accepted |
terminal not configured to accept this card type. |
If you believe you should be able to accept this card type, note the card type rejected with this error and Contact Support. |
H6 |
Acquirer not found |
The payment terminal has not been loaded correctly. |
The payment terminal has not been loaded correctly. Call support to arrange repair / replacement. |
H7 |
AS2805 field error |
The message from the host contains a field which the terminal does not expect. |
|
H8 |
Global memory error |
The terminal is having memory issues. |
Reboot the terminal. If problem persists, contact support to arrange repair / replacement |
HB |
Error on PP display message |
Error writing to PINpad Display |
Reboot the terminal. If problem persists, contact support to arrange repair / replacement |
HC |
MAC error on host response |
MAC Error on Host Response / Field. |
Retry the transaction. If problem persists, Contact Support. |
HD |
STAN mismatch on host response |
STAN mismatch on host response |
Retry the transaction. If problem persists, Contact Support. |
HE |
AIIC mismatch on host response |
AIIC match failure on host response |
Retry the transaction. If problem persists, Contact Support. |
HF |
CATID mismatch on host response |
CATID match failure on host response |
Retry the transaction. If problem persists, Contact Support. |
HG |
CAID mismatch on host response |
CAID match failure on host response |
Retry the transaction. If problem persists, Contact Support. |
HH |
Unknown host response code received |
The response code returned by the host / acquirer is not known by the terminal. |
|
HJ |
RSA sponsor key mismatch |
Unable to complete RSA Key init due to Sponsor Key validation failure |
|
HK |
Message type mismatch on host response |
Incorrect message type received waiting for Host response |
Retry the transaction. If problem persists, Contact Support. |
HL |
NMIC mismatch on host response |
Incorrect message type received during RSA Initialise |
|
HM |
Sequence error on host response |
Sequence error during File (CPT, SPT, BOPT) download from host |
|
HN |
Sponsor key initialisation required |
Sponsor Key Initialisation is required (In field Init) |
Initiate a Host Logon or Key Initialisation. If problem persists, Contact Support. |
HP |
Acquirer iniitialisation required |
Acquirer initialisation required |
Initiate a Host Logon or Key Initialisation. If problem persists, Contact Support. |
HQ |
Logon required |
Logon required. |
Retry the transaction. If problem persists, Contact Support. |
HR |
Error accessing the EFB FIFO |
Error accessing the EFB FIFO |
|
HS |
Last transaction incomplete |
Last transaction incomplete |
Retry transaction. If problem persists, Contact Support. |
HT |
Can not process cancel in current state |
The cancel has been attempted after a the transaction has progressed passed PIN entry (or card tap if the transaction does not require PIN). |
Allow the transaction to complete and display the result. |
HU |
Invalid / unknown command |
A function has been attempted with the terminal or acquirer application on the terminal does not support. |
Retry the function. If problem persists, Contact Support. |
HV |
Invalid membank |
The command was directed to an incorrect application / memory bank. |
Try function / transaction again. If problem persist, contact Quest. |
HW |
Transaction Unknown |
Transaction Unknown |
|
HX |
AMT NOT VALIDATED | The amount of the transaction was not able to be validated internal to the terminal. |
Reboot the terminal. If problem persists, Contact Support. |
HZ |
No pending offline trans advice messages |
No pending offline trans advice messages stored in terminal |
No further action required. |
J0 |
No pending offline trans advice repeat |
No pending offline repeat messages store in terminal |
No further action required. |
J1 |
No pending reversal |
No reversal messages stored in terminal |
No further action required. |
J2 |
No incomplete transaction |
No incomplete transactions stored in terminal |
No further action required. |
J3 |
Deactivated by kernel |
Interruptible procedure (Offline upload) interrupted for Transaction processing |
No action required. |
J4 |
File not found |
When attempting to dump or delete a file, the specified file does not exist. |
No action required. |
J5 |
|
When attempting to dump or delete a file, the specified action is not allowed on that file. |
No action required. |
J6 |
Card prefix not found in BOPT |
Card prefix has not been configured within the ANZ card file. |
If you believe the card should be accepted on your terminal, Contact Support. |
J7 |
Processing code mismatch on host response |
Incorrect processing code received in Host response |
Retry the transaction. If problem persists, Contact Support. |
JB |
Application activation failed |
terminal application failed to wake. |
|
JC |
Application is activation - status |
terminal application is in the process of activating. |
Wait and try again. |
JD |
AS2805 library error |
A message from the host has been received with unexpected formatted. |
Reboot terminal and attempt a Host Logon or Key Initialisation. If problem persists, Contact Support. |
JE |
Can not process, please try again |
Cannot process the current transaction because a pending logon / reversal could not be cleared. |
Wait 30 seconds and attempt again. If problem persists, Contact Support. |
JF |
Power failure |
Transaction failed due to power failure during the transaction. |
No further action required. |
JK |
Timeout |
Timeout waiting for a response to a 320 request. The PinPad display is the same as CA no response allows more detailed display text. |
|
JL |
Unable to process |
Temporarily unable to process the request. |
Retry the function. If problem persists, Contact Support. |
JM |
Error accessing ESCT |
There was an error attempting to access the ESCT parameters file |
|
JN |
|
The terminal has not been loaded correctly. |
|
JP |
Crypto library function error |
An error has been encountered in a cryptography operation |
|
JR |
Invalid voucher date |
Invalid voucher date. |
Try voucher again with a valid date. |
JS |
Invalid voucher time |
Invalid voucher time |
Try voucher again with a valid time. |
JT |
Voucher daily limit exceeded |
Voucher daily limit exceeded |
No further vouchers allowed that day. |
JU |
Invalid voucher details |
Invalid voucher details |
Correct voucher details and try again. |
JV |
KVC not verified |
KVC not able to be verified |
|
JW |
PPID not verified |
PPID not verified |
|
JX |
Card not accepted |
Card not accepted. |
Contact support if you believe you should be able to accept this card. |
JY |
Transaction not allowed |
Transaction not allowed |
No further action. |
KH |
Error reading card entry message |
Error reading card entry message |
Contact support |
KJ |
INVALID BANK SWITCH |
An unauthorised bank switch was detected. |
|
KK |
EFT DISABLED |
Transaction declined because, EFT has been disabled because some form of security/ownership/location concern. |
|
KW |
Limit check declined |
Limit check failed with an response code that is unsupported in the financial application |
|
KX |
Export function error |
Internal terminal error. |
|
M1 |
No pending pre auths |
Can’t delete pre auths as there are none in the terminal. |
No further action required. |
N0 |
Removal detection |
Unattended device has been removed from its enclosure. |
|
N5 |
Lane swap prohibited |
Lane swap not allowed if pending transactions are stored in the terminal. |
Clear pending transactions and retry. |
N6 |
Rapid API error |
Internal terminal error. |
|
ND |
Contactless entry disabled for this card prefix |
Contactless entry disabled for this card prefix |
Contact support if you believe this is in error. |
NF |
Nexus API error |
Internal terminal error. |
|
NG |
Socket message error |
Invalid length message or message parsing failed on message received on socket. |
Retry transaction. If problem persists, Contact Support. |
NH |
Nothing to cancel |
Cancel received at idle. |
No further action required. |
NJ |
Socket message too large to be buffered |
Networking error. |
Retry transaction. If problem persists, Contact Support. |
NK |
Invalid socket handle |
Networking error. |
Retry transaction. If problem persists, Contact Support. |
NL |
Command not supported |
Function attempted is not support by the terminal. |
|
NP |
TID not configured |
The CAID/CATID supplied in the tender request does not match any of the terminal’s configured values on the Cloud EFTPOS Web Portal. |
Use a CAID/CATID configured on your terminal. |
NT |
Host request field error |
Internal terminal error. |
|
NU |
Invalid SPT prompt index |
Internal terminal error. |
|
NV |
SPT not loaded |
Internal terminal error. |
|
S0 |
The terminal is currently busy performing other processing. It may be logging on "PROCESSING", Reversing "AUTO RECOVERY" or uploading offlines "UPLOADING OFFLINES?SENDING x of xx" |
Wait until the display indicates READY or goes back to the main logo and then try again. |
|
S3 |
Operator timeout |
The terminal has timed out waiting for the operator to verify the signature or get an authorisation number. |
Perform the EFTPOS Tender again. |
S4 |
Card damaged |
The terminal was unable to read the card. |
Perform the EFTPOS Tender again. If problem persists, enter the card number manually (if available on your terminal). If the problem persists regularly across multiple customer’s cards, Contact Support. |
S7 |
Cancelled by POS |
The transaction was cancelled by the operator by hitting the CANCEL EFTPOS key on the Cash Register. |
No further action required. |
S8 |
Cancelled by PINpad |
The transaction was cancelled by the operator or the customer by hitting the CANCEL EFTPOS key on the terminal. |
No further action is required. |
S9 |
Account selection error |
The customer has selected an invalid account for this transaction type too many times. |
Perform the EFTPOS Tender using another card or selecting a different account. |
SA |
Signature mismatch |
The Operator has declined the EFTPOS Tender because the signature given by the customer did not match the signature on the card. |
No further action required. |
SC |
Tran amount exceeds PINpad limit |
The EFTPOS Tender amount exceeds that allowed for this transaction type. |
Perform EFTPOS Tender again with a lesser amount, or a different card. |
SF |
EFB storage full |
The transaction is unable to be completed as the offline storage area is full. |
As the transaction was declined offline. you should first resolve the offline condition. Determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, you may be able to perform a Manual Voucher if your acquirer has provided this facility. |
SG |
|
The PINpad has had a power disturbance, and will not locally approve Refunds until it has successfully logged on to the Bank. |
Perform a host logon. If problem persists, Contact Support. |
SH |
Expired card |
The card used has expired. |
Perform the EFTPOS tender again with a different card or use another form of Tender. |
SK |
Tran amount exceeds the EFB limit |
The link to the bank is down, and the transaction amount exceeds the amount the PINpad can approve. |
Reduce the amount, or use another form of Tender. |
SL |
Lane swap in progress |
The PINpad has been moved to another Lane and needs to upload data to the Bank before it can process transactions. |
Use other forms of Tender until the PINpad display says READY. |
SM |
Reversal pending |
The PINpad cannot allow a transaction until it has sent the reversal to the Bank. |
Retry the EFTPOS Tender or use another form of Tender. |
SN |
Settlement pending |
The PINpad cannot allow a transaction until it has settled with the BANK. |
Retry the EFTPOS Tender, or use another form of Tender. |
SP |
Invalid transaction amount |
A Transaction has been attempted of a zero, or large amount. |
Check the amount and perform the EFTPOS Tender again. |
SQ |
Refund not allowed |
A Refund transaction is not allowed for this card or account type. |
Perform the EFTPOS Tender with a different card or account type. |
SR |
|
Last 4 digits of PAN not entered, rejected or invalid length |
Perform the EFTPOS Tender and be careful to enter the last 4 digits correctly. |
SS |
EFB debit trans not allowed |
The Link to the Bank is down. The PINpad is unable to approve a Debit transaction. |
As the transaction was declined offline. you should first resolve the offline condition. Determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, contact support and seek a different form of tender from your customer. |
ST |
EFB credit trans not allowed |
The Link to the Bank is down. The PINpad is unable to approve a Credit transaction. |
As the transaction was declined offline. you should first resolve the offline condition. Determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, contact support and seek a different form of tender from your customer. |
SX |
PIN change not allowed |
PIN change is not allowed on this card prefix. |
No further action. |
T1 |
Transaction receipt reprint unavailable |
Reprint of the last transaction receipt is not currently available. The last transaction receipt buffer has been cleared. |
If this problem persists over multiple transactions, Contact Support. |
T2 |
Trans type is not allowed |
Transaction type is not allowed for this bank application / merchant. |
Contact support if you believe this is not the correct configuration. |
T3 |
No matching entry in the CPT for this card |
Invalid card. This card cannot be processed by the terminal since it does not appear in the CPAT |
Perform the EFTPOS Tender with a different card or account type. |
T5 |
Generic EFB failure |
Trying to process offline the current transaction has failed, due to the transaction type not falling within the offline category. |
As the transaction was declined offline. you should first resolve the offline condition. Determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, contact support and seek a different form of tender from your customer. |
T7 |
Power failure |
The PP has suffered a Power failure whilst in the middle of a transaction. This will be returned on a reprint of a receipt. (Paymark only) |
Perform the EFTPOS Tender again. |
T8 |
PAN exceeds maximum length |
The manually entered card number exceeds the maximum card number length. |
Perform the EFTPOS Tender and carefully manually enter the card details again.. |
T9 |
Card appears on hot card list |
When a card number appears on the HOT card list. |
No further action. |
TA |
Partial Tender |
Partial tender, with an EFT component is not allowed on this card prefix. |
Retry the transaction using a different tender. |
TE |
Cancel in progress |
You have initiated a command whilst a cancel is in progress. |
Wait until the terminal display says READY or returns to the main logo screen. |
TS |
Link failure |
The terminal was processing a transaction and then received a "resend last trans" admin request. |
Perform the EFTPOS Tender again. If problem persists, Contact Support. |
TU |
ESC Check failed |
The Extended service code from track 2 on the card has restricted EFB Offline processing |
As the refund transaction was declined offline. you should first resolve the offline condition. Determine if you have host connectivity by performing a host logon. If this logon fails, note the response code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, seek a different card which may be accepted offline, or Contact Support. |
TZ |
Application execution error |
Internal terminal Error |
Communication Response Codes
Below are codes returned for network and connectivity errors.
| Response Code | Error Text | Error Explanation | Troubleshooting Steps |
C3 |
EFT Gateway Error |
This error indicates an issue with the Cloud EFTPOS service. |
|
C5 |
No Network Layer / No internet |
Cloud EFTPOS Wedge or terminal does not have internet connectivity. |
Check if your terminal has Wi-Fi or Cellular connection. |
C6 |
Not Authenticated |
Cloud EFTPOS Wedge unable to commission to Cloud EFTPOS due to credentials being incorrect. |
|
C7 |
Bad Link Header |
BAD HDLC Header |
Retry transaction. If problem persists, Contact Support. |
C8 |
Bad Network Error |
BAD CLNP / TPDU Header |
Retry transaction. If problem persists, Contact Support. |
C9 |
No EFT Gateway |
Terminal has internet connectivity, but can not communicate with Cloud EFTPOS. |
Check if your terminal has Wi-Fi or Cellular connectivity. |
CA |
No Response |
No Response From Host. |
Retry transaction. If problem persists, Contact Support. |
CE |
No Comms Gateway |
This error indicates an issue with the Cloud EFTPOS service. |
Cloud EFTPOS Middleware (Wedge) Response Codes
The below codes are returned by the Cloud EFTPOS subsystem.
| Response Code | Error Text | Error Explanation | Troubleshooting Steps |
| E250 | Unknown client, need to Connect first | Wedge has received a message from a client, but has never received a ConnectRequest for this client. | Initiate a ConnectRequest from the client. A restart of the client may be required to force it to send a ConnectRequest message. |
| E252 | Not Authorised - 'reason' (11111-222222-333-4, 72147214) | Wedge has received a failure response to the AuthorisePaymentRequest (normally from the Cloud EFTPOS Web Portal). The reason, Cloud ID and PINpad serial number is included in the text. |
Check the Cloud ID and serial number is valid according to the Cloud EFTPOS Web Portal. |
| E253 | Unable to commission PINpad to terminal |
The Wedge has failed to complete the commission process. Likely cause is due to a configuration mismatch (application list) or link (to PINpad or Cloud) issue. | Check that the list of active applications in PINpad matches the configured applications in the Cloud EFTPOS Web Portal. Check the Cloud EFTPOS Web Portal. |
| E254 | NOT IMPLEMENTED | Wedge received an IPPI request message that is not supported. | Check the format of the request. Check the version of Wedge supports the request that wasn't processed, update Wedge if necessary. |
| E255 | Transaction not found | Used during LastTenderStatusRequest. Indicates that the (Last Tender) supplied PosRef does not match the PosRef of any previous/known TenderRequest. | Check (in the logs) that the terminal is using the same PosRef during transaction recovery as was used in the original TenderRequest. |
| E256 | OUT OF SYNC | The Wedge is in a Tender or trying to cancel a Tender while the PINpad is in an idle state. | Refer to the receipt or Cloud EFTPOS Web Portal if available to determine the Tender result. Contact QPS Helpdesk. |
| E258 | System error | System error during Tender Finalise. | Contact Support. |
| E259 | System error | System error during Sale Begin. | Contact Support. |
| E260 | System error | System error during Sale End. | Contact Support. |
| E261 | System error | System error during Product Totals. | Contact Support. |
| E262 | System error | System error during Status Request. | Contact Support. |
| E263 | System error | System error during Tender Request. | Contact Support. |
| E264 | System error | System error during a Multi-Application function. | Contact Support. |
| E265 | Unhandled error during Admin Request | An Admin Request failed with an unhandled error. | Contact Support. |
| E266 | System Busy | Wedge upgrade in progress | Retry again. If problem persists, Contact Support. |
| E267 | Unable to configure PINpad |
Wedge cannot commission (lane swap) the PINpad with the values supplied by the terminal in the ConnectRequest. |
Check that the bank application list in the ConnectRequest matches the list of active applications in the PINpad. Check if any applications have a stuck host message which is preventing a successful lane swap. |
| E268 | TID Not Configured | The terminal has provided a CAID/CATID in the IPPI request (Tender, Logon, Settlement) that does not match a pre-configured CAID/CATID. | Compare the CAID/CATID in the request against the configured CAID/CATID values in Cloud EFTPOS Web Portal (CEWP). Correct configuration in CEWP. |
| E270 | Failed to download file | This is when wedge fails to download a file from download URL to its local folder (applicable in case of MTP file copy/wedge download) | Action depends on the failure reason provided as an additional details in the error text |
| E271 | Failed to download file due to reason 'Received a file for MTP copy but PINpad does not support MTP | Failed to download file due to reason 'Received a file for MTP copy but PINpad does not support MTP | Check file configuration for PT in CEWP. |
| E272 | Failed to download file due to hash mismatch | Failed to download file due to hash mismatch (applicable in case of MTP file copy/wedge download) | Failed to download file due to hash mismatch (applicable in case of MTP file copy/wedge download) |
| E273 | failed to download the file due hash calculation error
|
failed to download the file due hash calculation error (applicable in case of MTP file copy/wedge download)
|
Action depends on the failure reason provided as an additional details in the error text |
| E2003 | SYSTEM BUSY | The EFT sub-system is currently busy processing another request. | Wait for the sub-system to return to the idle state and try the function again. If the problem persists, restart EPP |
| E2100 | PINPAD COMMUNICATIONS TIMEOUT | There has been an error communicating with the PINpad. | Possible causes include no COM port available, incorrect COM port selected, invalid Baud Rate configured, PINpad unplugged, faulty cable, faulty PINpad. |
| E2101 | PINPAD HARDWARE FAILURE | The PINpad has failed. | This error is no longer reported. |
| E2102 | INVALID PINPAD TYPE | EftposPlus is incorrectly configured. | This error is no longer reported. |
| E2104 | UNABLE TO CREATE PINPAD MESSAGE | There has been an internal error within the PINpad driver of EftposPlus. | Escalate the issue immediately. |
| E2107 | PINPAD DEVICE ERROR | A PINpad error has occurred. | Wedge is unaware of the response code supplied by the PINPad.
It is most likely that a new response code has been added to the PINpad. Contact Support. |
| E2110 | PLD TX NOT STARTED | Pinpad pld'd (rebooted) prior to the start trans going to bank application | Retry transaction. If problem persists, Contact Support. |