Code 06: General Error

Decline Code 06: What 'General Error' Means & How to Resolve It

Decline code 06 means a general error occurred during transaction processing. Unlike code 05, which is a deliberate bank refusal, code 06 more often points to a technical or processing issue somewhere in the transaction chain. It is typically a soft decline and in many cases a single retry resolves it.

What Does Decline Code 06 Mean?

Payment transactions pass through multiple systems before an approval or decline comes back: the terminal, the gateway, the payment network, and the issuing bank. Code 06 is what gets returned when something goes wrong in that chain but the error doesn't fit a more specific code.

It can originate anywhere along the route. A temporary hiccup in the bank's processing system, a communication failure between the gateway and the issuer, a formatting issue in the transaction data — any of these can produce a 06 without necessarily meaning the card is invalid or the customer's account has a problem.

That's the key difference from a code 05. A Do Not Honor response is a deliberate decision by the bank. A code 06 is more often the payment equivalent of a dropped call: something went wrong with the transmission, not with the underlying account.

Common Causes of Decline Code 06

• Temporary bank system error. The issuing bank's processing system encountered an issue and couldn't complete the authorization. Usually resolves quickly.
• Network communication failure between gateway and issuer. The transaction data didn't make it cleanly from the payment gateway to the bank, or the response got lost on the way back.
• Incorrect transaction data format. The data submitted didn't conform to what the network or bank expected, triggering a general validation failure.
• Terminal or gateway misconfiguration. An outdated integration, incorrect settings, or a miscommunication between systems can produce a 06 on otherwise valid transactions.
• Bank processing system outage. If the bank is experiencing broader issues, code 06 may appear across multiple transactions simultaneously rather than in isolation.
• Transaction data failed internal validation checks. The bank or network ran the transaction against internal validation rules and it didn't pass, without a more specific reason being returned.

Is Decline Code 06 a Hard or Soft Decline?

Code 06 is typically a soft decline. Because it most often reflects a temporary technical issue rather than a deliberate account-level block, a single retry after a short wait frequently succeeds where the first attempt failed.

The caveat: if the same transaction returns a 06 on retry, the issue is likely something more persistent, either a configuration problem on the merchant side or a sustained outage somewhere in the processing chain. At that point it stops behaving like a soft decline and needs to be escalated rather than retried again.

How Merchants Should Handle Decline Code 06

1. Wait 30 to 60 seconds and retry once. Give the systems a moment to recover before attempting again. A retry immediately after the decline gives the same conditions the same chance to produce the same result.
2. If the retry fails, check your terminal and gateway connection. Look for error indicators, connection issues, or any recent changes to your setup that could have introduced a problem.
3. Contact your payment processor if the issue persists. Provide the transaction ID and details. Your processor can see where in the chain the error is occurring and whether there's a broader outage affecting multiple merchants.
4. Ask the customer for an alternate payment method if the issue can't be resolved quickly. A code 06 is worth one careful retry. It's not worth holding up a line or making a customer wait while you troubleshoot a technical issue in real time.

Frequently Asked Questions About Decline Code 06

Is decline code 06 the same as code 05? No, and the distinction matters. Code 05 is a Do Not Honor response: the bank has made a deliberate decision to decline the transaction, usually without specifying why. Retrying a code 05 is unlikely to help. Code 06 is a general processing error that may have nothing to do with the cardholder's account at all. A retry after a short wait is appropriate for a 06. It is not appropriate for a 05.

Should I retry after a code 06 decline? Yes, once, after waiting 30 to 60 seconds. Code 06 often reflects a temporary technical issue that clears on its own. One careful retry is reasonable. If it fails again, stop retrying and either check your setup or contact your processor. Repeated retries on a persistent error won't fix the underlying issue and add unnecessary noise to your transaction log.

Is code 06 always a bank error? No. Code 06 can originate from the bank, the payment network, the gateway, or the merchant's own terminal or integration. If you're seeing code 06 on multiple transactions in a short window, it's worth checking whether your gateway or terminal is the source before assuming the bank is having issues. A sudden pattern of 06 declines across different cards often points to something on the merchant or gateway side rather than the bank.

How is code 06 different from code 12 (invalid transaction)? Code 12 means the transaction itself was flagged as invalid, usually because of a problem with how it was constructed: a zero amount, an unsupported transaction type, or a misconfigured merchant account setting. It's a specific validation failure. Code 06 is a broader general error that can come from anywhere in the processing chain and doesn't necessarily point to a problem with the transaction structure itself. Code 12 usually requires investigating your merchant setup. Code 06 usually warrants a retry first and escalation if that doesn't work.

Related Decline Codes

Code 06 sits in the technical error category, separate from deliberate bank blocks or account-level issues. These related codes cover adjacent scenarios:

• Code 05 — Do Not Honor. A deliberate bank refusal rather than a processing error. No retry path.
• Code 12 — Invalid Transaction. A specific transaction validation failure, usually merchant-side.
• Code 14 — Invalid Card Number. The card number doesn't match a valid account, a card-level issue rather than a processing error.
• Code 51 — Insufficient Funds. A balance issue on an otherwise valid card with no technical error involved.
• Code 63 — Security Violation. A security check failure rather than a general processing error.
• Code 57 — Transaction Not Permitted to Cardholder. A permissions issue at the account level, not a technical failure.
• Code 01 — Refer to Issuer. The bank wants cardholder verification before approving, a soft decline with a resolution path.
• Code 78 — Blocked First Use. The card hasn't been activated. An account issue rather than a processing error.