What transaction not allowed means
The bank refused this type of transaction on this card. Stripe classifies it with the unknown-reason declines and points the customer at their issuer, but the practical meaning is narrower than a generic decline: something about the shape of the charge, not the balance, was refused. Recurring charges, card-not-present charges and cross-border charges are the usual candidates.
Why it happens
- The card is a debit, prepaid or corporate card with recurring billing disabled.
- The cardholder or the bank has blocked online or card-not-present transactions.
- The card is restricted to a region and your Stripe account bills from another.
- A corporate card's controls do not permit this merchant category.
What Stripe does on its own
Retrying an identical charge will usually produce an identical refusal, because nothing about the transaction has changed. This is the decline where waiting for Stripe's retry schedule is least likely to pay off.
Bank decline codes you may see alongside transaction_not_allowed
Your customer's bank sends its own numeric code, which Stripe surfaces separately from its decline_code. The same number means different things on different card networks, and Stripe does not publish a strict one-to-one mapping between them, so treat these as codes commonly seen with this failure rather than as equivalents.
| Code | Network | What the network calls it |
|---|
57 | Visa | Transaction not permitted to cardholder. |
58 | Visa | Transaction not allowed at terminal. |
62 | Visa | Restricted card (card invalid in this region or country). |
57 | Mastercard | Transaction not permitted to issuer / cardholder. |
5C | Visa | Transaction not supported/blocked by issuer. |
119 | American Express | Not enrolled / permitted. |
Quoted from Stripe's network decline codes reference.
The recovery playbook
- Do not wait for the retry cycle to finish. The condition is structural, so the same charge will be refused the same way.
- Email promptly with the hosted invoice link and ask the customer to pay with a different card — ideally a personal credit card rather than a debit, prepaid or corporate card.
- Say plainly that the bank blocked this type of payment rather than that the payment failed. It tells the customer what to change, and it is the truth.
- If the customer wants to keep the same card, the fix is on their side: the bank has to allow recurring or online transactions on it. Only they can request that.
- Watch for a cluster of these from one region or card type. It usually points at a billing-configuration issue rather than a run of unlucky customers.
Highly recoverable, but only by changing card — not by retrying. The customer almost always still wants the subscription; their card simply cannot do this kind of charge.
The email to send
This is the exact template MRRdue's recovery assistant suggests for transaction_not_allowed cases. Copy it, swap the details, and send it from your own address.
Subject: Let's keep your subscription running
Hi Alex,
Your $49.00 payment is still pending (your bank doesn't allow this type of payment on that card), and I wanted to reach out personally so nothing gets interrupted on your end.
Here's a secure link to update your payment details — it only takes a minute:
https://invoice.stripe.com/i/…
If something doesn't look right, or you're not sure what changed, just reply here and we'll help you figure it out.
Thanks so much,
Your SaaS
More variants (and retention-risk templates) in the free recovery email template gallery.
Stop working declines from a spreadsheet
MRRdue imports your failed payments with read-only access, ranks them by recoverable dollars and decline reason, and drafts this email for every case. You stay the sender.