BILLING EDGE-CASE LAB
Replay the event.
Check the access.
Catch duplicate credits, stale subscription updates, and access that survives cancellation.
Try the synthetic example below.
Use the local CLI to test your app’s actual access decisions.
Activate paid access
A paid subscription should unlock the customer’s account.
subscription.activeAlice starts a subscriptionAn active subscription grants access to its customer.
02 / YOUR APP, YOUR RULES
Keep the expectations.
Replace the demo adapter.
The CLI sends normalized test events to your adapter and checks the access decision returned by your application. Reports show the expectation and the observed result for each step.
A test adapter is required. These fixtures are not complete Stripe events, and passing this suite is not a security certification.
Download the CLI + examples Node.js 22+ · no runtime dependencies# See a seeded failure
node bin/billing-replay.mjs demo --mode vulnerable --html report.html
# Check your staging adapter
node bin/billing-replay.mjs run --suite examples/basic-suite.json --adapter ./your-adapter.mjs --json report.jsonExpectations are authored separately from the handler. A failed assertion returns a failing exit code.
03 / SCOPED INTEGRATION PILOT
Test one real
billing flow.
- One agreed staging billing flow
- Three agreed failure scenarios
- Replayable suite and evidence report
Developer preview. Scope is reviewed before payment. Production changes, a full security audit, and guaranteed bug discovery are not included.