7 Tools That Support an Apple External Checkout Flow in 2025

Summary

Bypassing Apple's 30% commission is now legal in the US, but forcing users to an external web checkout can cause a 25% to 45% drop in conversions.
Switching from IAP makes you the Merchant of Record, responsible for handling global sales tax, fraud, chargebacks, and customer support.
A compliant solution requires a native SDK, automatic StoreKit sync, and jurisdiction-aware routing to manage complexity and reduce user friction.
Allocents provides a drop-in SDK with full Merchant of Record coverage to handle these complexities for a simple 5% + 50¢ fee.

You finally have the legal green light to bypass Apple's 30% cut. Now comes the harder question: which payment infrastructure actually supports a compliant Apple external checkout flow end-to-end?

This is the question developers are actively wrestling with in communities like r/AppBusiness, and the answers are rarely straightforward. The central dilemma, as one developer put it bluntly, is whether to "pay the platform commission (15% to 30%) or introduce user friction and complexity to save that fee." And the friction is real — forcing users out to a web checkout can cause a 25% to 45% drop in initial conversions.

The April 2025 Epic v. Apple ruling permanently barred Apple from forcing US developers to use its In-App Purchase (IAP) system, unlocking what analysts estimate to be $150B+ in annual IAP volume. But with that freedom comes a new set of headaches: your startup now assumes full responsibility for sales tax compliance, chargebacks, fraud, refunds, and direct customer support — all the operational infrastructure Apple quietly handled for its 30% fee.

At the same time, the rules are now genuinely developer-friendly in the US:

One link allowed: Apps can embed a single, clear button linking to an external web checkout.
No Apple surcharge: The previously proposed 27% "work-around fee" is eliminated in the US.
No scare screens: Apple can only show a neutral "Leaving the app" modal.
Price disclosure: Apps can openly advertise lower prices available through the external checkout.

Outside the US, complexity remains. The EU's Digital Markets Act allows external links but with Apple fees up to 20%. South Korea permits external payments but charges a 26% commission. This means any serious solution needs jurisdiction-aware routing — showing external payment options only where economics actually make sense.

The financial upside in the US is compelling. A direct transaction can improve your margin from roughly $7.00 per $10 transaction (after Apple's 30% cut) to $9.30–$9.40 using a processor like Stripe. The question is which tool helps you capture that margin without rebuilding your entire payment stack from scratch.

This article evaluates 7 tools across five consistent criteria:

SDK Availability — Native SDKs for Swift/SwiftUI, Kotlin, Flutter, React Native
Apple Parameter Support — StoreKit sync, isEligible flag handling, jurisdiction routing
Hosted PSP Page Compliance — Compliant checkout pages that minimize drop-off
MoR Coverage — Who handles tax, fraud, chargebacks, and support
Platform Breadth — iOS + Android coverage

7 Tools for Your Apple External Checkout Flow

1. Allocents

Best for: Developers who want a purpose-built, end-to-end solution for the post-Epic StoreKit migration.

Allocents is the only tool on this list built from the ground up to solve the post-Epic migration use case — not a generic payments tool retrofitted for mobile. It provides a single SDK to handle direct billing, compliance, and subscription management.

SDK Availability: ✅ Drop-in SDK for Swift/SwiftUI, Kotlin, Flutter, and React Native. Integrates in roughly 15 minutes.
Apple Parameter Support: ✅ Automatic StoreKit product sync from App Store Connect eliminates duplicate catalog management. Built-in jurisdiction-aware routing ensures external links only surface in compliant regions like the US.
Hosted PSP Page Compliance: ✅ Instead of a jarring browser redirect, Allocents presents native-feeling UI flows — such as "Sign Up & Save" paywalls that let users choose App Store or direct billing side-by-side, and "Switch & Save" campaigns to migrate existing StoreKit subscribers with a targeted offer. Native web checkout supports Apple Pay and Google Pay to reduce friction.
MoR Coverage: ✅ Two flexible models: Allocents Billing (full MoR at 5% + 50¢/transaction — covers tax in 190+ countries, chargebacks, fraud, and support) or Bring Your Own Stripe (BYOS at 0.5% of migrated revenue for teams with existing Stripe infrastructure).
Platform Breadth: ✅ iOS + Android

Allocents also includes gradual rollout controls (start with 10% of users, scale up, instant rollback), A/B testing for offers and copy, and an analytics dashboard tracking migration rates and revenue impact. For developers navigating this transition for the first time, that operational scaffolding alone is significant.

2. Stripe (Raw Implementation)

Best for: Teams with significant engineering bandwidth who want maximum flexibility.

Stripe's payment infrastructure is battle-tested and highly capable — but using it for an Apple external checkout flow means building nearly all the compliance and migration logic yourself.

SDK Availability: ✅ Comprehensive, well-documented SDKs for iOS and Android.
Apple Parameter Support: ❌ Entirely manual. Your team must implement isEligible checks, sync products between your backend and App Store Connect, and build regional display rules. One developer in the community noted: "Apple's picky w/ the isEligible flag + wording" — and getting it wrong means rejections.
Hosted PSP Page Compliance: ✅ Stripe Checkout provides a compliant hosted payment page. The developer is responsible for the correct redirect flow (external browser or SFSafariViewController — not a WebView).
MoR Coverage: ❌ You are the Merchant of Record. Stripe Tax, Stripe Radar, chargeback management, and customer support are all your responsibility to configure and fund.
Platform Breadth: ✅ iOS + Android

Stripe is the right raw ingredient, but it's not a complete meal. The real cost isn't Stripe's fees — it's the engineering months required to build what purpose-built tools already provide.

3. Paddle

Best for: Developers who want a proven Merchant of Record solution and don't mind building the IAP migration logic themselves.

Paddle is a well-established all-in-one commerce platform popular in the SaaS and software world, known primarily for its full MoR service that handles global tax and compliance.

SDK Availability: ✅ Paddle provides mobile SDKs for checkout integration.
Apple Parameter Support: ❌ Manual. Developers manage their product catalog on Paddle separately from App Store Connect. Jurisdiction logic must be handled server-side by the developer.
Hosted PSP Page Compliance: ✅ Paddle's hosted checkout is fully compliant and localized for global markets.
MoR Coverage: ✅ This is Paddle's core strength. They act as full MoR — handling VAT, sales tax across jurisdictions, fraud, and compliance — which directly addresses the common pain point of developers who don't want to "handle VAT and compliance yourself."
Platform Breadth: ✅ iOS + Android

Paddle solves the MoR problem well, but it was built for SaaS, not for the nuances of StoreKit migration. You'll still need to engineer the IAP-to-Paddle handoff, eligibility checks, and migration flow yourself.

4. RevenueCat + Stripe (Cobbled Together)

Best for: Teams already using RevenueCat for subscription management who want to add direct billing incrementally.

This is the most common "DIY" approach in the community — using RevenueCat for subscription and entitlement tracking, then directing users to a Stripe Checkout link for the actual payment. RevenueCat's own blog covers the app-to-web purchase guidelines in detail, and the pros/cons of external iOS payments are worth reading before committing.

SDK Availability: ✅ But requires integrating and maintaining two separate SDKs with separate backend logic.
Apple Parameter Support: ⚠️ Partial. RevenueCat handles StoreKit products and entitlement tracking well. But linking a user's paywall action to the correct Stripe Checkout session is a custom integration the developer must build and maintain.
Hosted PSP Page Compliance: ✅ Via Stripe Checkout, but the handoff between the two systems is the developer's responsibility.
MoR Coverage: ❌ You are the MoR through your Stripe account, inheriting all associated tax, fraud, and support responsibilities.
Platform Breadth: ✅ Both services support iOS and Android.

The core risk here is the seams between systems. When something breaks — and in payment infrastructure, something always eventually breaks — you're debugging across two vendors, two dashboards, and two sets of webhooks.

5. Appcharge

Best for: Mobile game publishers looking for customizable direct-to-consumer web stores.

Appcharge is a platform focused on helping mobile app and game publishers set up direct-to-consumer sales channels with branded checkout flows — think customizable web stores for selling coins, gems, and bundles.

SDK Availability: ✅ Provides SDKs for major mobile frameworks.
Apple Parameter Support: ⚠️ Partial. Appcharge supports A/B testing and player segmentation. However, automatic StoreKit product synchronization is not a native feature — product catalog management is manual.
Hosted PSP Page Compliance: ✅ Its core feature is "Payment Links" — customizable external checkout pages designed to match the app's branding while complying with Apple's guidelines.
MoR Coverage: ❌ Appcharge operates on a "bring your own processor" model. The developer remains the MoR for tax, fraud, and chargebacks.
Platform Breadth: ✅ Mobile-focused, supporting iOS and Android.

Appcharge is a solid fit for gaming studios with large consumable catalogs. For subscription apps or teams without dedicated fraud/support infrastructure, the lack of MoR coverage is a meaningful gap.

6. Lemon Squeezy

Best for: Indie developers selling digital products who want simple MoR coverage and don't need deep mobile SDK integration.

Lemon Squeezy is a Merchant of Record platform originally designed for selling ebooks, courses, and software licenses. Some developers explore it as a quick way to get MoR coverage for external mobile checkouts.

SDK Availability: ⚠️ Primarily web-based. Mobile integration typically means linking out to their hosted checkout pages — there is no dedicated mobile SDK.
Apple Parameter Support: ❌ Not designed for StoreKit syncing or in-app subscription logic. Product setup is entirely manual and web-centric.
Hosted PSP Page Compliance: ✅ Provides compliant, hosted checkout pages for products created on the platform.
MoR Coverage: ✅ Like Paddle, this is the main value prop. Lemon Squeezy handles tax collection and compliance across jurisdictions.
Platform Breadth: ⚠️ Primarily web, linkable from any mobile app but without native SDK depth.

Lemon Squeezy works for simple use cases, but the lack of a mobile SDK and StoreKit integration makes it a friction-heavy path for developers managing complex subscription lifecycles.

7. In-House Custom Build

Best for: Large, well-resourced companies with dedicated engineering, legal, and finance teams.

This is the path of maximum control and maximum cost. Building your own external payment infrastructure on top of a gateway like Adyen or Stripe means every piece of compliance logic is yours to build.

SDK Availability: ❌ Your team builds everything from scratch.
Apple Parameter Support: ❌ Your engineers own isEligible logic, product catalog syncing, jurisdiction compliance, and every future API change Apple makes.
Hosted PSP Page Compliance: ❌ Your responsibility to design, build, test, and maintain.
MoR Coverage: ❌ 100% on you — requiring dedicated legal, finance, and support headcount.
Platform Breadth: ✅ As broad as your engineering capacity allows.

The in-house path makes sense at a certain scale (think Spotify or Epic themselves), but for most indie studios and growth-stage apps, the engineering cost alone compounds faster than the commission savings.

At a Glance: External Checkout Tools Comparison

Tool	SDK Availability	Auto StoreKit Sync	Hosted PSP Compliance	MoR Coverage	Platform
Allocents	✅ Native multi-platform	✅	✅ Native UI flows	✅ Full MoR or BYOS	iOS + Android
Stripe (Raw)	✅	❌	✅	❌ Developer is MoR	iOS + Android
Paddle	✅	❌	✅	✅ Full MoR	iOS + Android
RevenueCat + Stripe	✅ (Two SDKs)	❌	✅	❌ Developer is MoR	iOS + Android
Appcharge	✅	❌	✅	❌ Developer is MoR	iOS + Android
Lemon Squeezy	⚠️ Web-first	❌	✅	✅ Full MoR	Web/Mobile
In-House	❌ (Build yourself)	❌	❌ (Build yourself)	❌ Developer is MoR	iOS + Android

Stop Choosing Between High Fees and High Friction

The 2025 Epic v. Apple ruling created a genuine opportunity to reclaim margin — but it also shifted a significant operational burden onto developers. As developers in the community have noted, "it's a paperwork-heavy process" with real rejection risk if you miss the right disclosure language.

Most tools on this list solve part of the problem. Stripe gives you raw payment power but no migration scaffolding. Paddle and Lemon Squeezy solve the MoR burden but weren't designed for mobile IAP. Cobbling together RevenueCat and Stripe introduces multi-system complexity with no automatic StoreKit sync.

For developers who want a compliant apple external checkout flow without months of custom engineering, Allocents stands out as the only single-SDK option purpose-built for the post-Epic StoreKit migration — with native UI flows that protect conversion rates, automatic StoreKit sync that eliminates dual catalog management, and flexible MoR options that let you choose how much operational ownership you want to take on.

If you're sitting on $500K+ in IAP revenue and paying 15–30% of it to Apple, the math on making this change is compelling. The question is just finding the right tool to make it operationally feasible — and that answer now exists.

Frequently Asked Questions

What is an Apple external checkout flow?

An Apple external checkout flow is a process where an app directs users to a webpage outside the app to complete a purchase, bypassing Apple's native In-App Purchase (IAP) system. Following the Epic v. Apple ruling in the US, developers can now include a single link or button in their app that takes users to an external website to pay for digital goods. This allows developers to use third-party payment processors but also makes them responsible for the entire checkout experience and post-purchase support.

Why should I switch from Apple's IAP to an external payment system?

The primary reason to switch from Apple's IAP is to significantly increase your profit margins by avoiding Apple's 15% to 30% commission on every transaction. For a $10 transaction, you might only keep $7.00 after Apple's cut. With a direct payment processor, your take-home could increase to $9.30–$9.40. The trade-off is that you assume full responsibility for operations like tax compliance, fraud, and customer support.

What does being a "Merchant of Record" (MoR) mean?

A Merchant of Record (MoR) is the legal entity responsible for processing customer payments, handling sales tax, managing fraud and chargebacks, and ensuring payment compliance. When you use Apple's IAP, Apple acts as the MoR. When you switch to an external system using a raw processor like Stripe, you become the MoR. Some third-party solutions, like Allocents or Paddle, can act as your MoR, handling these complexities for a fee.

How can I reduce user drop-off with an external payment link?

You can reduce drop-off by making the external checkout experience feel as seamless and native to the app as possible. A jarring redirect to a generic web browser checkout can cause conversion rates to drop by 25% to 45%. To mitigate this, use solutions that offer native-feeling UI flows, support trusted payment methods like Apple Pay and Google Pay on the web, and clearly communicate the value (e.g., lower prices) to the user before they click the link.

What are the main risks of using external payments for my iOS app?

The main risks are a decrease in conversion rates due to user friction, the operational burden of becoming the Merchant of Record, and the potential for app rejection if your implementation doesn't strictly follow Apple's guidelines. Apple's rules around the isEligible flag, disclosure language, and link presentation are very specific. Getting them wrong can lead to delays in app approval.

Are the rules for external payments the same outside the US?

No, the rules for external payments vary significantly by country and are often less favorable than in the US. For example, the EU's Digital Markets Act allows external links, but Apple can still charge fees up to 20%. In South Korea, Apple's commission on external payments is 26%. This complexity means any robust solution needs jurisdiction-aware routing to only show the external payment option where it is financially advantageous.

Can I just use Stripe for my external checkout flow?

While you can use Stripe's core processing, it is not a complete, out-of-the-box solution for an Apple-compliant external checkout flow. Using a raw payment processor like Stripe means you must build all the surrounding infrastructure yourself. This includes implementing the logic for Apple's isEligible flag, syncing your product catalog with App Store Connect, building jurisdiction-aware display rules, and managing all MoR responsibilities.