ZeroSettle Lets iOS Developers Bypass Apple's 30% Cut With Direct Billing

The Macro: The 30% Tax That Built an Industry of Workarounds

Apple takes 30% of every in-app purchase on iOS. For smaller developers, that drops to 15%, but for anyone doing real volume, it is 30%. This is not news. Developers have been complaining about it since the App Store launched. What is relatively new is that developers can now legally offer alternative payment methods in many jurisdictions, thanks to regulatory changes and court rulings (the Epic v. Apple saga, the EU’s Digital Markets Act, and similar actions in Japan, South Korea, and elsewhere).

The problem is that “legally allowed” and “practically easy” are very different things. Apple has complied with these rulings in the most grudging way possible, adding friction to alternative payment flows, requiring specific disclosures, and generally making it as annoying as possible for developers to route around the App Store billing system. The result is that most developers still use Apple’s system because implementing an alternative is complicated, risky, and filled with compliance landmines.

This creates an opportunity for companies that make the switch easy. Paddle and FastSpring handle web-based payment processing outside the App Store. RevenueCat provides subscription infrastructure that can work with multiple payment processors. But a dedicated SDK that handles the specific challenge of switching iOS users from App Store billing to direct billing, while managing the compliance requirements, is a more focused bet.

That is what ZeroSettle is building. A mobile SDK that plugs into your existing iOS app, switches customers from App Store billing to direct billing, and handles the compliance layer.

The Micro: An SDK That Pays for Itself on Day One

Ryan Elliott and Gabe Roeloffs founded ZeroSettle with the Y Combinator-backed company (W25) offering a straightforward value proposition. You integrate their SDK, your users get offered direct billing, and you stop sending 30% of your revenue to Apple.

The setup claims to take 15 minutes, which if true, removes the biggest barrier to adoption. Most developers know they should move off App Store billing but do not because the engineering work to build and maintain an alternative payment system is significant. A drop-in SDK that handles payment processing, compliance disclosures, and the user-facing billing switch reduces months of work to a quick integration.

The pricing is 5% plus 50 cents per transaction, with an optional SDK Pro tier at $9.99/month or $79.99/year. Compare that to Apple’s 30%: even with ZeroSettle’s fee, you are keeping roughly 25% more of every dollar. For an app doing $100K/month in subscriptions, that is $25K/month in recovered revenue. The ROI math is obvious and immediate.

The “instant payouts” feature is a nice bonus. Apple pays developers on a monthly cycle with a delay. Direct billing through ZeroSettle apparently settles immediately, which matters for cash flow, especially for smaller developers who are counting every dollar.

The compliance piece is where I have the most questions. Apple’s rules around alternative payment methods are deliberately complex and constantly changing. In the EU, the rules are different from the US, which are different from Japan. Keeping up with all of that is a full-time legal and engineering job. If ZeroSettle handles it well, that alone justifies the fee. If they miss something and an app gets rejected or removed from the App Store, the developer eats the consequences.

The competitive positioning is interesting because this is partially an arbitrage play. As long as Apple charges 30% and ZeroSettle charges 5%, the value proposition exists. If Apple reduces its cut significantly (unlikely but possible), the spread narrows.

The Verdict

The math is simple and compelling. Any iOS developer doing meaningful subscription revenue should at least evaluate this. The 15-minute integration claim, if accurate, makes the decision even easier.

At 30 days: how many apps have integrated the SDK, and what is the user opt-in rate for direct billing? The developer adoption is one thing. Whether end users actually switch from the familiar App Store billing to a direct payment flow is the critical unknown.

At 60 days: has any app using ZeroSettle had issues with Apple’s review process? This is the risk that keeps developers up at night. Apple has historically been aggressive about anything that routes around their payment system.

At 90 days: what does the churn look like? If developers integrate and then remove the SDK after Apple pushes back or users complain about the billing change, the retention story falls apart.

I think ZeroSettle is making a smart bet on a structural market opportunity. The regulatory environment is moving in favor of alternative payments. The economics are clear. The main risk is Apple finding ways to make life difficult for developers who use tools like this, and that risk is real but declining over time.