Decline code 57: Transaction Not Permitted to Cardholder
By Sean Weas · Co-Founder, Product & EngineeringReviewed by Travis SteffenUpdated 3 min readQuick answer
Decline code 57 — “Transaction Not Permitted to Cardholder” — is an issuer decline meaning the cardholder’s account is not authorized for this specific type of transaction (often recurring, card-not-present, or international charges). Under the ISO 8583 standard it’s a hard decline, so retrying the same charge won’t clear it. Stripe surfaces this as the transaction_not_allowed decline_code, and Authorize.net returns it as a generic “Declined” (reason code 2). Recovery needs the cardholder to authorize the charge or use a different card.
What code 57 means
Don't blind-retry a 57 — the issuer is saying this card is not allowed to make this kind of transaction, so the same charge will keep failing. Recover it with customer outreach to fix the card or the restriction, not back-to-back re-attempts.
Cross-processor equivalents
The same issuer decision surfaces under a different code on every processor. Here is how code 57 maps across the stacks Revatto recovers on.
Why it happens
- The card is not enabled for recurring or subscription billing — some debit and prepaid cards block automated repeat charges by default.
- The issuer blocks card-not-present or online transactions on the account, so an e-commerce or subscription charge is refused.
- The card type or account is restricted from this merchant category or from international transactions.
- A prepaid, gift, or corporate card with usage limits the issuer hasn’t itemized as a separate code.
- An issuer-side account control the cardholder has to lift directly with their bank before the charge can go through.
How to recover it
- 1Don’t re-run the same charge — a 57 is an account-level restriction, so repeated attempts just inflate your decline ratio without changing the outcome.
- 2Reach the customer on a channel they actually answer — email and SMS — and explain their bank declined this type of charge on the card.
- 3Ask them to either authorize recurring charges with their issuer or update the payment method to a card that allows the transaction, then re-attempt once the card is fixed.
- 4When the customer doesn’t self-serve, a real person — not another automated email — works the card update directly. That AI-plus-human handoff is exactly what Revatto does for you: AI-timed retries where the processor API supports them, plus email, SMS, and human outreach, fully done-for-you. You only pay if it works — 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.See how Revatto recovers 57declines →
See what Revatto would recover for you
Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.