gocardless payment failed "insufficient_funds" on the second attempt

gocardless payment failed "insufficient_funds" on the second attempt

TL;DR

The account was short on funds twice, so retrying on the same schedule will likely fail a third time. Space out the next attempt, tell the customer the payment failed and when you will retry, and pause before the failures start costing fees or goodwill. Two failures is a pattern, not a fluke.

gocardless payment failed "insufficient_funds" on the second attempt

Steps

1. Confirm both failures are insufficient funds, not a mandate or account issue. Success check: the failure reason is identical on both attempts.
2. Notify the customer now: the payment failed twice, here is the amount, and here is the next retry date. Success check: the customer can fix the balance before the retry.
3. Schedule the next retry several days out, not tomorrow; back-to-back retries against an empty account fail the same way. Success check: the retry date gives the customer a real chance to fund the account.
4. Cap the retry count per your policy and define what happens at the cap: pause, dunning, or human outreach. Success check: the policy names the next step after the final retry.
5. If the pattern repeats across billing cycles, offer the customer a different payment day or method. Success check: the customer picks a day that matches their cash flow.

When this applies

• A GoCardless payment fails twice with insufficient funds.
• You need a retry schedule that does not just repeat the failure.
• Failed debits are starting to cost fees or customer patience.

When it doesn't

• First-attempt insufficient funds; one retry on schedule is usually fine.
• Mandate or bank-account failures; those need a new mandate.
• Disputed debits; those are customer intent, not empty accounts.

Tool + version compatibility

GoCardless payments and retry configuration (all current API versions).

"gocardless insufficient funds retry"

Space the retry out and tell the customer first.

"gocardless payment failed twice"

Two identical failures is a pattern; change the plan, not just the date.

"gocardless direct debit failed no funds"

Offer a different payment day before the next cycle.

Why it happens

Direct debit retries cost little per attempt but each failure is a signal: the account is empty on your schedule. Immediate retries hit the same empty account. Customers often just need notice and a few days; payroll lands, the account fills, the retry succeeds. Systems that retry blindly convert a cash-flow timing issue into a collections problem.

Edge cases / pitfalls

• Some banks charge per failed debit attempt; count the cost before scheduling many retries.
• Do not retry on weekends if the customer's funding pattern is weekday payroll.
• Track insufficient-funds rate per customer; chronic cases need a payment-day change, not more retries.
• Agent retry jobs must read the failure reason before each attempt; retrying a cancelled mandate as insufficient funds is a bug.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstkZa2IGGIJs1fVJA6t2cmw