7 Web Checkout SDK Options for Mobile Apps After the Epic v. Apple Ruling
Summary
- The April 2025 Epic v. Apple ruling allows iOS apps in the U.S. to use direct billing, bypassing Apple's 30% commission on over $150B in annual transactions.
- Migrating users requires solving complex challenges like payment processing, global tax compliance, and fraud, plus the user experience of convincing subscribers to switch payment methods.
- Most existing solutions like Stripe or Paddle lack the specific tooling for US-only geo-fencing and native migration campaigns, demanding significant custom engineering work.
- For a purpose-built solution, Allocents provides a single SDK with automated compliance and "Switch & Save" campaigns to migrate users in as little as 15 minutes.
On April 30, 2025, a U.S. District Court handed down a landmark ruling that permanently barred Apple from forcing developers to use its In-App Purchase system in the United States. For mobile developers, this was the moment everything changed. The court mandated that Apple must allow iOS apps to link to external checkout options without charging commission on off-app purchases — and strip away the intimidating warnings that previously scared users away from tapping those links. Overnight, an estimated $150B+ in annual IAP volume became contestable.
Spotify was one of the first out of the gate, updating its US iOS app within days of the ruling to add direct payment links. If Spotify is moving, you should be too.
But here's the honest reality developers are facing: the ruling created an extraordinary opportunity and a genuinely complex technical challenge — simultaneously. You now need to handle payment processing, tax compliance across jurisdictions, fraud prevention, and — most critically — the delicate UX problem of migrating loyal subscribers who are comfortable paying through Apple. Getting this wrong means compliance exposure, broken entitlements, and churned users.
This guide evaluates seven web checkout SDK options for mobile apps against the three criteria that actually matter in the post-Epic landscape:
- Epic Ruling Compliance Readiness — Does the solution handle US-only jurisdiction routing and Apple's new rules out of the box?
- IAP Migration Capability — How powerful are its tools for converting existing StoreKit subscribers to direct billing?
- Total Effective Fee at $1M ARR — What is the all-in cost, including transaction fees and Merchant of Record overhead?
Let's get into it.
1. Allocents
Best for: iOS developers who want a purpose-built, end-to-end migration platform
Allocents is the only web checkout SDK for mobile apps built specifically for the post-Epic opportunity. Born from the landmark April 2025 Epic v. Apple ruling, Allocents provides a single SDK that replaces what competitors require 2-3 products to achieve (e.g., RevenueCat for subscription management + Paddle for web checkout + Stripe for payment processing).
The single SDK (Swift/SwiftUI, Kotlin, Flutter, React Native) integrates in as little as 15 minutes and provides two billing modes:
- Allocents Billing (Merchant of Record): At 5% + 50¢ per transaction, Allocents acts as full MoR — handling payments, tax remittance across 190+ countries, chargebacks, fraud, and customer support.
- Bring Your Own Stripe (BYOS): At just 0.5% of migrated revenue, you connect your existing Stripe account and retain MoR duties while using Allocents' checkout infrastructure and migration UI.
What makes Allocents genuinely different is its jurisdiction-aware routing — the SDK automatically displays direct billing options only to users in eligible regions, so you stay compliant without writing a single line of geo-fencing logic. Combine that with automatic StoreKit product sync from App Store Connect, native "Switch & Save" campaigns to convert existing subscribers, and a gradual rollout feature that lets you start with just 10% of your US users — and you have a migration platform, not just a payment SDK.
- Epic Ruling Compliance Readiness: ✅ Excellent — jurisdiction-aware routing is built-in
- IAP Migration Capability: ✅ Excellent — Switch & Save campaigns, StoreKit sync, gradual rollout
- Total Effective Fee at $1M ARR: ~$34k (BYOS) to ~$50k (MoR), no MoR overhead with Allocents Billing
2. Stripe (DIY)
Best for: Teams with deep engineering resources who want maximum flexibility
Stripe's iOS SDK gives you powerful, battle-tested payment infrastructure with solid Swift/Objective-C tooling, prebuilt Mobile Payment Sheet components, Apple Pay integration, and a customizable Appearance API. If you need total control over your checkout experience, Stripe is the foundation most developers already trust.
The catch is what Stripe doesn't give you. Every piece of Epic ruling compliance logic — geo-fencing direct billing to US users, building migration UI to convince subscribers to switch, syncing entitlements between StoreKit and your own backend — is yours to build, test, and maintain. That's months of engineering work, not a weekend project.
- Epic Ruling Compliance Readiness: ❌ Poor — all compliance logic is developer-owned
- IAP Migration Capability: ❌ Poor — zero built-in migration tooling
- Total Effective Fee at $1M ARR: ~$29k on paper (2.9% + 30¢), but this figure is misleadingly low. Add engineering time, MoR infrastructure (tax, fraud, chargebacks), and ongoing maintenance and the real cost is dramatically higher.
3. Paddle
Best for: Web-first SaaS businesses expanding to mobile
Paddle is a well-regarded Revenue Delivery Platform that acts as your Merchant of Record, abstracting away global tax compliance, fraud, and chargebacks. If your primary product is a web app with a mobile companion, Paddle's unified platform is a compelling option.
For mobile-first developers focused on migrating existing StoreKit subscribers, however, Paddle shows its limitations. The SDK provides a checkout experience, but there are no specialized "Switch & Save" flows or deep App Store Connect integration. You'll still need to build the persuasion layer (the UI that convinces users to switch) and the entitlement sync logic yourself.
- Epic Ruling Compliance Readiness: 👍 Good — handles MoR duties, but regional display logic is on you
- IAP Migration Capability: 🟡 Moderate — solid checkout, no native migration campaigns
- Total Effective Fee at $1M ARR: ~$50k (comparable to Allocents MoR) without the migration-specific tooling
4. RevenueCat + Stripe
Best for: Teams already on RevenueCat who want to extend their existing stack
RevenueCat has become the de-facto subscription management layer for many mobile apps, and for good reason — its entitlement tracking across App Store, Play Store, and web is outstanding. Paired with Stripe for payment processing, this combination can handle the post-Epic world, but it requires you to treat them as two separate systems.
RevenueCat's migration documentation covers both server-side migration (sending receipts to the POST /receipts endpoint, which is the preferred bulk approach) and client-side SDK sync. The server-side method is powerful for importing existing subscribers at scale, but it solves the technical problem of entitlement tracking, not the user experience problem of actually getting subscribers to choose a new billing method. Building the persuasion layer — the paywall that surfaces the direct billing offer, the cancellation flow that offers a discount — is entirely on your team.
As RevenueCat themselves note, adapting to the new payment landscape requires developers to move quickly; the multi-system nature of this setup adds meaningful integration time.
- Epic Ruling Compliance Readiness: 👍 Good — strong entitlement infrastructure, but routing logic is developer-owned
- IAP Migration Capability: 👍 Good — robust back-end migration via
POST /receipts, no native front-end migration UX - Total Effective Fee at $1M ARR: ~$41k+ (RevenueCat Pro ~$12k/year + Stripe's ~$29k) with MoR overhead remaining on the developer for the Stripe portion
5. Lemon Squeezy
Best for: Indie developers and creators selling new digital products
Lemon Squeezy is a beloved all-in-one platform for digital sales, with a clean interface, full MoR handling, and built-in tools for email marketing, affiliate programs, and license key generation. For a developer launching a new product who wants simplicity, it's genuinely excellent.
For a mobile app team trying to migrate an existing subscriber base from StoreKit, it's the wrong tool entirely. Lemon Squeezy wasn't designed with iOS entitlement management, App Store Connect sync, or mobile-specific migration flows in mind. Using it for an IAP migration would require building essentially everything from scratch on top of it.
- Epic Ruling Compliance Readiness: 🟡 Moderate — MoR duties handled, mobile geo-fencing routing is not a built-in feature
- IAP Migration Capability: ❌ Poor — not designed for mobile subscriber migration
- Total Effective Fee at $1M ARR: ~$50k (standard 5% + 50¢)
6. Shopify Checkout Kit
Best for: Retail brands with physical goods and a mobile companion app
Shopify Checkout Kit lets you embed Shopify's highly optimized checkout — with access to Shop Pay, 100+ payment gateways, and Shopify's backend management — directly into a native mobile app. If you're a brand that sells physical products and wants a unified commerce layer across web and mobile, this is powerful.
For subscription apps or mobile games trying to bypass Apple's commission post-ruling, the platform mismatch is significant. There is no concept of StoreKit entitlements, no App Store Connect sync, and no tooling for migrating existing IAP subscribers. The Epic v. Apple ruling's specifics are largely irrelevant to Shopify Checkout Kit's design philosophy — you'd be adapting a physical commerce platform to solve a digital billing problem.
- Epic Ruling Compliance Readiness: 🟡 Moderate — robust infrastructure, but not designed with Epic ruling specifics in mind
- IAP Migration Capability: ❌ Poor — completely separate commerce system from App Store
- Total Effective Fee at $1M ARR: ~$20k–$30k (Shopify Plus fees + gateway fees), but with significant platform mismatch for digital-only subscription apps
7. Pure WebView Approach
Best for: Rapid prototyping only — not production
The most basic option: open a WKWebView or SFSafariViewController pointing at your existing web checkout. The payment processing happens on your website (typically via Stripe.js), and you pass tokens between the native app and the web layer to manage entitlements.
The appeal is obvious — you can theoretically ship something in a day using infrastructure you already have. The reality is messier. Apple's App Review guidelines are strict about WebView experiences that feel like they're trying to sidestep native patterns. A poorly implemented WebView checkout can feel jarring to users, trigger rejection, and create a fragile token-passing architecture that breaks on edge cases. The complexity of integrating payments this way tends to lead to exactly the frustration and broken user experiences that cause subscribers to churn rather than migrate.
- Epic Ruling Compliance Readiness: ❌ Poor — high App Review risk; compliance logic entirely on developer
- IAP Migration Capability: ❌ Poor — complex, brittle entitlement sync between native app and WebView
- Total Effective Fee at $1M ARR: ~$29k (underlying Stripe fees) with the highest developer cost and UX risk of any option on this list
Comparative Scoring Table
| Solution | Epic Compliance Readiness | IAP Migration Capability | Total Effective Fee at $1M ARR |
|---|---|---|---|
| 1. Allocents | ✅ Excellent | ✅ Excellent | ~$34k (BYOS) to ~$50k (MoR) |
| 2. Stripe (DIY) | ❌ Poor | ❌ Poor | ~$29k + High Dev/Ops Cost |
| 3. Paddle | 👍 Good | 🟡 Moderate | ~$50k |
| 4. RevenueCat + Stripe | 👍 Good | 👍 Good | ~$41k+ + MoR Overhead |
| 5. Lemon Squeezy | 🟡 Moderate | ❌ Poor | ~$50k |
| 6. Shopify Checkout Kit | 🟡 Moderate | ❌ Poor | ~$20k–$30k (Platform Mismatch) |
| 7. Pure WebView | ❌ Poor | ❌ Poor | ~$29k + High Dev/UX Cost |
Choosing Your Path in the New App Store Economy
The April 2025 Epic v. Apple ruling is a once-in-a-generation shift in mobile monetization. The commission savings alone — moving from Apple's 30% cut to a direct billing fee of 5% or less — represent a meaningful step-change in unit economics for any app with significant ARR. But the ruling also made clear that the opportunity belongs to developers who can execute.
Retrofitting a general-purpose tool like a DIY Stripe integration or a pure WebView introduces compliance risk and technical debt that compounds over time. Stitching together RevenueCat and Stripe is a viable path for teams already invested in that stack, but you'll still need to build and maintain the user-facing migration layer yourself — the paywall copy, the discount offers, the cancellation flows that convince real subscribers to switch. That's not a weekend project.
The platforms designed for web-first commerce — Paddle, Lemon Squeezy, Shopify — are excellent at what they were built for. What they weren't built for is the specific challenge of migrating a mobile subscriber base away from StoreKit while staying compliant with a US-specific court ruling.
Allocents is the only option on this list designed from the ground up for exactly that problem. The jurisdiction-aware routing, the StoreKit sync, the native Switch & Save campaigns — these aren't add-ons. They're the core product.
How to Start Migrating in a Weekend
The opportunity to reclaim your revenue is here, and it doesn't require a multi-month engineering sprint. With Allocents' single SDK, you can integrate native Switch & Save campaigns into your iOS app in as little as 15 minutes. Start by rolling out to just 10% of your US users, watch the migration rates and revenue impact in the analytics dashboard, and scale up with confidence.
If you already have Stripe and want to keep your existing payment stack, the Bring Your Own Stripe (BYOS) plan adds Allocents' migration UI and intelligent offers at just 0.5% of successfully migrated revenue — hands down the lowest-cost path to capitalizing on the ruling.
Stop leaving 30% on the table. Learn more at allocents.com and start your migration this weekend.
Frequently Asked Questions
What did the Epic v. Apple ruling change for iOS app payments?
The April 30, 2025, U.S. District Court ruling permanently allows iOS developers to direct users to external payment options for purchases, bypassing Apple's In-App Purchase system. This means you can now use links in your app to your own web checkout and avoid paying Apple's 15-30% commission on those transactions within the United States. The ruling also prohibits Apple from using scare-warnings on these external links.
Why is migrating users from Apple IAP to direct billing so difficult?
Migrating subscribers is difficult because it involves both technical and user experience challenges. Technically, you need to handle payment processing, global tax compliance, fraud, and sync entitlements between Apple's system and your own. From a UX perspective, you must convince loyal users who trust Apple's one-tap payment flow to manually enter their credit card details on your website, a process that can easily lead to churn if not handled with care.
What is a Merchant of Record (MoR) and do I need one?
A Merchant of Record is a service that takes on the financial and legal responsibilities for processing your customer payments. This includes handling all sales tax calculations and remittance, managing fraud, dealing with chargebacks, and ensuring currency conversion is handled correctly. While you can act as your own MoR (e.g., when using Stripe directly), using an MoR service like Allocents or Paddle offloads significant operational complexity, especially when selling globally.
How can I handle compliance with the US-only Epic ruling?
To comply with the ruling, you must ensure that links to external payment systems are only shown to users located in the United States. This requires implementing reliable geo-fencing or jurisdiction-aware routing logic within your app. A purpose-built SDK like Allocents handles this automatically, while DIY solutions require you to build, test, and maintain this complex logic yourself to avoid violating Apple's App Store policies in other regions.
What's the most cost-effective way to switch from Apple IAP to direct payments?
The most cost-effective solution is one that minimizes both direct fees and hidden engineering costs. While a DIY Stripe setup appears cheapest on paper (e.g., ~2.9%), the total cost becomes much higher when you factor in the engineering time required to build compliance logic, migration UI, and entitlement systems. Solutions like Allocents' "Bring Your Own Stripe" (BYOS) plan offer a low-cost middle ground, adding a small fee (0.5%) to your existing Stripe account in exchange for a pre-built, compliance-ready migration platform.
Can I start offering direct payments without a big engineering project?
Yes, you can begin offering direct payments quickly by using an end-to-end platform built for this purpose. A solution like Allocents provides a single SDK that integrates in minutes and includes pre-built user interfaces for migrating subscribers, automatic compliance with the Epic ruling, and entitlement management. This approach allows you to capitalize on the opportunity immediately without dedicating months to building and maintaining a custom payment infrastructure.