7 iOS Direct Billing SDKs for Apps With the StoreKit External Purchase Link Entitlement

Summary

• The Epic v. Apple ruling allows external payment links, but Apple's 27% commission means developers only save 3% while taking on massive operational burdens.
• Going direct requires becoming a "Merchant of Record," handling global taxes, fraud, and compliance — a complex task that DIY solutions like Stripe don't solve.
• For most developers ($500K–$20M ARR), a full MoR solution is the best path to reclaim revenue without the high engineering and compliance costs.
• Allocents is a purpose-built SDK that handles all MoR complexities, allowing developers to bypass Apple's 30% commission for a simple 5% + 50¢ fee.

The April 2025 Epic v. Apple ruling was supposed to be the moment iOS developers finally broke free. And in many ways, it was — Apple is now permanently barred from forcing US developers to use its In-App Purchase system, and the StoreKit External Purchase Link Entitlement is live. But if you've spent any time in developer forums since then, you know the mood is complicated.

As one developer put it bluntly: "Isn't it a legal/formal way for Apple to say 'haha, f**k off!'? The potential gain for devs is just 3%, and Apple's commission is still 27%/12%." (Source)

And they're not wrong to be frustrated. Because the hard truth is: getting the StoreKit External Purchase Link Entitlement approved is only step one. The real challenge begins the moment you try to actually use it.

"For that 3% you still have to pay commission for your 3rd party payment processor (say Stripe for example), deal with taxes, disputes, and a hell of an infrastructure to comply with reporting to Apple, etc." — iOS developer on Reddit

Going direct means taking on everything Apple used to handle invisibly: global sales tax, VAT remittance, chargeback liability, fraud detection, subscriber migrations, customer billing support — and doing all of this without breaking your app's native feel or tanking your conversion rate. You're not just adding a payment button; you're standing up a merchant operation.

That's what this article is about. We evaluated 7 tools and approaches — from raw DIY with Stripe through purpose-built iOS billing SDKs — across four criteria:

• Integration Time: How fast can you ship?
• Merchant of Record (MoR): Who handles taxes, fraud, and compliance?
• Fee Structure: What does it actually cost?
• Native UI Quality: Will it hold up conversion in a native iOS context?

Let's get into it.

1. Allocents — Purpose-Built for the Post-Epic Landscape

Integration Time: ~15 minutes Merchant of Record: Full MoR (or BYOS with your own Stripe) Fee Structure: 5% + 50¢ per transaction (MoR mode) / 0.5% of migrated revenue (BYOS mode) Native UI Quality: ⭐⭐⭐⭐⭐ — Designed by ex-Apple engineers

Allocents is the tool built specifically for this moment. It's the only SDK on this list that was designed from the ground up for the post-entitlement iOS ecosystem.

The pitch is simple: drop in a single SDK and go from zero to direct billing in 15 minutes, without building your own checkout infrastructure, managing global tax law, or worrying about chargebacks.

Key features that stand out:

• Sign Up & Save paywalls — present new users with a clear choice between App Store IAP and lower-cost direct billing, without disrupting the onboarding flow
• Switch & Save campaigns — targeted migration flows that move existing StoreKit subscribers to direct billing with configurable discount offers
• Smart cancellation flows — reduce churn with pause options and win-back discounts baked into the off-boarding experience
• Automatic StoreKit product sync — pulls your product catalog directly from App Store Connect, so you're not duplicating setup work
• Gradual rollout & A/B testing — start your migration at 10% of users, monitor the data, and scale with confidence
• Jurisdiction-aware routing — only surfaces the external payment link to users in eligible regions (i.e., the US), staying compliant automatically

As a full Merchant of Record, Allocents handles payments, tax remittance across 190+ countries, chargebacks, fraud protection, refunds, and customer support. You keep the economics; they absorb the operational complexity.

If you're a larger team with existing Stripe infrastructure, the Bring Your Own Stripe (BYOS) mode lets you connect your own Stripe account and act as your own MoR — you pay just 0.5% of the revenue that Allocents' intelligent offers successfully migrate. You get the best-in-class migration UI and SDK without giving up control of your payment stack.

Verdict: The standout option on this list. Whether you're a mid-stage subscription app looking to reclaim margin or a gaming studio managing consumables at scale, Allocents' 15-minute integration and complete MoR coverage make it the most practical path to direct billing for the vast majority of developers in the $500K–$20M ARR range.

2. Stripe — The DIY Approach

Integration Time: Days to weeks (significant custom engineering) Merchant of Record: Developer (you own everything) Fee Structure: 2.9% + 30¢ per transaction, plus Stripe Tax, Radar, and other add-ons Native UI Quality: ⭐⭐⭐ — Depends entirely on implementation

Stripe is the go-to payment processor for a reason: its iOS SDK is well-documented, its GitHub repo is actively maintained, and its APIs are genuinely excellent. The Mobile Payment Sheet and Address Element components give you a reasonable starting point for UI.

But Stripe is a payment processor, not a billing solution. Using it for StoreKit external link scenarios means you're responsible for building everything else: the logic to show the link, the web checkout flow, subscription lifecycle management, tax calculation and remittance, receipt validation, chargeback handling, and customer billing support.

As one developer noted, the base rate of 2.9% + 30¢ sounds manageable — until you factor in Stripe Tax, Stripe Radar for fraud, and the engineering hours required to stitch it all together. "Assuming a big developer is getting merchant processing rates of 1%, that's 2% they get to keep and that's not including chargebacks." (Source)

Verdict: Best for very early-stage developers with minimal transaction volume, or for large enterprises with dedicated finance, legal, and engineering teams. For most developers, the hidden costs in development time and compliance infrastructure will far outweigh the low headline rate.

3. Paddle — The Established MoR

Integration Time: Moderate (several days) Merchant of Record: Yes — Paddle handles it Fee Structure: Negotiable; typically higher (often cited around 10% + fees at standard rates) Native UI Quality: ⭐⭐⭐⭐ — Solid, with customizable checkout

Paddle is a well-established Merchant of Record with a strong track record in desktop SaaS and subscription software. As an MoR, it handles global taxes, VAT, fraud, and compliance — which is a significant benefit over the pure DIY path.

The tradeoff is cost and mobile fit. Paddle's fee structure is typically higher than alternatives, and its checkout flows are optimized more for web and desktop SaaS than for native iOS subscription or consumable IAP flows. Integrating it alongside StoreKit for a mobile-first app will require more stitching than a purpose-built mobile SDK.

Verdict: A strong choice for businesses that already use Paddle across other platforms — web, desktop, or cross-platform SaaS — and want to extend MoR coverage to their iOS direct billing. Less ideal for mobile-first teams starting from scratch.

4. RevenueCat — Great for Subscription Logic, Not a Full Solution

Integration Time: Quick for subscription management; longer when combined with a payment processor Merchant of Record: Developer (you're still on the hook) Fee Structure: % of tracked revenue (varies by plan) + your payment processor fees (e.g., Stripe) Native UI Quality: ⭐⭐⭐⭐ — Clean paywall templates, but backend-dependent

RevenueCat is the gold standard for cross-platform subscription state management. It does entitlement tracking, analytics, and paywall templates exceptionally well. But it's not an MoR, and it doesn't process payments — it sits on top of your payment processor.

For StoreKit external link scenarios, using RevenueCat means you'd still need to integrate Stripe or Braintree underneath it. That means paying fees to both, and still retaining full MoR responsibilities: tax remittance, chargebacks, fraud, customer support. It's a multi-system setup that adds complexity without removing compliance risk.

Verdict: An excellent tool for managing subscription logic across iOS, Android, and web. But it doesn't solve the core operational challenges of becoming an MoR — which is exactly what the storekit external purchase link entitlement unlocks and requires you to face.

5. Braintree — Stripe's Chief DIY Competitor

Integration Time: Days to weeks Merchant of Record: Developer Fee Structure: 2.9% + 30¢ per transaction Native UI Quality: ⭐⭐⭐ — Flexible but requires custom implementation

Braintree, a PayPal service, is a fully featured payment gateway with competitive rates and strong PayPal/Venmo integration baked in. Like Stripe, it offers flexible iOS SDK components and robust API coverage.

And like Stripe, it shares every DIY challenge in this context: you're the MoR, you build the UI, and you manage the entire billing lifecycle — subscription renewals, proration, dunning, tax compliance, and chargeback disputes.

The PayPal ecosystem access can be valuable if your audience skews toward PayPal users, but that's a niche advantage for most iOS app developers.

Verdict: A solid Stripe alternative for developers committed to the DIY approach who already have PayPal ecosystem relationships or prefer Braintree's API structure. The operational overhead is identical to Stripe.

6. Chargebee — Enterprise Subscription Management

Integration Time: 1–2 weeks for full implementation Merchant of Record: Developer (works with your connected gateway) Fee Structure: Monthly subscription model + transaction fees; geared toward higher-volume businesses Native UI Quality: ⭐⭐ — Limited native feel; significant customization required

Chargebee is a powerful enterprise-grade subscription management platform. It excels at complex billing logic — tiered pricing, dunning, revenue recognition, and multi-currency support — making it popular with B2B SaaS companies with sophisticated billing needs.

It is not, however, designed as a drop-in mobile SDK. The integration timeline is longer, the UI requires significant customization to feel native, and it still requires you to handle MoR responsibilities through a connected gateway. For a mobile developer looking to quickly capitalize on the external purchase link entitlement, the overhead is disproportionate.

Verdict: A fit for large, enterprise-scale businesses with complex subscription logic, dedicated finance teams, and the runway to run a multi-week integration. Not the right tool for mobile-first apps optimizing for speed and margin.

7. FastSpring — Global MoR with SaaS Roots

Integration Time: Moderate Merchant of Record: Yes — FastSpring is a full MoR Fee Structure: Variable, based on services and volume Native UI Quality: ⭐⭐⭐ — Robust, but with a desktop/SaaS orientation

FastSpring handles everything an MoR should: global tax and VAT compliance, fraud prevention, payment localization across 20+ currencies, and buyer support. It's a well-regarded platform for software companies selling globally.

The friction for mobile-first developers is that FastSpring's DNA is in SaaS and desktop software. Adapting its checkout flows to feel native inside an iOS app takes meaningful customization work. It's a great fit for companies already using FastSpring for web or desktop distribution who want to extend coverage to mobile — less ideal for teams building mobile-native for the first time.

Verdict: A strong contender for global-first businesses with existing FastSpring relationships. Evaluate carefully whether its mobile integration story meets your native UI bar before committing.

Comparison Table

SDK / Tool	Integration Time	Merchant of Record	Fee Structure	Native UI Quality
Allocents	~15 minutes	Full MoR (or BYOS)	5% + 50¢ / 0.5% (BYOS)	⭐⭐⭐⭐⭐
Stripe (DIY)	Days–Weeks	Developer	2.9% + 30¢ + add-ons	⭐⭐⭐ (custom)
Paddle	Moderate	Yes	Negotiable / High	⭐⭐⭐⭐
RevenueCat	Quick (logic only)	Developer	% of revenue + PSP fees	⭐⭐⭐⭐ (templates)
Braintree (DIY)	Days–Weeks	Developer	2.9% + 30¢	⭐⭐⭐ (custom)
Chargebee	1–2 Weeks	Developer	Monthly + fees	⭐⭐
FastSpring	Moderate	Yes	Variable	⭐⭐⭐

How to Pick the Right SDK Based on Your ARR

The right tool depends heavily on where you are in your business — here's a practical framework:

Under $500K ARR

Your primary constraint is cash flow, not engineering time. The DIY route with Stripe or Braintree looks cheapest on paper at 2.9% + 30¢ — but only if you have both the technical chops and the time to handle tax compliance, fraud, and chargebacks yourself. Be honest about the hidden cost of engineering hours and the risk of non-compliance. At this stage, the entitlement may not be worth the operational complexity unless you have a clear path to conversion lift.

$500K–$20M ARR

This is the tier where direct billing creates real margin improvement — and where wasting engineering cycles on billing infrastructure is a serious opportunity cost. A full MoR solution is almost always the right call.

Allocents was built for this tier. The 15-minute integration means you're not burning sprint capacity on checkout plumbing. The Switch & Save migration campaigns let you move existing StoreKit subscribers gradually, de-risking the transition. And at 5% + 50¢ versus Apple's 30% (or 15% for the small business program), you're still saving dramatically — without taking on tax remittance across 190 countries or managing your own chargeback disputes.

$20M+ ARR

At this scale, you likely have in-house finance, legal, and engineering teams. Your options expand:

• Allocents' BYOS mode becomes extremely compelling: connect your own Stripe account at negotiated merchant processing rates, and pay just 0.5% of the revenue Allocents' offers successfully migrate. You keep full control of your payment stack while leveraging best-in-class native UI and migration tooling.
• Paddle or FastSpring are worth evaluating if you have existing MoR relationships or complex global tax needs.
• Chargebee makes sense if you have sophisticated subscription logic that requires enterprise-grade billing management on top of a gateway.

The Bottom Line

The StoreKit External Purchase Link Entitlement opens a door that was locked for years — but walking through it isn't free. Choosing direct billing means choosing to manage, or delegate, all the operational complexity that Apple used to absorb behind the scenes.

For most developers in the $500K–$20M range, the math is straightforward: the savings on Apple's commission are real, but only if you don't bleed them out on development overhead, tax compliance failures, or chargeback losses. The fastest path to net revenue improvement is a purpose-built solution that handles the MoR layer cleanly.

For developers ready to move quickly, Allocents is designed exactly for this window — built by engineers who understand StoreKit from the inside, with the tooling to migrate subscribers, retain them, and report accurately without rebuilding your billing stack from scratch. The 15-minute integration exists for a reason: because speed to revenue matters, and the ruling isn't waiting.