
For years, giving Apple 30% of your app's revenue felt like paying a "creative tax" with no opt-out clause. Developers vented on forums about feeling "trapped by Apple's ecosystem" and watching a third of every dollar disappear before it hit their bank account. Then, in April 2025, everything changed.
The landmark Epic v. Apple ruling permanently barred Apple from forcing US developers to use its In-App Purchase (IAP) system — cracking open a $150B+ annual IAP market for the first time. For US iOS developers, the question is no longer whether you can route around the App Store commission. It's how, and at what cost.
You now have three real options: stick with Apple IAP, use Apple's new external payment link entitlement, or go fully external with a direct billing processor. Each path has a very different financial profile — and a very different set of hidden costs that don't show up in the headline fee. This guide breaks down every dollar.
Before we get to the numbers, here's a quick definition of each scenario:
Apple IAP (Standard or Small Business): Apple remains the Merchant of Record (MoR). They handle payments, tax, refunds, and fraud. You pay 30% (standard) or 15% if you qualify for the App Store Small Business Program — available to developers who earned under $1M in the prior calendar year.
Apple External Purchase Link Entitlement: You apply for Apple's entitlement to include a link in your app pointing users to your own website to complete a purchase. Apple still charges 27% on resulting transactions (or 12% for Small Business members). You're also on the hook for your own payment processor fees on top of that.
Fully External Direct Billing: You bypass Apple's commission structure entirely by integrating a third-party SDK. This is where the real savings live — but also where new responsibilities kick in.
The table below maps out the true cost of each scenario at three revenue levels. For transaction-based fees, we assume a $20 average transaction value to calculate per-transaction costs.
| Scenario | ARR | Effective Fee Rate | Total Fees | Net Revenue |
|---|---|---|---|---|
| Apple IAP (Standard, 30%) | $500K | 30% | $150,000 | $350,000 |
| Apple IAP (Small Business, 15%) | $500K | 15% | $75,000 | $425,000 |
| Apple External Link (Standard, 27% + ~2.9% processor) | $500K | ~29.9% | $149,500 | $350,500 |
| Apple External Link (Small Biz, 12% + ~2.9% processor) | $500K | ~14.9% | $74,500 | $425,500 |
| Allocents Billing (MoR, 5% + 50¢/tx) | $500K | ~7.5% | $37,500 | $462,500 |
| Allocents BYOS (0.5% + ~2.9% Stripe) | $500K | ~3.4% | $17,000 | $483,000 |
| Apple IAP (Standard, 30%) | $1M | 30% | $300,000 | $700,000 |
| Apple External Link (Standard, ~29.9%) | $1M | ~29.9% | $299,000 | $701,000 |
| Allocents Billing (MoR, ~6.25%) | $1M | ~6.25% | $62,500 | $937,500 |
| Allocents BYOS (0.5% + ~2.9% Stripe) | $1M | ~3.4% | $34,000 | $966,000 |
| Apple IAP (Standard, 30%) | $5M | 30% | $1,500,000 | $3,500,000 |
| Apple External Link (Standard, ~29.9%) | $5M | ~29.9% | $1,495,000 | $3,505,000 |
| Allocents Billing (MoR, ~5.25%) | $5M | ~5.25% | $262,500 | $4,737,500 |
| Allocents BYOS (0.5% + ~2.9% Stripe) | $5M | ~3.4% | $170,000 | $4,830,000 |
Per-transaction fees calculated assuming a $20 average transaction value.
The takeaway is stark: Apple's External Link option saves you almost nothing at the standard rate — you go from paying 30% to paying ~29.9%. The real savings only materialize when you go fully external.
Those percentages don't tell the full story. Before you reroute your billing, here are the friction points and operational burdens you need to price in.
Using Apple's External Purchase Link Entitlement is not a free-for-all. You must apply for and be granted the StoreKit External Purchase Link Entitlement — and Apple's UX requirements are deliberately friction-laden. Before any user reaches your external page, Apple requires you to display a mandatory system-provided alert sheet warning them they're leaving Apple's ecosystem.
This modal is designed to create hesitation. Developers who've gone through the process describe the documentation as "a headache to navigate" — and the rules are subject to change without much notice. For the External Link path specifically, you save less than 0.1% compared to standard IAP once processor fees are added. The compliance burden is high; the reward is slim.
When you go fully external — skipping Apple's IAP entirely — you inherit every responsibility that Apple currently handles on your behalf. This is where many developers underestimate the real cost:
This is why the billing model you choose matters as much as the fee rate. Allocents' full Merchant of Record plan (5% + 50¢ per transaction) absorbs all of the above — tax remittance across 190+ countries, chargeback management, fraud protection, and customer support. You save ~22–25% on revenue without adding a billing operations team.
For teams that already have Stripe infrastructure and in-house compliance capabilities, Allocents' Bring Your Own Stripe (BYOS) plan drops the fee to just 0.5% of migrated revenue, with Allocents providing the checkout UI and migration flows while you retain full control.
Apple's IAP is seamless. Millions of users have a card saved, Face ID set up, and click "Subscribe" in two taps. The moment you redirect them to a web page and ask them to re-enter payment details, you introduce friction — and friction kills conversions.
This is the risk that makes "changing payment methods feel like a gamble," as developers put it themselves. The solution isn't to avoid going external — it's to go external with purpose-built migration UX.
Allocents was built specifically for this problem by engineers who understand StoreKit from the inside out. The Allocents SDK includes:
The result is a native-feeling external billing experience instead of a jarring web redirect — which is the difference between a successful migration and a leaky paywall.
Not every app should switch tomorrow. Here's a framework to figure out where you stand:
1. What is your ARR?
2. Do you have dedicated finance, ops, and support staff?
3. How sensitive is your user base to checkout friction?
4. How risk-averse is your team?
The Epic v. Apple ruling created a real opening — but navigating app store external payment rules, operational overhead, and conversion risk is exactly why most developers haven't moved yet. The complexity is real.
The good news: you don't have to choose between Apple's 30% and rebuilding your entire billing infrastructure from scratch. Allocents was purpose-built to sit in that gap. A 15-minute SDK integration unlocks native-feeling external billing flows, full Merchant of Record coverage (or BYOS flexibility), and a gradual migration path that lets you move at your own pace — all at a fraction of what Apple charges.
US iOS developers now have three main billing options: continue using Apple's In-App Purchase (IAP) system, use Apple's External Purchase Link entitlement, or integrate a fully external direct billing solution. Sticking with Apple IAP means paying a 15-30% commission. The External Link option still requires paying Apple a 12-27% commission on top of your own payment processing fees. A fully external solution bypasses Apple's commission entirely, offering the most significant savings but also requiring you to handle tasks like tax compliance, fraud, and customer support.
Apple's External Purchase Link is generally not a good deal because the savings are minimal while the compliance and user experience friction are high. Apple still charges a 27% commission (or 12% for Small Business Program members) on transactions made through an external link. After adding standard payment processor fees (around 2.9%), your total cost is about 29.9%, saving you almost nothing compared to the standard 30% IAP fee. Additionally, Apple requires a mandatory, friction-inducing warning screen before users can leave the app to pay.
A Merchant of Record (MoR) is the entity that takes legal and financial responsibility for processing customer payments, including handling tax collection, fraud, chargebacks, and compliance. When you use Apple's IAP, Apple acts as the MoR. If you move to a fully external billing system, you must either become the MoR yourself or use a third-party MoR service. Handling MoR duties in-house involves significant operational overhead, from calculating global sales tax to managing payment disputes and customer billing support.
To migrate users effectively, you must minimize friction and clearly communicate the value of switching, typically through a discount. Instead of a jarring redirect to a generic web page, use a native-feeling SDK that supports one-click payment options like Apple Pay and Google Pay. You can use in-app campaigns to offer existing subscribers a discount to switch ("Switch & Save") or present new users with a choice between standard App Store pricing and a lower direct price. A/B testing these offers is crucial to optimize your conversion rate.
Yes, it is often still worth it, as the savings can be substantial even for smaller developers. If you earn under $1M annually, you qualify for Apple's Small Business Program and pay a 15% commission. While better than 30%, this is still significantly higher than the typical 5-8% all-in rate for a third-party Merchant of Record solution. Switching could double your net margin on every transaction, allows you to build a direct relationship with your customers, and prepares your billing infrastructure for future growth.
Yes, you can offer both Apple's IAP and a direct payment option simultaneously. A common strategy is to present users with a choice on your paywall, showing the standard price via Apple IAP and a discounted price for paying directly. This "Sign Up & Save" approach allows you to capture users who prefer the convenience of IAP while incentivizing others to choose the more profitable direct channel.
To link out, developers must be granted a specific entitlement from Apple and display a mandatory, system-provided alert sheet that warns users they are leaving Apple's secure payment system. Apple's rules, known as "anti-steering" policies, are designed to create friction. The required alert modal can deter users from completing a purchase. You must apply for the StoreKit External Purchase Link Entitlement and adhere strictly to Apple's UX guidelines, which are subject to change.
Curious what the numbers look like for your specific ARR? Contact us for a free revenue impact analysis to see your potential savings.
Ready to get hands-on? Book a call to explore the SDK — no commitment required.