How this is verified

This person is an authorised operator of online payment accounts that have processed this much real customer revenue, over this period, from these sources.

It does not say the person is profitable, a good teacher, or good at ads. It verifies a measurable fact.

Successful customer payments—the full amount the customer paid, including tax—minus refunds and lost disputes. Payment and platform fees are ignored.

It is a simple, consistent turnover figure, not a profit figure.

Verified: first verified sale. Steel: $10K+. Titanium: $100K+. Platinum: $250K+. Carbon: $1M+. Obsidian: $10M+, by invitation. Tiers are earned by verified net revenue only. Nothing purchasable changes a tier, and tiers never regress.

Sales, revenue checkpoints and tiers count the moment they are read from a connected source. There is no settlement hold. Refunds and lost disputes are subtracted as they arrive, so figures can move down as well as up. Tiers, once earned, never regress.

Some platforms only let us read part of an account's history. When that happens the profile says “verified since” a date, and revenue before that date is not counted. The displayed figure covers only the history we can verify; it is not necessarily all revenue ever earned.

Revenue is displayed in USD. We keep the source ledger amount and currency and convert non-USD records using the available exchange rate for the transaction date. If a conversion rate is unavailable, the sync reports an error rather than treating that currency as USD.

Stripe MRR summarizes current recurring subscription commitments normalized to one month. It is separate from collected revenue and uses current exchange rates. Active and past-due fixed-price subscriptions are included; trials, paused collection, canceled subscriptions and one-off charges are excluded.

Recurring discounts are reflected. Unsupported pricing, unavailable permissions or stale data hide the figure rather than displaying a misleading zero. Every connected Stripe account for that business must provide usable subscription data. Other providers are not included in the Stripe MRR figure.

MRR appears by default only when it is positive. The business can hide it or choose exact or range visibility. Existing restricted keys may need Subscriptions and Coupons read access.

• Whop: paid payments, refunds and lost disputes returned by the account key; no history cap is documented, so coverage starts at the earliest record the source returns.
• Dodo Payments: successful live payments and refunds, plus accepted or lost disputes; test-host records are excluded and no history cutoff is documented.
• Stripe: the balance ledger for payments, refunds and dispute reversals; available history depends on the restricted key's read scopes and Stripe's API allocation.
• Shopify: paid, non-test orders, refunds and Shopify Payments disputes; access normally begins with 60 days of orders and grows from connection unless full-history access is granted.
• Paddle: completed transactions and their refund or chargeback adjustments, read with a read-only API key.
• Lemon Squeezy: paid, non-test orders and their refunded amounts, read with a read-only API key; disputes are not exposed by the API and are stated as uncovered.
• Gumroad: sales and refunds, read with an access token; chargebacks are not exposed by the API and are stated as uncovered.

• We never read or store card data.
• We never store customer identities; source identifiers are hashed for counting.
• No write access is used: connections are read-only where scoped keys exist, and we never make write requests.
• We never include test-mode data.
• Verified revenue never includes projections or future payments. Optional MRR is labelled separately as a recurring commitment.

Operators choose, per metric, whether to show an exact figure, a range, or only that the figure is verified. The default is a range. A hidden figure was still verified.

Refund rate. Unique customer count. Active months. Coverage window. Whether each connection is live, stale or disconnected. Disconnecting freezes history rather than deleting it.