Trust the evidence.
Keep control.
A focused check. Clear boundaries. Your decision on what happens next.
What the check can read
- Stripe account identity
- Read-only
- Subscriptions and items
- Read-only
- Prices and plans
- Read-only
- Access snapshot
- You provide it
- Changes to Stripe or your product
- None
Only what the comparison needs.
Six access fields. No full database export, personal names, emails or secret keys.
A result with its limits.
A subscription state is not invoice-payment proof. Supplied access records are not live observation of product use.
Separate sources. Separate controls.
Removing an access snapshot clears its dependent rule and result detail. Disconnecting Stripe is a different action.
Permissions and data handling
No Stripe password, live secret API key or authentication cookie is required. The check makes no changes to Stripe or your product.
What can the Subscription Integrity connection access?
The check requests read-only account identity, subscriptions and subscription items, and prices/plans. It compares those facts with the access snapshot and rules you provide. It does not change Stripe or your product. Review the actual Stripe permission screen before installing; cancel if it requests other permissions.
- Three read-only permissions
- No payments, disputes or write access for this check
- Connection and uploaded-data withdrawal are separate
The permissions for this check
- connected_account_read: bind the selected Stripe account.
- subscription_read: read subscriptions and subscription items.
- plan_read: read prices and plans used by those subscriptions.
Review the actual Stripe screen before installing. If it requests other permissions, cancel. Your workspace shows whether the supported source is available; a requested permission is not an established grant.
Upload only the access data you need
Review the CSV template, limits and retention notice before uploading. Source contents and results require current workspace and source authority. Data that is stale or unavailable is not shown as a current result.
Read access snapshot handling and withdrawalCan Recovra move payouts or issue refunds?
No. Recovra does not use Stripe access to move payouts, transfer funds, issue refunds, change bank details, change account settings, use customer payment methods, or manage subscriptions and invoices.
How do I disconnect Stripe or remove access data?
Review or disconnect the check's connection from Recovra. You can also remove the app in Stripe to revoke its provider permissions. Withdraw an uploaded access snapshot separately through Sources, then Manage data, even after Stripe disconnect; this removes its retained payload and dependent rule/result detail. Disconnecting Stripe does not withdraw a snapshot.
You stay in control.
Your workspace uses only the sources you authorize. The public Sample stays synthetic and separate. Share only the information needed for the check; never passwords, live secret keys, card credentials or unrelated sensitive evidence.
Ready to see the evidence?
Explore the sample