Mastercard Payment Decline Code

Mastercard Decline Code 12: Invalid Transaction

Category Invalid Payment DataRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Mastercard Decline Code 12 Means

Mastercard decline code 12 (Invalid Transaction) indicates that the issuer considers the transaction invalid as submitted and will not process it. It is returned during authorization to tell the merchant the payment could not be approved as submitted.

Where the Response May Come From

Mastercard code 12 (Invalid Transaction) is returned by the card issuer during authorization and signals that the issuer treats the transaction type or submitted field values as invalid for this account. Issuers rarely disclose the precise internal cause, so treat it as a directional signal rather than a full explanation.

Common Reasons for This Response

Common causes include an unsupported transaction type, incorrect field values, or a request the issuer does not allow for that account. The exact trigger depends on the issuer, the account, and how the transaction was submitted, so the same code can appear in several different situations.

Should the Merchant Retry the Payment?

Whether a retry helps depends entirely on the fact that the issuer treats the transaction type or submitted field values as invalid for this account; retry only once that condition is genuinely resolved, and avoid immediate repeat attempts that conflict with network retry expectations.

Recommended Merchant Action

Confirm the cause first, since the issuer treats the transaction type or submitted field values as invalid for this account, then check the transaction type and field values before resubmitting, and ask the customer to contact their issuing bank if the response points to their account.

What to Tell the Customer

Let the customer know the payment did not go through because the issuer treats the transaction type or submitted field values as invalid for this account, and suggest confirming their details or trying another payment method. Keep the wording neutral and avoid asserting issuer details you cannot confirm.

How to Reduce Similar Payment Failures

Segmenting how often the issuer treats the transaction type or submitted field values as invalid for this account appears by issuer and BIN, validating transaction types and field formats before submission, and submitting clean, correctly formatted authorization data can reduce avoidable occurrences of this decline over time.

Important Limitations

Decline-code meanings vary by processor, gateway, and payment environment, and issuers do not always disclose the specific reason behind a response. The retry classification on this page is Payment Defender editorial guidance, not an official Mastercard rule. Merchants should confirm handling with their processor or gateway.

Related Decline Codes

Sources and Review Information

Last reviewed July 17, 2026

Raw network-response codes are supplemental to the complete processor or gateway response. Meanings and recommended actions can vary by issuer, processor, gateway, card network, payment method, region, and merchant configuration.

Turn the Code Into Action

Know What to Do Next

Payment Defender helps merchants connect reason codes to transaction history, dispute alerts, refunds, evidence, fraud activity, VAMP exposure, and payment-performance decisions.