Stripe Decline Code · Glossary
revocation_of_all_authorizations is the nuclear version of revocation_of_authorization — the cardholder has instructed their bank to revoke every active payment authorization associated with their card, not just the one with your merchant.
What It Means
What It Means
revocation_of_all_authorizations is the nuclear version of revocation_of_authorization — the cardholder has instructed their bank to revoke every active payment authorization associated with their card, not just the one with your merchant. This is a sweeping, account-level action that simultaneously cancels recurring billing permissions for every merchant that card is connected to — meaning your subscription isn't uniquely targeted, but it is absolutely stopped, and the customer's bank has classified this card as having zero active merchant authorizations going forward.
Not sure if this code is recoverable for your specific situation? Use the Stripe Failure Lookup →
Why It Happens
Why It Happens
What NOT to Do
What NOT to Do
✕ Never retry — not once, not ever
revocation_of_all_authorizations means the bank has voided every permission on this card. A retry attempt is not just futile — it is an unauthorized transaction attempt against a card that has had all merchant permissions explicitly wiped. The legal and chargeback exposure here is identical to retrying after revocation_of_authorization, but compounded by the fact that the bank has taken a formal account-level protective action.
✕ Don't treat it identically to revocation_of_authorization
The critical operational difference: revocation_of_authorization targets your merchant specifically — meaning the customer had a reason related to your subscription. revocation_of_all_authorizations is a card-wide sweep — meaning the customer may have no grievance with you specifically, making win-back and recovery significantly more achievable if you move quickly and frame your outreach correctly.
✕ Don't delay outreach waiting for the customer to contact you
Unlike codes where customers are aware they've acted against your merchant specifically, revocation_of_all_authorizations customers may not immediately realize your subscription was affected — especially if the revocation was bank-initiated (fraud protection) or triggered via a bulk "cancel all" feature. Fast, neutral outreach gets ahead of this before the customer churns passively.
Retry Timing
Retry Timing
Zero retries. The response is entirely a new payment method capture sequence — the old card is permanently unusable for any merchant authorization.
Recovery Benchmark
Recovery Benchmark
| Metric | Result |
|---|---|
| Overall recovery rate | 20–35% |
| Recovery from bank-initiated sweep (fraud/compliance) | 40–55% — customer still wants the subscription |
| Recovery from customer-initiated bulk cancel | 10–20% — partial intent to cancel |
| Recovery from account closure | 3–8% — card is gone permanently |
| Recovery via alternate payment method offer | +15–20% lift |
| Recovery with immediate, neutral Day 0 outreach | +20–25% vs. delayed outreach |
A 30–35% overall recovery rate is the realistic ceiling — and timing is the primary lever. revocation_of_all_authorizations has a narrow recovery window: customers who receive fast, neutral, no-blame outreach within 2 hours convert at 2–3x the rate of those contacted 24+ hours later. The bank-initiated fraud sweep subset especially — these customers actively want to continue their subscription once their card situation resolves.
At Scale
At Scale
Automated
Manual Escalation
FAQs
FAQs
What does the Stripe revocation_of_all_authorizations decline code mean?
revocation_of_all_authorizations means the cardholder's bank has revoked every active payment authorization on the card — not just yours. This is a card-wide sweep that cancels all standing merchant recurring billing permissions simultaneously. It can be triggered by the customer closing their account, using a bulk cancel feature in their banking app, or by the bank itself as a fraud protection measure.
What are the most common causes of a revocation_of_all_authorizations in Stripe?
Common causes include the bank performing a full authorization sweep after detecting card compromise, the customer closing or switching their card account, the customer using a bulk cancel all subscriptions feature in modern banking apps, a bank-initiated fraud protection sweep, or a bank compliance action placing the account in a state that voids all standing authorizations.
How is revocation_of_all_authorizations different from revocation_of_authorization?
revocation_of_authorization specifically targets your merchant — the customer had a reason related to your subscription. revocation_of_all_authorizations is a card-wide sweep that cancels all merchant authorizations simultaneously — the customer may have no specific grievance with you. This makes recovery more achievable for revocation_of_all_authorizations, particularly when the sweep was bank-initiated rather than customer-initiated.
Should I retry a payment after a revocation_of_all_authorizations decline?
Never. All payment permissions on this card have been voided. Retrying constitutes an unauthorized transaction attempt and creates direct chargeback exposure. Cancel all future scheduled charges on the card immediately and focus entirely on capturing a new payment method — new card, PayPal, bank transfer, or a local payment option — through fast, neutral outreach.
What is the recovery rate for Stripe revocation_of_all_authorizations failures?
Overall recovery rates are 20–35%. For bank-initiated fraud or compliance sweeps where the customer still wants the subscription, recovery rates of 40–55% are achievable with fast, neutral outreach within 2 hours. Customer-initiated bulk cancellations recover at 10–20%. Account closure cases have minimal recovery potential at 3–8%. Timing is the primary lever — outreach within 2 hours outperforms 24-hour-delayed contact by 2–3x.
What to do next
You are here
revocation_of_all_authorizations
Decline code reference
Check recoverability
Stripe Failure Lookup
See what's recoverable — and what isn't →
Then
Sign up for Recurflux
Automate recovery for every decline code →
Before you retry
Before you retry
Most revocation_of_all_authorizations failures are retried on the wrong schedule — which recovers the payment about 30% of the time. The other 70% leaves permanently. See what this code is actually costing at your MRR before deciding how to handle it.
Stop leaving revenue on the table
Recurflux handles code-specific retry scheduling, adaptive dunning, and dispute intelligence across all 30 Stripe decline codes. Connect in under 5 minutes.