Error codes
Hard decline
Stripe
revocation_of_authorization
The card was declined for an unknown reason.
What does revocation_of_authorization mean?
The revocation_of_authorization decline code is returned when the cardholder has instructed their issuing bank to stop allowing a specific merchant's recurring charges. This is different from a general dispute — the customer is using their Regulation E / chargeback rights to pre-emptively block future billing from your business specifically.
Is it a soft or hard decline?
revocation_of_authorization is a hard decline. The block is intentional and targeted. Retrying the same card will continue to fail until the customer re-authorizes the merchant or provides a new payment method.
Common root causes
The customer tried to cancel the subscription and couldn't find a clear cancel flow, so they called their bank instead
A billing dispute that was escalated to the issuer rather than resolved with the merchant
The customer forgot they had the subscription and blocked it as unauthorized
Shared or family payment methods where one user revoked access
Recommended recovery steps
Do not retry with the same card. The revocation is logged with the issuer and will keep failing. Additional retries risk further chargebacks.
Make cancellation easy and obvious. Customers who revoke authorization usually do so because they couldn't cancel through your product.
Request a new payment method through proactive outreach. If the customer still wants the service, collecting a different card or bank account is the only path forward.
Audit your billing disclosures. Clear receipts, descriptor names, and renewal reminders reduce revocations substantially.
How FlyCode handles revocation_of_authorization
FlyCode's ML models classify revocation_of_authorization as a hard decline and immediately stop retry logic that would otherwise waste attempts and risk additional chargebacks. Instead, FlyCode's AI outreach engine reaches out to the customer through the optimal channel and at the optimal moment to request a new payment method — preserving the customer relationship where possible, while protecting merchant standing with the networks.
What does revocation_of_authorization mean?
The revocation_of_authorization decline code is returned when the cardholder has instructed their issuing bank to stop allowing a specific merchant's recurring charges. This is different from a general dispute — the customer is using their Regulation E / chargeback rights to pre-emptively block future billing from your business specifically.
Is it a soft or hard decline?
revocation_of_authorization is a hard decline. The block is intentional and targeted. Retrying the same card will continue to fail until the customer re-authorizes the merchant or provides a new payment method.
Common root causes
The customer tried to cancel the subscription and couldn't find a clear cancel flow, so they called their bank instead
A billing dispute that was escalated to the issuer rather than resolved with the merchant
The customer forgot they had the subscription and blocked it as unauthorized
Shared or family payment methods where one user revoked access
Recommended recovery steps
Do not retry with the same card. The revocation is logged with the issuer and will keep failing. Additional retries risk further chargebacks.
Make cancellation easy and obvious. Customers who revoke authorization usually do so because they couldn't cancel through your product.
Request a new payment method through proactive outreach. If the customer still wants the service, collecting a different card or bank account is the only path forward.
Audit your billing disclosures. Clear receipts, descriptor names, and renewal reminders reduce revocations substantially.
How FlyCode handles revocation_of_authorization
FlyCode's ML models classify revocation_of_authorization as a hard decline and immediately stop retry logic that would otherwise waste attempts and risk additional chargebacks. Instead, FlyCode's AI outreach engine reaches out to the customer through the optimal channel and at the optimal moment to request a new payment method — preserving the customer relationship where possible, while protecting merchant standing with the networks.
What does revocation_of_authorization mean?
The revocation_of_authorization decline code is returned when the cardholder has instructed their issuing bank to stop allowing a specific merchant's recurring charges. This is different from a general dispute — the customer is using their Regulation E / chargeback rights to pre-emptively block future billing from your business specifically.
Is it a soft or hard decline?
revocation_of_authorization is a hard decline. The block is intentional and targeted. Retrying the same card will continue to fail until the customer re-authorizes the merchant or provides a new payment method.
Common root causes
The customer tried to cancel the subscription and couldn't find a clear cancel flow, so they called their bank instead
A billing dispute that was escalated to the issuer rather than resolved with the merchant
The customer forgot they had the subscription and blocked it as unauthorized
Shared or family payment methods where one user revoked access
Recommended recovery steps
Do not retry with the same card. The revocation is logged with the issuer and will keep failing. Additional retries risk further chargebacks.
Make cancellation easy and obvious. Customers who revoke authorization usually do so because they couldn't cancel through your product.
Request a new payment method through proactive outreach. If the customer still wants the service, collecting a different card or bank account is the only path forward.
Audit your billing disclosures. Clear receipts, descriptor names, and renewal reminders reduce revocations substantially.
How FlyCode handles revocation_of_authorization
FlyCode's ML models classify revocation_of_authorization as a hard decline and immediately stop retry logic that would otherwise waste attempts and risk additional chargebacks. Instead, FlyCode's AI outreach engine reaches out to the customer through the optimal channel and at the optimal moment to request a new payment method — preserving the customer relationship where possible, while protecting merchant standing with the networks.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is revocation_of_authorization a soft or hard decline?
Can revocation_of_authorization be recovered by retrying?
No. The block is issuer-level and targeted at your merchant descriptor. Retrying will continue to fail and can increase chargeback risk. A new payment method is required.
How does FlyCode handle revocation_of_authorization?
FlyCode detects hard declines like revocation_of_authorization and skips wasted retries. It immediately triggers AI-driven outreach asking the customer for a new payment method at the optimal moment.
