Verify the payment-to-access path
Test Stripe safely, reconcile fulfillment, and catch revenue drift before it reaches customers.
Revenue protection begins where ordinary payment monitoring ends. A successful Stripe charge is not the customer outcome; the outcome is a paid customer receiving the expected access in your application. The Revenue workspace traces that chain—from checkout to webhook to fulfillment—and helps you catch the drift that quietly becomes churn, refunds, and support tickets.
Map the payment to the entitlement
Connect Stripe and the data service that represents access, typically Supabase, in Connections. Confirm which event creates fulfillment: a subscription row, role, credit balance, entitlement, or account flag. PreFlight needs this mapping to distinguish a completed Stripe session from a customer who can actually use the product.
Use test-mode credentials while setting up. Nothing in a rehearsal should charge a real customer.
Run a safe checkout test
Open Checkout test and run the synthetic flow. PreFlight begins a Stripe test-mode checkout, observes the signed provider event, and waits for the expected fulfillment side effect. The saved trace gives you a concrete answer to the question every subscription SaaS should ask: does a paid test customer get access?
Read Payment Sync
Payment Sync reconciles completed Stripe sessions against the database state that should exist after fulfillment. A clean snapshot means the expected records are present. Drift means the customer path needs attention: inspect the event, webhook destination, signature verification, application logs, and the database mutation before retrying blindly.
Use the trace to isolate the broken handoff. Stripe success plus webhook failure is a different problem from a received webhook that never updates the entitlement.
Keep an eye on the money signal
Use MRR Pulse for the revenue view and schedule the test or reconciliation through Revenue Guard where your plan supports it. Run it after deploys that touch billing, auth, webhooks, or data access. The goal is not an impressive chart; it is early detection of a payment path that has silently stopped delivering value.