How payment events keep member access in sync

The event-driven model

You never manually flip a member from paid to unpaid. Payment providers notify your platform the moment something happens — a new subscription, a successful renewal, a failed charge, a cancellation, a pause, a refund — and membership access updates automatically to match. This is what lets you sell while you sleep.

Stripe: nothing to configure

Once you've connected Stripe under Payments, its events flow to your platform automatically — there's no webhook setup on your side. Signups grant access, cancellations schedule access to end at the period close, and refunds revoke access, all without your involvement.

ThriveCart: one-time webhook setup

If you use ThriveCart as your checkout, you register your platform's webhook URL once in ThriveCart (the setup checklist under Integrations → ThriveCart walks you through it). From then on it behaves the same way: purchases create members, rebills extend access, failed payments mark accounts past-due, and cancellations, pauses, resumes, and refunds all sync automatically. Abandoned checkouts are captured to your Leads page so you can win them back.

Safety nets

Webhooks can occasionally be missed by any system, so a daily automatic reconciliation compares your member records against the payment provider and corrects drift. Admins can also trigger a resync for an individual member, and the AI assistant can report a member's sync status if you ask.

Every incoming event is verified (signed by the provider) and scoped to your platform only. If you ever suspect a member's access is wrong, check their page in Members — and prefer resyncing from the provider over hand-editing billing state.