5 Best Subscription Billing Platforms When You Have Outgrown Apple IAP

Summary

Apple's 30% commission is a massive operating expense—$150,000 for every $500K in revenue—which a 2025 court ruling now allows US developers to bypass.
The biggest risk in leaving Apple's IAP is conversion drop-off; a clunky checkout experience can easily erase any savings by driving away customers.
This guide compares five top billing platforms (Allocents, Stripe, Chargebee, Paddle, RevenueCat) to help you choose the right solution based on your app's scale and engineering resources.
For a purpose-built migration, Allocents offers a drop-in SDK designed to move subscribers to direct billing without sacrificing the native user experience.

Your app just crossed $500,000 in Annual Recurring Revenue. Congratulations — that's a genuine milestone. But after a quick look at your P&L, a sobering reality sets in: your single largest operating expense isn't your AWS bill or even your headcount. It's the 30% commission you're handing to Apple every single month.

At $500K ARR, that's $150,000 a year — gone. At $1M ARR, you're writing Apple a $300,000 check annually. And for the first time, you're asking a very reasonable question: does it have to be this way?

The answer, as of April 2025, is no. The landmark Epic v. Apple ruling permanently barred Apple from forcing US developers to use its In-App Purchase (IAP) system, unlocking what analysts estimate is over $150 billion in annual IAP volume. For developers with meaningful scale, this is the most significant monetization shift in mobile history.

But here's the honest catch: moving away from IAP isn't just flipping a switch. There's a real developer dilemma here. Users are comfortable with IAP — it's one tap, Face ID, done. Research consistently shows that "reducing friction in the checkout process has been proven time and again to increase conversion rate," and a clunky web redirect can absolutely hurt your numbers. As one developer bluntly put it about poorly-executed alternatives: "you are going to lose too many customers trying to avoid them."

The goal, then, isn't just to escape the 30% fee — it's to find the best subscription billing platform that lets you save money without sacrificing the native experience that got you to this revenue level in the first place.

This guide is written specifically for that decision. Here are the five platforms worth evaluating, who each one is actually built for, and the hard numbers on what switching can mean for your bottom line.

The 5 Best Subscription Billing Platforms for Apps That Have Outgrown IAP

1. Allocents — Built Specifically for IAP Migration

Best for: Mobile-first app developers with $500K to $20M+ ARR who want a drop-in, fully managed solution built specifically for moving off StoreKit.

Allocents is the only platform on this list designed from the ground up for the post-Epic IAP migration problem. Because it was purpose-built for this transition, Allocents understands StoreKit at a level most billing vendors simply don't. That context matters enormously when you're building the tooling to replace it.

How it works: Allocents offers a single SDK (supporting Swift/SwiftUI, Kotlin, Flutter, and React Native) that slots into your existing app alongside StoreKit. You don't rip anything out overnight. Instead, you introduce direct billing gradually — and that's one of its core differentiators.

Key features:

Sign Up & Save paywalls — new users see a side-by-side choice: App Store billing or a discounted direct billing option
Switch & Save campaigns — native prompts that migrate your existing StoreKit subscribers to direct billing
Gradual rollout — start showing direct billing to just 10% of your user base, monitor conversion and revenue metrics, then scale up with instant rollback if anything looks off
StoreKit product sync — automatically pulls your existing products from App Store Connect so you're not re-entering everything manually
Native web checkout with Apple Pay and Google Pay support, so the experience doesn't feel foreign to users
Smart cancellation flows with discount offers and pause options built in
Full Merchant of Record (MoR) — Allocents handles payments, sales tax remittance across 190+ countries, chargebacks, fraud protection, and customer support

Pricing: 5% + 50¢ per transaction. That's it. Compared to Apple's 30%, the math is straightforward.

For larger teams with existing Stripe infrastructure, Allocents also offers a Bring Your Own Stripe (BYOS) option at just 0.5% of successfully migrated revenue — you remain the MoR but use Allocents' migration SDK and UI flows.

Who it's NOT for: Developers outside the US (the Epic ruling is currently jurisdiction-specific, though Allocents is expanding globally). Teams with deeply custom billing infrastructure who want full control over every layer may prefer building on Stripe directly.

The 15-minute integration claim and the gradual rollout model directly address the two biggest fears developers have: implementation complexity and conversion risk. For anyone who's thought "it's the hidden complexity most folks that have never implemented monetization don't realize initially," this is the platform designed to absorb that complexity for you.

2. Stripe Billing — Maximum Flexibility, Minimum Hand-Holding

Best for: Engineering-heavy teams that want full control over their billing stack and are comfortable building their own migration flows, UI, and compliance infrastructure.

Stripe Billing is the gold standard for payment infrastructure. If you need a powerful, globally trusted payment processor and your team has the development bandwidth to build everything around it, Stripe gives you more flexibility than any other platform on this list.

As TechCrunch covered, Stripe has published guidance for iOS developers on bypassing Apple's commission — but it provides the engine, not the car. There's no native migration SDK, no Switch & Save campaign tooling, no gradual rollout mechanism. You're building all of that yourself.

Key features:

Supports recurring, usage-based billing, tiered, and flat-rate pricing models
Payments across 135+ currencies and 100+ payment methods
AI-powered Smart Retries that recover an average of 9% more failed recurring payments
Comprehensive developer documentation and API coverage

Pricing: Approximately 2.9% + 30¢ per transaction — but remember, as MoR, you are responsible for sales tax, chargebacks, fraud, and customer support across every jurisdiction you operate in. Those costs add up fast, especially internationally.

Who it's NOT for: Teams without a dedicated engineering resource to build and maintain the migration infrastructure. Stripe won't hold your hand through an IAP transition — it's infrastructure, not a solution. If your concern is "handling taxes/VAT if you sell outside your country," Stripe requires you to solve that yourself or layer on additional tooling.

3. Chargebee — The Enterprise Web SaaS Choice

Best for: Web-based SaaS companies with complex billing logic — tiered pricing, multiple product lines, revenue recognition requirements — and strong integrations with accounting systems.

Chargebee is a mature subscription management platform with deep capabilities around dunning, proration, revenue recognition, and integrations with tools like NetSuite, QuickBooks, and Salesforce. If you're running a B2B SaaS with a web-first sales motion, it's a credible choice.

Key features:

Advanced subscription billing lifecycle management (upgrades, downgrades, pauses, cancellations)
Built-in dunning and smart retry logic
Strong accounting integrations for revenue recognition
Support for complex billing logic across multiple pricing dimensions

Pricing: Tiered plans based on features and revenue volume.

Who it's NOT for: Mobile-first app developers. Chargebee's iOS support is limited — there's no native SDK for in-app migration flows, no StoreKit sync, and no tooling to move existing subscribers off IAP. It's a strong web billing platform being evaluated for the wrong use case if you're primarily monetizing through an iOS app. It's also worth noting that developer communities have flagged support issues as an ongoing concern with Chargebee at scale.

4. Paddle — The MoR for Web-Centric Software

Best for: SaaS developers who want a Merchant of Record (MoR) solution that handles global tax compliance automatically and primarily sell through a web interface.

Paddle Billing takes a similar MoR approach to ZeroSettle — they handle sales tax, fraud, chargebacks, and customer support on your behalf — but their design center is web-first software, not native mobile apps.

Key features:

Full MoR covering tax compliance in 100+ jurisdictions automatically
Bundled fraud protection and customer support
ProfitWell Metrics included free for subscription analytics (LTV, churn, MRR)
Claims a migration onboarding process of "12 days or less" with dedicated support

Pricing: Typically a bundled percentage rate that varies by volume and plan.

Who it's NOT for: Apps where the primary purchase experience is inside an iOS app. While Paddle can technically support mobile, it doesn't offer native SDK tooling for in-app StoreKit migration, Switch & Save campaigns, or gradual rollout mechanisms. Its strengths are most apparent in a browser-based checkout context.

5. RevenueCat — Analytics Layer, Not a Billing Replacement

Best for: Developers who want a unified, cross-platform view of their subscription data and need to manage subscription state across iOS, Android, and web without rebuilding their entire billing infrastructure.

RevenueCat is excellent at what it does — but it's critically important to understand what it doesn't do. RevenueCat itself has published honestly about the pros, cons, and gotchas of external iOS payments. It is a subscription management and analytics layer, not a payment processor.

Key features:

Single source of truth for subscription status across platforms
Cohort analysis, LTV, churn, and MRR dashboards
Webhook and integration support for downstream systems
Simplifies the engineering complexity of tracking subscription state across StoreKit, Google Play, and Stripe

Pricing: Up to 3.5% on transactions processed through the platform.

Who it's NOT for: Anyone whose primary goal is reducing Apple's 30% commission. RevenueCat sits on top of IAP or other billing systems — it doesn't replace them. If you use RevenueCat alongside Stripe for direct billing, you're adding a layer (and a fee) rather than getting out-of-the-box migration tooling. It's a powerful analytics and management tool, but evaluating it as an IAP alternative is a category mistake.

The Savings Calculator: This Is a Bottom-Line Decision

Features and integrations matter — but let's be honest about what's really driving this conversation. Here's the math, kept simple:

Scenario	Annual Revenue	Platform Fee	What You Keep
Apple IAP	$1,000,000	$300,000 (30%)	$700,000
Allocents (MoR)	$1,000,000	~$50,000 (5%)	$950,000
Annual Savings		~$250,000

If your app generates $1M ARR through Apple IAP, switching to Allocents saves you approximately $250,000 per year. That's not a rounding error — that's a product hire, a marketing budget, or two years of infrastructure costs.

At $500K ARR, the savings are $125,000 annually. At $2M ARR, you're looking at $500,000 recaptured.

The question isn't really whether to explore moving off IAP at this revenue level — the question is how to do it without disrupting the user experience that drove your growth in the first place.

Which Platform Is Right for You?

Here's the quick-reference summary:

Allocents — Best overall for mobile-first apps at $500K–$20M+ ARR that want a purpose-built IAP migration solution with full MoR coverage, native SDK, and gradual rollout. Lowest friction path from Apple IAP to direct billing.
Stripe Billing — Best for engineering-heavy teams who want to build a fully custom billing stack and have the resources to handle MoR responsibilities (tax, fraud, support) themselves.
Chargebee — Best for web-based B2B SaaS with complex billing logic and accounting integration needs. Not a fit for native mobile migration.
Paddle — Best for web-centric software companies that want a full MoR solution with built-in global tax compliance. Limited native mobile tooling.
RevenueCat — Best as a subscription analytics and management layer on top of your existing billing setup — not a replacement for Apple IAP.

The April 2025 ruling didn't just change what's allowed — it changed what's smart. At $500K ARR, staying on Apple's 30% is a choice you're actively making. For most mobile developers, the best subscription billing platform isn't the one with the most features — it's the one that gets you off that 30% fee the fastest, without breaking the checkout experience your users already trust.

For a purpose-built path to doing exactly that, Allocents is worth a serious look.

Frequently Asked Questions

Why should I move away from Apple's In-App Purchase (IAP) system?

The primary reason to move away from Apple IAP is to avoid the standard 30% commission fee on all transactions. For an app with $1 million in annual recurring revenue (ARR), this fee amounts to $300,000 per year. Switching to a direct billing platform can reduce that cost to around 5%, saving your business approximately $250,000 annually.

Is it legal to use third-party payment systems in an iOS app?

Yes, it is legal for developers in the United States. A landmark ruling in the Epic v. Apple case, effective April 2025, permanently prevents Apple from blocking developers from using alternative payment systems or linking to external payment options from within their apps.

What is a Merchant of Record (MoR) and why does it matter?

A Merchant of Record (MoR) is the entity that takes legal and financial responsibility for processing customer payments. This includes managing sales tax compliance across different states and countries, handling fraud protection, dealing with chargebacks, and providing customer support. Using a platform with a built-in MoR, like Allocents or Paddle, offloads this significant operational complexity from your team.

What is the biggest risk of switching from Apple IAP?

The biggest risk is a potential drop in conversion rates. Users are accustomed to the seamless, one-tap experience of IAP with Face ID or Touch ID. Introducing a clunky or unfamiliar web-based checkout flow can create friction and cause potential customers to abandon their purchase. This is why choosing a platform with a native-feeling UI and features like gradual rollouts is critical.

How do I migrate my existing subscribers to a new billing system?

You cannot automatically transfer subscribers from Apple IAP to a direct system. Instead, you must convince them to switch manually. Platforms built for this transition, like Allocents, offer tools such as "Switch & Save" campaigns. These present native, in-app prompts to your existing subscribers, often with a discount, to incentivize them to re-subscribe directly.

Can I just use Stripe to avoid Apple's fees?

Yes, you can use Stripe as your payment processor, but it is not a complete solution. Stripe provides the payment infrastructure, but your team will be responsible for building the entire user interface for checkout, managing subscription logic, creating migration tools, and handling all Merchant of Record responsibilities (like sales tax). This requires a significant and ongoing engineering investment.

What's the difference between Allocents and RevenueCat?

Allocents is a complete IAP replacement and Merchant of Record designed to help you migrate off Apple's 30% fee with its own billing system. RevenueCat is an analytics and management layer that sits on top of your existing billing systems (like Apple IAP and Stripe). RevenueCat simplifies tracking subscription data across platforms but does not replace the underlying payment processor or help you avoid the 30% commission.