Xsolla vs Appcharge vs Allocents for Mobile Game Web Stores
Summary
- Mobile game studios are launching web stores to bypass Apple's 30% commission, with 72% of top-grossing games already operating one.
- Traditional web stores like Xsolla and Appcharge require redirecting users to an external website, which creates friction and hurts conversion rates.
- The best platform depends on your goals: Xsolla for maximum global payment methods, Appcharge for high-ARPU games, and SDK-first solutions for a native user experience.
- SDK-first platforms like Allocents allow developers to add direct billing inside their app in minutes, providing a native checkout flow that maximizes conversion.
You've decided it's finally time to launch a web store for your mobile game. Smart move — 72% of top-grossing mobile games already operate one. But then you start researching platforms, and suddenly you're knee-deep in Reddit threads where developers are saying things like "the info on Xsolla makes them seem sketchy or very hit-and-miss" and "I Googled and saw some articles about how they handle finances that seemed weird."
That skepticism is valid, and it's exactly why this article exists.
The April 2025 Epic Games v. Apple ruling permanently barred Apple from forcing developers to use its In-App Purchase (IAP) system in the US — unlocking an estimated $150B+ in annual IAP volume for studios willing to go Direct-to-Consumer (DTC). The opportunity is real. But so is the choice paralysis.
In this guide, we'll do an honest head-to-head comparison of the two dominant mobile game web store platforms — Xsolla and Appcharge — and contrast them with a newer, SDK-first alternative that's changing the game: Allocents. We'll evaluate them across six dimensions every monetization lead cares about: integration time, transaction fees and Merchant of Record (MoR) coverage, IAP/consumable support, subscription migration tooling, tax and compliance footprint, and iOS-native checkout quality.
Why Every Top Mobile Game Studio Is Launching a Web Store
The math is almost embarrassingly simple. Apple and Google charge a 30% commission on every in-app purchase. Third-party payment processors like Stripe run at roughly ~3%. Even web store platforms — which sit in the middle — charge between 5% and 15%, still a massive improvement.
The results speak for themselves. Playtika reported DTC revenues of $639.4M in 2023 — nearly 25% of their total revenue — after successfully migrating users off-platform and cutting effective platform fees from 30% down to 3–4%. (Source)
Adoption by genre tells a clear story too:
- Social Casino: 100% of top games operate a web store
- Strategy Games: 80%
- Action Games: 75%
If your studio is in any of these categories, a mobile game web store isn't a nice-to-have — it's a competitive necessity.
The Contenders: A Head-to-Head Comparison
Here's a quick-reference feature table across the six dimensions that matter most:
| Feature | Xsolla | Appcharge | Allocents |
|---|---|---|---|
| Integration Time | Weeks to months; significant dev lift required | Streamlined, but still a multi-system setup | 15 minutes via native SDK |
| Transaction Fees | 5% + variable channel costs | Competitive; lower than Xsolla; custom pricing | 5% + 50¢ (MoR) or 0.5% (BYOS) |
| Merchant of Record (MoR) | ✅ Full MoR | ✅ Full MoR | ✅ Full MoR |
| IAP/Consumable Support | ✅ Strong; 700+ payment methods | ✅ Strong; optimized for high-ARPU games | ✅ Strong; native SDK |
| Subscription Migration Tooling | Basic | ✅ Strong; a core differentiator | ✅ Strong; native SDK tooling |
| Tax & Global Compliance | 200+ geographies, PCI DSS compliant | Full MoR compliance | ✅ 190+ countries |
| iOS-Native Checkout Quality | Web redirect; creates friction | Mobile-optimized web; still a web view | ✅ Fully native UI; no redirect |
| Core Technology | Web-based Pay Station | Web-based DTC platform | Native SDK (iOS, Android, cross-platform) |
Now let's go deeper on each dimension.
Deep Dive: 6 Key Dimensions
1. Integration Time & Developer Experience
This is where established web store platforms often disappoint. Xsolla's Pay Station is powerful, but configuring it properly — handling webhooks, syncing your virtual goods catalog, managing player entitlements — is a multi-week project at minimum. Appcharge is more streamlined, but it's still fundamentally a separate system living outside your app's native codebase.
The hidden cost here isn't just the integration sprint. It's the ongoing maintenance: every time you update your IAP catalog, add a new store item, or run a seasonal sale, your team has to manage synchronization between your App Store products and your web store. That's engineering time pulled away from actual game development.
This is where SDK-first platforms like Allocents have a structural advantage. Because it's a native SDK, not a separate website, integration takes minutes, not weeks, and it can automatically sync with your existing App Store Connect product catalog.
2. Transaction Fees & Merchant of Record (MoR) Coverage
Quick jargon check: a Merchant of Record (MoR) is the entity legally responsible for processing a payment, including handling taxes, fraud, chargebacks, and refunds. When a platform acts as your MoR, you offload enormous operational and legal complexity. All three platforms here offer full MoR — that's a genuine baseline advantage over rolling your own Stripe integration.
Xsolla charges 5% plus variable channel costs — which can include additional fees for chargebacks ($7–15 for credit cards, $10 for PayPal). Their strength is sheer coverage: 700+ payment methods across 200+ geographies, which is genuinely hard to match.
Appcharge positions itself as more cost-competitive than Xsolla, with pricing typically negotiated based on volume. Their focus is higher-ARPU games where even marginal fee differences compound significantly.
Allocents offers two transparent pricing models. Its full Merchant of Record service is a flat 5% + 50¢ per transaction. For larger studios with existing Stripe infrastructure, its Bring Your Own Stripe (BYOS) model is just 0.5% of migrated revenue, offering maximum savings and control.
3. IAP / Consumable & Subscription Support
For consumables — coin packs, gem bundles, energy refills — all three platforms do the job. Web stores excel at selling these outside the native app flow with custom bundle promotions like the "Starter Pack" or limited-time offers that aren't possible through Apple's IAP.
Subscriptions are where differentiation starts to matter. Battle passes, VIP tiers, and ad-free upgrades are growing rapidly as mobile game monetization models, and migrating existing App Store subscribers to your web store is high-value but technically tricky. While web-based platforms like Appcharge have developed tooling for this, an SDK-first solution like Allocents can manage the entire migration flow natively within the app, presenting targeted offers to existing subscribers without sending them to an external website.
4. Tax, Fraud, and Global Compliance
This is the operational nightmare that drives most studios toward MoR platforms in the first place. Sales tax, VAT, GST — the rules vary by country, sometimes by state or province, and they change constantly. If you're selling to players in 50+ countries (and you probably are), DIY compliance with raw Stripe is a legal and accounting burden few teams can absorb.
Xsolla handles this well with PCI DSS compliance and built-in anti-fraud protection baked into Pay Station. Appcharge similarly covers global compliance as part of their MoR arrangement. As a full Merchant of Record, Allocents handles tax remittance in over 190 countries, offloading the entire compliance burden from developers.
5. iOS-Native Checkout Quality & User Experience
This is the most underappreciated dimension — and where all three traditional web store platforms share a structural weakness.
By definition, a web store pulls the user out of your app. Whether it's a WebView overlay or a redirect to a browser, there's a context switch that breaks the native app experience. For casual games that monetize on impulse purchases, this friction is a direct conversion rate killer. Players who were ready to buy a gem pack mid-session become players who closed the tab and moved on.
Xsolla's mobile checkout is functional but still a web experience. Appcharge has invested in mobile-optimized UIs that reduce friction, but it's still fundamentally a web checkout. In contrast, Allocents is the only platform of the three that offers a truly native payment experience inside the app, using the same UI components as Apple's own IAP to maximize conversion.
The Modern Alternative: The SDK-First Approach with Allocents
After evaluating the web store landscape, it's clear that the modern approach is fundamentally different — one built specifically for the post-Epic v. Apple era.
Allocents was born from the landmark April 2025 ruling. It's not a web store; it's a single mobile SDK (Swift/SwiftUI, Kotlin, Flutter, React Native) that lets you drop direct billing inside your app with fully native UI.
The structural difference: With Allocents, there is no browser redirect, no WebView, and no context switch. The checkout feels just like Apple's own IAP, eliminating the friction that kills conversion rates on web-based payment flows.
What that means in practice:
- 15-minute integration — vs. weeks or months for a web store setup
- Automatic StoreKit product sync from App Store Connect — your virtual goods catalog syncs automatically, no manual duplication
- Native UI flows including Apple Pay and Google Pay, presented inside your app
- Sign Up & Save paywalls — let new users choose direct billing or App Store at the moment of conversion
- Switch & Save campaigns — migrate existing StoreKit subscribers with targeted offers
- Gradual rollout controls — start with 10% of users, monitor, then scale with instant rollback if needed
- A/B testing for discount levels, copy, and timing
- Analytics dashboard tracking migration rates, cohort adoption, and revenue impact
On pricing, Allocents offers two transparent models:
| Model | Fee | Who handles MoR? |
|---|---|---|
| Allocents MoR | 5% + 50¢ per transaction | Allocents (full MoR: tax in 190+ countries, fraud, chargebacks, support) |
| Bring Your Own Stripe (BYOS) | 0.5% of migrated revenue | You (developer handles MoR duties) |
The BYOS model is particularly compelling for larger studios with existing Stripe infrastructure — at 0.5%, you're essentially paying for Allocents' migration UI and intelligent offer tooling, while keeping full control of payments and customer data.
How to Choose: A Decision Framework for Monetization Leads
Cut through the noise with these clear criteria:
Choose Xsolla if: You need maximum global payment method coverage (700+ methods, 200+ geographies) and have the team bandwidth to handle a complex integration. Your business model can absorb 5% + variable channel costs, and your primary market includes regions where local payment methods (not Apple Pay) drive conversions.
Choose Appcharge if: You're a top-grossing studio with high ARPU and your primary goal is a sophisticated DTC web platform. Appcharge's strength in subscriber migration tooling and high-value user offers makes it a strong fit for games with established paying user bases you're actively trying to move off-platform.
Choose Allocents if: Your priority is speed to revenue, developer experience, and a seamless native user flow. If you want direct billing inside your app — not just on a separate website — with a native UI that doesn't hurt conversion rates, Allocents is the only option built for that use case. This is especially true if you're running subscriptions or high-frequency consumable IAP where checkout friction directly costs you money.
The Bottom Line
The shift to DTC revenue is no longer optional for serious mobile game studios. The question isn't whether to capture direct billing revenue — it's how.
Traditional mobile game web store platforms like Xsolla and Appcharge have real strengths: established brand relationships, game-industry partnerships, and mature MoR infrastructure. If your monetization strategy centers on a standalone web destination with rich promotional capabilities, they're proven options.
But if your goal is to maximize in-app conversion rates, minimize integration time, and capture direct billing revenue without breaking the native iOS experience, the new generation of SDK-first tools like Allocents changes the calculus entirely.
Frequently Asked Questions
What is a mobile game web store?
A mobile game web store is an e-commerce platform that allows developers to sell in-game items like currency, subscriptions, and bundles directly to players, bypassing Apple's App Store or Google's Play Store. This Direct-to-Consumer (DTC) approach enables studios to avoid the standard 30% platform commission, significantly increasing revenue.
Why should my game have a web store?
The primary reason to launch a web store is to increase your net revenue by avoiding the 30% commission charged by Apple and Google on in-app purchases. By using a direct-to-consumer platform, which typically charges between 0.5% and 15%, you keep a much larger share of the money your players spend.
What is a Merchant of Record (MoR) and why is it important?
A Merchant of Record (MoR) is the legal entity that takes responsibility for processing all your player payments. This includes handling complex tasks like sales tax calculation and remittance, fraud prevention, chargebacks, and global payment compliance. Using a platform that acts as your MoR—like Xsolla, Appcharge, or Allocents—offloads this massive operational burden from your studio.
What's the difference between a web store and a native SDK solution?
A web store directs players out of your game to a separate website to complete a purchase, which can interrupt the user experience and lower conversion rates. In contrast, a native SDK solution like Allocents integrates the entire billing process directly inside your app, providing a seamless checkout flow that feels identical to Apple's default IAP.
How do I migrate existing subscribers from the App Store to my web store?
Migrating subscribers requires specialized tools that can identify users subscribed through the App Store and present them with targeted offers to switch to direct billing. SDK-first platforms like Allocents are particularly effective at this, as they can run "Switch & Save" campaigns natively within the app, making the transition seamless for the player.
Can I use a web store for both one-time purchases and subscriptions?
Yes, all major web store platforms support both one-time consumable purchases (like coin packs or gems) and recurring subscriptions (like battle passes or VIP tiers). They excel at offering custom bundles and promotions that aren't possible through the standard App Store IAP system.
Ready to launch direct billing in 15 minutes? Learn more about the Allocents SDK →