Payment Status Sync

Covers what breaks after basic webhook handling is in place: events arriving out of order, status that looks stale to the user mid-flow, and building a status display that accurately reflects every sub-state without confusing users. Assumes idempotency and basic event handling already exist (see subscription-fullstack).

Discovery

Before writing anything, answer:

1. Do you have a webhookEvent deduplication table? If not, add one before this skill adds anything useful.
2. What's the user-visible status page? Account settings, a dedicated billing page, or a banner in the app header?
3. Retry behavior: How many payment retry attempts does Stripe make before marking unpaid? (Configurable in Stripe Dashboard — default is 4 over ~4 weeks.)
4. Dunning emails: Sent by Stripe Smart Retries, your own system, or both?

Core Patterns