Your web shop is a product: the mobile game DTC LiveOps playbook

Direct answer — how should a mobile game studio run its web shop in 2026? Run it as an operated product with a roadmap and an owner, not as a checkout page bolted onto the game. In Appcharge’s own platform data — covering, by its account, nearly $700 million in annual direct-to-consumer transactions and millions of checkout sessions across the US, Europe and Asia — “97% of web store revenue came from repeat buyers”, and repeat rates “jump above ~84%” once a player reaches their third web store purchase. That makes a web shop a retention problem before it is a payments problem: the work that pays is recruiting the first purchase, then scheduling offers, covering local payment methods and running lifecycle messaging against a base that compounds.

Most studios still budget the web shop like an integration ticket: a quarter of engineering, a payment key, a discount banner, done. That framing made sense when the whole case for direct-to-consumer was fee arbitrage. It no longer is — and the operators clearing real volume are the ones who staffed the shop like a live game.

Has the web shop actually become infrastructure?

Two payment vendors say so about their own books — directional evidence, not market measurement.

Appcharge, a DTC payments platform for mobile game publishers, states it “has crossed $1 billion in annualized direct-to-consumer transaction volume”. The ramp it publishes is the interesting part: “In July 2025, we were at $500 million. By January 2026, $700 million. Today, $1 billion.” GamesBeat dated that milestone to 23 March 2026, and PocketGamer.biz covered it the next day. Appcharge adds that it supports “more than 150 mobile games worldwide” and names partners “from King and Huuuge to Tripledot Studios and SciPlay”.

Read the scope before reusing that figure: it is annualized run-rate volume through one vendor’s rails, self-reported, not a measurement of DTC across the mobile games market. What it supports is a claim about operating scale — enough publishers now run web shops seriously that one provider doubled its throughput in eight months.

Xsolla’s August 2026 repositioning says the same thing from the product side. It describes itself as “Powering over 800 mobile game D2C experiences with global payments and merchant-of-record services tailored for the video games industry” and “Trusted by more than 70% of the top 100 highest-grossing games” — again, its own figures. It folded the storefront into a bundle organised around Core, Engagement, Monetization and Operations, with no-code LiveOps, analytics and attribution in that last box. President Chris Hewish put the reason plainly: “A checkout page on its own was never enough. Studios needed the acquisition, engagement, and live-operations tools around it to increase monetization opportunities and player retention, which most could not build on their own.”

When your payment vendor stops selling checkout and starts selling LiveOps, it has told you where the difficulty is. Deciding where a web shop sits alongside the stores, OEM channels and alternative marketplaces you already run is the sequencing work our distribution practice does before any integration ticket gets written.

Why is the web shop a retention product rather than a payments product?

Because almost none of the money is new money. Appcharge’s report on its own transaction data states that “97% of web store revenue came from repeat buyers”, then names the inflection: “Once a player reaches their third web store purchase, churn effectively collapses. Across regions, repeat rates jump above ~84% and continue climbing.”

Together those sentences reorganise the roadmap. If the revenue is repeat revenue, a percentage-point of checkout conversion is a rounding error: the asset is the cohort past the third-purchase line, and the scarce event is the first web purchase.

So the dashboard metric is not “web shop conversion rate” — that moves with traffic mix and tells you nothing. It is the share of your paying base with three or more web purchases, by cohort, plus the time a new DTC buyer takes to get there. It also settles ownership: a LiveOps calendar for in-game events plus a separate marketing calendar for shop promotions will drift apart within a quarter, and the shop will lose, because the game has the audience. One owner, one calendar, offers built against the progression and season your live team already runs.

None of this says fees stopped mattering — only that they stopped being the whole case. In the EEA, UK and US since 30 June 2026, Google states its service fee is “10% + billing fee, if applicable (standard, recurring, new installs)” and “20% + billing fee, if applicable (standard, non-recurring, new installs)”, with the billing fee “set at 5%” in those three regions. We ran the per-transaction arithmetic against those rates in our breakdown of Google Play’s 2026 fees. The conclusion there is the premise here: the fee card is public and fixed, so the variable left under your control is how much of your revenue the shop actually captures — an operating question.

What does the on-ramp to a web shop look like?

The gap between a player who has never bought outside the game and one on their third web purchase is where the design work lives, and Appcharge’s data gives that funnel a shape.

Its report describes payment links — a checkout handed to a specific player rather than a browsable storefront — as a recruiting instrument. In the US, “56% of players who used Payment Links were completely new to DTC”, and “about 25% of those Payment Link buyers later go on to make a first web store purchase”. The storefront, meanwhile, carries the bigger basket: “the average web store purchase value in the U.S. was 3× higher than Payment Links”.

That is a two-stage funnel, not two competing products. Links recruit players who would never have navigated to a shop; the storefront monetises them once the habit exists. Sequencing follows: launch link-based offers into your existing LiveOps beats, measure how many of those buyers come back through the storefront, and only then invest in merchandising and personalised bundles for that returning cohort.

The rail that carries this in the US opened through litigation, and it is worth knowing exactly how far. Apple’s App Review Guidelines state that its external purchase link entitlements “are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps”, the anti-steering prohibition applying “In all other storefronts, except for the United States storefront, where this prohibition does not apply”. The toll on that rail is unsettled: in its 11 December 2025 opinion in Epic Games v. Apple the Ninth Circuit affirmed the contempt findings but reversed the blanket commission ban and remanded, recommending that “Apple should be able to charge a commission on linked-out purchases based on the costs that are genuinely and reasonably necessary for its coordination of external links for linked-out purchases, but no more”. TechCrunch reported in August 2026 that Apple’s district-court filing proposed “new commissions of 15% for standard apps, with further discounts for developers who are enrolled in special Apple programs” — a proposal, not a rate in force.

So: build the shop with its margin assumption as a configurable input, not a number hard-coded into a spreadsheet somebody wrote in 2025.

Why payment coverage is a distribution decision

The most under-resourced part of a web shop is the payment method list, and it is where a US-designed shop quietly loses European revenue. Appcharge’s report puts the contrast in one line each. In the US, “three payment methods (credit cards, Apple Pay, Google Pay) drive roughly 75% of web store revenue”. In Europe, “No single method crosses even 30% share, and a meaningful portion of volume sits in country-specific methods”.

Ship the American checkout into Germany, Poland or the Netherlands and you ask most of your addressable buyers to reach for a second-choice instrument at the exact moment they are deciding whether they want the bundle at all. The fix is a distribution decision, not a plumbing one: treat local method coverage per market the way you treat store availability per market, on the same review cadence. The same logic runs further down the income curve, where cards are not a second choice but no choice at all — the reasoning we set out in why carrier billing converts where cards fail.

What should a studio do next?

Who should build one. Live-service titles with a real LiveOps calendar and a payer base large enough that a repeat-buyer cohort is a cohort, not a handful of accounts. A game with no seasonal structure, no offer cadence and no segmentation will hand all three gaps to its web shop.

The sequence. Stand the shop up against one live region and one existing event beat. Recruit first purchases with link-based offers inside that beat. Instrument the third-purchase cohort before anything else. Add local payment methods per market as a scheduled workstream, not a bug fix. Only then build the merchandising layer — tiers, personalised bundles, lifecycle email — against the cohort that has proven it returns.

What to measure. Share of payers with three or more web purchases, by cohort. Days from first to third web purchase. Web-shop capture rate as a share of payer revenue, by market. Payment-method coverage against each market’s actual mix. Blended take-home per hundred dollars across every rail you operate.

When not to proceed. If nobody owns the shop on the live team, do not ship it — an unowned storefront decays into a permanent discount that trains your best payers to wait. If the payer base is too small for repeat-buyer economics to compound, spend the quarter on channel reach instead; the ordering logic is in our multi-channel distribution framework, and the case for owned channels over auctions in the argument for distribution beyond paid UA.

FAQ

Is a mobile game web shop still worth building now that store fees have fallen?

Yes, but for a different reason than in 2023. Fee arbitrage narrowed: Google states that in the EEA, UK and US since 30 June 2026 its service fee is 10% plus a billing fee on standard recurring transactions for new installs, with the billing fee set at 5% in those three regions. What remains is control over pricing, offer scheduling, payment methods and the direct relationship with repeat buyers — and that only pays if the shop is operated, because Appcharge’s platform data puts 97% of web store revenue with repeat buyers.

What should a web shop’s main KPI be?

The share of your paying base that has made three or more web store purchases, tracked by cohort, rather than checkout conversion rate. Appcharge reports that once a player reaches their third web store purchase, “repeat rates jump above ~84% and continue climbing” across regions. That makes the third purchase the threshold worth engineering toward, and the time it takes a new DTC buyer to reach it the number worth compressing.

Do payment links cannibalise a web store?

Appcharge’s own transaction data treats them as two stages of one funnel. It reports that in the US “56% of players who used Payment Links were completely new to DTC”, that about 25% of those buyers later make a first web store purchase, and that the average US web store purchase was 3× the value of a payment link purchase. Links recruit, the storefront compounds — so links first, merchandised storefront second, is the lower-risk order.

Can US players be sent to a web shop from inside an iOS app?

Apple’s App Review Guidelines state that its external purchase link entitlements “are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps”, the anti-steering prohibition applying in every storefront except the United States. What Apple may charge for that link-out is unresolved: the Ninth Circuit reversed the blanket commission ban on 11 December 2025 and remanded, and Apple’s August 2026 filing proposing 15% for standard apps is a proposal, not a rate in force.

---

Working out whether a web shop earns its engineering quarter — against the alternative stores, OEM channels and carrier billing already on your roadmap — is the modelling our distribution team runs with studios. Talk to us before you commit the sprint, or start with the Founding Developer Program if channel order still matters more to you than checkout.