Checkout test
Rehearse a real Stripe Checkout flow without charging a real customer.
Rehearse a real Stripe Checkout flow without charging a real customer.
What this feature is for
Checkout test creates a test-mode purchase, verifies signed webhook delivery, checks fulfillment, and records a trace that can be repeated after risky changes. 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 keys, a test price, a webhook endpoint reachable from Stripe, and the expected fulfillment record.
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
Select the price, start the test, complete the hosted flow with a test method, and wait for the trace to reach reconciliation.
- 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
The result shows Checkout, provider event, verified webhook, database fulfillment, and final reconciliation states. 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
Use only test-mode credentials. If the event is missing, inspect endpoint configuration and signature verification before changing application code.
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 Checkout test with Revenue Guard, Release desk, and Payment Sync. 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.