7 Best Mobile App Payment Processing SDKs for iOS Developers
Summary
- The Epic v. Apple ruling allows US iOS apps to bypass Apple's 15-30% commission but shifts the complex burden of global tax, fraud, and compliance onto the developer.
- A Merchant of Record (MoR) solution is crucial, as it handles these complex payment liabilities on your behalf.
- For apps with $500K+ ARR, Allocents offers a full MoR and a 15-minute SDK to help you migrate from Apple IAP and add ~25% to your margins.
The iOS app economy just had its most significant shakeup in years. On April 30, 2025, the landmark Epic v. Apple ruling permanently barred Apple from forcing developers to use its In-App Purchase (IAP) system in the US. As of May 1, 2025, apps can include buttons and direct links to web-based payments — no Apple commission required.
For iOS developers, this is the moment you've been waiting for. But the freedom to bypass Apple's 15–30% "tax" comes with a new set of responsibilities that Apple used to handle for you: global tax remittance, fraud protection, chargebacks, and PCI compliance. As one developer put it on Reddit, "the complexity of different tax systems across regions leads to significant time loss and frustration."
This is where choosing the right mobile app payment processing SDK becomes mission-critical.
The key term to understand is Merchant of Record (MoR) — a legal entity that takes on the liability for managing payments, global sales tax, chargebacks, and compliance on your behalf. A full MoR solution can unlock the revenue benefits of direct billing without the operational nightmare.
We evaluated the top 7 mobile app payment SDKs across four criteria critical to iOS developers in the post-Epic era:
- Integration Speed — How fast can you ship?
- Fee Structure — What's the all-in cost per transaction?
- Checkout Quality — Does it support Apple Pay, Google Pay, and native UI?
- MoR Coverage — Does it handle global tax and compliance for you?
1. Allocents — Best for Apps with $500K+ ARR Ready to Escape Apple's Commission
Allocents was built specifically for the post-Epic world. Their single SDK lets you offer direct billing alongside or instead of Apple IAP — and the integration takes just 15 minutes.
- Integration Speed: 15 minutes. Drop-in SDK for Swift/SwiftUI, Kotlin, Flutter, and React Native.
- Fee Structure: Two modes:
- Allocents Billing (MoR): 5% + 50¢ per transaction — all-in, no hidden fees.
- Bring Your Own Stripe (BYOS): 0.5% of migrated revenue (you handle MoR responsibilities).
- Checkout Quality: Best-in-class native UI flows — "Sign Up & Save" paywalls, "Switch & Save" campaigns to migrate existing StoreKit subscribers, native web checkout with Apple Pay/Google Pay, and smart cancellation flows with built-in A/B testing.
- MoR Coverage: Full MoR in the Allocents Billing model — payments, tax remittance in 190+ countries, chargebacks, fraud protection, and customer support, all handled.
Standout features include automatic StoreKit product sync from App Store Connect, gradual migration rollout (start with just 10% of users and scale up with instant rollback capability), and jurisdiction-aware routing that only shows direct billing where it's legally compliant.
| Pros | Cons |
|---|---|
| Fastest integration (15 mins) to escape Apple's fee | Primarily targets apps with $500K+ ARR |
| Full MoR handles all tax/compliance headaches | US-first due to the Epic ruling's jurisdiction |
| Single SDK replaces Paddle + RevenueCat multi-system setup | Newer player in the payments space |
Recommended for: Mobile apps and games with $500K to $20M+ ARR — particularly subscription apps (fitness, media, dating, productivity) and mobile games with consumables (coins, gems) looking to add ~25% to their margins with minimal engineering lift.
2. Paddle — Best for SaaS Apps with Cross-Platform Needs
Paddle is a veteran Merchant of Record built for SaaS businesses. If you're already selling on the web and want a unified payments and compliance partner for your iOS app, Paddle is a proven, enterprise-trusted solution.
- Integration Speed: Fast, with comprehensive developer documentation and a well-maintained SDK.
- Fee Structure: Volume-based pricing (not publicly flat-rate; requires a quote for apps at scale).
- Checkout Quality: Localized, high-performance checkout with broad payment method support.
- MoR Coverage: Yes — full MoR handling tax, fraud, chargebacks, and global compliance.
| Pros | Cons |
|---|---|
| Proven, comprehensive MoR for global sales | Pricing can be less transparent than flat-rate competitors |
| Excellent for SaaS teams with existing web storefronts | Can feel like a multi-system setup for mobile-only migrations |
| Strong reputation and community trust for tax compliance | Not purpose-built for the post-Epic iOS StoreKit migration use case |
Recommended for: SaaS companies and cross-platform developers who already have a web presence and want a unified MoR to handle sales across web, iOS, and Android.
3. Stripe — Best for Large Teams that Want Full Control
Stripe is the developer's standard for building custom payment flows. Its APIs are world-class — but using Stripe means you become your own Merchant of Record, taking on the full burden of tax compliance, fraud, and chargebacks.
- Integration Speed: Moderate. Excellent APIs, but a complete implementation demands significant in-house dev work.
- Fee Structure: Standard 2.9% + 30¢ per successful card charge.
- Checkout Quality: Highly customizable. Supports Apple Pay and Google Pay.
- MoR Coverage: No. You are the MoR — tax remittance, chargebacks, and compliance are your problem.
| Pros | Cons |
|---|---|
| Extremely powerful and flexible APIs | Developer is the MoR — must handle all tax/compliance |
| Massive ecosystem of integrations and community support | Requires dedicated engineering, finance, and legal resources |
| Best-in-class documentation | Not a turnkey solution for escaping Apple IAP |
Recommended for: Well-resourced companies with dedicated engineering, finance, and legal teams who require full control over their payment stack.
4. RevenueCat — Best Subscription Management Layer (Needs a Payment Processor)
RevenueCat is not a payment processor — it's a powerful subscription management platform that acts as a single source of truth for user entitlements across iOS, Android, and the web. It's a frequent topic in developer communities, including this popular Flutter thread on subscription SDK comparisons.
- Integration Speed: Fast for managing subscription state and entitlements.
- Fee Structure: Tiered pricing based on tracked revenue.
- Checkout Quality: Doesn't process payments directly — integrates with Stripe, Paddle, or others for web billing.
- MoR Coverage: No. It's a management layer, not a payment or compliance solution.
| Pros | Cons |
|---|---|
| Excellent for managing cross-platform subscriptions and entitlements | Not a payment processor — requires a separate payments provider |
| Powerful analytics and user lifecycle tracking | Adds cost and complexity to your stack |
| Abstracts away StoreKit and Play Billing complexity |
Recommended for: Subscription apps that need robust entitlement management across multiple platforms. Often used in combination with a payment processor like Stripe or an MoR like Allocents or Paddle for direct billing.
5. Braintree — Best for Apps Where PayPal/Venmo Conversion Matters
Braintree, owned by PayPal, is a strong choice for any app where your user base is likely to prefer paying via PayPal or Venmo. Its standout strength is breadth of payment method support.
- Integration Speed: Fast, with well-maintained SDKs and clear documentation.
- Fee Structure: Standard 2.9% + 30¢ per transaction.
- Checkout Quality: Supports credit cards, PayPal, Venmo, Apple Pay, and Google Pay.
- MoR Coverage: No. Developer handles MoR responsibilities.
| Pros | Cons |
|---|---|
| Native PayPal and Venmo support can boost conversion meaningfully | Developer is responsible for tax remittance and compliance |
| Backed by a globally trusted brand | Limited built-in fraud protection vs. a full MoR |
| Works well for both mobile and web payments | Less suited to StoreKit migration use cases |
Recommended for: E-commerce apps or marketplaces where the user base has strong PayPal or Venmo preference and the team is equipped to handle their own MoR responsibilities.
6. Adyen — Best for Large Enterprises with Global Omnichannel Needs
Adyen is an enterprise-grade, all-in-one payments platform built for large global companies. It unifies payment processing, fraud management, and acquiring across countries and channels.
- Integration Speed: Slower and more complex due to enterprise compliance requirements and extensive setup.
- Fee Structure: Custom pricing based on volume, region, and payment method.
- Checkout Quality: Excellent global and local payment method support.
- MoR Coverage: Yes — Adyen can act as MoR in its full-service model.
| Pros | Cons |
|---|---|
| Powerful all-in-one global payments platform | Overkill for most small-to-mid-size app teams |
| Ideal for businesses operating across physical and digital | Higher complexity and longer onboarding timelines |
| Can act as a full Merchant of Record | Custom pricing lacks the transparency of flat-rate options |
Recommended for: Large, multinational enterprises managing high-volume, complex payment operations across many countries and sales channels.
7. Square — Best for Businesses Bridging In-Person and In-App Payments
Square's Mobile Payments SDK is a great fit for businesses that already use Square for point-of-sale and want to create a unified payment experience within their mobile app.
- Integration Speed: Fast and straightforward with clear developer documentation.
- Fee Structure: Competitive at approximately 2.9% + 30¢ for online transactions.
- Checkout Quality: Clean native UI for in-app payments.
- MoR Coverage: No.
| Pros | Cons |
|---|---|
| Excellent for businesses with both online and offline sales | Not suited to digital subscription or StoreKit migration use cases |
| Simple, developer-friendly SDK and trusted brand | Primarily strong in regions where Square operates |
| Strong fit for SMBs already on the Square ecosystem | Developer handles tax and compliance |
Recommended for: Cafes, fitness studios, and service businesses that use Square's POS in-person and want a consistent payment experience in their mobile app.
Decision Matrix: Which SDK Is Right for Your App?
Not every app needs the same solution. Here's a quick map from your app's profile to the right tool:
| App Profile | Primary Need | Best SDK |
|---|---|---|
| $500K–$20M+ ARR, lean iOS team | Escape Apple's 30% cut fast with zero ops overhead | Allocents |
| SaaS with global web + mobile presence | Unified MoR for cross-platform tax compliance | Paddle |
| Large team, dedicated engineering & finance | Full payment control and custom flows | Stripe |
| Subscription app, multi-platform entitlements | Manage subscription state across iOS/Android/web | RevenueCat + processor |
| E-commerce app with PayPal-heavy users | Maximize payment method conversion | Braintree |
| Enterprise with complex global operations | High-volume, multi-country omnichannel payments | Adyen |
| Omnichannel business (in-store + in-app) | Unify in-person and mobile payments | Square |
Take Back Your Revenue
The Epic v. Apple ruling has fundamentally redrawn the map for iOS app monetization. For the first time, you have a genuine, legally protected choice: stop handing 30% of your revenue to Apple and invest it back into your product and your team.
But freedom comes with responsibility. Moving off Apple IAP means you now own the questions of global tax remittance, fraud protection, and chargeback management — headaches that Apple quietly absorbed in exchange for that commission. The good news: the right mobile app payment processing partner can take all of that off your plate, leaving you to focus on what you actually do — build a great app.
If your app is pulling in $500K or more in ARR, the math is straightforward. At Apple's 30%, you're leaving roughly $150,000 per million dollars of revenue on the table every year. With a full MoR like Allocents at 5% + 50¢, you recapture most of that — in as little as 15 minutes of integration work.
Frequently Asked Questions
What is a Merchant of Record (MoR) and why do I need one for my iOS app?
A Merchant of Record is a company that takes on the full legal and financial liability for processing your app's payments. This includes handling global sales tax, fraud, chargebacks, and PCI compliance. After the Epic v. Apple ruling, developers who bypass Apple's IAP must manage these responsibilities themselves. Using an MoR like Allocents or Paddle offloads this entire operational burden, allowing you to focus on your app while still benefiting from lower transaction fees.
Can I legally stop using Apple's In-App Purchases in my iOS app?
Yes, in the United States, the Epic v. Apple court ruling permanently allows developers to include buttons and links in their apps that direct users to external payment systems. This ruling applies specifically to the US App Store, so you must still adhere to local guidelines in other regions. Solutions like Allocents offer jurisdiction-aware routing, which means they only show direct billing options to users in legally compliant regions.
Why shouldn't I just use Stripe to process payments directly?
While Stripe is a powerful payment processor, using it directly makes you the Merchant of Record. This means you are solely responsible for calculating and remitting sales tax globally, managing fraud, and handling chargebacks. This requires significant engineering, finance, and legal resources. A full MoR solution absorbs this complexity for a slightly higher fee, providing a much faster and safer path to escaping Apple's 30% commission.
How is Allocents different from Paddle for mobile app payments?
Allocents is built specifically for the post-Epic iOS migration use case with a 15-minute SDK integration, whereas Paddle is a veteran MoR traditionally focused on cross-platform SaaS businesses. Allocents offers features tailored to iOS developers, like "Switch & Save" campaigns to migrate existing subscribers and automatic StoreKit product syncing. Paddle is a robust, enterprise-trusted solution, especially for companies that already have a significant web presence.
What is the difference between RevenueCat and a payment processor?
RevenueCat is a subscription management platform, not a payment processor; it tracks user entitlements and subscription status but does not handle the actual financial transaction. You would use RevenueCat to manage cross-platform subscription logic, but for direct billing, you still need a payment processor like Stripe or a full MoR solution like Allocents to process the payment and manage compliance.
How do I migrate my existing subscribers from Apple IAP to a direct payment system?
The best practice is to use a tool with built-in migration campaigns that incentivize users to switch, such as offering a discount. SDKs like Allocents provide "Switch & Save" flows that present a native UI to existing subscribers, making it easy for them to re-subscribe via the web with Apple Pay. It's crucial to use a gradual rollout feature to test the migration with a small percentage of users first to ensure a smooth transition.
Ready to see exactly what direct billing could mean for your bottom line?
Book a free migration analysis with Allocents → Their team will map out the exact revenue impact and build a step-by-step plan to migrate your users off Apple IAP — with gradual rollout controls so you never risk disrupting your existing subscriber base.