
Quick clarification before we dive in: There are two products named "StoreKit" in the wild. One is a restaurant point-of-sale system. The other — and the one this article is entirely about — is Apple's StoreKit framework, the developer API that powers In-App Purchases (IAP) on iOS. If you're an app developer hunting for a StoreKit alternative to escape Apple's 15–30% commission, you're exactly where you need to be.
The iOS payment landscape changed permanently in April 2025. The landmark Epic v. Apple ruling barred Apple from forcing US developers to use its IAP system, unlocking what analysts estimate to be over $150 billion in annual IAP volume. For the first time, iOS developers can legally offer direct billing to their users — and keep far more of their revenue.
But choosing the right path is genuinely hard. Developers on r/iOSProgramming put it bluntly: "RevenueCat is great, but fees stack fast, especially when you're already giving Apple 15–30% + taxes." Others on r/SaaS describe global tax compliance as "WAY too much of a bureaucratic nightmare" — registering for Sales Tax and VAT in dozens of jurisdictions is a full-time job, not a side task.
To cut through the noise, we evaluated each StoreKit alternative across the five criteria that actually move the needle:
Let's get into it.
Commission: 5% + 50¢ (MoR) or 0.5% (Bring Your Own Stripe) Integration: ~15 minutes · Single SDK Merchant of Record: ✅ Yes (on standard plan) Tax Remittance: ✅ Yes (190+ countries)
Allocents is the most purpose-built StoreKit alternative on this list. Born from the landmark April 2025 Epic v. Apple ruling, Allocents was designed from day one for the post-Epic world — and it shows in every API surface.
The headline differentiator is the price. Apple charges 15–30% commission. Allocents charges 5% + 50¢ per transaction as a full Merchant of Record. On a $9.99/month subscription, that's the difference between handing Apple $3.00 and paying Allocents $1.00. At scale, that gap is enormous.
For teams who already have Stripe infrastructure, Allocents offers a Bring Your Own Stripe (BYOS) mode that drops the fee even further to 0.5% of revenue that Allocents' intelligent offers successfully migrate from StoreKit — putting you firmly in control of the billing relationship while still leveraging Allocents' proven migration UI.
What makes integration genuinely fast:
Allocents ships a single SDK supporting Swift/SwiftUI, Kotlin, Flutter, and React Native. Critically, it auto-syncs your existing products from App Store Connect — no manual re-entry of SKUs. The typical integration time is 15 minutes, compared to the multi-day (or multi-week) effort of stitching together Stripe + RevenueCat + a tax compliance service.
Migration, not a rip-and-replace:
This is where Allocents pulls ahead for any app with an existing subscriber base. The SDK includes:
Who handles the hard stuff:
On the standard plan, Allocents is the Merchant of Record. That means they absorb the legal liability for every transaction: payment processing, fraud protection, chargeback disputes, customer support, and — critically — tax remittance in 190+ countries. The VAT-and-Sales-Tax nightmare that haunts developer forums simply disappears from your to-do list. Jurisdiction-aware routing also ensures that direct billing options are only surfaced in regions where it's legally permitted, keeping you compliant without extra engineering effort.
Best for: iOS app developers with $500K–$20M+ ARR who want to exit Apple's commission structure without building their own payments and tax infrastructure from scratch.
Commission: Tiered % on Monthly Tracked Revenue (MTR) — added on top of Apple's or your processor's fees Integration: Fast (SDK wrapper) Merchant of Record: ❌ No Tax Remittance: ❌ No
RevenueCat is the most widely-adopted subscription management backend in the iOS ecosystem — and for good reason. One developer on their site noted it "replaced 37,000 lines of code with ~1K lines of RevenueCat integration." If StoreKit's subscription lifecycle events feel like wrangling chaos (pending purchases, receipt validation, App Store Server Notifications), RevenueCat tames them elegantly.
What RevenueCat is not, however, is a payment processor or a Merchant of Record. It's a smart orchestration layer that sits on top of Apple's IAP or a direct processor like Stripe. That means its tiered pricing is an additional fee on top of whatever you're already paying Apple or Stripe — exactly the fee-stacking that developers complain about. It also means tax remittance and MoR responsibilities remain entirely with you.
Best for: Developers who want clean subscription logic, cross-platform analytics, and webhook events, and are content to keep Apple as their payment processor (or manage their own).
Commission: ~5–10% (all-in, includes MoR services) Integration: Moderate (full payment platform) Merchant of Record: ✅ Yes Tax Remittance: ✅ Yes (global)
Paddle has been the go-to Merchant of Record for SaaS companies for years, and it's extending into mobile billing in the post-Epic environment. As Paddle's own documentation explains, acting as MoR means Paddle takes legal responsibility for each transaction: currency conversion, Sales Tax and VAT calculation, fraud detection, chargeback disputes, and PCI-DSS compliance.
The trade-off is complexity. Paddle is built for web-first products and can require additional tooling for deep in-app subscription logic — meaning many teams end up pairing it with RevenueCat, which reintroduces integration overhead and stacked fees. It's a powerful choice for teams already in the Paddle ecosystem, but for a mobile-first app starting fresh, the single-SDK simplicity of Allocents is significantly leaner.
Best for: SaaS teams with existing Paddle infrastructure expanding into mobile, or developers who prioritize an established MoR with a long global track record.
Commission: ~2.9% + 30¢ (Stripe) + Stripe Tax % + RevenueCat MTR fee Integration: High (multi-system setup) Merchant of Record: ❌ No (you are) Tax Remittance: ❌ No (you are liable)
For developers whose worldview is "whenever possible, I prefer to build, not buy" (r/iOSProgramming), pairing Stripe with RevenueCat is the classic power-user approach. You own the payment stack, control the customer data, and can customize every flow — but you take on every responsibility that comes with it.
The fee structure adds up fast: Stripe's standard 2.9% + 30¢, plus Stripe Tax for automated compliance, plus RevenueCat's MTR-based subscription fee. You also remain the Merchant of Record, meaning chargebacks, fraud disputes, and tax remittance are your team's problem. If you don't have in-house legal, compliance, and support infrastructure, the operational cost of this route often outweighs the savings.
Best for: Large app teams with existing Stripe accounts, in-house compliance capabilities, and a strong preference for owning every layer of the stack.
Commission: Tiered % on MTR (free tier up to $10K/month) Integration: Moderate (SDK) Merchant of Record: ❌ No Tax Remittance: ❌ No
Adapty carved out a strong niche by going deep on what RevenueCat covers more lightly: paywall design, A/B testing, and monetization analytics. Its visual paywall builder lets you iterate on pricing, copy, and layout without shipping new app versions, and its flexible pricing model includes a generous free tier for apps under $10K/month — making it a great entry point for early-stage apps.
Like RevenueCat, Adapty is a subscription management layer, not a payment processor. It doesn't handle MoR responsibilities or tax remittance.
Best for: Growth-focused teams who want to aggressively optimize conversion rates on their paywalls and run data-driven pricing experiments.
Commission: Tiered % on MTR (free tier available) Integration: Fast (SDK wrapper) Merchant of Record: ❌ No Tax Remittance: ❌ No
Glassfy is a reliable subscription infrastructure SDK that emerged as a popular alternative to legacy lightweight frameworks like SwiftyStoreKit after Apple introduced StoreKit 2. It handles receipt validation, entitlement management, and App Store Server Notifications cleanly, with competitive pricing, and a straightforward SDK.
Best for: Developers who need a dependable subscription backend and find RevenueCat's pricing steep at their revenue tier.
Commission: Tiered % on MTR Integration: Fast (SDK wrapper) Merchant of Record: ❌ No Tax Remittance: ❌ No
Apphud goes slightly broader than pure subscription management, bundling in rules-based in-app messaging, push notification triggers, and user segmentation tools alongside its IAP infrastructure. Think of it as RevenueCat with a lightweight CRM layer on top.
Best for: Indie developers or small teams who want subscription infrastructure and basic lifecycle messaging tools without stitching together separate services.
| Alternative | Commission Rate | Integration Effort | Merchant of Record? | Tax Handled? | Key Differentiator |
|---|---|---|---|---|---|
| Allocents | 5% + 50¢ (MoR) or 0.5% (BYOS) | ~15 min · Single SDK | ✅ Yes (standard plan) | ✅ 190+ countries | All-in-one MoR + migration SDK built for post-Epic |
| RevenueCat | Tiered % on MTR (+ processor fees) | Fast (SDK wrapper) | ❌ No | ❌ No | Best-in-class subscription logic & analytics |
| Paddle | ~5–10% all-in | Moderate | ✅ Yes | ✅ Global | Established MoR, strong global tax compliance |
| Stripe + RevenueCat | ~2.9% + 30¢ + Tax % + RC % | High (multi-system) | ❌ No (you are) | ❌ No (you're liable) | Maximum control and customization |
| Adapty | Tiered % on MTR | Moderate (SDK) | ❌ No | ❌ No | Advanced paywall A/B testing |
| Glassfy | Tiered % on MTR | Fast (SDK wrapper) | ❌ No | ❌ No | Reliable StoreKit 2 subscription infrastructure |
| Apphud | Tiered % on MTR | Fast (SDK wrapper) | ❌ No | ❌ No | IAP tools + basic app growth & messaging features |
The options above fall into three clear camps:
For most developers earning $500K+ ARR who want to meaningfully recapture margin after the Epic ruling, Allocents sits in a uniquely compelling position. The 5% + 50¢ fee structure versus Apple's 30%, a 15-minute single-SDK integration, automatic StoreKit product sync, and full MoR coverage across 190+ countries deliver Apple-quality billing infrastructure without Apple's price tag. The gradual 10% rollout feature alone removes the biggest risk most teams feel about migrating an existing subscriber base.
Switching from Apple's StoreKit allows developers to bypass Apple's 15-30% commission on in-app purchases, significantly increasing revenue. Following the Epic v. Apple ruling, US developers are no longer required to use Apple's IAP system exclusively. By implementing a StoreKit alternative, you can offer direct billing to your users and keep a much larger portion of your earnings. For example, a service like Allocents charges 5% + 50¢, compared to Apple's up to 30%, which can translate to thousands or even millions of dollars in reclaimed revenue.
A Merchant of Record (MoR) is the legal entity that takes responsibility for all of your customer transactions, including handling payments, sales tax, fraud, and chargebacks. Using a provider that acts as your MoR, like Allocents or Paddle, means they handle the complex and legally-liable aspects of global sales. This includes calculating and remitting VAT and Sales Tax in over 190 countries, managing payment disputes, and ensuring PCI compliance. Without an MoR, your company is legally responsible for all of these tasks.
Allocents is an all-in-one payment processor and Merchant of Record, while RevenueCat is a subscription management layer that sits on top of a separate payment processor like Apple's StoreKit or Stripe. RevenueCat helps you manage subscription logic but does not process payments or handle tax compliance; you still pay processor fees plus RevenueCat's fee. Allocents is a complete alternative that replaces StoreKit, handling payment processing, tax remittance, and subscription logic within a single SDK for a single, lower fee.
Yes, you can migrate existing subscribers by offering them an incentive to switch. You cannot automatically move subscribers from StoreKit to a new system. Instead, you need to prompt them within your app to switch their subscription. Solutions like Allocents are built for this, providing "Switch & Save" campaigns that offer existing users a discount to move to direct billing, allowing for a gradual, controlled migration.
Following the Epic v. Apple ruling, developers in the US are legally permitted to include buttons and external links that direct customers to purchasing mechanisms besides Apple's IAP. Your app can present both Apple IAP and direct payment options side-by-side. Some solutions have jurisdiction-aware routing built-in, ensuring that direct billing options are only shown to users in regions where it is legally compliant, protecting you from policy violations.
The biggest risks are the legal and operational burdens of becoming your own Merchant of Record, which include global tax compliance, fraud management, and handling chargeback disputes. While a DIY stack with Stripe gives you maximum control, it also means you are legally liable for every transaction. You must register for, collect, and remit sales taxes and VAT in every jurisdiction where you have customers, a complex process that can lead to significant penalties if done incorrectly.
Ready to see what a 15-minute integration looks like in practice? Learn more about Allocents or book a call with our team to get your first direct-billing paywall live today.