Code 13: Invalid Amount

Decline Code 13: What 'Invalid Amount' Means & How to Fix It

Decline code 13 means the transaction amount submitted is invalid. It may be zero, negative, incorrectly formatted, or exceed the maximum allowed for the merchant account. This is nearly always a merchant-side error, and the fix is correcting the amount and resubmitting rather than asking the customer for a different card.

What Does Decline Code 13 Mean?

Most decline codes are the bank's answer to a question: should this transaction be approved? Code 13 means the question never got asked properly. The amount field contained something the payment network couldn't process, so the transaction was rejected before the bank even had a chance to evaluate the account.

That's what separates code 13 from a code 51. With a 51, the card number is valid, the bank reviewed the account, and determined there weren't enough funds. With a 13, the transaction data itself is the problem. The cardholder's account may have more than enough available. It doesn't matter because the request that reached the network was malformed.

Common Causes of Decline Code 13

• Zero-amount authorization submitted incorrectly. Some systems use zero-amount authorizations for card verification, but submitting one through a standard purchase flow will return a 13.
• Negative amount submitted as a purchase. A refund amount entered into a purchase transaction rather than a refund transaction produces a negative value the network can't process as a sale.
• Amount includes letters or special characters. A field that contains anything other than a valid numeric value will fail immediately.
• Amount exceeds the per-transaction maximum on the merchant account. Merchant accounts can have per-transaction limits set by the processor. A transaction above that ceiling returns a 13 rather than processing normally.
• Incorrect formatting. A missing decimal, a currency symbol in the wrong field, or a value formatted for a different currency standard than what the network expects can all produce a 13.
• Test amount used in a live environment. Some test values that work in sandbox environments are not valid in production and will return a 13 when used against a live processor.

How to Fix Decline Code 13

1. Check the transaction amount field immediately. Look for obvious issues: a zero, a negative number, a formatting error, or any non-numeric characters that shouldn't be there.
2. Correct the formatting. The amount should be a positive number formatted correctly for your payment system, typically with a decimal point and no currency symbols in the amount field itself.
3. Verify the amount doesn't exceed your merchant account's per-transaction maximum. If you're processing an unusually large transaction and seeing a 13, this is worth checking with your processor. Limits can often be adjusted if there's a legitimate business need.
4. Retry with the corrected amount. Once the amount is fixed, the transaction should process normally assuming no other issues with the card or account.
5. Contact your processor if the error persists despite correct formatting. A 13 that keeps appearing on correctly formatted transactions points to a configuration issue at the account or gateway level that your processor needs to investigate.

Frequently Asked Questions About Decline Code 13

Is decline code 13 always a merchant error? Almost always. Code 13 fires because the amount submitted was something the network couldn't process, and the amount is merchant-submitted data. The cardholder has no control over what goes into that field. The only exception worth noting is a per-transaction maximum: if a processor has set a limit that's lower than the transaction a customer legitimately wants to complete, the 13 comes from a configuration decision rather than a data entry mistake. Either way, the fix is on the merchant side.

How is code 13 different from code 12? Both are merchant-side errors involving invalid transaction data, but they point to different problems. Code 12 means the transaction type is invalid, the request was for something the merchant account isn't configured to process, like an unsupported transaction type or a refund not enabled on the account. Code 13 means the amount specifically is the problem. The transaction type may be perfectly valid, but the value in the amount field isn't. Same general category of error, different field causing it.

Can code 13 be caused by a software bug? Yes, and it's more common than manual entry errors in automated or integrated environments. A bug that produces a zero amount, drops a decimal, or passes a null value into the amount field will generate a 13 on every transaction until it's fixed. If you're seeing consistent code 13 declines across multiple transactions with no obvious manual entry error, a software or integration issue is the likely culprit. Check your integration logs and the raw transaction data being submitted to your gateway.

Should I ask the customer for a different card when I see code 13? No. The customer's card has nothing to do with a code 13. Asking for a different card won't help and creates unnecessary friction for someone whose payment method is fine. Fix the amount and retry. If you're in a situation where the error can't be resolved quickly, apologize and explain that there's a technical issue on your end rather than implying the problem is with their card.

Related Decline Codes

Code 13 is specifically about an invalid amount in the transaction data. These related codes cover adjacent merchant-side and transaction-level errors:

• Code 12 — Invalid Transaction. A transaction-level error involving an unsupported transaction type or merchant configuration issue rather than the amount field.
• Code 06 — General Error. A broader processing error that can sometimes overlap with formatting issues.
• Code 51 — Insufficient Funds. A balance issue on a valid transaction. The amount was fine, the account just couldn't cover it.
• Code 10 — Partial Approval. The bank approved part of the amount rather than rejecting the transaction outright.
• Code 05 — Do Not Honor. A bank-level refusal rather than a data validation failure.
• Code 14 — Invalid Card Number. The card number field has a problem, a different field from the amount.
• Code 63 — Security Violation. A security check failure rather than an amount formatting issue.
• Code 01 — Refer to Issuer. The bank wants cardholder verification before approving, unrelated to the amount format