Stripe and App Store revenue in one dashboard

Updated 2026-08-04

This is the most common revenue split in indie software: a web product billing through Stripe, and an iOS app billing through Apple. It is also the hardest pair to reconcile by hand, and the reason FRGMNT exists.

Why this is genuinely hard

It isn't laziness that stops people adding these two numbers up. The platforms disagree on almost every dimension that matters.

	Stripe	Apple App Store
Latency	Near real time	Reports delayed, typically a day+
Fee model	Gross reported, fee itemised	Proceeds reported already net of 15–30%
Access	REST API, restricted key	Signed JWT, gzipped TSV reports
Period	Exact timestamps	Apple's fiscal calendar
Currency	Per-charge currency	Consolidated with Apple's FX

Add Stripe's gross to Apple's proceeds and you have added a pre-fee number to a post-fee number. The result isn't wrong by a rounding error — it's wrong by somewhere between 15% and 30% of your Apple revenue.

What "one number" actually requires

To combine these honestly you have to:

Normalise the fee basis. Either compare gross to gross, or net to net. Mixing them is the most common mistake.
Normalise the billing interval. An annual iOS subscription and a monthly Stripe plan are not comparable until both are expressed per month. See how to calculate MRR.
Accept different latencies. Your Stripe figure is live; your Apple figure is yesterday's. A combined number is only ever as fresh as its slowest source, and a tool that hides this from you is lying by omission.

Where FRGMNT is today

Being straight about it, because this pairing is the one people arrive for:

Stripe side: complete. True MRR from active subscriptions, today's cash net of fees and refunds, and a live ledger. See the Stripe integration.
App Store side: authentication and key validation only. The Sales and Trends reporting pipeline is still in development, so App Store revenue does not yet contribute to the combined figure. The app shows this status rather than a misleading zero. See the App Store integration.

So today, FRGMNT gives you a complete real-time picture of the Stripe half and a connected-but-not-yet-reporting Apple half. If the Apple half is the part you need right now, wait for that pipeline before buying.

What to do in the meantime

If you need a combined figure today, the honest manual approach is:

Take Stripe MRR from FRGMNT — interval-normalised and already correct.
Take Apple's proceeds (not gross) from App Store Connect's Sales and Trends, for a full month.
Divide any annual iOS subscriptions by twelve before adding.
Compare like with like: either add Apple proceeds to Stripe net, or gross up Apple's figure by your commission tier.

It's tedious. That tedium is the entire product thesis.

Also selling one-off products?

Plenty of people running this split also sell templates or courses on the side. Those are cash, not MRR — see Stripe + Gumroad for why keeping them separate matters.

Frequently asked

Can I see Stripe and App Store revenue in one place?

FRGMNT connects to both. Stripe reports True MRR and today's cash today; the App Store integration currently authenticates and validates, with sales reporting still in development. So the combined figure is Stripe-complete and Apple-pending.

Why can't I just add the two numbers together?

Apple reports proceeds after its commission on a delayed schedule, in a different currency basis, with a different definition of a period. Stripe reports gross and fees separately in near real time. Adding the headline figures compares two different things.

Does Apple's 15% or 30% commission get subtracted?

Apple reports proceeds already net of commission. Stripe reports gross with fees itemised. This is one of the main reasons naive addition overstates or understates your true position.