---
title: "Cardzone Developers"
description: "Sell game top-ups and digital vouchers from your own store with one REST API. Your Cardzone store wallet pays for each order."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.cardzone.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cardzone Developers

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:

1. You list Cardzone products.
2. You place orders. Your **store wallet** pays for each order. The store wallet is your store's balance with Cardzone.
3. Cardzone delivers the item. This is called **fulfillment**.
4. 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.

## Start building

- [Quickstart](https://docs.cardzone.ai/quickstart/) — See each step of a sandbox (test) order with real responses, then place one from your server in five minutes.
- [Order lifecycle](https://docs.cardzone.ai/concepts/order-lifecycle/) — The five order statuses, which ones are final, and what to do for each one.
- [Webhooks](https://docs.cardzone.ai/guides/webhooks/) — Get status changes sent to your server. Skip duplicates, and stay correct when messages arrive in the wrong order.
- [API reference](https://docs.cardzone.ai/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_id` and `zone_id`. So one form works for every game. See [catalog and recipients](https://docs.cardzone.ai/concepts/catalog-and-recipients/).
- **An account check before the customer pays.** [Look up the player](https://docs.cardzone.ai/guides/player-lookups/) 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's `email` or `mobile` in `recipient`. 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 in `actions[]`. 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:

> **Building with an AI coding agent?**
>
> Every page has a Markdown version. The site also publishes `/llms.txt` and `/llms-full.txt`. See [Build with AI agents](https://docs.cardzone.ai/resources/for-ai-agents/).

Source: https://docs.cardzone.ai/index.mdx