Check whether subscriptions and access agree.

Your subscription check, free in v0.1

You can create an account and review the setup. Running a check requires a verified account, a separately approved read-only Stripe connection and a supported account and access binding. Creating an account does not enable Stripe reads.

The check compares the supplied evidence. It does not change Stripe subscriptions, change your application's access, move money or enable continuous monitoring.

What the check needs

1. Review and authorize the read-only Stripe App connection. Stripe shows the actual requested permissions before installation.
2. Provide one Access Snapshot CSV for the supported access path. Include only the identifiers and access state needed for the comparison.
3. Confirm the expected access rules and account binding, then run the Integrity Scan.

The App requests only connected_account_read, subscription_read and plan_read. Review access and security boundaries.

Understand the result before acting

• A mismatch identifies a difference between subscription facts, the supplied access state and confirmed rules.
• A no-action result means the compared evidence agrees within the declared coverage.
• Unknown means evidence is missing, stale, unsupported or insufficient to make the comparison.

Each result shows coverage, freshness and a next step. A match does not certify everything in your business; a mismatch does not prove its root cause or authorize a corrective action.