Skip to content

The method

How a number gets on this site

A revenue figure is only worth reading if you know where it came from. Here is exactly what happens between a founder's payment provider and the number on their profile — including what we cannot verify.

1. The founder connects a read-only key

Verification starts with the founder granting us the narrowest credential their provider offers. We test it immediately, and only store it if the test call succeeds — so a key that does not work is never saved.

RevenueCat

Provider docs

In RevenueCat, open Project settings → API keys and create a new V2 secret key. Give it one permission: charts_metrics:overview:read. That key can read your revenue charts and nothing else — it cannot see customers, issue refunds, or change anything in your project.

App Store Connect

Provider docs

In App Store Connect, go to Users and Access → Integrations → App Store Connect API and create a key with the Sales and Reports role. Download the .p8 file — Apple only lets you download it once. Your vendor number is on the Payments and Financial Reports page. Apple publishes sales data a day behind, so figures from this source lag by one day.

2. The key is encrypted before it reaches the database

Credentials are encrypted with AES-256-GCM using a key held only by the server, then written to a table that no browser session can read. The founders who add them cannot read them back either — reconnecting always means entering the credential again.

3. Revenue is re-read every day

A figure that was true last quarter is not verification. Every active connection is re-read daily and written to an append-only history, which is what draws the chart on each app page. Profiles show the last sync time so you can judge freshness yourself.

App Store Connect publishes sales data a day behind, so apps verified through that route show a data as of date rather than today's.

4. Multiple providers add up, they don't double-count

An app billing through both in-app purchase and a web checkout can connect both. Each provider is stored separately and summed once per day, so connecting a second source cannot inflate a figure.

What this does not prove

Verification confirms that a provider account reports this revenue. It does not audit the business behind it. Specifically, it cannot tell you:

  • Whether refunds and chargebacks have been fully deducted — that depends on how the provider reports.
  • Whether the connected account belongs solely to the app shown, if a founder ships several apps under one provider project.
  • Profit. Every figure here is revenue, before Apple's cut and costs.

We state these limits rather than round them off. If you are buying a business on the strength of a number here, ask for provider access directly.

Superwall

Superwall is not currently a connectable provider. It issues public SDK keys only, and publishes no API for reading revenue charts, so there is no way for us to verify a figure through it. We would rather list nothing than a badge we cannot stand behind. If that changes, we will add it.

Ready to verify your app?

Connecting takes about two minutes and needs one read-only key.

Questions about the method? About this site.

How verification works · IosAppMRR