How RevenueCat Makes Money Despite App Store Holding Payments

How RevenueCat Makes Money (Even Though the App Store Holds the Subscription Payment)

When a user subscribes inside an iOS or Android app, Apple or Google processes the transaction and holds the money — RevenueCat never touches those funds. It's purely a middleman for tracking and infrastructure, not a payment processor for app store purchases. Here's how it still gets paid.

1. It bills the developer directly, separately from the app store payout

RevenueCat's fee is charged straight to the developer's own credit/debit card on file (via Stripe), on a normal monthly billing cycle — completely outside of Apple's or Google's payout pipeline. It never needs to intercept or redirect the subscription money itself.

2. Its fee is based on tracked revenue, not on holding funds

• Free for apps generating under $2,500/month in Monthly Tracked Revenue (MTR).
• 1% of MTR above that threshold, on the Pro plan.
• Custom/volume pricing for Enterprise customers with high transaction volume.

MTR is calculated on the gross revenue — before Apple/Google take their 15–30% platform commission — which RevenueCat can measure precisely because it validates every receipt and processes every server-to-server notification from Apple/Google in real time.

3. How it "sees" the revenue without holding it

• The app's purchases go through Apple/Google as normal (Apple/Google hold the cash and pay the developer on their usual schedule, e.g. monthly, net-30-ish).
• RevenueCat's SDK and backend validate each receipt/webhook, which lets it calculate MTR accurately — without ever being in the money's custody path.
• At the end of the billing period, RevenueCat looks at total tracked revenue and charges its 1% (above $2,500) directly to the developer.

4. Additional/optional revenue levers

• RevenueCat Billing and web-to-app funnels / web purchase button: for purchases made outside the app stores (e.g. via Stripe on the web), RevenueCat can be closer to the transaction itself and monetize those conversions too.
• Growth Tools (Paywalls, Experiments) can be used stand-alone with a developer's own purchase infrastructure, billed per conversion.
• Enterprise contracts: custom/negotiated pricing for large-volume apps, often flat-fee or volume-discounted instead of the 1% rate.

In short

RevenueCat's business model works precisely because it doesn't need to hold the subscription money. It earns by acting as the analytics/infrastructure layer that measures revenue accurately (via receipt validation), then invoices the developer a small percentage of that measured revenue on a normal billing cycle — independent of when or how Apple/Google actually release the cash to the developer.

Sources: revenuecat.com/pricing (accessed Sept 2026) and related pricing analyses.