Use the Cardzone B2B API to sell game top-ups and digital vouchers in your own checkout. This page shows what you can build and where to start.
- A top-up adds credit straight to a player’s game account.
- A voucher is a code or PIN that the customer uses later.
How it works:
- You list Cardzone products.
- You place orders. Your store wallet pays for each order. The store wallet is your store’s balance with Cardzone.
- Cardzone delivers the item. This is called fulfillment.
- You get the result in one of two ways. A webhook is a message that Cardzone sends to your server. Polling means you ask the API for the order again.
Your backend lists products and renders each product's recipient_fields as the customer form.
GET /api/b2b/v1/productsStart building
Quickstart
See each step of a sandbox (test) order with real responses, then place one from your server in five minutes.Order lifecycle
The five order statuses, which ones are final, and what to do for each one.Webhooks
Get status changes sent to your server. Skip duplicates, and stay correct when messages arrive in the wrong order.API reference
Every endpoint, field, and webhook. Generated from the live OpenAPI spec.What you can build
- Top-ups for any game in the catalog. Each product lists the account fields it needs, such as
player_idandzone_id. So one form works for every game. See catalog and recipients. - An account check before the customer pays. Look up the player to show the in-game name and avatar first.
- Voucher sales. When an order is fulfilled, the codes and PINs are in
codes[]. You can also send the customer’semailormobileinrecipient. Then Cardzone sends the code to the customer too. - A reliable back office. You can safely retry creating an order when you send your own
merchant_order_ref. Each order lists what needs your attention inactions[]. Webhooks and polling return the same order object.
Try it now
Every interactive example on this site shows a real sandbox response. The sandbox is a test mode: nothing is charged, no order is created, and no webhook is sent.
The responses were recorded from the API, and they are checked against the API on every change. They are static, so they never change on their own. If you send the same request with your own sandbox API key, you get the same answer:
GETRead https://docs.cardzone.ai/llms.txt, then add a Cardzone B2B API client to this project: list products, render recipient_fields as a form, create orders with a merchant_order_ref, and poll GET /api/b2b/v1/orders/{id} until the status is final.