57 | Transaction not permitted
This code indicates the issuer declined the authorization because the transaction type is not permitted for the account.
What This Code Means
Response code 57 (“Transaction not permitted”) is returned when the issuer’s rules do not allow the requested transaction type for the card or account. Issuers apply controls based on account configuration, card product rules, risk settings, and transaction category. This decline is not primarily about funds availability; it is about permission and policy. The code indicates the issuer recognized the request but rejected it due to account-level restrictions. It does not automatically imply the card is invalid or expired; it indicates the authorization request is outside what the issuer will permit.
Where Users Usually See This Code
- Payment gateway declines for certain purchase categories or transaction flows
- POS terminal declines for restricted transactions
- Processor authorization logs showing response code 57
Why This Code Appears
- Account product does not allow the transaction type (e.g., certain cash-like transactions)
- Issuer restrictions limit specific merchant categories or channels
- Account-level settings restrict certain card-present or card-not-present flows
- Transaction permissions are limited due to issuer risk controls
What Typically Happens Next
- Authorization is declined and the transaction does not settle
- Merchant sees a permissions-based decline code
- Reattempting the same transaction type may result in the same decline while restrictions remain
What This Code Is Not
- It is not an invalid amount (see 13)
- It is not a generic “do not honor” (see 05)
- It is not an issuer downtime error (see 91)
Troubleshooting Checklist
- □ Review transaction attributes recorded in authorization logs (channel, type, category)
- □ Compare against prior successful transactions for the same account type, if available
- □ Document the response code for support handling and reconciliation
- □ Use official processor/acquirer support workflows when 57 occurs repeatedly for valid-looking requests
Notes And Edge Cases
Issuer permission rules can differ between card-present and online transactions, and between domestic and international contexts. Some declines that appear similar to merchants may be coded as 57 or 62 depending on issuer policy mapping. The code does not specify which permission rule triggered the decline; detailed context is typically available only through issuer/acquirer support channels. In some environments, merchant configuration can influence how certain transaction types are categorized, affecting whether issuer rules allow them.