Sign in Get started →
Demo Tools Metrics Library Pricing How It Works Sign in Get started →
How it works

Four steps from
your Stripe key
to traceable reports.

No payment processing. No card data. No broad permissions. You create a restricted key with exactly the permissions your plan needs and nothing else.

Setup & data flow
01
You create a restricted Stripe key
In Stripe Dashboard -> Developers -> API Keys you create a restricted key and choose exactly which data we can read. You stay in control. Delete the key in Stripe at any moment and we are immediately cut off, no emails, no process. The key cannot move money and this is a Stripe-enforced technical constraint, not our policy.
Read-only by design You choose permissions Cannot charge or refund No card PAN or CVV ever
02
We sync and normalize your billing events
From your Stripe account we read and nothing else: charges, invoices, subscriptions, refunds, disputes, and payouts. Every event is normalized into a consistent billing state: revenue, exposure, losses, recovery. If source data is missing or a permission is not granted, we return an explicit unavailable state. We never guess or fabricate a number.
Charges & invoices Subscriptions & refunds Disputes & payouts Multi-processor support
03
Reports are pre-computed in the background
Heavy aggregations run as background jobs and not on-demand when you open a page. When you load a report we return cached data fast. Each report payload includes a contract version, formula version, and payload fingerprint so you can reproduce the exact same number later and show it to an auditor.
Pre-aggregated, not live-computed Formula version locked per report Payload fingerprint for audit
04
Every number is traceable to a source event
We keep an append-only event trail for supported metrics. When a number changes you can see exactly why: which Stripe event caused it, when, and by how much. Duplicates and out-of-order events are deduplicated before they reach reporting. Corrections are new events, not silent edits.
Append-only event trail Duplicate event protection Export trace to CSV
⚠
Important: the Client Data addon needs your data, not just your key
Your Stripe key permissions are the same regardless of whether you add Client Data. What changes with the addon is whether you have uploaded CRM, usage, or support data. Dnoise cannot work around missing data and we never guess or fabricate data.

The rule is simple: base plan = Stripe data only. Client Data addon = Stripe data + your uploaded data. You can start on the base plan and add Client Data whenever you are ready to upload.
What happens without the Client Data addon
You're on the base $50 plan -> all billing and revenue reports work correctly.
You add the Client Data addon but haven't uploaded any data yet -> segmentation, cohorts, and usage-based LTV show a partial or unavailable state until you upload.
ℹ
Need the formulas behind the reports?
Dnoise does not stop at dashboards. The public Metrics Library documents how MRR, ARR, NRR, GRR, churn, Quick Ratio, and CAC payback are defined, compared, and benchmarked.
Stripe key permissions

One plan, one key. Below is exactly what your Stripe key needs, and what optionally uploading your own data adds on top.

Required - report won't work without it Recommended - partial data without it
Your Dnoise plan works with a single Stripe read-only key. This is the full permission set for every report and metric included in the base plan.
■chargesread
■customersread
■subscriptionsread
■invoicesread
■invoiceitemsread
■refundsread
■disputesread
■payoutsread
■productsread
■pricesread
■payment_intentsread
■tax_ratesreadrecommended
■subscription_itemsread
What's included
✓ All billing and revenue reports
✓ MRR movements (new, expansion, reactivation, contraction, churn)
✓ Insights from billing
✓ Metadata filtering
✓ Multi-processor compare
✓ Payment decline reasons
✓ Charge outcome analysis
— LTV with usage/CRM data
— Customer segmentation
— Cohort analysis
Multiple Stripe accounts in one workspace
Dnoise is architected to support multiple Stripe accounts within a single workspace and each with its own restricted key, sync state, and report set. Designed for consulting agencies and finance teams managing revenue across several products or legal entities.
SaaS founders
Multiple products or brands under one account. Compare MRR, losses, and recovery across all of them without switching workspaces.
Consulting agencies
Connect each client's Stripe account separately. View portfolio-level health or drill into any single client's billing data.
Multi-entity companies
Different legal entities with separate Stripe accounts. Consolidated view with per-entity breakdown and independent audit trails.
COMING SOON
Team access & roles
Dnoise is designed for teams, not just individuals. Register once, get your own workspace (tenant), and invite colleagues with different permission levels. Every workspace always has at least one owner.
Owner
Full control
Manage billing & plan
Invite & remove users
Connect Stripe accounts
View all reports
Delete workspace
Transfer ownership
Manager
Operational access
Manage billing & plan
Invite members (not owners)
Connect Stripe accounts
View all reports
Delete workspace
Transfer ownership
Member
Read-only access
Manage billing & plan
Invite users
Connect Stripe accounts
View reports
Delete workspace
Transfer ownership
Every workspace must always have at least one owner. Ownership can be transferred but not deleted.
COMING SOON
What Dnoise is not
✕
Not a payment processor
We never touch payment flows, card data, or settlement. Read-only access only.
✕
Not an accounting system
Operational analytics on a cash basis. Not GAAP/IFRS records.
✕
Not an AI recommendation engine
We surface billing facts. No predictions without your data.
✕
Not guaranteed strict real-time
Pre-aggregation with eventual consistency. Freshness metadata always shown.
Consistency model
Pre-aggregated
Heavy reports computed in background, not on page load
Eventual
Some metrics update with short delay and freshness always shown
Append-only
Event trail never edited and corrections are new events
Why a number changed
For supported metrics, every delta is backed by a source event. Not a chart and a traceable chain you can export to CSV and show to your accountant.
Mar 6, 18:15 UTCMRR-$200SUBSCRIPTION_CANCELLED · evt_sub_1
Mar 6, 19:05 UTCMRR-$100SUBSCRIPTION_UPDATED · evt_sub_2
Mar 6, 21:12 UTCMRR-$50SUBSCRIPTION_PAUSED · evt_sub_3
Total: -$350 explained. Read FAQ / Verification guide ->

Ready to see your numbers?

Connect Stripe in 5 minutes. First report is free.

Connect Stripe See demo first
No credit card required - Cancel anytime