← Blog
Square·July 29, 2026·6 min read

How to Set Up Failed-Payment Recovery (Dunning) for Square

Square has no real dunning beyond a few subscription retries. Here’s how to set up proper failed-payment recovery for Square — decline-aware retries, branded card-update emails, and expiry warnings.


Square doesn’t have a real dunning system. It retries a failed subscription invoice a few times, can fire off a generic reminder email, and stops there. No decline-aware retry timing, no emails from your own brand, no one-click card-update page, and nothing at all for failed one-time invoices. If you run memberships or subscriptions on Square, setting up proper dunning is the single highest-ROI thing you can do — it’s the 20–40% of churn that’s involuntary. Here’s how.

What a real dunning setup includes

  • Decline-aware retries. Retry soft declines on a card-network-safe schedule (≥24h apart, capped), and never retry a hard decline that can’t work.
  • A branded email sequence. Four touches over ~two weeks (day 0/3/7/14), from your verified domain — not a generic Square address — each with a one-click card-update link.
  • A hosted card-update page. Where a customer taps once to drop in a new card and the payment retries itself, with no login.
  • Expiry warnings. Nudge customers before the card on file expires, so the charge never fails.
  • Auto-stop on success. Every retry and email halts the instant the payment clears — no one gets dunned after they’ve paid.

The DIY path (and why it’s hard)

You can approximate this with Square’s API and a spreadsheet: poll for failed invoices, track decline codes, schedule retries, send emails, and record who paid. In practice it’s a real engineering project — webhook handling, idempotent re-charges (so a retry never double-charges), quiet-hours logic, unsubscribe handling, and coordination with Square’s own retries. Most sellers who start this abandon it.

The fast path: a Square-native recovery tool

The quicker route is a tool built for exactly this. With Recoup, setup is roughly:

  • Connect Square via OAuth (about ten minutes, read-first).
  • Set your retry policy — schedule, max attempts, and cap window — or keep the safe defaults.
  • Verify your sending domain so dunning goes out as your brand.
  • Turn it on. Every failed payment now recovers automatically.
Because Recoup is a flat monthly fee with no revenue share, you keep 100% of what it recovers — unlike Stripe-world tools that skim 20–30% of every win-back (and don’t support Square anyway).

See how it compares to the alternatives, or read what Square does and doesn’t do on its own in does Square retry failed payments.

FAQ

Does Square have dunning?

Only barely. Square retries a failed subscription invoice a few times and can send a generic reminder email. There’s no decline-aware retry schedule, no own-domain branded emails, no one-click card-update page, and no recovery for one-time invoices.

How do I set up dunning for Square?

Connect a Square-native recovery tool via OAuth, set your retry schedule and email sequence, verify your sending domain, and turn it on. It then handles every failed payment automatically — retries, card-update emails, and re-charges.

What is a good dunning email sequence?

A four-touch sequence over about two weeks — day 0, 3, 7, and 14 — sent from your own domain, each with a one-click card-update link, and stopping the instant the payment clears. Hard declines skip the retries and go straight to the card-update ask.

Recover failed Square payments automatically.

Recoup retries declined Square charges on a smart, decline-aware schedule and duns from your own domain — flat monthly, no revenue share. Connect Square read-only and see what you can recover.