GUIDE / PAYMENTS SDK

A payments SDK for games that sells on the web, not through the app store

A game payments SDK that opens your web store or one pack from the game, same four methods on Unity, iOS, Android, Flutter, React Native and web, status stated per platform.

Updated

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

  1. 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.
  2. The game calls openStore(token) or purchase(sku, token). The store opens in a browser sheet on iOS or Custom Tabs on Android, in your game's look, already signed in.
  3. The player pays with a card, Apple Pay or Google Pay. 3-D Secure runs when the issuer asks. Every payment is fraud-screened.
  4. Your backend receives order.paid, verifies the HMAC signature, grants once per order_id and returns 200. Refunds arrive as order.refunded with the same ID.
  5. 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

Create your store free, download the SDK for your platform from the status page, and sell your first pack on the web.

Frequently asked questions

What does a game payments SDK do?

In the app store model it wraps StoreKit or Google Play Billing. In the web model it does something smaller and more useful: it opens your web store (or checkout for one pack) from inside the game with the player already signed in, and it hands the return link back to the game so the balance can refresh. The money moves on the web, where your fee is the web store's fee, not 30%.

Which platforms does the Appside SDK cover?

Web/JS, Android (Kotlin), iOS (Swift Package), Unity (UPM), Flutter and React Native on the client; Node and Python on the server. All of them expose the same four methods: configure, openStore, purchase and handle. The SDK status page lists what has been verified on each platform and what is still marked preview.

Is the SDK required?

No. Players can sign in to your web store with the player ID they see in the game, confirmed by one player.verify webhook from your backend. Many studios launch that way first and add the SDK later for the in-app path, where the player is already signed in and sees their balance.

How does the game know the purchase went through?

It doesn't decide; your backend does. Appside sends a signed order.paid webhook to your server, which grants the item once per order ID. The SDK's PurchaseResult is a UI hint for refreshing the screen, never the proof of payment.

What does it cost?

The SDKs are free. Appside charges 3.9% per successful payment, with no setup fee, no monthly plan and no minimum. Xsolla, whose ads promote a "Payments SDK for Unity", does not publish a rate card; its 2022 blog quoted 5% per transaction.

Does it handle Apple Pay and Google Pay?

Yes, in the web checkout the SDK opens: cards, Apple Pay and Google Pay, with 3-D Secure when the card issuer asks for it and fraud screening on every payment. The SDK itself never touches card data.

Sources

Related

SEE IT YOURSELF

Build your store
before the first call.

Try the live demo ↗Create your store
LET’S TALK

Book a demo

Connect with Oded to arrange a walkthrough of Appside.

Contact Oded on LinkedIn ↗