Introduction

This article provides an overview of the most common transaction statuses returned by the Acceptance Devices product, their associated Cybersource Business Center Reason Codes, Business Center flags, and recommended explanation or action steps for each status.

This article is intended for internal support teams handling transaction inquiries for merchants using Acceptance Devices, including those using PAX, Miura, and Verifone terminal hardware where noted.

Applicability Notice: This article applies exclusively to the Acceptance Devices product. Transaction statuses described here are specific to Acceptance Devices workflows and may not apply to other Cybersource products or services.

For general Cybersource transaction status information, refer to:
Understanding Transaction Statuses

Note: Some statuses — such as INITIALIZED and PENDING — are temporary and may only be visible in transaction logs. They do not represent a final transaction outcome.

Transaction Status Reference Table

The table below lists all supported Acceptance Devices transaction statuses grouped by status category. Each row includes the specific status detail, the associated Business Center Reason Code, the Business Center flag, and the explanation or recommended action steps.

APPROVED

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
APPROVED	100	SOK	The transaction completed successfully. The cardholder will be charged.

INITIALIZED

Note: INITIALIZED statuses are temporary and may only appear in transaction logs. They do not represent a final transaction outcome.

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
INITIALIZED_SERVER	N/A	N/A	The transaction session has been started. If no activity occurs within 15 minutes, the transaction will time out. See ERROR_SESSION_TIMEOUT.
INITIALIZED_TRANSACTION_REPLACED	N/A	N/A	Temporary state for soft declines where the issuer rejects a contactless transaction and requests that the card be inserted and confirmed with a PIN. See DECLINED_PROCESSOR_EXCEEDS_WITHDRAWAL_COUNT_LIMIT.
INITIALIZED_TRANSACTION_REQUEST_PIN	N/A	N/A	Request for PIN on Near Field Communication (NFC) Integrated Circuit Card (ICC) contactless payments. The customer should input their PIN to proceed.

PENDING

Note: PENDING statuses are temporary and may only appear in transaction logs. They do not represent a final transaction outcome.

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
PENDING_WAITING_FOR_FINALIZATION	N/A	N/A	The system is waiting for the transaction to be finalized.
PENDING_WAITING_FOR_PROCESSOR	N/A	N/A	The system is waiting for the processor's response.

DECLINED

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
DECLINED_AUTHORIZATION_PROCESSOR_MALFUNCTION	207	PLEASE RETRY	Decline. The issuing bank is unavailable. Wait a few minutes and resend the request.
DECLINED_CARD_STOLEN	205	DCARDREFUSED	⚠ Security Notice: This card has been reported to the card issuer as stolen. Do not proceed with the transaction. Follow your standard security protocol.
DECLINED_PROCESSOR	203	DCARDREFUSED	The acquiring or issuing bank declined authorization for this transaction. This is a generic decline reason that often originates from the issuing bank and the specific reason may not be visible. If this is occurring for one merchant across multiple cards, the acquirer should review the Merchant ID (MID) setup in their system. Resolution steps: Ask the cardholder to contact the issuing bank to determine why the transaction was rejected. Ask the acquirer to review the MID setup in their system. Ask the issuer to check whether they have blocked the specific MID being used. Confirm whether an unsupported or foreign card is being used.
DECLINED_INSUFFICIENT_FUNDS	204	DCARDREFUSED	The cardholder does not have sufficient funds to cover the transaction amount. The customer should use another card.
DECLINED_INVALID_CURRENCY	N/A	N/A	The currency used in the transaction has not been added to the processing path. Contact Support.
DECLINED_INVALID_CVN	211	DCARDREFUSED	An incorrect Card Verification Number (CVN) was entered. Applicable to Mail Order / Telephone Order (MOTO) transactions. Confirm the CVN is correct and retry.
DECLINED_INVALID_AMOUNT	N/A	N/A	A negative amount or invalid character may have been entered in the amount field. Retry the transaction with correct amount values.
DECLINED_INVALID_CONFIGURATION	N/A	N/A	This status typically relates to invalid values — such as an incorrect Merchant ID (MID) or Terminal ID (TID) — in the processing path, or values that have not been activated at the acquirer. This does not relate to the configuration on the terminal or card reader. There is no need to replace the terminal. Resolution steps: Review whether the acquirer MID and TID are correct on the merchant account and update if incorrect. If the details are correct, contact the acquirer to confirm the MID and TID have been activated.
DECLINED_INVALID_SCHEME	N/A	N/A	The card scheme used is not supported. Check whether the card scheme is enabled on the merchant account. If it is enabled, contact Support.
DECLINED_INVALID_WORKFLOW	N/A	N/A	Contact Support.
DECLINED_MALFORMED_REQUEST	N/A	N/A	This occurs when the acquirer does not accept the format of the transaction that was submitted. Contact Support.
DECLINED_FRAUD	N/A	N/A	⚠ Fraud Notice: A fraudulent action is suspected. Do not proceed with the transaction. The cardholder may try again or use another card. Follow your standard fraud handling protocol.
DECLINED_CARD_LOST	N/A	N/A	⚠ Security Notice: This card has been reported as lost. The cardholder should contact the card issuer. Do not proceed with the transaction.
DECLINED_CARD_OR_TERMINAL_DECLINED	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The transaction was rejected by the card or the terminal. Possible reasons include: Card is not supported (for example, local debit schemes such as Dankort) Card was used too many times consecutively The card does not trust the response from the acquirer or issuer due to a missing cryptogram Incorrect data was returned Card is blocked for the country or merchant category Card is a gas pump-only card Contact Support if further advice is required. Note — SDK Version: This status was replaced by DECLINED_CARD_OR_TERMINAL_DECLINED_2ND_GEN_AC and DECLINED_CARD_OR_TERMINAL_DECLINED_1ST_GEN_AC in later Software Development Kit (SDK) versions (approximately version 2.43 and above). See the rows below.
DECLINED_CARD_OR_TERMINAL_DECLINED_2ND_GEN_AC DECLINED_CARD_OR_TERMINAL_DECLINED_1ST_GEN_AC	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The transaction was rejected by the card or the terminal. If the terminal is a PAX device being used for the first time, this may indicate a problem with the terminal's Remote Key Injection (RKI) or the terminal configuration. Contact Support.
DECLINED_FORBIDDEN_CARD_CAPTURE_CARD	N/A	N/A	⚠ Security Notice: The issuer has indicated that this card should not be used — possibly because it was reported as lost or stolen. The merchant should retain the card and follow their standard security protocol.
DECLINED_PROCESSOR_PIN_ENTRY_NECESSARY	203	DCARDREFUSED	The issuer sent a soft decline and requested additional authentication because: A certain number of consecutive contactless transactions was reached, or A certain cumulative transaction amount was reached with contactless transactions. The merchant and cardholder should follow the instructions on the terminal. Depending on the situation: The cardholder can enter the PIN immediately. The previous transaction will be resubmitted with the online PIN. The terminal may request that the card be presented as a contact card. The cardholder will then need to provide the offline PIN. See DECLINED_PROCESSOR_EXCEEDS_WITHDRAWAL_COUNT_LIMIT for similar transaction behavior.
DECLINED_PIN_WRONG	208	DCARDREFUSED	An incorrect PIN was entered. Ask the cardholder to enter the correct PIN.
DECLINED_PIN_WRONG_TOO_OFTEN	251	DCARDREFUSED	The wrong PIN was entered too many times and the card has been blocked. The cardholder should contact the card issuer to unblock the card.
DECLINED_PROCESSOR_CARD_EXPIRED	202	DCARDEXPIRED	The card has expired. The cardholder should use a different card.
DECLINED_PROCESSOR_EXCEEDS_WITHDRAWAL_COUNT_LIMIT	478	DAUTHENTICATE	The issuer sent a soft decline and requested additional authentication because: A certain number of consecutive contactless transactions was reached, or A certain cumulative transaction amount was reached with contactless transactions. The merchant and cardholder should follow the instructions on the terminal. The terminal will request that the card be presented as a contact card. The cardholder will then need to provide the offline PIN. See DECLINED_PROCESSOR_PIN_ENTRY_NECESSARY for similar transaction behavior.
DECLINED_MERCHANT_REJECTED	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The Merchant ID (MID) used may not have been configured or activated, or does not exist on the acquirer side. Contact the acquirer to check the MID or provide further details on the decline.
DECLINED_CARD_BLOCKED	208	DCARDREFUSED	The card is blocked and cannot be used. The cardholder should use another card.

ERROR

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
ERROR_APPROVED_OFFLINE	N/A	N/A	Currently known only for PAX devices. This error occurs due to a wrong or missing configuration — usually caused by an incorrect transacting country configured on the device. Contact Support.
ERROR_AUTOREVERSAL_APPLIED	N/A	N/A	An error occurred and the backend applied a successful auto-reversal. Contact Support if further details are required.
ERROR_AUTOREVERSAL_DECLINED	N/A	N/A	An error occurred and the backend attempted an auto-reversal, which failed — usually because the original charge was not successful. This is the opposite outcome of ERROR_AUTOREVERSAL_APPLIED.
ERROR_CARD_INVALID_CARD	N/A	N/A	Generally indicates that a card was used that did not provide all the necessary information required for the transaction. Ask the cardholder to try again or use another card.
ERROR_PROCESSOR_MALFORMED_REQUEST	102	DINVALIDDATA	Something was wrong with the transaction request. Contact Support to review.
ERROR_PROCESSOR_CONNECTION_NO_RESPONSE	N/A	N/A	This typically occurs when no response is received from the acquirer. For some acquirers, this can happen if they receive unexpected data — for example, if the Terminal ID (TID) is not activated or is in an incorrect format. Resolution steps: Verify the Terminal IDs in the processing path to ensure they are all valid. Confirm that the TIDs have been activated by the acquirer. ⚠ Refund Notice: For refunds returning this error, check whether the original charge was a debit-routed transaction. Debit-routed transactions cannot be refunded via a follow-on refund because a PIN is required for that refund type.
ERROR_PROCESSOR_CONNECTION_ERROR	N/A	N/A	The processor or acquirer did not respond to the request. Try again. Contact Support if the issue persists.
ERROR_SDK_INTERNAL_ERROR	N/A	N/A	Indicates an issue with the Software Development Kit (SDK). Contact Support.
ERROR_SESSION_TIMEOUT	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The transaction session was registered on the system but was not completed. This can be caused by: Connection to the terminal was dropped Point of Sale (POS) application crashed Internet connectivity stopped working Contact Support to investigate.
ERROR_SERVER_ACCESSORY_NOT_ASSIGNED_TO_MERCHANT	N/A	N/A	The merchant is attempting to use a terminal that has not been assigned or cannot be assigned to that merchant. Refer to the related article: Terminal / POS System Shows "Terminal Not Whitelisted" During a Transaction
ERROR_SERVER_UNAVAILABLE	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	This may be caused by one of the following: The acquirer experienced an internal issue and returned an error code The acquirer was unable to receive a response from the issuer No response was received from the acquirer Local connection issues at the POS system Contact Support to investigate if the issue persists.
ERROR_TERMINAL_ERROR	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	Usually indicates a problem between the SDK and the terminal. Possible causes include: The terminal lost connection during the transaction No or invalid terminal keys — card data or PIN cannot be encrypted (Verifone terminals) Terminal configuration does not support the transaction currency Terminal could not be assigned automatically because it was deactivated For Miura terminals, ensure the Bluetooth connection is stable and perform the pairing process again. Contact Support.
ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_UNRESOLVED	151 / 237 / 246 / 233 Note: These reason codes relate to Reversal or Voided Transactions at Business Center.	N/A	⚠ Financial Risk Notice: This status indicates that a cardholder may have been charged by accident because the automated reversal with the acquirer failed. This transaction must be reviewed manually by Support. The status will be updated to ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_RESOLVED once the transaction status has been clarified.
ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_RESOLVED	See ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_UNRESOLVED above.	N/A	This transaction previously had the status ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_UNRESOLVED but has since been reviewed and resolved by Support. No further action is required.
ERROR_PROCESSOR	234 / 150 Note: The reason code returned may differ depending on the processor.	DINVALIDDATA / ESYSTEM	There was an issue sending the transaction to the acquirer or processor. The transaction failed somewhere in between. Possible reasons include: Invalid merchant credentials Invalid merchant configuration at the acquirer The acquirer did not respond Contact Support if further information is required.
ERROR_SERVER_INVALID_RESPONSE	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center. ERROR_SERVER_TIMEOUT or ERROR_NO_TERMINAL_CONFIG_AVAILABLE	N/A	Possible reasons for the error include: Invalid, missing, or malformed data was presented or received during the transaction. A request to a server did not receive a response and timed out. No terminal configuration is available for the context of that merchant — for example, country, clearing institute, or terminal model. Contact Support for further advice.

ABORTED

Status Detail	Business Center Reason Code	Business Center Flag	Explanation / Action Steps
ABORTED_MERCHANT_ABORTED	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The merchant aborted the transaction using a button on the Point of Sale (POS) system — for example, during signature capture. This is usually intentional, such as when an incorrect amount or product was entered. This may also occur due to a connection error. If this happens frequently for a specific merchant, request additional information from the merchant and contact Support.
ABORTED_SHOPPER_REMOVED_CARD	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	The card was removed too early during the transaction process. Ask the cardholder to retry the transaction and keep the card presented until the transaction is complete.
ABORTED_MERCHANT_MANUALLY_REVERTED	100 Note: Reason Code 100 in this context relates to a Reversal or Voided Transaction being successful at Business Center.	N/A	This occurs when the terminal or SDK loses connection during a transaction and the transaction status is looked up after the terminal reconnects. Any charge will be reversed and the cardholder will not be charged. Ensure the terminal has a stable connection and retry the transaction.
ABORTED_PIN_ENTRY_TIMED_OUT	N/A	N/A	The transaction was aborted automatically because the PIN entry screen timed out. Ask the cardholder to retry the transaction and enter their PIN promptly when prompted.
ABORTED_PRESENT_CARD_TIMED_OUT	N/A	N/A	No card was presented within the required timeframe (usually 30 seconds), so the transaction was aborted automatically. Try again or ask the cardholder to use another card. If this issue occurs frequently, it may indicate a hardware problem with the device's ability to read the card via contactless, chip, or magnetic stripe. Contact Support in that case.
ABORTED_SHOPPER_ABORTED	N/A	N/A	The customer aborted the transaction. This is usually intentional but may also occur due to slow responses or terminal connectivity issues that cause the customer to lose patience. Contact Support if this issue occurs frequently.

Potential Client Questions

Why does Reason Code 100 appear on both successful and unsuccessful transactions?
- Reason Code 100 has two distinct meanings depending on context. When associated with an APPROVED status, it indicates a successfully completed transaction. When associated with certain DECLINED, ERROR, or ABORTED statuses, it indicates that a Reversal or Voided Transaction was successfully processed at Business Center. Always review the full transaction status alongside the reason code to determine the correct outcome.
Why does the transaction status show DECLINED even though the cardholder says their card is valid?
- A decline can originate from the issuing bank, the acquirer, or the terminal — not always from the card itself. Common causes include contactless transaction limits being reached, incorrect terminal or merchant configuration, or the issuer blocking the transaction for security reasons. Review the specific status detail to determine the correct next step.
What should the merchant do if they see ERROR_PROCESSOR_FAILED_INCONSISTENT_STATE_UNRESOLVED?
- This status requires manual review by Support because the automated reversal with the acquirer failed and the cardholder may have been charged. The merchant should contact Support immediately and avoid retrying the transaction until the status has been resolved.
Can a debit-routed transaction be refunded if it returns ERROR_PROCESSOR_CONNECTION_NO_RESPONSE?
- No. Debit-routed transactions cannot be refunded via a follow-on refund because a PIN is required for that refund type. If the original charge was debit-routed, contact Support to determine the correct resolution path.
Why does the transaction show an ABORTED status when the merchant did not intentionally cancel it?
- ABORTED statuses can occur due to connection drops, session timeouts, or the cardholder removing their card too early — not only from intentional cancellations. Review the specific ABORTED status detail to identify the cause. If the issue occurs frequently, contact Support to investigate.
Does this article apply to all Cybersource transaction statuses?
- No. This article applies exclusively to the Acceptance Devices product. For general Cybersource transaction status information, refer to: Understanding Transaction Statuses.

Additional Resources

Understanding Transaction Statuses — General Cybersource transaction status reference for non-Acceptance Devices products
Why Was My Acceptance Devices Transaction Reversed or Voided Automatically After It Was Successful?
Terminal / POS System Shows "Terminal Not Whitelisted" During a Transaction
Cybersource Reason Codes Reference

Internal Note: The following related articles were flagged as pending in the source content and have not yet been finalized. Do not share these references externally until the links have been confirmed and published:

Gateway Authentication Failed — KA-08121 (link pending confirmation)
Gateway Verification Failed (link pending confirmation)

Was this article helpful?

Articles Recommended for You

Acceptance Devices - Transaction Status Overview (Internal)