Paid Up

Guide

When a client misses a payment plan instalment

Most missed instalments are fixable: a card with no funds, an expired card, a bank account that changed. Read the failure reason, retry only when a retry can work, tell the client the same day, and give a fixed number of days to catch up before your cancellation terms apply.

SWritten by Sam Ade · Facts checked Nov 17, 2026 · Updated

The short answer

  • Read the reason before you retry. "Insufficient funds" is worth retrying in a few days. "Lost card", "account closed" or "instruction cancelled" never is: you need a new card or bank details.
  • Tell the client the same day, in a plain, friendly email: what failed, how much, when you'll try again, and a link to update their card or bank.
  • Retry two or three times over about a week for soft card declines; for US bank debits returned R01 or R09, at most twice within 180 days; for UK Direct Debits marked "refer to payer", once the client says the money is there.
  • Give a fixed catch-up period (14 days is common) and put it in writing. After it, your cancellation terms decide what you keep.
  • Plan for this from the start: finish the last instalment weeks before the date, so a failed payment can be chased while you still have time to re-book.

Why this is different from an overdue invoice

Most advice about late payment is written for overdue invoices: work already done, a bill sent, money owed. The usual steps there are reminders, late fees, a final demand and, in the end, a collections agency or small-claims court.

A missed instalment on a booking is a different problem. The work hasn't happened yet. You're holding a date (a Saturday in June, a retreat week, a studio term) that you could sell to someone else, and every week that passes makes it harder to re-book. The client usually still wants the service; their card expired, their pay came late, or they moved banks. So the goals are different:

  • Fix the payment method fast, because most failures are technical, not refusals.
  • Find out early if the client can't or won't go ahead, because a cancellation 4 months out is far cheaper for you than one 4 weeks out.
  • Keep the relationship. This person is going to be at the event you're working.

It's a real cost when this goes wrong. Small businesses in online booking-software communities describe losing thousands over a few years to plans that weren't paid, and a common fix is to require autopay. Autopay helps, but only with a plan for the payments that still fail.

Card declines: soft, hard and fixable

When a saved card is charged without the client present (an "off-session" payment), the issuer either approves it or returns a decline. Stripe passes on a decline code (why) and, where the network gives one, an advice code (what to do next). The advice code is the quickest guide: try_again_later means a retry can work, confirm_card_data means the client must fix their details, and do_not_try_again means stop using that card for this payment (Stripe, Card declines).

Most declines come back as a generic "do not honor" or generic_decline, and issuers only explain the detail to their own cardholder. That's why the client, not you, usually has to call their bank.

Common card decline codes on an instalment and what to do
Decline code (Stripe)What it meansRetry?What to ask the client
insufficient_funds, withdrawal_count_limit_exceededNot enough money or credit right nowYes, in 2–4 days (after payday helps)Pay from another card now, or confirm when funds are in
card_velocity_exceeded, invalid_amountOver a spending or single-payment limitOnce, after the client raises the limitCall the bank to allow the payment, or use another card
processing_error, issuer_not_available, reenter_transactionA temporary fault at the bank or networkYes, the same or next dayUsually nothing; tell them only if it fails again
authentication_requiredThe bank wants the client to confirm (3D Secure / SCA)No, not off-sessionOpen their payment link and approve the payment
expired_card, incorrect_number, incorrect_cvcThe saved card details no longer workNoAdd the new card on their link
lost_card, stolen_card, pickup_card, restricted_cardThe card is blocked; Stripe says to present this as a generic declineNever"Your bank declined the card; please add another"
do_not_honor, generic_decline, call_issuerDeclined, no reason givenOnce or twice at mostCall the bank or use another card
revocation_of_authorization, stop_payment_orderThe client told their bank to stop your paymentsNeverTalk to them: this is usually a decision, not a glitch

Codes and next steps from Stripe's decline codes page, read Nov 17, 2026. Other processors use different names for the same issuer responses.

Card network retry limits. Networks don't want merchants hammering a card. Stripe recommends no more than eight retries for a charge that permits retries. As summarized by PayPal (a secondary source; check with your own processor): Visa treats any retry of a "Category 1" decline (issuer will never approve) as excessive and allows up to 20 reattempts in 30 days on other declines before charging fees, and Mastercard charges fees for retries after a "do not try again" merchant advice code (MAC 03) or a cancelled-payment code (MAC 21). A payment plan never needs anywhere near these numbers: two or three tries is enough, and if they fail, a person needs to talk to the client.

US bank debits: ACH return codes

ACH debits don't fail on the spot. Stripe says it can take up to 4 business days to learn whether an ACH Direct Debit succeeded (Stripe, ACH Direct Debit). If it's returned, the bank gives a Nacha return code. The code decides whether you're allowed to try again.

ACH return codes you'll see on payment plan debits
CodeMeaningReturn windowCan you retry?
R01Insufficient funds2 banking daysYes, up to 2 more times within 180 days, identical entry marked RETRY PYMT
R09Uncollected funds (money is there but not yet available)2 banking daysYes, same limits as R01
R02Account closed2 banking daysNo. New bank account and authorization needed
R03 / R04No account found / invalid account number2 banking daysNo. Ask for correct details (verify them by bank login if you can)
R07Authorization revoked by the customer60 calendar daysNo. Talk to the client; you need a new authorization
R08Payment stopped2 banking daysOnly if the client authorizes it again
R10Customer says the debit wasn't authorized60 calendar days (consumer accounts)No. Treat it as a dispute (see our disputes guide)
R29Business account holder says it wasn't authorized2 banking daysNo, without a new authorization

Meanings and windows from EPCOR's Return Reason Code Resource (an ACH payments association, 2021 edition) and Nacha's rules summary, read Nov 17, 2026. Nacha's Reinitiation Rule requires a retried entry to have identical content and the description "RETRY PYMT". Check current rules with your provider; your processor may handle reinitiation for you.

Watch your return rates. Nacha monitors originators whose unauthorized returns (R05, R07, R10, R11, R29, R51) pass 0.5% of debits, whose administrative returns (R02, R03, R04) pass 3%, or whose overall returns pass 15% (Nacha). For a small business on Stripe, Stripe sits between you and Nacha, but repeated returns can still lead Stripe to block a bank account: Stripe says it may block an account after a "blockable" return until the problem is fixed.

Notice before a changed debit. If you move an ACH instalment to a new date after a failure, Stripe's docs say you must give the client at least 7 calendar days' notice of a change in timing of recurring preauthorized debits. If the amount changes, Regulation E (12 CFR 1005.10(d)) expects written notice at least 10 days before. A same-amount retry under the Reinitiation Rule is different from a reschedule, but the safe habit is to tell the client the new date in writing every time.

UK Direct Debit: Bacs failure codes

A Bacs Direct Debit also fails late. Stripe says it typically takes 4 business days to confirm success or failure when the mandate is already in place (Stripe, Bacs Direct Debit). Unpaid collections are reported through Bacs ARUDD reports, which GoCardless says are generated the day after the payment was due (GoCardless, ARUDD messages). Cancelled mandates arrive separately, on ADDACS reports.

Bacs ARUDD reason codes and what to do
ARUDD codeMeaningWhat to do
0 – Refer to payerThe bank refused it, usually for lack of funds. GoCardless calls it by far the most common reason.Contact the client, agree a date when the money is there, collect again. The mandate still works.
1 – Instruction cancelledThe client cancelled the Direct Debit with their bankDon't retry. Ask why; they need to set up a new Direct Debit (or pay another way) to stay on the plan.
2 – Payer deceasedThe account holder has diedStop collections and handle it personally.
5 – No accountThe account is closed or doesn't existAsk for new bank details and a new mandate.
6 – No instructionNo valid Direct Debit Instruction at the bank (for example after a bank switch went wrong)Set up a new mandate before collecting again.

Code meanings from GoCardless and Bacs participants' published tables, read Nov 17, 2026. If you collect through Stripe, Stripe shows its own failure reason and cancels the mandate where needed, rather than raw ARUDD codes.

Retrying. For its own invoices, Stripe will retry a failed Bacs payment caused by insufficient funds up to 2 times, within 30 days of the first attempt. That's a sensible ceiling for a payment plan too. Each Bacs collection also needs advance notice: the Direct Debit Guarantee promises notice of a change "normally 10 working days" ahead "or as otherwise agreed", and Stripe sends its own notice email before each debit. So say clearly in your plan's terms that a failed payment may be collected again, and email the new date before you do.

A retry calendar that finishes before the date

The calendar matters more than the wording. A failed payment needs roughly a week to retry and two more to catch up, so the last instalment should land well before the event. Here's a worked example.

The booking: a US wedding photographer, $8,400 package, wedding on Sat, Aug 21, 2027, booked Jan 15, 2027. $2,100 deposit at booking (25%), then six monthly card payments of $1,050 on the 3rd, Feb 3 to Jul 3. The last payment is 49 days before the wedding.

The May instalment fails: what happens, and how much time is left
  1. Reminder
  2. Second reminder
  3. Card declinedClient emailed
  4. Retry 1 failsYou're alerted
  5. Retry 2 failsFirm notice
  6. Catch-up deadlinePaid, or release the date

96 days to re-book the dateWedding · Sat, Aug 21

Retry calendar for a missed May instalment on an $8,400 booking
DateWhat happensWho acts
Mon, Apr 26Reminder: "$1,050 will be taken on May 3"Automatic
Fri, Apr 30Second reminder, 3 days beforeAutomatic
Mon, May 3Card declined: insufficient_funds. Client emailed the reason and the next try date, with a link to change cardAutomatic
Wed, May 5Retry 1 fails. Client emailed again; you get an alertAutomatic, then you
Wed, May 5Personal message from you (template 2 below)You
Fri, May 7Retry 2 fails. No more automatic triesAutomatic
Fri, May 7Firm notice in writing: pay by May 17 or the booking is treated as cancelled (template 3)You
Mon, May 17Catch-up deadline (14 days after the first failure notice). Paid: carry on. Not paid: final notice and release (template 4)You
Sat, Aug 21Wedding. If you released on May 17, you had 96 days to re-book the date–

If the same failure happened to the last payment on Jul 3, the 14-day catch-up would end on Jul 17, still five weeks before the wedding. That's the reason to set the final payment date first and work backwards: last payment + a week of retries + your catch-up period + the time you'd need to re-book or cut your losses. Paid Up won't let a plan's last payment fall later than 14 days before the date for exactly this reason; 30 to 60 days is more comfortable for weddings. Our payment plan calculator works the dates out for you.

UK version, by Direct Debit. A £6,000 wedding with a £1,500 card deposit and six £750 Direct Debits on the 1st of each month. If the £750 collection on Mon 1 March 2027 comes back "refer to payer", you'll typically know by Thursday 4 March. Email the client that day, agree a date when the money will be in, give notice of the new collection date, and collect again. Allow about a week per Bacs attempt rather than the two days a card retry takes.

Reminder wording: friendly, firm, final

Three rules: say exactly what failed and how much; give one clear action and a date; never threaten anything you can't or won't do. Square brackets are yours to fill in. For a full pre-event sequence (deposit, each instalment, final balance), see our payment reminder email templates.

1. Friendly: the day it fails

Subject: Your [Month] payment for [event] didn't go through

Hi [Name],

The [amount] payment for [event] on [event date] didn't go through today. Your bank gave the reason as "[insufficient funds / card expired]". Nothing else changes and there's no fee.

We'll try again on [date]. If you'd like to use a different card or bank account, you can change it here: [link].

Thanks,
[Your name]

2. Personal: after the second failure

Hi [Name], just checking in personally, as the [amount] payment for [event] has now failed twice. Is everything OK? If the timing's difficult this month, tell me and we can look at moving this payment to later in the plan, as long as everything is paid by [last payment date]. Otherwise, updating the card here will sort it: [link].

3. Firm: catch-up deadline

Subject: Action needed by [deadline] to keep [event date]

Hi [Name],

We still haven't been able to take the [amount] due on [due date] for [event]. Under section [X] of our agreement, payments must be up to date within [14] days of a missed payment. Please pay by [deadline] using this link: [link].

If we haven't received it by then, we'll treat the booking as cancelled under our cancellation terms, and your date will be released. If something has changed and you need to cancel or postpone, please tell me now: the earlier we know, the more options we both have.

4. Final: releasing the date

Subject: Your booking for [event date] has been cancelled

Hi [Name],

As the [amount] due on [due date] wasn't paid by [deadline], we've cancelled your booking for [event date] under section [X] of our agreement, effective today. You've paid [paid so far]. Under our cancellation terms we'll keep [amount kept] and refund [amount refunded] within [N] days [or: no refund is due]. If we re-book the date, [what your terms say]. No further payments will be taken.

What to leave out: late fees your contract doesn't mention, "legal action" you won't take, messages to the client's family or employer, and anything sent at odd hours or every day. In the UK, a threat to take action that can't legally be taken is a factor in an "aggressive practice" under section 228 of the Digital Markets, Competition and Consumers Act 2024, and harassing someone with payment demands calculated to cause alarm or distress is an offence under section 40 of the Administration of Justice Act 1970.

Releasing the date and keeping what you're owed

You can only release the date and keep money if your signed agreement says how. Before any booking, check that your terms cover four things:

  1. A catch-up period. For example: "If a payment is still unpaid 14 days after we tell you, we may treat the booking as cancelled by you." Our free payment plan agreement uses this wording, with 14 days as the default.
  2. What "cancelled by you" costs. Tiered by how close the date is (for example, deposit only more than 6 months out, 50% between 3 and 6 months, 100% inside 3 months). See our cancellation policy template.
  3. Re-booking. Many terms promise to refund what you recover if you re-book the date, minus reasonable costs. In the UK, this helps show your charges reflect a real loss rather than a penalty.
  4. No surprise fees. If you want a late fee, it must be in the agreement and proportionate. Many event businesses use none.

Worked example. Back to the $8,400 booking. On May 17 the client has paid the $2,100 deposit plus three $1,050 instalments: $5,250. Suppose the terms say: deposit non-refundable; cancelling 3–6 months before the date costs 50% of the total. The wedding is 96 days away, so the client owes 50% of $8,400 = $4,200. You keep $4,200 and refund $1,050. If the terms had said "deposit only" for that window, you'd keep $2,100 and refund $3,150. The arithmetic is simple; what matters is that the client signed it before paying anything.

UK caution. Under the Consumer Rights Act 2015, a term letting you keep more than your likely loss can be unfair and unenforceable against a consumer. A non-refundable deposit is normally fine if it's a reasonable amount; keeping 100% of instalments months before the date is much harder to defend. See our non-refundable deposit guide, and have a solicitor check your tiers.

When the client is a business (a company retreat, a corporate event), consumer fairness rules mostly don't apply and the contract governs. Get the purchase order or the authorized signer's name before you start the plan.

US vs UK: notice and tone

Differences between the US and UK when chasing a missed instalment
United StatesUnited Kingdom
Usual bank methodACH debitBacs Direct Debit
Notice before a moved bank debit7 calendar days for a timing change (Nacha, via Stripe); 10 days for a changed amount (Reg E)Normally 10 working days, or as agreed in the mandate (Direct Debit Guarantee)
Retry limit (bank debits)R01/R09: 2 more tries within 180 daysNo fixed scheme count; Stripe's own retries stop at 2 within 30 days
Law on chasingFederal FDCPA covers third-party collectors, not you collecting your own bookings; some states (such as California's Rosenthal Act) also cover businesses collecting their own debtsDMCC Act 2024 (aggressive practices); harassment offence in s.40 Administration of Justice Act 1970
Fair terms testContract law; liquidated damages must be a reasonable estimate, not a penalty (varies by state)Consumer Rights Act 2015, Part 2 fairness test
Tone that reads wellDirect and warm: "Can you update your card by Friday?"Polite and specific: "Could you update your card by Friday 7 May?"

The US state-law point is a general flag, not a full survey. If you're in a state with its own collection law, ask an attorney whether a pre-event instalment counts as a "debt" there.

Decision table

What to do for each kind of missed instalment
SituationRetry?Do todayIf still unpaid
Card: insufficient funds or a temporary errorYes, 2 more times over ~a weekFriendly email with change-card linkPersonal message, then catch-up deadline
Card: expired, wrong details, needs authenticationNoAsk for a new card or approval on their linkCatch-up deadline
Card: lost, stolen, blocked, "do not try again"Never"Your bank declined the card, please add another"Catch-up deadline
ACH R01 / R09Yes, max 2, within 180 daysEmail with the retry dateAsk for another payment method
ACH R02 / R03 / R04NoAsk for new bank details and authorizationCatch-up deadline
ACH R07 / R08 / R10, Bacs code 1NoCall or email: did they mean to stop paying?Treat as a likely cancellation; follow your terms
Bacs code 0 (refer to payer)Yes, once funds are confirmed (max ~2)Email, agree a date, give noticeCatch-up deadline
Client says they want to cancelNoConfirm the cancellation in writing with the figuresYour cancellation tiers apply
Client asks for more timeOn the new dateAgree a new date before your last-payment date; put it in writingCatch-up deadline, no second extension

What Paid Up does, and doesn't

Paid Up handles the automatic part of the calendar above, so you only step in when a person is needed:

  • Reminders: an email 7 days and 3 days before every automatic payment, with the amount, the date and the card or account it will come from.
  • Retries: a failed payment is tried 3 times in all, 2 days apart. Every failure emails the client with the bank's reason, the next try date (or that there won't be one), and their link to change card or bank. From the second failure, you get an email too, or from the first if the payment can't be retried.
  • Client fixes it themselves: from their link the client can switch card or bank, pay the missed payment now, or pay off the rest, without stopping the plan.
  • You stay in control: from the booking you can try a payment again now, or mark it paid if the client paid another way.
  • The date is protected: every plan finishes at least 14 days before the service date, so there's always time to retry and chase.

Limits, honestly: Paid Up retries a failed payment twice, two days apart, except when the bank says not to: lost, stolen, closed or blocked cards, "do not try again" declines, and bank debits returned for a closed, missing or invalid account or as not authorised get no retry, and you're told straight away so you can ask the client for another card or bank account. It doesn't send texts, it doesn't charge late fees, and it doesn't cancel a booking for you: releasing the date is your decision, under your terms. Card and bank payments go through your own Stripe account, so Stripe's fees and rules apply.

Questions people ask

How many times should I retry a failed card payment?

Two or three tries spread over a week is plenty for a payment plan. Retry only soft declines such as insufficient funds; a card reported lost or stolen, or a decline with Stripe's do_not_try_again advice, won't go through however often you try. Stripe recommends no more than eight retries for any one charge, and card networks charge fees for excessive reattempts.

Can I charge a late fee when an instalment fails?

Only if your signed agreement says so, and the fee is a fair estimate of your cost rather than a penalty. In the UK, a fee that's out of proportion can be unfair under the Consumer Rights Act 2015. Many event businesses choose no late fee and a firm catch-up deadline instead, because the real risk is losing the date, not a few days' delay.

Can I cancel the booking if the client misses one payment?

Only if your terms allow it, and it's usually wiser to give a fixed catch-up period first (14 days is common) and say in writing what happens after it. If the client still doesn't pay, treat it as a cancellation by the client: your cancellation tiers decide what you keep and what you refund.

What does 'refer to payer' mean on a Direct Debit?

It's Bacs ARUDD reason code 0. The payer's bank refused the collection, most often because there wasn't enough money in the account. The mandate is still in place, so you can collect again once the client confirms the money is there.

Should I retry an ACH payment returned as R01?

Yes, an R01 (insufficient funds) or R09 (uncollected funds) return can be reinitiated, at most twice, within 180 days of the original entry, and the retry must be identical and labelled RETRY PYMT. Don't retry R02, R03, R07, R08 or R10 returns: you need new bank details or a new authorization first.

Is it legal to keep the deposit if a client stops paying?

Usually, if your agreement says the deposit is non-refundable and the amount is a reasonable pre-estimate of your loss. In the UK, keeping instalments beyond your actual loss can be challenged as unfair. Check your own terms with a lawyer before you rely on them.

Sources

  1. Stripe: Decline codes: every card decline code and Stripe's suggested next step (read Nov 17, 2026)
  2. Stripe: Card declines (retries and advice codes): advice codes do_not_try_again / try_again_later / confirm_card_data; Stripe recommends at most eight retries (read Nov 17, 2026)
  3. PayPal: How to avoid excessive retries penalties: summary of Visa and Mastercard reattempt rules and fees (secondary source; check with your processor) (read Nov 17, 2026)
  4. Stripe: ACH Direct Debit: up to 4 business days to confirm, 60-day consumer dispute window, 7 days' notice of a timing change, retries (read Nov 17, 2026)
  5. Nacha: ACH Network risk and enforcement topics: Reinitiation Rule (identical entry, "RETRY PYMT"), return-rate thresholds (read Nov 17, 2026)
  6. EPCOR: Return Reason Code Resource (2021): R-code meanings, 2-banking-day vs 60-day time frames, when you may reinitiate (read Nov 17, 2026)
  7. Stripe: Bacs Direct Debit: 4 business days to confirm, mandate cancellation, up to 2 automatic retries within 30 days (read Nov 17, 2026)
  8. GoCardless: ARUDD messages: ARUDD 0 (refer to payer) and 1 (instruction cancelled), what to do for each (read Nov 17, 2026)
  9. Direct Debit: The Direct Debit Guarantee: 10 working days' notice of a change "or as otherwise agreed" (read Nov 17, 2026)
  10. Digital Markets, Competition and Consumers Act 2024, s.228 (aggressive practices): UK: harassment, coercion and threats of action that can't legally be taken (read Nov 17, 2026)
  11. Administration of Justice Act 1970, s.40: UK offence of harassing debtors (read Nov 17, 2026)

About this page

General information, not legal advice. Card network and Nacha rules change; check current rules with your payment provider, and have a lawyer or solicitor check your cancellation and late-payment terms. Spotted something out of date? Tell us at [email protected] and we'll correct it.

Let the retries and reminders run themselves.

Paid Up reminds the client before each payment, retries a failed one twice, and tells you when it needs a human. Every plan finishes before the date.