Search for a game payments SDK and the ads you see are for in-app purchase wrappers: one SDK for StoreKit, Google Play Billing and PC storefronts. They make the 30% model easier to live with. This page is about the other kind of payments SDK, the one that moves the purchase to your own web store where the fee is a few percent, and brings the player straight back to the game.
The Appside SDK is that second kind. It is small on purpose: four methods, the same on every platform.
Create your store free. The SDKs are included; you pay 3.9% per successful payment and nothing else.
The four methods
| Method | What it does | Where the money is |
|---|---|---|
configure(storeId, environment, returnURL) |
Once at startup. Tells the SDK which store to open and where to send the player back. | Nowhere yet |
openStore(playerToken) |
Opens your whole web store in the platform browser, signed in as this player. | On the web, at your web store's fee |
purchase(sku, playerToken) |
Opens checkout for one pack, straight from the in-game shop. The payment link flow. | On the web |
handle(url) |
Turns the return link into a PurchaseResult so the game can refresh the balance from your backend. |
Already moved |
Events: onPurchaseCompleted, onPurchaseCanceled, onPurchaseFailed, onStoreClosed. That is the whole client surface. There is no card form in the SDK, no receipt validation and no wallet; those belong to the web checkout and to your backend.
One API, seven platforms
| Platform | Package | Verified so far (status page, November 2026) |
|---|---|---|
| Web / JS | appside/web |
Unit tests and a real-browser end-to-end journey on the demo game |
| Android (Kotlin) | AAR | Builds with Gradle, 12 JUnit tests pass, release AAR produced |
| iOS (Swift Package) | AppsideSDK |
Core compiled and smoke-tested; marked preview until the Xcode device build is published |
| Unity (UPM) | tarball | Source published, marked preview; the Unity integration, step by step |
| Flutter | package | flutter analyze clean, 12 tests pass; marked preview until a device build |
| React Native | npm tarball | Bridge tests pass; marked preview |
| Node and Python | @appside/server, appside |
Sign player tokens, verify webhooks, getOrder |
We publish the status rather than call every platform done. The web and Android SDKs are the tested routes today; the preview packages share the same API and the same server side, so an integration written against one carries over.
The flow, from tap to grant
- Your backend signs a player token behind the game's own login: player ID, five-minute expiry, your key ID. Optional attributes (level, spender tier, country) let the store target offers.
- The game calls
openStore(token)orpurchase(sku, token). The store opens in a browser sheet on iOS or Custom Tabs on Android, in your game's look, already signed in. - The player pays with a card, Apple Pay or Google Pay. 3-D Secure runs when the issuer asks. Every payment is fraud-screened.
- Your backend receives
order.paid, verifies the HMAC signature, grants once perorder_idand returns 200. Refunds arrive asorder.refundedwith the same ID. - The player returns through a Universal Link, App Link or custom scheme.
handle(url)gives the game a result it can show while it refreshes the balance from your backend.
// Server (Node): behind your own login
app.post('/appside/token', requireLogin, (req, res) =>
res.json({ token: appside.playerToken(req.user.id) }));
// Game (web shown; Kotlin, Swift, C#, Dart and TS versions in the quickstart)
await appside.purchase('voyager', await freshToken());
appside.onPurchaseCompleted = () => refreshWalletFromBackend();
The quickstart shows the same three steps in every language. The webhook guide covers signatures, retries, replays and refunds.
Without any SDK: Player ID login
If you cannot ship an app update yet, turn on Player ID login. Players type the ID they see in the game; your backend answers one player.verify webhook; purchases are delivered through the same signed order.paid webhook. No SDK, no token, no new build. Add the SDK later for the in-app path, where the player is already signed in and sees their balance.
What the in-app-purchase SDKs are selling, and what this one is
The SDKs advertised against this search unify StoreKit and Google Play Billing, or add paywalls and subscription analytics on top of them. They are good at that job, and the job keeps the purchase inside the app store at the app store's commission. A web payments SDK is a different decision: the purchase happens on your web store, at 3.9% with Appside, and the SDK's role is to make the trip there and back feel like part of the game.
Where you may show the link from inside the app depends on the storefront and region. Our dated guides cover iOS and Google Play.
Before you ship
- Grant only from the webhook, once per order ID. Test a replayed webhook and a bad signature.
- Fresh token per launch. Never cache a player token in the client.
- Handle all three results in the UI: completed, canceled, failed.
- Register the exact return URL in Studio → Integration and in your app's link handling.
- Try it on the demo game first: the live demo runs the full loop with the web SDK.
Create your store free, download the SDK for your platform from the status page, and sell your first pack on the web.