Active subscription MRR
$64,280
Illustrative sample
30-day successful charges
$84,390
Illustrative sample
Active products
03
Illustrative sample
Last data sync
DEMO
No Stripe connection
Revenue terminalSample / offline
Example lifetime charge volume
$1,842,910
Sample calculation · no Stripe account or customer data is connected.
Active MRR
$64,280
Annualized run rate
$771K
Example MRR trendSynthetic
All chart values are synthetic demo data. Live profiles add Revenue/MRR/Churn and time-range selectors computed from dated charges.
Data boundary
Public metrics only. Charge responses may contain billing fields; the live app encrypts the raw response server-side, keeps it out of public profile data, and reveals it only to the credential-verified owner.
// Catalog snapshot
Revenue streams
NODE_01
API Studio
Annual plan
Example MRR$34,200
NODE_02
Indie Toolkit
Monthly plan
Example MRR$18,080
NODE_03
Workspace Pro
Team plan
Example MRR$12,000
// Activity sample
Recent charges
Fictional transaction IDs and amounts, shown for layout only. Live profiles publish aggregate metrics and catalog labels, never transaction records, customer names, emails, or payment details.
| DATE / ID | AMOUNT |
|---|---|
| APR 18ch_demo_8f3aSUCCEEDED | $249.00 |
| APR 17ch_demo_2c91SUCCEEDED | $99.00 |
| APR 16ch_demo_74e1SUCCEEDED | $1,200.00 |
| APR 15ch_demo_c620SUCCEEDED | $49.00 |
Scope status
No key was submitted. This page does not represent a verified Stripe connection.
// Demo scope manifest
The requested reads, not a live audit.
This sample shows the permission preset from the Stripe link. Live onboarding still needs key checks and a dashboard-level review of its complete grant set.
// Stripe restricted key
Requested permission set
- rak_charge_readREAD
- rak_subscription_readREAD
- rak_plan_readREAD
- rak_product_readREAD
Stripe does not expose a restricted key's complete grant list through its API. Endpoint probes confirm access only. Before publishing, the owner must review the complete key in Stripe Dashboard and attest that only these four read permissions are enabled.
Only charge/refund, subscription, plan/price, and product reads are requested. Connect-account and Files access are deliberately excluded; set them to None on an existing key or create a new key from this updated preset. Stripe responses can include billing or contact metadata; epic.li encrypts raw responses server-side and publishes aggregate metrics and public catalog labels only.