Code 12: Invalid Transaction

Decline Code 12: What 'Invalid Transaction' Means & How to Fix It

Decline code 12 means the transaction has been flagged as invalid. Unlike most decline codes that point to something on the cardholder's end, code 12 almost always indicates a problem with the transaction data or merchant setup. It is typically a soft decline and a merchant-side error, which means the fix is usually on your end, not the customer's.

What Does Decline Code 12 Mean?

Most decline codes originate with the issuing bank. Code 12 is different. When the payment network or processor returns a 12, it's usually because something about the transaction itself didn't pass validation before it even reached the bank. The card may be perfectly fine. The customer's account may have plenty of available funds. The problem is in how the transaction was constructed or how the merchant account is configured.

That distinction matters because the instinct when a transaction declines is to ask the customer for a different card. With a code 12, that's the wrong move. A different card will return the same result if the underlying issue is a misconfigured gateway, an unsupported transaction type, or a malformed transaction amount.

Common Causes of a Decline Code 12

• Incorrect transaction amount. A zero dollar amount, a negative value, or a number formatted incorrectly for the payment network will invalidate the transaction before it processes.
• Transaction type not enabled on the merchant account. Refunds, voids, and certain transaction types need to be explicitly enabled. Attempting one that hasn't been configured will return a 12.
• Incorrect batch settlement attempt. A batch submitted with errors, duplicates, or mismatched transaction records can trigger a 12 during settlement.
• MCC or SIC code mismatch. If the merchant category code on file doesn't align with the transaction being processed, some networks will reject it as invalid.
• Gateway misconfiguration. Incorrect API parameters, outdated integration settings, or a miscommunication between the gateway and processor can produce a 12 on otherwise valid transactions.
• Test transaction run in a live environment. Test card numbers or sandbox credentials used against a live processing environment will return a 12.
• Invalid transaction type for the card being used. Certain cards don't support certain transaction types. Attempting a cash advance on a card that doesn't allow it, for example, can return a 12 rather than a 57.

Is Decline Code 12 a Merchant or Cardholder Error?

Almost always a merchant-side issue. The cardholder's card and account are typically fine, which is exactly why asking the customer for a different card is the wrong first step when you see a code 12.

Before doing anything else, check the transaction details: the amount, the transaction type, and whether the request matches what your merchant account is configured to handle. If everything looks correct on the surface, the next step is checking your gateway configuration or contacting your payment processor directly.

The customer can't fix a code 12 by handing you a different card. The problem is upstream of the card.

How to Fix Decline Code 12

1. Check the transaction amount first. Make sure it's a valid positive number formatted correctly. A zero amount or negative value is one of the most common triggers and one of the easiest to miss.
2. Verify the transaction type is enabled on your merchant account. If you're attempting a refund, a void, or any transaction type that requires separate configuration, confirm it's been set up with your processor.
3. Review your gateway configuration. Check API parameters, integration settings, and whether any recent changes to your setup could have introduced an error. If you're running a new integration, test mode credentials finding their way into a live environment is a common culprit.
4. Contact your payment processor if the issue persists. A code 12 that keeps appearing across multiple transactions with no obvious cause on your end points to a configuration or account-level issue that your processor needs to investigate.

Do not ask the customer to try a different card as a first response. It won't help and it creates unnecessary friction for a customer whose card isn't the problem.

Frequently Asked Questions About Decline Code 12

Is decline code 12 always the merchant's fault? Almost always, yes. Code 12 points to a problem with the transaction itself or how the merchant account is configured, not with the cardholder's card or account. There are edge cases where a specific card type is incompatible with a specific transaction type, which can look like a cardholder issue, but the starting assumption with a code 12 should always be to check your own setup first.

How is code 12 different from code 14 (invalid card number)? Code 14 means the card number submitted doesn't match a valid account in the network. It's a card-level issue and the fix is re-entering the number correctly or using a different card. Code 12 means the transaction itself is invalid regardless of the card. The card number may be perfectly fine. The problem is in the transaction data or merchant configuration. Different problem, different fix.

Should I ask the customer for a different card when I see code 12? Not as a first step. A different card will produce the same result if the issue is on the merchant side, which it almost always is with a code 12. Check the transaction details and your gateway configuration first. If you've confirmed everything on your end is correct and the issue persists, then asking for an alternate card is reasonable, but it should be the last step rather than the first.

Can code 12 be caused by a gateway outage? Indirectly, yes. If a gateway is experiencing issues, it may return a 12 on transactions that would otherwise process normally. If you're seeing a sudden spike in code 12 declines across multiple cards and transaction types with no changes to your configuration, checking your gateway's status page or contacting your processor is the right move before troubleshooting individual transactions.

Related Decline Codes

Code 12 is about transaction validity, not card or account issues. These related codes cover other failure types worth understanding:

• Code 14 — Invalid Card Number. The card number doesn't match a valid account. A card-level issue rather than a transaction-level one.
• Code 05 — Do Not Honor. The bank's catch-all decline. Originates with the issuing bank rather than the transaction data.
• Code 51 — Insufficient Funds. A balance issue on a valid card. No transaction configuration involved.
• Code 57 — Transaction Not Permitted to Cardholder. A permissions issue at the account level. Related but distinct from a transaction type not being enabled on the merchant account.
• Code 63 — Security Violation. A security check failure, typically a CVV or AVS mismatch.
• Code 54 — Expired Card. The card's expiration date has passed. A card-level issue unrelated to transaction configuration.
• Code 62 — Restricted Card. Card-level restrictions blocking a specific transaction type.
• Code 78 — Blocked First Use. The card hasn't been activated. A cardholder issue rather than a merchant configuration issue.