Support · Troubleshooting
Events arriving late or out of order
Stripe retries failed deliveries with exponential backoff, so events occasionally arrive minutes or hours late, occasionally reordered. Correctness survives; timing is what late arrivals tax.
Why correctness survives
Workers read live state rather than trusting payload snapshots, so a late event computes against the ledger as it exists now. Ordering races are additionally covered by the delay-plus-lock pair.
What latency actually costs
Detection latency is recovery-window time. An event arriving three hours late is three hours of payout-cycle decay on that finding — usually tolerable, occasionally decisive on instant-payout accounts.
The remedy
If a late window mattered, run a targeted historical re-scan for the affected period; it recomputes against current state and reconciles anything the delay blurred.