Error Codes
Host Error Codes
These errors are returned by the acquiring host!Error Code | Error Text |
00 | APPROVED |
01 | REFER TO CARD ISSUER |
02 | REFER TO CARD ISSUER |
03 | INVALID MERCHANT |
04 | PICK UP CARD |
05 | DO NOT HONOUR / CVV VALIDATION ERROR |
06 | ERROR |
07 | PICK UP CARD |
08 | APPROVED WITH SIGNATRUE |
HH 09 | REQUEST IN PROGRESS |
11 | APPROVED VIP |
12 | INVALID TRANSACTION |
13 | INVALID AMOUNT |
14 | INVALID CARD NUMBER |
15 | NO SUCH ISSUER |
19 | RE-ENTER TRANSACTION |
21 | NO ACTION TAKEN |
23 | UNACCEPTABLE FEE |
24 | UPDATE NOT SUPPORTED |
25 | UNABLE TO LOCATE FILE RECORD |
26 | DUPLICATE FILE RECORD |
27 | UPDATE FILE EDIT ERROR |
28 | UPDATE FILE LOCKED OUT |
29 | FILE UPDATE UNSUCCESSFUL |
30 | FORMAT ERROR |
31 | BANK NOT SUPPORTED BY SWITCH |
HH 32 | PARTIAL COMPLETION |
33 | EXPIRED CARD |
34 | SUSPECTED FRAUD |
35 | CONTACT ACQUIRER |
36 | RESTRICTED CARD |
37 | CALL ACQUIRER |
38 | PIN TRIES EXCEEDED |
39 | NO CR/CHQ/SAV/INVESTMENT/UNIVERSAL ACCOUNT |
41 | CALL CARD ISSUER |
43 | STOLEN PICK UP CARD |
51 | INSUFFICIENT FUNDS |
54 | EXPIRED CARD |
55 | INCORRECT PIN |
56 | NO CARD RECORD |
57 | TRANSACTION NOT PERMITTED FOR CARD |
58 | TRANSACTION NOT PERMITTED FOR TERMINAL |
59 | SUSPECTED FRAUD |
60 | CALL ACQUIRER |
61 | LIMIT EXCEED |
62 | RESTRICTED CARD |
63 | SECURITY VIOLATION |
65 | TAP UNAVAILABLE |
66 | CALL ACQUIRER |
68 | LATE RESPONSE |
HH 67 | HARD CAPTURE |
75 | PIN TRIES EXCEEDED |
90 | CUT OFF IN PROGRESS |
91 | ISSUER UNAVAILABLE |
92 | CANNOT ROUTE TO ACQUIRER |
93 | ILLEGAL TRANSACTION |
94 | DUPLICATE TRANSMISSION |
95 | SETTLEMENT FAILED |
96 | SYSTEM ERROR / SUSPECTED MALFUNCTION |
97 | SETTLEMENT COMPLETED |
98 | SYSTEM / MAC ERROR |
Terminal Error Codes
Below is a list of error codes the terminal may return.Error Code | Error Text | Error Explaination | Troubleshooting Steps |
E0 |
Generic EMV application error |
Generic EMV error |
Contact support. |
E1 |
Card error |
EMV level 1 error, refer to EMV Error Codes tab for meaning of nnn |
Contact support. |
E2 |
Processing error |
EMV level 2 error, refer to EMV Error Codes tab for meaning of nnn |
Contact support. |
E3 |
Not accepted |
No terminal supported AID on the ICC or "service not allowed" returned by the ICC in theGEN AC response |
Card is not accepted due to configuration of the terminal. If you believe the card type being used should be accept, contact support. Otherwise, as the customer to try with a different card. |
E4 |
Declined by the ICC (ICC returned a AAC) |
Card declined the transaction by returning an AAC in the GEN AC response |
Retry transaction. If problem persists, contact support. |
E5 |
Declined by the issuer |
Reserved for future use |
Reserved for future use. |
EA |
Card removed during transaction |
Card was removed prematurely |
Ensure card is left in insert slot for duration of transaction until ‘Approved’ or ‘Declined’ appears on the screen of the terminal. If this error occurs repeatedly with different cards, you may have an issue with your insert reader on your terminal. Contact support who will investigate to determine if your terminal requires repair / replacement. |
EB |
TLV / EMV library error |
EMV TLV library error |
Contact support. |
EC |
ICC Read / Data error |
Reserved for future use |
Reserved for future use |
ED |
EMV export error |
EMV Module export function call failed |
Reserved for future use |
EE |
ICC chip card blocked |
Card reported card blocked |
Request customer use a different card. |
EF |
Remove card |
Card must be removed due to EMV error. |
Contact support. |
EG |
Fallback not permitted |
Fallback to MSR after failed ICC read is not permitted on this card prefix |
Request customer use a different card. |
EH |
Already declined |
Fallback to MSR after previous transaction on this card was declined by the ICC is not permitted |
Request customer use a different card. |
EJ |
Card not accpeted |
Card prefix is flagged in the MAST as not accepted |
Request customer use a different card. |
EK |
Cards do not match |
Fallback to MSR / fallforward to EMV, the 2 swipes were from different cards |
Ensure the customer uses the same card for the duration of their interaction with the terminal. |
ER |
EMV level 1 reset error, model C / D |
EMV level 1 error returned by emvReset() |
Contact support. |
ES |
EMV level 1 command error, model C / D |
EMV level 1 error returned by emvCommand() |
Contact support. |
ET |
EMV level 1 reset error, model X |
EMV level 1 error returned by emvReset() |
Contact support. |
EU |
EMV level 1 command error, model X |
EMV level 1 error returned by emvCommand() |
Contact support. |
Y1 |
EMV trans approved offline |
Approved by the terminal offline without an online attempt |
Transaction approved. Provide customer with the goods or services. |
Y3 |
EMV trans approved offline after online failure |
Approved by the terminal offline after failed attempt to go online |
Transaction approved. Provide customer with the goods or services. |
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 error 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 error 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. |
Contact support. |
FC |
Contactless AID lookup error |
A contactless read error has occurred. |
Contact support. |
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. |
Contact support. |
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. |
Contact support. |
H8 |
Global memory error |
The terminal is having memory issues. |
Reboot the terminal. If problem persists, contact support to arrange repair / replacement |
H9 |
Error transmitting POS message |
Error sending any type of message to the POS during function |
Retry transaction. If problem persists, reboot terminal and POS. If problem still continues, contact support. |
HA |
Display response timeout |
Error sending POS Display request/receiving response |
Retry transaction. If problem persists, reboot terminal and POS. If problem still continues, contact support. |
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. |
HF |
Invalid CATID supplied by the POS |
POS supplying invalid CATID in transaction request. |
Check if your POS supports sending CATID in transaction request. If it does, ensure it is correct. If it doesn’t, contact support. |
HG |
CAID mismatch on host response |
CAID match failure on host response |
Retry the transaction. If problem persists, contact support. |
HG |
Invalid CAID supplied by the POS |
POS supplying invalid CAID in transaction request. |
Check if your POS supports sending CAID in transaction request. If it does, ensure it is correct. If it doesn’t, contact support. |
HH |
Unknown host response code received |
The response code returned by the host / acquirer is not known by the terminal. |
Contact support. |
HJ |
RSA sponsor key mismatch |
Unable to complete RSA Key init due to Sponsor Key validation failure |
Contact support. |
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 |
Contact support. |
HM |
Sequence error on host response |
Sequence error during File (CPT, SPT, BOPT) download from host |
Contact support. |
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 |
Contact support. |
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 |
Contact support. |
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. |
Contact support. |
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 POS display text. |
Contact support. |
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 |
Contact support. |
JN |
|
The terminal has not been loaded correctly. |
Contact support. |
JO |
Invalid response received from the POS |
Invalid response received from the POS. |
Contact support. |
JP |
Crypto library function error |
An error has been encountered in a cryptography operation |
Contact support. |
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 |
Contact support. |
JW |
PPID not verified |
PPID not verified |
Contact support. |
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. |
JZ |
Pre auth storage full |
Pre auth storage within the terminal is full |
No further pre-auths allowed until a) previous pre-auths are voided; or b) previous pre-auths are completed. |
KG |
EFB daily refund limit exceeded |
EFB daily refund limit exceeded |
No further offline refunds that calendar day. As the refund was declined offline. you should first determine if you have host connectivity by performing a host logon. If this logon fails, note the error 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. |
KH |
Error reading card entry message |
Error reading card entry message |
Contact support |
KJ |
INVALID BANK SWITCH |
An unauthorised bank switch was detected. |
Contact support. |
KK |
EFT DISABLED |
Transaction declined because, EFT has been disabled because some form of security/ownership/location concern.. |
Contact support. |
KL |
Signature required - declined |
PIN was required and terminal did not support PIN for this card type whilst offline. |
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 error 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. |
KM |
Invalid pre swipe amount |
A card was pre swiped/ inserted and the amounts in the start trans were invalid, probably because a tip or cashout was entered on the PINpad then also passed from the pos. |
Check implementation with your POS provider. |
KN |
Invalid pre swipe transaction type |
A card was pre swiped/ inserted and the transaction type was not purchase. Pre swipe is only available for purchase. |
Contact your POS provider. |
KP |
Invalid pre swipe route ID |
A card was pre swiped/ inserted and the route ID in the start trans was not the same route ID as in the pre swipe request. |
Contact your POS provider. |
KQ |
Tranasaction cashed |
Transaction has been cashed |
No further action required. |
KR |
Transaction voided |
Transaction has been voided |
No further action required. |
KS |
Invalid cashout amount |
The cashout amount is not a valid increment |
Typically cashout must be an increment of $0.05. Retry with a cashout amount which is a multiple of $0.05. |
KT |
Invalid product format |
The format of the Trans-Product request message is incorrect. |
Contact your POS supplier |
KU |
Surcharge mismatch |
The surcharge returned from the POS does nor match the surcharge calculated in the PINpad |
Contact your POS supplier |
KV |
Loyalty point earn only, pay by cash |
Customer selected earn only and payed by cash. |
No further action required. |
KW |
Limit check declined |
Limit check failed with an error code that is unsupported in the financial application |
Contact support. |
KX |
Export function error |
Internal terminal error. |
Contact support. |
KY |
Loyalty card not processed |
Loyalty card is not processed due to invalid card number or card not accepted. |
Try another card. |
KZ |
Loyalty card swiped |
Transaction was declined because a loyalty card was used in conjunction with a payment card which can’t be used in conjunction with loyalty. |
Pay with another card or do not use loyalty card. |
M1 |
No prending pre auths |
Can’t delete pre auths as there are none in the terminal. |
No further action required. |
M2 |
Incorrect Passcode |
The passcode entered to allow manual entry was incorrect. |
Try again and enter the correct Merchant Passcode. Log onto Cloud EFTPOS and update Merchant Passcode if it has been forgotten. |
M3 |
Exceeds Preauth Amount |
Completion transaction amount exceeds the pre-auth limit (+tolerance set in payment app). |
Check transaction amount and re-submit completion. If problem persists, contact support. |
N0 |
Removal detection |
Unattended device has been removed from its enclosure. |
Contact support. |
N1 |
Registration mismatch |
The vehicle registration number attached to the card was not verified by the operator |
If operator has made a mistake, attempt transaction again. |
N2 |
Card already in use |
Attempt to process a pre auth on a debit card where there is already a buffered pre auth on the same debit card |
Void the original pre-auth and submit a new pre-auth which totals the amount required. |
N3 |
Invalid card type |
Card type restriction applied by the POS in the start trans and a different card type was presented |
Ask the customer to use a different card. |
N4 |
Cash exceeds limit |
Not in use. |
Not in use. |
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. |
Contact support. |
N7 |
CAID not configured |
The PINpad has attempted a transaction too quickly before it has synced with the POS. |
Perform a host logon and try again. |
N8 |
CATID not configured |
The PINpad has attempted a transaction too quickly before it has synced with the POS. |
Perform a host logon and try again. |
N9 |
Manual entry not permitted |
Manual entry not permitted. |
Contact support if you wish to enable the manual entry feature. |
NA |
Manual entry disabled for this card prefix |
Manual entry disabled for this card prefix |
Some card types (ie. eftpos only cards) do not allow manual entry. Ask the customer to provide another card. |
NB |
Manual entry disabled for this transaction type |
Manual entry disabled for this transaction type |
Contact support if you believe this is in error. |
NC |
Insert entry disabled for this card prefix |
Insert entry disabled for this card prefix |
Contact support if you believe this is in 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. |
NE |
Invalid parameter on POS API request |
Invalid parameter on POS API request |
Contact POS provider. |
NF |
Nexus API error |
Internal terminal error. |
Contact support. |
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. |
Contact support. |
NM |
Low Battery |
Returned by an AP3 if there is not enough battery to perform downloads |
Charge the AP3 unit. |
NN |
Invalid Message After PreSwipe Card Tap |
Returned by the AP3 when a card has been tapped in PreSwipe mode but it received a PreSwipe message instead of a Start Trans request |
Contact POS provider. |
NP |
TID not configured |
The CAID/CATID supplied in the POS 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. |
NQ |
Restricted items |
Transaction has been declined as basket contains items which are restricted from being purchased on a CDC card |
Remove restricted items from basket or pay with different card. |
NR |
No PreAuth storage |
Internal terminal error. |
Contact support. |
NS |
PreAuth storage full |
Internal terminal error. |
Contact support. |
NT |
Host request field error |
Internal terminal error. |
Contact support. |
NU |
Invalid SPT prompt index |
Internal terminal error. |
Contact support. |
NV |
SPT not loaded |
Internal terminal error. |
Contact support. |
NW |
MIDs / TIDs in use |
Fuel Pre Auth Only: The configured MIDs and TIDs are all in use with buffered pre auth transactions. |
Free up MIDs and TIDs by processing completions or allocate more MIDs and TIDs. |
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. |
|
S1 |
Print response timeout |
There was an error printing the receipt. The transaction has not been completed successfully. |
Remedy the error (Check the printer has paper, is turned on etc) and re-tender. If problem persist, contact support. |
S1-01 |
Generic printer error |
There was an error printing the receipt. The transaction has not been completed successfully. |
Remedy the error (Check the printer has paper, is turned on etc) and re-tender. If problem persist, contact support. |
S1-02 |
Out of paper |
There was an error printing the receipt. The transaction has not been completed successfully. |
Remedy the error by checking the printer has paper and the paper roll is oriented correct, then re-tender. |
S1-03 |
Printer offline |
There was an error printing the receipt. The transaction has not been completed successfully. |
Check that the printer is turned on and connected, then retender. If problem persist, contact support. |
S1-04 |
No printer |
There was an error printing the receipt as no printer is available. The transaction has not been completed successfully. |
Connect a printer and then retender. |
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. |
S5 |
Invalid card number - manual entry |
The Card number that was keyed in by the operator is incorrect. |
Perform the EFTPOS Tender again, being careful to enter the card number correctly |
S6 |
Invalid expiry date - manual entry |
The Expiry date that was keyed in by the operator is not Valid. |
Perform the EFTPOS Tender again, being careful to enter the expiry date correctly |
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 (Standalone only). |
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. |
SB |
Manual entry not allowed on this tran type |
The operator has key entered the card number for an account type which requires the card to be successfully swiped on the PINpad. |
Swipe the card or ask the customer for a different card. |
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. |
SD |
Invalid auth number entered |
The Authorisation number entered by the operator is not valid. |
Ensure the Authorisation number is entered correctly. |
SE |
Cashout not allowed |
Cashout is not allowed for this transaction type. Select a different account, or use a different card. Cashout is not allowed for refund transactions. |
No further action required. |
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 error 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. |
SJ |
No EFB cashout |
The link to the Bank is down. The PINpad cannot approve a Transaction which includes Cashout. |
Retender without Cashout. |
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 error 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 error 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. |
SU |
EFB refund trans not allowed |
The Link to the Bank is down. The PINpad is unable to approve a Refund transaction. Fix the condition causing the Offline and retry the transaction or retender using a different Tender. |
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 error 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. |
SV |
Card limit exceeded |
POS rejected this card for this amount - using the Account Select message to the POS. |
This is normal operation should your POS have implemented limits. Contact your POS supplier. |
SW |
Pre auth not allowed |
Pre Authorisation support not enabled. |
Contact support if you believe this is not the correct configuration. |
SX |
PIN change not allowed |
PIN change is not allowed on this card prefix. |
No further action. |
SY |
Product totals pending |
terminal has no received the total products before the timeout has expired. |
Contact your POS supplier. |
SZ |
EFB trans already stored |
EFB transaction is already stored for this card. |
Void the original pre-auth and submit a new pre-auth which totals the amount required. |
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. |
T4 |
Void details mismatch |
Trying to void the previous transaction failed due to previous transaction detail mismatch from POS. |
Perform the EFTPOS Tender and ensure transaction details match the previous transaction. |
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 error 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. |
T6 |
Invalid tip details |
Invalid details of the original transaction has supplied to the terminal when trying to add a Tip. |
Perform the EFTPOS Tender and ensure transaction details match the original transaction you are adding a tip to. |
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, with an EFT component is not allowed on this card prefix. |
Retry the transaction using a different tender. |
TB |
Trans amount exceeds the EFB refund limit |
Trans amount exceeds the EFB refund limit. |
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 error code and investigate to resolve the underlying issue causing your terminal to be offline. If the offline condition can’t be resolved, contact support. |
TC |
Training mode not allowed |
The POS has submitted the training mode flag when starting the transaction and this terminal does not support training mode. |
Contact you POS supplier if training mode was not intentional. Contact support if you wish Training mode to be enabled on your terminal. |
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. |
TT |
ICC Field Error |
The chip card being read returned invalid data. |
Perform the EFTPOS Tender again using a different card. 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 error 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. |
TW |
Void not required |
Attempt to void a transaction that was declined |
No further action. |
TX |
Void already performed |
The void has already been completed |
No further action. |
TY |
POS Requested Reversal |
POS has requested reversal via Transack Reverse |
No further action. |
TZ |
Application execution error |
Internal terminal Error |
Contact support. |
Communication Error Codes
Below are codes returned for network and connectivity errors.Error Code | Error Text | Error Explanation | Troubleshooting Steps |
C3 |
EFT Gateway Error |
This error indicates an issue with the Cloud EFTPOS service. |
Contact support. |
C5 |
No Network Layer / No internet |
Cloud EFTPOS Wedge or terminal does not have internet connectivity. |
Wedge: Confirm your POS PC has network and internet connectivity to https://*.cloudeftpos.com. terminal: Check if your terminal has WiFi, Cellular or Ethernet connectivity (depending on what communication methods should be available to you). |
C6 |
Not Authenticated |
Cloud EFTPOS Wedge or terminal unable to commission to Cloud EFTPOS due to credentials being incorrect. |
Confirm you have configured the correct Cloud ID into Cloud EFTPOS Wedge configuration (C:\ProgramData\Quest Payment Systems\Wedge IPPI\etc\quest\ippi\qpswedge.pos.config) Confirm your terminal has been correctly configured in Cloud EFTPOS and verify the Cloud ID. |
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 |
Cloud EFTPOS Wedge or terminal has internet connectivity, but can not communicate with Cloud EFTPOS. |
Wedge: Confirm your POS PC has network and internet connectivity to https://*.cloudeftpos.com. terminal: Check if your terminal has WiFi, Cellular or Ethernet connectivity (depending on what communication methods should be available to you). Confirm that your network allows internet connectivity to https://*.cloudeftpos.com. If you have confirmed both of the above, contact support. |
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. |
Contact support. |
Cloud EFTPOS Middleware (Wedge) Response Codes
The below codes are returned by the Cloud EFTPOS subsystem and can apply to both Standalone and Integrated modes.Error Code | Error Text | Error Explanation | Troubleshooting Steps |
E250 | Unknown client, need to Connect first | Wedge has received a message from a client (POS or Cloud Explorer), 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. If using Cloud Explorer, select 'File - Logoff', 'File - Logon'. |
E251 | PosID mismatch | The 'Pos ID' field in the request from the POS does not match a Pos ID supplied during the commission process. | Check the Pos ID (in Cloud Web Portal) against the Pos ID of the POS. May need to retrieve the Wedge log if you can't determine what Pos ID value is being sent from the POS. Note that some systems do not authorise to the Cloud Web Portal. |
E252 | Not Authorised - 'reason' (11111-222222-333-4, 72147214) | Wedge has received a failure response to the AuthorisePaymentRequest (normally from Cloud 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 Cloud 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. Note: In Wedge 2.6.2400, all commission errors were reported as E3210. |
Check that the list of active applications in PINpad matches the configured applications in the Cloud Web Portal. Check Wedge config file, Cloud Web Portal, link PINpad - Wedge, link Wedge - Cloud 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 POS is using the same PosRef during transaction recovery as was used in the original TenderRequest. |
E256 | OUT OF SYNC | The POS/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, supply the Wedge log if investigation is required. |
E257 | Invalid Admin Request | The PINpad Admin Request is not valid. | The POS if faulty. Contact your POS Helpdesk. |
E258 | System error | System error during Tender Finalise. | Contact support. Supply Wedge log file for further investigation. |
E259 | System error | System error during Sale Begin. | Contact support. Supply Wedge log file for further investigation. |
E260 | System error | System error during Sale End. | Contact support. Supply Wedge log file for further investigation. |
E261 | System error | System error during Product Totals. | Contact support. Supply Wedge log file for further investigation. |
E262 | System error | System error during Status Request. | Contact support. Supply Wedge log file for further investigation. |
E263 | System error | System error during Tender Request. | Contact support. Supply Wedge log file for further investigation. |
E264 | System error | System error during a Multi-Application function. | Contact support. Supply Wedge log file for further investigation. |
E265 | Unhandled error during Admin Request | An Admin Request failed with an unhandled error. | Contact support. Supply Wedge log file for further investigation. |
E266 | System Busy | Wedge upgrade in progress | Retry again. If problem persists, contact support. |
E267 | Unable to configure PINpad |
Wedge cannot configure (lane swap) the PINpad with the values supplied by the POS 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 POS 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 the POS or CEWP. |
E269 | MISSING REQUIRED TID | This is a single merchant POS, but the lane is configured for multi-merchant. The POS did not supply a CAID/CATID in the Tender Request, but this is required when the terminal is configured for multi-merchant (multiple TIDs) |
Most likely cause is that CEWP has been configured with multiple TIDs (CAID/CATID pairs), but the POS is in single TID mode or doesn't support multiple TIDs. Remove additional TIDs in CEWP (check first before deleting) then either wait for the next terminalUpdate or do 'Check for updates' on the POS if this is available, or restart wedge. |
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. |
E2103 | UNABLE TO OPEN PINPAD COM PORT | EftposPlus or Wedge cannot open the specified COM port to communicate with the PINpad. EFT will be unavailable until this is resolved. Possible causes include incorrect configuration or a hardware conflict. | Try restarting the machine. Check the port configuration of other devices connected to the machine for a conflict. |
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 error code supplied by the PINPad.
It is most likely that a new error 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. |
E2112 | CAN'T OPEN CARD READER COM PORT | The com port for the card reader cannot be opened. | Check Wedge configuration (qpswedge.pos.config) and ensure it is using the same comm port as displayed in device manager. |