Payment Sync
Catch paid sessions that never produce the entitlement your customer expects.
Catch paid sessions that never produce the entitlement your customer expects.
What this feature is for
Payment Sync reconciles completed Stripe Checkout sessions against the Supabase or database side effect configured as fulfillment proof. It catches silent revenue drift. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
Stripe test or live credentials, a safe fulfillment query, and a clear mapping from paid session to customer access.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Run a snapshot, open any drift row, follow the event and webhook trace, correct the handler or data path, then rerun until the gap is reconciled.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
Evidence includes session identifier, event state, expected fulfillment, observed fulfillment, and reconciliation time. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Do not retry a payment blindly. First determine whether the webhook was absent, rejected, processed late, or wrote the wrong record.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Payment Sync with Checkout test, Revenue Guard, and Incidents & fixes. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.