Gift card or game key?
A gift card generally represents redeemable value; a game key represents an entitlement to specific content or a product. A gaming brand name alone does not tell you which object the customer receives.
Integration categories
Choose by what your customer needs to do.
A voucher, a player-account top-up and an eSIM solve different problems. Compare the customer outcome and the information your interface needs before opening a category-specific guide.
Side-by-side comparison
Five categories. Different decisions.
Compare the information a user needs before proceeding, not just the category names. Confirm the actual products and requirements privately for your account.
| Category | Customer outcome | What needs checking |
|---|---|---|
| Gift cards & vouchers | Redeem value later A recipient receives redeemable value for a reward, purchase or resale journey. | Brand or issuer, region, currency, denomination and redemption conditions. |
| Game top-ups | Credit a player account The journey targets a game account rather than handing over a standalone game key. | Game, player identifier, server or account region, and recipient confirmation. |
| Mobile top-ups | Recharge an existing mobile service A prepaid subscriber receives airtime or a recharge product. | Recipient number, country, operator and whether the product is airtime or a bundle. |
| Game keys & codes | Redeem a game entitlement The customer uses a code on the relevant platform or redemption service. | Title or content, edition, platform, region and activation instructions. |
| eSIM plans | Set up connectivity The customer chooses a plan and follows an installation and activation journey. | Device compatibility, destination, allowance, validity and activation conditions. |
Common mix-ups
Similar labels do not mean interchangeable products.
Choosing the wrong integration model creates the wrong interface: a missing player field, a misleading redemption button or a plan a device cannot use.
Game key or top-up?
A game key is redeemed by the customer. A direct top-up is planned around a player account. Identify the recipient and the confirmation step for the intended model instead of reusing the same checkout assumptions.
Mobile top-up or eSIM?
Mobile top-up concerns an existing prepaid service. An eSIM journey involves a compatible device and a connectivity plan. A phone number is not a substitute for checking device and activation requirements.
Define a first scope
Choose a launch category you can support well.
A broader list is not automatically a better launch. Start where the customer need is clear and your team can explain the choice, the restrictions and the support route.
- Start with one customer action
Write the action in plain language: redeem a reward, credit a player, recharge a phone, activate a key or connect a device.
- Name the missing information
List the product or recipient facts you need to validate. Separate desired markets from confirmed coverage.
- Identify the support owner
Explain who helps when redemption, account identification or activation does not go as the customer expects.
Illustrative planning example
A travel product choosing connectivity
If the customer needs mobile data on arrival, an eSIM plan may match the job. The review must cover compatible devices, destination needs and activation guidance.
If the customer instead wants to add airtime to an existing prepaid number, the relevant category is mobile top-up.
Explore business scenariosCommon questions
Questions when comparing categories.
Are the five categories confirmed product lists?
No. They describe integration interests and customer outcomes. Brand, title, operator, destination, price and availability details need confirmation for the approved scope.
Can our product combine categories?
You can state several category interests in the access request. Explain the customer action for each so the review can distinguish separate requirements. This does not guarantee that a combined scope will be approved.
Where do I find implementation details?
Read the integration guides and the API Reference in Docs. Reading documentation does not require partner approval; executing requests does. Keys, partner records and individual commercial terms remain private. Confirm each method in your approved environment before use.
Choose the categories that match your product.
Select your category interests and expected monthly volume in the form. Prepare the customer outcome for each category for the follow-up; desired scope is not confirmed availability.
Submitting a request does not create an account or guarantee approval.