What it is
For each payment adapter and each account enabled on it, the sweep lists settled payments from the last three days and replays any session not already recorded, through the same idempotent recorder the webhook uses.
Also called: missed webhook · payment didn't register · reconciliation · deploy window
See it
How it works
- 1The cron iterates every registered payment adapter.
- 2Each adapter lists the accounts it is configured for.
- 3Settled sessions in the lookback window are listed.
- 4Anything already recorded is skipped; anything missing is replayed.
- 5Counts of scanned, recovered, already-ok and failed are returned.
Why we built it
The route states the purpose: 'Safety net for the payment webhook. If a webhook is ever lost (deploy window, transient outage, misconfigured endpoint), this sweep re-drives it... This is what makes "automatically updates the invoice once paid" robust.'
The problem
- A webhook lost during a deploy or outage left an invoice permanently unpaid.
- Reconciliation was a manual comparison against the payment dashboard.
Sound familiar?
What you get
Missed payments self-heal within hours.
The sweep is provider-agnostic, so a second processor is covered automatically.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →