DUPLICATE - Duplicate transaction
The terminal/processor detected a potential duplicate transaction and blocked it to prevent double-charging.
Card-present terminal errors and device prompts during authorization, settlement, and configuration.
POS terminals and card-present devices can display short error prompts during authorization, settlement, batch close, or device pairing. Some identifiers are processor-related, while others reflect local configuration, connectivity, or device state.
This hub focuses on common, recognizable POS terminal error identifiers and what they typically indicate at a high level. Pages avoid guessing processor-specific meanings when the device only shows a generic prompt.
The terminal/processor detected a potential duplicate transaction and blocked it to prevent double-charging.
The terminal could not complete a chip read and is requesting a fallback method per EMV rules.
The terminal could not read the EMV chip data from the card.
The terminal or host detected a message authentication (MAC) validation failure.
The terminal cannot reach the payment host/gateway to authorize the transaction.
The PIN entry device is not available or not responding, so PIN-based transactions cannot proceed.
The processor indicates a reversal/void is required to correct an incomplete or errored transaction state.
The transaction is approved or conditionally approved but requires signature verification per the processing rules.
The terminal could not read the magstripe data from the card during a swipe.
The terminal detected a tamper condition and disabled sensitive functions to protect encryption keys.
The terminal indicates settlement/batch close was not completed successfully.
The terminal indicates the issuer requires the cardholder to contact them before approval.
The terminal could not communicate with the processing host to complete the request.
The terminal indicates the payment was not approved by the issuer.
The processing host was not reachable during the transaction attempt.
The terminal configuration did not validate the terminal identifier for processing.
The terminal is not ready to process because required keys are missing or not current.
The terminal or attached printer cannot print receipts because paper is missing.
The terminal could not read the EMV chip data from the card.
The terminal/processor detected a potential duplicate transaction and blocked it to prevent double-charging.
The terminal could not complete a chip read and is requesting a fallback method per EMV rules.
The terminal or host detected a message authentication (MAC) validation failure.
The terminal cannot reach the payment host/gateway to authorize the transaction.
The PIN entry device is not available or not responding, so PIN-based transactions cannot proceed.
The processor indicates a reversal/void is required to correct an incomplete or errored transaction state.
The transaction is approved or conditionally approved but requires signature verification per the processing rules.
The terminal could not read the magstripe data from the card during a swipe.
The terminal detected a tamper condition and disabled sensitive functions to protect encryption keys.
The terminal indicates settlement/batch close was not completed successfully.
The terminal indicates the issuer requires the cardholder to contact them before approval.
Advertisement
Ad slot: systems-hub
Start by separating these scenarios:
Safe steps include checking network signal, confirming the terminal has the correct merchant configuration, and reviewing processor dashboards for final transaction state.
No. Devices, gateways, and processors vary widely. This hub only includes identifiers that are commonly documented and searched.
Declines are payment decisions. Errors are technical failures (connectivity, configuration, or device state).
Yes. Timeouts can occur after submission. Always confirm final status in the processor record.
Confirm whether an authorization exists first to avoid duplicates.
They can, especially if keys or software updates are incomplete.
Verify connectivity and confirm whether other terminals are impacted.