Docs
Integrate RevLint for the private beta.
The usable path is the same for a free scan and a paid workspace: authenticate, connect Stripe read-only, create an ingest token, send app-state, run Revenue Pulse, then inspect findings.
- 1Free scan
Start from the Stripe Revenue Leak Scan and create the workspace context.
- 2Auth and setup
Sign in, land in settings, and confirm the private beta workspace.
- 3Connect Stripe
Use the read-only OAuth path. Never paste secret keys.
- 4Create ingest token
Generate a one-time token and send app-state snapshots.
- 5Run audit
Run Revenue Pulse after Stripe and app-state are present.
- 6Inspect findings
Review evidence, impact, recipes, and evidence packets.
1. Connect Stripe
Install the Stripe OAuth integration using read-only permissions. Do not paste secret keys or webhook secrets.
2. Send app-state
POST active users, entitlements, plan, Stripe customer IDs, and subscription IDs to the snapshot API with an ingest token.
3. Send evidence events
Emit terms accepted, login, feature usage, cancellation, refund, and support events for Evidence Readiness.
Snapshot example
POST /api/v1/app-state/snapshot
Authorization: Bearer <ingest_token>
{
"users": [{
"externalUserId": "user_123",
"appStatus": "active",
"entitlementStatus": "premium",
"plan": "pro",
"stripeCustomerId": "cus_123",
"stripeSubscriptionId": "sub_123"
}]
}Evidence event example
POST /api/v1/events/support
Authorization: Bearer <ingest_token>
{
"events": [{
"externalUserId": "user_123",
"stripeCustomerId": "cus_123",
"type": "TERMS_ACCEPTED",
"occurredAt": "2026-05-10T15:00:00.000Z",
"raw": { "policyVersion": "2026-05" }
}]
}Read-only by design
RevLint watches the signals. Your team stays in control.
RevLint mirrors and ingests revenue signals, generates deterministic findings, and packages evidence. It does not cancel subscriptions, issue refunds, change Shopify orders, mutate your production database, or submit disputes automatically.