What Should I Do When a Customer's Payment Fails?

By Bill Stilwell · Last reviewed October 17, 2026

The short answer

When a payment fails, tell the customer quickly and kindly, give them a secure way to update their payment method, and retry on a set schedule. For recurring billing, your written terms should say how many retries happen and when service pauses. Log every failed payment and what you did about it.

What this means

A payment can fail for many reasons: an expired card, a new card number after fraud, not enough funds, or a bank flag. Many failures are honest mistakes. Your process should treat them that way while still getting you paid.

Say Evergreen Lawn Care bills customers monthly. If a card fails, the processor sends an automatic email with a secure update link, retries in a few days, and alerts the office. If it still fails after the last retry, the office calls the customer. Service pauses only after the steps in the customer’s agreement are done.

Why it matters

Lost revenue. Failed recurring payments quietly pile up if nobody’s watching.
Bad reviews. Cutting off service with no notice, or sending a threatening message over an expired card, makes people angry.
Security risk. Asking customers to read card numbers over the phone or send them by text puts their data at risk.
Disputes. Without a record of notices, it’s hard to show you were fair.

Who this applies to

Every business that takes card or bank payments. It matters most for recurring services, memberships, and anything billed automatically (see 26.3 Recurring Billing).

How to do it

Check what your payment processor can do: automatic retries, failed-payment emails, and card update links.
Write your retry schedule. Use your processor’s tools, and keep it to a set number of tries.
Write a short, friendly notice. Say the payment didn’t go through, give the amount, and include a secure link to update the payment method. Don’t assume the customer did anything wrong.
Never ask customers to send full card numbers by email or text. Use the secure link or a payment terminal (see 10.7.6 Payment Security).
Turn on an alert to the person who owns billing (see 18.9 Internal Notifications).
After the last retry, contact the customer by phone or another personal message before taking further action.
For recurring billing, put the retry and pause rules in your written terms before the customer signs up (see 11.1.6 Payment Terms). Follow them the same way for everyone.
If the balance stays unpaid, move to your late-payment process (see 16.6.5 Late Payments and Collections).
Log each failure, notice, retry, and result.

26.3.5 Failed payment (recurring billing)

For subscriptions and memberships, the same steps apply with one addition: decide in advance whether service pauses, continues for a grace period, or ends, and say so in your terms. Check your state’s rules on automatic renewals and recurring charges, since they vary (see 26.3 Recurring Billing).

What proof to keep

Your written retry schedule and notice template
Processor records of each failure and retry
Copies of notices sent and notes from follow-up calls
The signed terms that describe retry and pause rules

Common mistakes

No alert. Failed payments sit unnoticed for months.
Unlimited retries. Retrying over and over annoys customers. Use a set schedule.
Cold, threatening notices. Many failures are just expired cards. Write like a person.
Pausing service without warning. Follow your written terms and give notice first.
Taking card numbers over text. Always use a secure update method.

When to get help from a pro

Your payment processor can explain its retry and update tools. An attorney can review recurring billing terms and state rules. A bookkeeper can help track unpaid balances. Questions to ask:

What automatic retry and card update tools does my processor offer?
Do my recurring billing terms meet my state’s rules?
How should failed payments show up in my books?

Bill’s note

[Bill: add a short note. For example, how you handle a SiteSmarty client whose monthly card fails, or a time a kind notice saved a customer relationship.]

How I did this for SiteSmarty

[Date I did this:]
[What I actually did, step by step: the retry schedule, notice, and alert I set up for SiteSmarty]
[What it cost and how long it took:]
[What surprised me or what I’d do differently:]
[Screenshot or photo to add, with private info blurred: the processor’s failed-payment settings and notice template]
[Result so far:]

Questions people ask

Why did my customer’s payment fail? Common reasons include an expired or replaced card, not enough funds, or a bank security flag. Your processor usually shows a reason code.

How many times should I retry? Set a fixed number using your processor’s tools, then contact the customer directly.

How should customers update their card? Through a secure link or payment terminal, never by sending the number in an email or text.

When can I pause a recurring service? When your written terms allow it and you’ve given the customer notice. Check your state’s rules too.

Audit check

Question: Is there a written failed-payment process with set retries, friendly notices, secure updates, alerts, and a log?
Pass looks like: Processor retries on a set schedule, a kind notice with a secure link, an alert to the billing owner, pause rules in the terms, and a log.
Fail looks like: Failed payments nobody notices, card numbers collected by text, service cut off without notice, or no record.
Evidence to collect: Processor settings, notice template, sample failed-payment log, and the terms customers agreed to.

Where this fits

Do this first: 16.6.1 Payment Requests and Confirmation

Do this next: 16.6.5 Late Payments and Collections

Sources

Federal Trade Commission, "Protecting Personal Information: A Guide for Business" (checked October 17, 2026)
Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 17, 2026)

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.