"Launch your web shop in days" is the promise in the ads. Here is what the days actually contain, so you can plan them. The plan assumes a live mobile game with a backend that knows its players, and a team of one producer plus whoever runs the game server. It does not assume a designer, a front-end developer or a payments integration.
Create your store free and follow along; the first step takes two minutes.
Day 1: the shop exists
Morning: draft it from your app link. Paste your App Store or Google Play link into the builder. It reads your icon and screenshots and drafts a web shop in your game's look: colours checked for contrast, a hero built from your own screenshots, pack names and pack art per price tier. Nothing is live yet.
Review every pack and price. The draft proposes; you confirm. Set the product IDs your backend expects, the amounts each pack grants, and the "save vs in-app" line if you want to show it. Prices can be shown in ten currencies.
Afternoon: payments and legal. Cards, Apple Pay and Google Pay are on by default, with 3-D Secure and fraud screening. Write the terms and privacy pages, or start from the legal pages guide. Decide who collects tax: on your own web shop that is you, so read the tax guide before you set prices.
End of day 1: a complete shop in your game's look, unpublished.
Day 2: the shop knows your players
This is the one task that needs your backend, and there are two ways to do it.
Fast path, no app update: Player ID login. In Studio → Integration → Player login, turn on Player ID and enter a verify URL on your server. Appside sends player.verify with the ID a player typed; your server answers valid or not, signed. Write the label players see ("Your Player ID · Settings → Profile"). Studio's Send test shows the exact request and your response, and the shop can publish only after the last test passed. For most game servers this is an afternoon.
Smooth path, needs an app update: the SDK. Your server signs a five-minute player token; the game calls openStore(token) so the player arrives signed in with their balance visible. Same server, same webhooks, better conversion from inside the app. Most studios launch with Player ID and add the SDK in the next app release. The payments SDK guide covers every platform.
Either way: the fulfilment webhook. Set your Fulfillment URL and a webhook secret. Appside delivers every paid order as a signed order.paid POST; your server verifies the signature, grants once per order ID and returns 200. Press Send test event in Studio and watch it acknowledge. Refunds arrive as order.refunded with the same ID, so the reversal is one more case in the same handler.
End of day 2: players can sign in, and purchases reach the game.
Day 3: prove it, publish it, announce it
Buy a pack yourself with a real card. Watch the webhook arrive, see the balance move in the game, then refund the order from Studio and watch order.refunded reverse it. If that loop works once, it works for every player.
Publish. Preview, then publish. Every version is kept, so a mistake is a restore, not an outage.
Launch with a reason to visit. The launch kit sets up a first-purchase bonus, a capped launch discount code or a gift code, each tested before it goes live, with a tracked link, the code, a QR image and ready text for Discord, X and your in-game news. Caps hold on real payments: checkout reserves a code use for 30 minutes, so the last use cannot be spent twice.
Watch the first numbers. Insights counts visits from real browsers only, checkout starts, paid orders, refunds and net, by source and campaign, so you know on day 4 whether the Discord post or the in-game news item brought the buyers.
What still needs a developer, and what never does
| Needs your backend developer | Never needs a developer |
|---|---|
The player.verify webhook (Player ID) or the player-token endpoint (SDK) |
Design, packs, prices, bonuses, bundles |
The order.paid and order.refunded handler |
Offers, promo codes, gift codes, banners, news posts |
| Adding the SDK call to the in-game shop, when you choose to | Languages, local prices, payment methods per region |
| Hosting the Universal Link file, if you use the SDK | Publishing, restoring versions, reading Insights |
Two webhooks on a server you already run. That is the whole engineering scope of a launch.
Where the days go wrong
- Prices set before tax is understood. Decide who collects first; the tax guide is short.
- Granting from the return link. The browser can close before the player returns. Grant only from the webhook.
- No reason to visit. A shop with no launch offer gets the players who were already looking for it. Use the launch kit.
- The link from the app, before the rules are checked. Where a game may link out depends on storefront and region: iOS and Google Play guides are dated and sourced.
What it costs
Nothing until a player pays. Appside charges 3.9% per successful payment, with no setup fee, no monthly plan and no minimum, and the builder, Studio, launch kit and Insights are included. The ads that promise a web shop in days come from vendors whose pricing pages have no rate card; ask them for the number before day 1.
Create your store free. Day 1 starts with your app link.