Production contracts for billing and access

Output

What a failed check looks like

Contracts

Deterministic. Fail-closed.

• Revenue leak

  Active billing subscription, but has_paid_access is false in your database.

• Wrongful access

  Cancelled or unpaid subscription, but the user still has paid access.

• Plan drift

  Price ID maps to pro in config, but the user row says starter.

• Duplicate customer

  Same billing customer ID linked to multiple app users.

Config contract: scan process.env references vs .env.example.

Nightly checks: schedule the Action, optional Slack on fail/warn, upload runs to your dashboard. See scheduled workflow example.

Install

Run in under a minute

# Demo — no credentials
npx prodverdict check access \
  --config examples/nextjs-stripe/prodverdict.yml \
  --fixtures \
  --fixtures-dir examples/nextjs-stripe/scenarios/fail-revenue-leak

# Live — Stripe or Paddle + Postgres
npx prodverdict check access --config prodverdict.yml