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
- 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.
- A code in the wild. A creator's old code still circulates after the switch. Item 7, with end dates.
- 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.