Tip from SmartRetry Suppress immediate automated retries on code 12, as resubmitting identical payloads will consistently fail. Instead, verify whether the decline stems from acquirer-level terminal or currency restrictions, then conditionally reroute through an alternative processing pathway that supports the transaction configuration.
Visa
Visa Issuer Response Code 12: Invalid Transaction
technical declinehard decline
Last updated: September 25, 2026
About 12 - "Invalid transaction"
Key details
- 12
- Issuer Response Codes
- 12
- Invalid transaction
technical declinehard decline
What it means
Visa response code 12 indicates an 'Invalid transaction.' This error occurs when the issuing bank or payment network rejects the transaction request because it contains invalid parameters or represents an operation not permitted for the card or merchant setup.
Classification & retryability
technicalhardRetryable: conditional
Do not automatically retry the identical authorization request. Retrying is only appropriate if you identify and correct a malformed payload or configuration parameter, or if the customer provides a different payment method.
Why does code 12 occur?
- The transaction request contains missing, malformed, or conflicting data fields.
- The cardholder's account is restricted from performing this specific type of transaction.
- The merchant account is attempting an operation or currency not supported by the issuing bank.
How to solve 12?
Examine your gateway and processor logs to verify the format and contents of the authorization request. Ensure that all mandatory transaction fields, currency codes, and processing indicators comply with Visa network rules. If the technical request is valid, advise the cardholder to use a different card or check with their issuing bank.
Solving as a merchant
Verify that your payment integration is sending properly formatted authorization requests and that your merchant account supports the attempted payment type. If the payload is correct, prompt the customer for an alternative payment method.
Solving as a customer
Contact your card-issuing bank to verify if your card has restrictions against this type of transaction, or use an alternative payment card to complete the purchase.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.