In the app store model you never think about payments: Apple or Google is the seller, the method is whatever the player saved, and 15 to 30% leaves before you see it. When a mobile game sells on its own web store, payments become a product decision you make once. This page is that decision laid out: methods, security, currencies, refunds, the webhook, reconciliation and the fee, plus the two things that stay with you.
Create your store free. Payments are live the moment you publish; you pay 3.9% per successful payment.
What the player sees
A mobile-first checkout in your store's colours. Cards, Apple Pay and Google Pay on the first screen, so a player on a phone can finish in a few taps. Prices in the currency you chose for their region, from a list of ten (USD, EUR, GBP, JPY, BRL, INR and more). 3-D Secure runs only when the card issuer asks for it, so most payments are not interrupted. After payment, the player is back in the game, or back on the store with the balance updated.
What happens behind it
| Step | What Appside does | What your backend does |
|---|---|---|
| Identity | Accepts a signed player token from your server, or a player ID your server verified | Signs tokens or answers player.verify |
| Payment | Takes the card, Apple Pay or Google Pay; runs 3-D Secure on request; screens every payment for fraud | Nothing |
| Proof | Sends order.paid, signed with HMAC-SHA256 over timestamp and body, deduplicated by order ID, retried until 200 |
Verifies, grants once, returns 200 |
| Refund | Sends order.refunded with the same order ID when you refund in Studio |
Reverses the grant |
| Reporting | Puts every order and refund in one ledger that Insights reads, to the cent | Reconciles against its own grants |
You never store card data, never integrate a gateway and never build a refund flow. You write one webhook handler with two cases.
Fraud and chargebacks, honestly
Every payment is screened before approval, and 3-D Secure shifts liability to the issuer when it runs. That removes most of the risk a game store sees. It does not remove all of it: a disputed card payment is still a dispute, and the refunds guide explains how to handle one and how the order.refunded webhook keeps your wallet correct. We do not promise chargeback protection, because nobody can promise that about a card.
Tax: the part that stays with you
On your own web store you are the seller, unless a merchant of record stands in between, and Appside is not one. That means sales tax or VAT is yours to collect and remit where you cross a threshold. The tax guide covers the US (state thresholds after Wayfair), the EU (OSS), the UK, Japan and Canada, and what to decide before you set prices. Platforms that are merchants of record price that service into their fee; the cheapest-way guide puts the public numbers side by side.
Reconciliation
Paid orders and refunds come from the same ledger as your order list, so Insights, your exports and your webhook log agree to the cent. The reconciliation guide shows the three-way match (your grants, our orders, your payout statement) and the two mismatches that actually happen.
The fee, against the alternatives
| Fee | What you build | Public source | |
|---|---|---|---|
| In-app purchase | 15 to 30% of every sale | Nothing | Apple and Google rate cards |
| Appside | 3.9% per successful payment, no setup fee, no subscription, no minimum | Two webhook cases | pricing |
| Self-built on Stripe | 2.9% + 30¢ per US card, more for international cards and currency conversion | The store, identity, fulfilment, refunds, fraud rules | Stripe pricing page |
| Platforms that advertise "game payments" | No rate card on their pricing pages; Xsolla's 2022 blog said 5%, Appcharge's blog says partners typically pay 4 to 5% | Nothing | Their own blogs |
On $300,000 a month, 3.9% is $11,700. The same volume in the app store at 30% is $90,000. Run your own numbers in the fee calculator.
What the ads for "game payments" are about
Two platforms advertise on these searches today. One promotes a payments SDK for Unity that unifies in-app purchases; the other promotes an iOS checkout SDK and payment links with a quoted conversion rate. Both are real products. Neither ad states a price. If you are choosing a payments layer for a web store, ask for the rate first, then compare the integration: with Appside it is a player token, one SDK call or Player ID login, and a webhook handler with two cases.
Create your store free, or watch a real payment, webhook and refund on the live demo.