Debit Not Authorized
What This Means
The debit transaction was not authorized by the cardholder or account holder. This typically appears for ACH or debit card transactions where the bank requires explicit prior authorization. SaaS businesses should verify the customer agreed to the charge.
Retrying will likely fail again. The customer needs to update their payment method or contact their bank.
Common Causes
- 1Debit authorization was not properly established before charging
- 2Customer disputes having authorized the recurring debit
- 3Bank requires a specific debit authorization format not provided
Recovery Tactics
- 1Verify that proper debit authorization was obtained from the customer
- 2Send the customer a new authorization form or agreement to sign
- 3If using ACH, ensure NACHA-compliant authorization is in place
How healthy is your Stripe account?
Get a free churn health report. Find pending cancellations, failed payments, and expiring cards putting your MRR at risk.
Run Free AuditRelated Decline Codes
FAQ
Do I need explicit authorization for debit transactions?
Yes, especially for ACH debits. You need written or electronic authorization from the account holder before initiating debit transactions. This protects against unauthorized charges and chargebacks.
How is this different from a chargeback?
This is a real-time decline, not a retroactive dispute. The bank is blocking the charge at the time of processing because proper authorization is not on file. A chargeback reverses a charge that already went through.
How healthy is your Stripe account?
Get a free churn health report. Find pending cancellations, failed payments, and expiring cards putting your MRR at risk.
Run Free Audit