How do I handle failed and declined payments?
Short answer
Notify the customer the moment a payment fails, with a simple way to retry or update their payment method. Set a short retry schedule for automatic charges, and escalate to a personal follow-up if it fails more than once.
Before you start
- Automated payment collection set up on invoices or plans.
- Notification templates ready for failed charges.
- A defined retry schedule for automatic billing.
- A staff process for manual follow-up on repeat failures.
Step by step
- 1
Notify the customer immediately
Send a message the moment a charge fails, not at the next billing cycle.
Most declines are simple issues like an expired card, easy to fix quickly if caught early.
- 2
Make updating payment details easy
Include a direct link for the customer to update their card or retry payment.
Extra steps to fix a failed payment mean many customers simply never do it.
- 3
Set an automatic retry schedule
Retry the charge a few days later before treating it as a serious issue.
Temporary declines often resolve themselves without any manual work.
- 4
Escalate after repeat failures
Move to a personal call or message after two or three failed attempts.
Automated messages alone rarely resolve a payment that keeps failing.
- 5
Pause related services if needed
For recurring plans, define when to pause service after extended non-payment.
Continuing service indefinitely with no payment creates real financial exposure.
- 6
Log every failure and resolution
Track the reason for the failure and how it was ultimately resolved.
Patterns in failure reasons can point to a card type or billing timing issue worth fixing.
- 7
Reconcile once resolved
Confirm the payment posts correctly against the original invoice once it succeeds.
A late payment needs to land on the same job it was originally billed for.
What good looks like
- Failed payments get resolved quickly instead of lingering unpaid.
- Customers have a fast, simple way to fix payment issues themselves.
- Repeat failures get personal attention before they become losses.
- Recurring revenue stays protected without indefinite unpaid service.
Common mistakes
The ways this goes wrong in money, and what to do instead.
Waiting for the next billing cycle›
A month passes before anyone notices a payment never went through.
Do this instead: Send a notification the same day any payment fails or declines.
No retry before escalating›
Treating every decline as urgent overwhelms staff with false alarms.
Do this instead: Set an automatic retry a few days out before involving a person.
Continuing service with no resolution›
Ongoing services keep running for months after payment fully stops.
Do this instead: Define a clear point where service pauses until payment is resolved.
Frequently asked
5 questions about handle failed and declined paymentsRelated guides
Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.
Do this next
The natural follow-on tasks once this one is working.
More in Money
Nearby tasks that share the same setup and vocabulary.
Was this guide helpful?
Tell us what worked and what didn't. It shapes what we rewrite next.
You didn't get into business to be in the tech business.
Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.