|
These errors are returned by the acquiring host!
|
| Error Code | Error Text | Troubleshooting Steps |
| E0 | Generic EMV application error | Contact support. |
| E1 | Card error | Contact support. |
| E2 | Processing error | Contact support. |
| E3 | Not accepted | 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) | Retry transaction. If problem persists, contact support. |
| E5 | Declined by the issuer | Reserved for future use. |
| EA | Card removed during transaction | 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 | Contact support. |
| EC | ICC Read / Data error | Reserved for future use |
| ED | EMV export error | Reserved for future use |
| EE | ICC chip card blocked | Request customer use a different card. |
| EF | Remove card | Contact support. |
| EG | Fallback not permitted | Request customer use a different card. |
| EH | Already declined | Request customer use a different card. |
| EJ | Card not accpeted | Request customer use a different card. |
| EK | Cards do not match | 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 | Contact support. |
| ES | EMV level 1 command error, model C / D | Contact support. |
| ET | EMV level 1 reset error, model X | Contact support. |
| EU | EMV level 1 command error, model X | Contact support. |
| Y1 | EMV trans approved offline | Transaction approved. Provide customer with the goods or services. |
| Y3 | EMV trans approved offline after online failure | Transaction approved. Provide customer with the goods or services. |
| Z1 | EMV trans declined 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. |
| Z3 | EMV trans declined offline after online failure | 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 | Advise the customer to try another card. |
| Z5 | Use Physical Card | Advise the customer to use a physical card, not a mobile phone or wearable. |
| F0 | Generic contactless application error | Retry the transaction. If problems persist on more than one card, contact support. |
| F1 | Bad contactless protocol | Retry the transaction. If problems persist on more than one card, contact support. |
| F2 | Contactless Manufacturer Init Requried | Retry the transaction. If problems persist on more than one card, contact support. |
| F3 | Contactless reader key init required | Retry the transaction. If problems persist on more than one card, contact support. |
| F4 | Contactless reader response timeount | Retry the transaction. If problems persist on more than one card, contact support. |
| F5 | Invalid contactless reader response format | Retry the transaction. If problems persist on more than one card, contact support. |
| F6 | Invalid contactless reader response code | Retry the transaction. If problems persist on more than one card, contact support. |
| F7 | Contactless reader initialisation error | Retry the transaction. If problems persist on more than one card, contact support. |
| F8 | Tap error | Retry the transaction. If problems persist on more than one card, contact support. |
| F9 | Try another entry mode | Retry the transaction. If problems persist on more than one card, contact support. |
| FA | Try another card | Retry the transaction on a different card. If problems persist, contact support. |
| FB | No contactless AID record found | Contact support. |
| FC | Contactless AID lookup error | Contact support. |
| FD | Declined by contactless reader | Retry the transaction on a different card. If problems persist, contact support. |
| FE | Offline data authentication failure | 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 | Retry the transaction. If problems persist, contact support. |
| FK | Ctls Tags file access error | 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 | Retry the transaction on a different card. If problems persist, contact support. |
| FP | CVM Error | Retry the transaction on a different card. If problems persist, contact support. |
| FQ | Card Action Analysis Error | Retry the transaction on a different card. If problems persist, contact support. |
| FR | terminal Does not have contact EMV | Retry the transaction on a different card. If problems persist, contact support. |
| FS | Unsupported Card | 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 | Retry the transaction on a different card. If problems persist, contact support. |
| H0 | Manufacturer initialisation required | 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. Call support to arrange repair / replacement. |
| H2 | MAST lookup error | 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. Call support to arrange repair / replacement. |
| H4 | Error reading the CPT | Contact support. |
| H5 | Card not accepted | 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. Call support to arrange repair / replacement. |
| H7 | AS2805 field error | Contact support. |
| H8 | Global memory error | Reboot the terminal. If problem persists, contact support to arrange repair / replacement |
| H9 | Error transmitting POS message | Retry transaction. If problem persists, reboot terminal and POS. If problem still continues, contact support. |
| HA | Display response timeout | Retry transaction. If problem persists, reboot terminal and POS. If problem still continues, contact support. |
| HB | Error on PP display message | Reboot the terminal. If problem persists, contact support to arrange repair / replacement |
| HC | MAC error on host response | Retry the transaction. If problem persists, contact support. |
| HD | STAN mismatch on host response | Retry the transaction. If problem persists, contact support. |
| HE | AIIC mismatch on host response | Retry the transaction. If problem persists, contact support. |
| HF | CATID mismatch on host response | Retry the transaction. If problem persists, contact support. |
| HF | Invalid CATID supplied by the POS | 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 | Retry the transaction. If problem persists, contact support. |
| HG | Invalid CAID supplied by the POS | 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 | Contact support. |
| HJ | RSA sponsor key mismatch | Contact support. |
| HK | Message type mismatch on host response | Retry the transaction. If problem persists, contact support. |
| HL | NMIC mismatch on host response | Contact support. |
| HM | Sequence error on host response | Contact support. |
| HN | Sponsor key initialisation required | Initiate a Host Logon or Key Initialisation. If problem persists, contact support. |
| HP | Acquirer iniitialisation required | Initiate a Host Logon or Key Initialisation. If problem persists, contact support. |
| HQ | Logon required | Retry the transaction. If problem persists, contact support. |
| HR | Error accessing the EFB FIFO | Contact support. |
| HS | Last transaction incomplete | Retry transaction. If problem persists, contact support. |
| HT | Can not process cancel in current state | Allow the transaction to complete and display the result. |
| HU | Invalid / unknown command | Retry the function. If problem persists, contact support. |
| HV | Invalid membank | Try function / transaction again. If problem persist, contact Quest. |
| HW | Transaction Unknown | Contact support. |
| HX | AMT NOT VALIDATED | Reboot the terminal. If problem persists, contact support. |
| HZ | No pending offline trans advice messages | No further action required. |
| J0 | No pending offline trans advice repeat | No further action required. |
| J1 | No pending reversal | No further action required. |
| J2 | No incomplete transaction | No further action required. |
| J3 | Deactivated by kernel | No action required. |
| J4 | File not found | No action required. |
| J5 | No action required. | |
| J6 | Card prefix not found in BOPT | If you believe the card should be accepted on your terminal, contact support. |
| J7 | Processing code mismatch on host response | Retry the transaction. If problem persists, contact support. |
| JB | Application activation failed | Contact support. |
| JC | Application is activation - status | Wait and try again. |
| JD | AS2805 library error | Reboot terminal and attempt a Host Logon or Key Initialisation. If problem persists, contact support. |
| JE | Can not process, please try again | Wait 30 seconds and attempt again. If problem persists, contact support. |
| JF | Power failure | No further action required. |
| JK | Timeout | Contact support. |
| JL | Unable to process | Retry the function. If problem persists, contact support. |
| JM | Error accessing ESCT | Contact support. |
| JN | Contact support. | |
| JO | Invalid response received from the POS | Contact support. |
| JP | Crypto library function error | Contact support. |
| JR | Invalid voucher date | Try voucher again with a valid date. |
| JS | Invalid voucher time | Try voucher again with a valid time. |
| JT | Voucher daily limit exceeded | No further vouchers allowed that day. |
| JU | Invalid voucher details | Correct voucher details and try again. |
| JV | KVC not verified | Contact support. |
| JW | PPID not verified | Contact support. |
| JX | Card not accepted | Contact support if you believe you should be able to accept this card. |
| JY | Transaction not allowed | No further action. |
| JZ | Pre auth storage 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 | 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 | Contact support |
| KJ | INVALID BANK SWITCH | Contact support. |
| KK | EFT DISABLED | Contact support. |
| KL | Signature required - declined | 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 | Check implementation with your POS provider. |
| KN | Invalid pre swipe transaction type | Contact your POS provider. |
| KP | Invalid pre swipe route ID | Contact your POS provider. |
| KQ | Tranasaction cashed | No further action required. |
| KR | Transaction voided | No further action required. |
| KS | Invalid cashout amount | 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 | Contact your POS supplier |
| KU | Surcharge mismatch | Contact your POS supplier |
| KV | Loyalty point earn only, pay by cash | No further action required. |
| KW | Limit check declined | Contact support. |
| KX | Export function error | Contact support. |
| KY | Loyalty card not processed | Try another card. |
| KZ | Loyalty card swiped | Pay with another card or do not use loyalty card. |
| M1 | No prending pre auths | No further action required. |
| M2 | Incorrect Passcode | 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 | Check transaction amount and re-submit completion. If problem persists, contact support. |
| N0 | Removal detection | Contact support. |
| N1 | Registration mismatch | If operator has made a mistake, attempt transaction again. |
| N2 | Card already in use | Void the original pre-auth and submit a new pre-auth which totals the amount required. |
| N3 | Invalid card type | Ask the customer to use a different card. |
| N4 | Cash exceeds limit | Not in use. |
| N5 | Lane swap prohibited | Clear pending transactions and retry. |
| N6 | Rapid API error | Contact support. |
| N7 | CAID not configured | Perform a host logon and try again. |
| N8 | CATID not configured | Perform a host logon and try again. |
| N9 | Manual entry not permitted | Contact support if you wish to enable the manual entry feature. |
| NA | 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 | Contact support if you believe this is in error. |
| NC | Insert entry disabled for this card prefix | Contact support if you believe this is in error. |
| ND | Contactless entry disabled for this card prefix | Contact support if you believe this is in error. |
| NE | Invalid parameter on POS API request | Contact POS provider. |
| NF | Nexus API error | Contact support. |
| NG | Socket message error | Retry transaction. If problem persists, contact support. |
| NH | Nothing to cancel | No further action required. |
| NJ | Socket message too large to be buffered | Retry transaction. If problem persists, contact support. |
| NK | Invalid socket handle | Retry transaction. If problem persists, contact support. |
| NL | Command not supported | Contact support. |
| NM | Low Battery | Charge the AP3 unit. |
| NN | Invalid Message After PreSwipe Card Tap | Contact POS provider. |
| NP | TID not configured | Use a CAID/CATID configured on your terminal. |
| NQ | Restricted items | Remove restricted items from basket or pay with different card. |
| NR | No PreAuth storage | Contact support. |
| NS | PreAuth storage full | Contact support. |
| NT | Host request field error | Contact support. |
| NU | Invalid SPT prompt index | Contact support. |
| NV | SPT not loaded | Contact support. |
| NW | MIDs / TIDs in use | Free up MIDs and TIDs by processing completions or allocate more MIDs and TIDs. |
| S0 | ||
| 1PINpad Busy | 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" | |
| S1 | Print response timeout | 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 | 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 | Remedy the error by checking the printer has paper and the paper roll is oriented correct, then re-tender. |
| S1-03 | Printer offline | Check that the printer is turned on and connected, then retender. If problem persist, contact support. |
| S1-04 | No printer | Connect a printer and then retender. |
| S3 | Operator timeout | Perform the EFTPOS Tender again. |
| S4 | Card damaged | 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 | Perform the EFTPOS Tender again, being careful to enter the card number correctly |
| S6 | Invalid expiry date - manual entry | Perform the EFTPOS Tender again, being careful to enter the expiry date correctly |
| S7 | Cancelled by POS | No further action required. |
| S8 | Cancelled by PINpad | No further action is required. |
| S9 | Account selection error | Perform the EFTPOS Tender using another card or selecting a different account. |
| SA | Signature mismatch | No further action required. |
| SB | Manual entry not allowed on this tran type | Swipe the card or ask the customer for a different card. |
| SC | Tran amount exceeds PINpad limit | Perform EFTPOS Tender again with a lesser amount, or a different card. |
| SD | Invalid auth number entered | Ensure the Authorisation number is entered correctly. |
| SE | Cashout not allowed | No further action required. |
| SF | EFB storage 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 | Perform a host logon. If problem persists, contact support. | |
| SH | Expired card | Perform the EFTPOS tender again with a different card or use another form of Tender. |
| SJ | No EFB cashout | Retender without Cashout. |
| SK | Tran amount exceeds the EFB limit | Reduce the amount, or use another form of Tender. |
| SL | Lane swap in progress | Use other forms of Tender until the PINpad display says READY. |
| SM | Reversal pending | Retry the EFTPOS Tender or use another form of Tender. |
| SN | Settlement pending | Retry the EFTPOS Tender, or use another form of Tender. |
| SP | Invalid transaction amount | Check the amount and perform the EFTPOS Tender again. |
| SQ | Refund not allowed | Perform the EFTPOS Tender with a different card or account type. |
| SR | Perform the EFTPOS Tender and be careful to enter the last 4 digits correctly. | |
| SS | EFB debit trans not allowed | 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 | 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 | 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 | This is normal operation should your POS have implemented limits. Contact your POS supplier. |
| SW | Pre auth not allowed | Contact support if you believe this is not the correct configuration. |
| SX | PIN change not allowed | No further action. |
| SY | Product totals pending | Contact your POS supplier. |
| SZ | EFB trans already stored | Void the original pre-auth and submit a new pre-auth which totals the amount required. |
| T1 | Transaction receipt reprint unavailable | If this problem persists over multiple transactions, contact support. |
| T2 | Trans type is not allowed | Contact support if you believe this is not the correct configuration. |
| T3 | No matching entry in the CPT for this card | Perform the EFTPOS Tender with a different card or account type. |
| T4 | Void details mismatch | Perform the EFTPOS Tender and ensure transaction details match the previous transaction. |
| T5 | Generic EFB failure | 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 | Perform the EFTPOS Tender and ensure transaction details match the original transaction you are adding a tip to. |
| T7 | Power failure | Perform the EFTPOS Tender again. |
| T8 | PAN exceeds maximum length | Perform the EFTPOS Tender and carefully manually enter the card details again.. |
| T9 | Card appears on hot card list | No further action. |
| TA | Retry the transaction using a different tender. | |
| TB | 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 | 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 | Wait until the terminal display says READY or returns to the main logo screen. |
| TS | Link failure | Perform the EFTPOS Tender again. If problem persists, contact support. |
| TT | ICC Field Error | Perform the EFTPOS Tender again using a different card. If problem persists, contact support. |
| TU | ESC Check failed | 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 | No further action. |
| TX | Void already performed | No further action. |
| TY | POS Requested Reversal | No further action. |
| TZ | Application execution error | Contact support. |
| Error Code | Error Text | Troubleshooting Steps |
| C3 | EFT Gateway Error | Contact support. |
| C5 | No Network Layer / No internet | 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 | 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 | Retry transaction. If problem persists, contact support. |
| C8 | Bad Network Error | Retry transaction. If problem persists, contact support. |
| C9 | No EFT Gateway | 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 | Retry transaction. If problem persists, contact support. |
| CE | No Comms Gateway | Contact support. |
| Error Code | Error Text | Troubleshooting Steps |
| E250 | Unknown client, need to Connect first | 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 | 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) | Check the Cloud ID and serial number is valid according to Cloud Web Portal. |
| E253 | Unable to commission PINpad to terminal | 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 | 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 | 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 | 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 POS if faulty. Contact your POS Helpdesk. |
| E258 | System error | Contact support. Supply Wedge log file for further investigation. |
| E259 | System error | Contact support. Supply Wedge log file for further investigation. |
| E260 | System error | Contact support. Supply Wedge log file for further investigation. |
| E261 | System error | Contact support. Supply Wedge log file for further investigation. |
| E262 | System error | Contact support. Supply Wedge log file for further investigation. |
| E263 | System error | Contact support. Supply Wedge log file for further investigation. |
| E264 | System error | Contact support. Supply Wedge log file for further investigation. |
| E265 | Unhandled error during Admin Request | Contact support. Supply Wedge log file for further investigation. |
| E266 | System Busy | Retry again. If problem persists, contact support. |
| E267 | Unable to configure PINpad | 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 | 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 | 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 | 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 | 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) |
| E273 | failed to download the file due hash calculation error | Action depends on the failure reason provided as an additional details in the error text |
| E2003 | SYSTEM BUSY | 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 | 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 | This error is no longer reported. |
| E2102 | INVALID PINPAD TYPE | This error is no longer reported. |
| E2103 | UNABLE TO OPEN PINPAD COM PORT | Try restarting the machine. Check the port configuration of other devices connected to the machine for a conflict. |
| E2104 | UNABLE TO CREATE PINPAD MESSAGE | Escalate the issue immediately. |
| E2107 | PINPAD DEVICE ERROR | 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 | Retry transaction. If problem persists, contact support. |
| E2112 | CAN'T OPEN CARD READER COM PORT | Check Wedge configuration (qpswedge.pos.config) and ensure it is using the same comm port as displayed in device manager. |