How to Reduce Apple App Store Fees From 30% to Under 5%

Summary

• Apple's App Store commission of 15-30% costs developers up to $300,000 for every $1 million in revenue.
• The Epic v. Apple court ruling now legally allows US-based developers to bypass this "Apple Tax" by offering direct billing options inside their apps.
• By implementing direct billing, you can reduce payment processing fees to under 5% and reclaim significant revenue.
• Allocents offers a drop-in SDK that enables direct billing in minutes, managing all payment, tax, and compliance complexities.

If your app generates $1,000,000 in annual revenue, Apple takes up to $300,000 of it. That's not a rounding error—that's a full-time engineering team, a marketing budget, or a year of runway, handed over for the privilege of being listed in a marketplace.

Here's what those fees look like across different scenarios:

Annual Recurring Revenue (ARR)	Lost to Apple (Standard 30%)	Lost to Apple (Small Business 15%)	Lost via Direct Billing (~5%)	Revenue Reclaimed
$500,000	$150,000	$75,000	$25,000	$50,000–$125,000
$1,000,000	$300,000	$150,000	$50,000	$100,000–$250,000
$5,000,000	$1,500,000	$750,000	$250,000	$500,000–$1,250,000

For years, developers have been vocal about the frustration of Apple's payment system feeling "exploitative," cutting into revenue to the point of making it hard to sustain a business. And yet, until recently, the options were grim: pay up, ship a crippled user experience (see: every Kindle purchase ever), or redirect users out of the app to a website like Amazon does with Safari—a clunky workaround that hurts conversion and trust.

That changed in April 2025. A landmark court ruling has legally opened the door to direct billing in the US—no workarounds, no redirects, no broken UX. This article walks you through exactly how to reduce Apple App Store fees from 30% to under 5%, including the legal mechanics, a real integration walkthrough, and the billing model options available to you today.

The "Apple Tax," Deconstructed

Before diving into the solution, it's worth being precise about what Apple actually charges, because the structure is more nuanced than it first appears.

Standard 30% Commission The default rate applies to most In-App Purchases (IAP) of digital goods—game currency, premium features, subscriptions in their first year, media, and so on.

Subscription Discount to 15% For auto-renewing subscriptions, the commission drops to 15% after a subscriber's first year. So a user who stays subscribed for two years gives Apple 30% in year one and 15% from year two onward.

App Store Small Business Program: 15% for Under $1M ARR If your app earns less than $1 million in annual App Store proceeds, you can apply for the Small Business Program and pay 15% instead of 30%. The catch: if you cross that $1M threshold during the year, the 30% rate kicks in for the rest of that calendar year.

What's exempt? The commission only applies to digital goods and services consumed inside the app. Physical goods and services—an Uber ride, an Amazon order, a DoorDash delivery—are exempt. This is why the Kindle app on iOS famously won't let you purchase eBooks inside the app. Amazon is avoiding the fee on digital goods, at the cost of a deeply frustrating user experience that forces users to "drop out of the app and open the website instead."

That deliberate crippling of UX isn't just frustrating for users—it's a real conversion drag for developers. And it's precisely the problem that the Epic v. Apple ruling was designed to fix.

How Epic v. Apple Legally Unlocked Direct Billing in the US

The Epic v. Apple lawsuit centered on Apple's anti-steering policies—the rules that prohibited developers from telling users about cheaper payment options available outside the App Store. Epic argued these policies were anticompetitive. The court agreed.

The result was a permanent injunction ruling that Apple cannot prohibit developers from including buttons, external links, or other calls to action that direct customers to purchasing mechanisms outside the App Store. As of April 2025, this injunction is fully in force in the United States.

In plain terms: you can now legally present a "pay directly and save" option inside your iOS app, link to an external checkout, and process the payment yourself—without fear of App Store rejection or policy violation.

This isn't an isolated development. Globally, regulatory pressure is building:

• South Korea passed legislation forcing Apple to allow third-party payment processors—though Apple's alternative rate is still 26% with StoreKit.
• The EU's Digital Markets Act (DMA) is pushing for similar mandates across Europe, targeting platform lock-in directly.

The US ruling is the most developer-friendly outcome so far—because it creates a clear legal path to fees well under 10%, not just a slightly discounted alternative rate.

Implementing Direct Billing: The Allocents SDK

Knowing direct billing is legal is one thing. Actually shipping it is another. The gap between "we should do this" and "it's live in production" is usually the integration complexity—juggling a payment processor, Merchant of Record compliance, tax remittance across jurisdictions, fraud protection, and a checkout UI that doesn't crater your conversion rate.

Allocents was built specifically to close that gap. It's a single SDK that lets mobile app developers offer direct billing without months of custom engineering. Backed by a team that knows the mobile ecosystem inside and out, Allocents handles the complexity so you can focus on your app.

The core mechanic is a 'Sign Up & Save' paywall: a native-feeling UI that presents users with a clear choice at checkout—pay the standard price via Apple's In-App Purchase, or get a discount by paying you directly. No redirect, no clunky web view, no UX compromise. Direct payments go through a native web checkout that supports Apple Pay, Google Pay, and credit cards.

Technical Walkthrough: Live in 15 Minutes

Here's exactly how the integration works, from zero to gradual rollout.

Step 1: Add the SDK

Allocents supports Swift/SwiftUI, Kotlin, Flutter, and React Native. For a SwiftUI app, add the package via Swift Package Manager and import AllocentsKit. The SDK configuration is a single call:

import AllocentsKit

struct PaywallView: View {
    @State var product: ASProduct?

    var body: some View {
        Button("Upgrade to Pro") {
            product = Allocents.shared.product(for: "pro_monthly")
        }
        .checkoutSheet(item: $product) { result in
            // Handle success, failure, or cancellation
        }
    }
    .onAppear {
        Allocents.shared.configure(publishableKey: "as_live_...")
    }
}

The .checkoutSheet modifier handles the entire paywall presentation—the choice UI, the checkout flow, and the result callback—in a single line.

Step 2: Automatic StoreKit Product Sync

Connect your App Store Connect account in the Allocents dashboard, and the SDK automatically syncs all your StoreKit products and pricing. No manual product configuration, no duplicate data entry. Your existing IAP product IDs map directly to Allocents' checkout.

Step 3: Configure a Gradual 10% Rollout

From the dashboard, set your rollout percentage to 10%. Allocents' jurisdiction-aware routing ensures the direct billing option only appears for US-based users (where the Epic ruling applies), and only for the percentage of new users you've configured. Everyone else sees your standard StoreKit paywall, unchanged.

Use the Allocents dashboard to monitor migration rates, cohort adoption, and revenue impact in real time. Once the numbers look good, scale to 25%, 50%, 100%—or roll back instantly if anything looks off.

Step 4: Migrate Existing Subscribers with 'Switch & Save'

For your existing App Store subscribers, Allocents includes 'Switch & Save' campaigns: smart, timed prompts that offer web-only discounts to encourage migration to direct billing. The SDK manages the subscription handoff to prevent service gaps or accidental double-billing—something that's notoriously tricky to handle manually.

Choosing Your Billing Model: MoR vs. BYOS

Allocents offers two distinct tiers depending on your team's size, existing infrastructure, and appetite for handling payment operations yourself.

Option 1: Allocents Billing (Full Merchant of Record)

Fee: 5% + 50¢ per transaction

Allocents acts as the Merchant of Record—meaning they handle global tax remittance across 190+ countries, fraud protection, chargebacks, refunds, and customer support. For most teams, this is the right default. You get Apple-level billing infrastructure at an effective rate that's 6x cheaper than Apple's standard commission.

Best for: Teams who want a complete, hands-off solution with no additional compliance overhead.

Option 2: Bring Your Own Stripe (BYOS)

Fee: 0.5% of migrated revenue

If you already have Stripe infrastructure and an in-house support and compliance team, BYOS lets you plug Allocents' SDK, checkout UI, and migration flows into your existing payment stack. You remain the Merchant of Record and handle chargebacks, tax, and customer support yourself. In exchange, you pay a fraction of the MoR rate—0.5% only on revenue that Allocents' offers successfully migrate.

Best for: Larger teams with established Stripe setups who want maximum control and the lowest possible fee.

Frequently Asked Questions

What is the "Apple Tax" and how much does it cost?

The "Apple Tax" refers to the commission Apple charges on digital goods and services sold through its App Store, which is typically 30% for most developers and 15% for those in the Small Business Program or on subscriptions after the first year. This fee applies to most in-app purchases, including premium features, game currency, and subscriptions. For example, on $1,000,000 in revenue, the standard fee amounts to $300,000. While some exceptions and discounts exist, this commission has been a major cost for developers.

How does the Epic v. Apple ruling allow developers to avoid these fees?

The Epic v. Apple ruling legally allows developers in the United States to direct users to alternative payment methods outside of Apple's In-App Purchase system. Specifically, the court issued a permanent injunction preventing Apple from enforcing its "anti-steering" rules. This means you can now include buttons, links, and other calls to action within your app that guide users to a direct payment checkout, effectively bypassing the 15-30% commission.

Can I offer direct billing to users outside the US?

The ability to offer direct billing as described in this article is currently based on the US-specific Epic v. Apple court ruling. While other regions like the EU and South Korea have their own regulations pushing for alternative payment systems, the rules and associated fees can differ significantly. A solution like Allocents uses jurisdiction-aware routing to ensure that the direct billing option is only shown to users in legally permitted regions like the US, keeping your app compliant everywhere else.

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

A Merchant of Record (MoR) is a service that takes on the financial and legal responsibilities of processing payments, including handling tax remittance, fraud, chargebacks, and regulatory compliance. When you use Apple's IAP, Apple is the MoR. By using a full-service direct billing provider like Allocents, they become your MoR, saving you the significant operational overhead of managing these complexities yourself. This is different from a "Bring Your Own Stripe" model where you remain the MoR.

How can I migrate my existing App Store subscribers to direct billing?

You can migrate existing subscribers by using targeted in-app campaigns that offer them a discount to switch to a direct payment plan. Specialized tools like Allocents' 'Switch & Save' feature are designed for this purpose. They manage the technical handoff between the App Store subscription and your new direct subscription, ensuring there are no service gaps or accidental double-billing for the user, which can be complex to manage manually.

Is it worth implementing direct billing if I'm in Apple's Small Business Program?

Yes, it is still highly beneficial, as direct billing can reduce your payment processing fees from the Small Business Program's 15% rate down to around 5%. For a business earning $500,000, the difference between a 15% fee ($75,000) and a ~5% fee ($25,000) is $50,000 in reclaimed revenue. Furthermore, by moving revenue off of Apple's platform, you have a better chance of staying under the $1M threshold that would push you into the standard 30% commission tier.

See Your Exact Savings

The era of the mandatory 30% Apple tax—where your only options were to pay up or deliberately break your UX—is over. Thanks to the Epic v. Apple ruling, US developers now have a legal, clean path to direct billing that brings effective platform fees to under 5%.

With a 15-minute SDK integration, automatic StoreKit product sync, and a gradual rollout that lets you validate conversion before going all-in, there's no reason to wait.

Stop guessing what you're leaving on the table. Use Allocents' benchmarking calculator to enter your ARR and see exactly how much revenue you can reclaim by reducing your Apple App Store fees today.