GUIDE / SWITCHING PROVIDERS

Switching web store providers: the checklist

Everything that has to be true before, during and after a mobile game moves its web store from one provider to another: player identity and tokens, the catalogue and prices, grants and webhooks, the domain and the return link, promo codes and offers, running both providers in parallel, the order table, refunds in flight, support scripts and the day you turn the old one off.

Updated

Switching providers isn't a re-integration; it's a migration with players mid-purchase, codes in circulation and refunds still open. The code is the small part. This is the checklist we use; the Appcharge migration guide has the code mapping for that specific case, and the A/B test design covers deciding in the first place.

Before: 8 items

# Item Done when
1 Player identity. Your backend can mint a signed player token for any authenticated player A token endpoint behind your login, tested
2 Catalogue parity. Every pack, price, currency amount, bundle and badge from the old store exists in the new one A diff of the two catalogues is empty, or the differences are deliberate
3 Grant handler. Your backend grants on the new provider's signed order.paid, exactly once per order ID, and reverses on order.refunded Test events acknowledged; the webhook proof passes
4 Order table with a provider column. Old and new orders in one table Yesterday's reconciliation runs on both (how)
5 Domain. The new store on your own domain (or a new subdomain you control) DNS verified, legal pages linked
6 Return link. The deep link back into the game works on every device you ship on Tested on a real iOS and Android device (deep links)
7 Offers and codes. The first-purchase offer, current bundles and live codes recreated; old codes mapped or retired with an end date A list of every live code, with its fate
8 Support script. One paragraph: what changed, what to do if a purchase doesn't arrive, which order ID to ask for The support team has it

During: 7 items

# Item Done when
9 Both providers live. Your backend decides per player which store to open A flag per player or per tier
10 Move by tier, not all at once. Non-spenders first, then low, medium, high Each tier moved after a week without a delivery ticket
11 Daily three-way match on both. Old orders, new orders, grants Zero unexplained rows for seven days
12 Old refunds still honoured. The old webhook handler stays live; old orders stay refundable Refund on an old order reverses the grant correctly
13 Links updated. In-game, email, Discord, website: every store link points at the new store A search of your own channels for the old URL finds nothing current
14 Measure both. Net revenue per eligible player per tier, both sides (A/B design) A week-2 reading that holds
15 Keys and secrets. New provider's keys registered; old provider's keys scheduled for revocation on the cutoff date A dated note in the runbook

After: 5 items

# Item Done when
16 Cutoff date. All players on the new store; old store unpublished No new old-provider orders for seven days
17 Old refund window. Old handler stays live until the last old order's refund window closes Date on the calendar
18 Old keys revoked. After the window Confirmed revoked
19 Order table frozen for the old provider. Rows kept, marked closed Finance has the final old-provider total
20 Retrospective. What broke, what took longest, what you'd keep One page in the runbook

The three things that go wrong

  1. Identity. The old provider used its own web accounts; players on the new store "lose" nothing, but support gets "where's my account?" for a month. The script in item 8 answers it: your game account is the account.
  2. A code in the wild. A creator's old code still circulates after the switch. Item 7, with end dates.
  3. A refund on an old order after cutoff. Item 12 and 17. The grant must still reverse, or you're paying twice.

On Appside

The new-side integration is the three steps in the quickstart; item 9 is one line in your backend; items 3, 4 and 11 use the same signed webhook and order table as everything else on this site. The migration guide maps an Appcharge Payment Links integration step by step, and you can verify the integration with test cards before you decide the cutoff.

Create your store free as side B. No card needed to start; 3.9% per successful payment.

Frequently asked questions

How long does switching web store providers take?

The integration is days with a three-step provider (player token, openStore, signed webhook). The switch is weeks, because you run both providers in parallel, move players gradually and keep the old provider''s orders reconcilable until its last refund window closes.

Do players have to log in again?

Not if the new provider signs players in from the game. With a player token minted by your backend, the player never had a web login to lose. If the old provider used web accounts, those don''t move; the game account does.

What about orders and refunds still open on the old provider?

Keep the old webhook handler live until the old provider''s refund window has closed for its last order, and keep its orders in your order table with a provider column, so a refund on an old order still reverses the grant.

Can I keep my store domain?

If the domain is yours, yes: repoint it when the new store is published. If the store lived on the old provider''s domain, you''re also moving links in the game, in emails and in communities, which is a reason to put the new store on your own domain from day one.

Is there a migration guide for Appcharge specifically?

Yes, Appside''s docs have one; it maps the Payment Links flow onto the three Appside steps and covers running both providers during the switch.

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 ↗