Tip from SmartRetry Implement BIN-level validation during checkout to detect card types—such as non-reloadable or cross-border prepaid cards—that issuers routinely restrict for your transaction category. Steering customers to alternate payment methods before authorization avoids unnecessary decline fees and prevents checkout abandonment.
Visa, Mastercard
Decline Code 57: Transaction Not Permitted
Last updated: November 20, 2026
Key details
Code by card network
| Network | Code | Official wording |
|---|---|---|
| Visa | 57 | Transaction not permitted to cardholder |
| Mastercard | 57 | Transaction not permitted to issuer/cardholder |
| V Pay | 57 | Transaction not permitted to cardholder |
| Diners | 57 | Transaction not permitted to Issuer/Cardholder |
| Discover | 57 | Transaction not permitted to Issuer/Cardholder |
| Maestro | 57 | Transaction not permitted to issuer/cardholder |
What it means
Why does code 57 occur?
How to solve 57?
Solving as a merchant
Solving as a client
Frequently asked questions about this topic
Author
Kyle Regacho
Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >How providers report this
- Stripe: transaction_not_allowed (Transaction Not Allowed)
- Adyen: 23 (Transaction Not Permitted)
Articles you may find interesting:
View all
When Processing Stops: Navigating Gateway Locks and Account Holds
When aggregators freeze processing, standard support tickets fail. Discover how fintech operators diagnose automated underwriting triggers, appeal held funds, and deploy redundant routing to eliminate single points of failure.

Fine-Tuning Stripe for Subscriptions: How to Stop Losing Customers to Failed Payments
Default billing setups quietly surrender recurring revenue to preventable declines. Discover how adjusting stored credential flags, deploying network tokens, and timing retries protect subscriber retention and improve authorization health.

Understanding CAVV: How 3D Secure Tokens Secure Approvals and Shift Liability
Mastering 3D Secure CAVV tokens helps payment teams prevent false declines and secure fraud liability shifts. Learn how cryptographic validation impacts issuer authorization decisions and recurring payment retry performance.

Does Numeral Offer Load Balancing for Payment Requests?
Discover why traditional load balancing fails across banking rails and multi-acquirer setups, and how intelligent routing protects your transaction approval rates.
Decline codes tell you why. We fix it.
SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.