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.
Mastercard
Mastercard Issuer Response Code 57: Transaction Not Permitted to Issuer/Cardholder
hard decline
Last updated: September 25, 2026
About 57 - "Transaction not permitted to issuer/cardholder"
Key details
- 57
- Issuer Response Codes
- 57
- Transaction not permitted to issuer/cardholder
hard decline
What it means
Mastercard response code 57 indicates that the issuing bank or the cardholder's account configuration does not allow the specific transaction being attempted. This is a policy-based hard decline triggered by issuer product rules, geographic restrictions, or unsupported transaction types, such as attempting to load a prepaid card across borders or process refunds on non-reloadable cards.
Classification & retryability
hardRetryable: no
Do not automatically retry this authorization attempt. A later retry is only viable if a material change has occurred, such as the customer successfully lifting an account restriction with their issuer or activating a restricted card.
Why does code 57 occur?
- The merchant attempted to process a refund to a non-reloadable prepaid Mastercard, which the issuer explicitly blocks.
- A prepaid card activation or funding attempt failed because the merchant, acquirer BIN, and issuer BIN are not all strictly domestic.
- The issuer's policy prohibits the specific transaction type being attempted, such as restricted China Domestic transaction categories (e.g., funds-transfer, ATM, or POS).
- The cardholder's account has strict geographic, channel, or product-level restrictions preventing the transaction.
How to solve 57?
Treat this code as a hard policy decline and do not immediately retry the identical authorization payload. Review the transaction context—such as the card product type, geographic region of the BINs, and transaction category—to determine if a specific restriction applies (e.g., cross-border prepaid loading). Prompt the customer with a clear, non-technical decline message and request an alternative payment method.
Solving as a merchant
Inspect your payment channel, transaction type, and BIN context to ensure you are not submitting fundamentally unsupported requests, such as refunding a non-reloadable prepaid card or violating domestic-use restrictions. Stop any automated retries for this credential, present a clear failure message to the shopper, and offer them an alternative payment method.
Solving as a customer
Provide a different payment method or alternative card to complete the purchase. If the transaction restriction appears to be an error, contact the issuing bank via the number on the back of the card to ask if the block can be reversed.
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.