Reseller guide
How to start a digital goods store with an API (2026)
A digital goods store sells codes and top-ups with instant, automated delivery — no stock, no shipping. The hard part isn't the storefront, it's the supply and fulfilment behind it. With one reseller API you can pull a 10,000-SKU catalog, place orders programmatically, and deliver via webhooks. Here's the build.
Step by step
- 1
Connect a catalog source
Open a FazerCards reseller account (no-documents trial) and pull GET /api/v2/catalog. You get 10,000+ SKUs with live wholesale pricing to render in your storefront.
- 2
Render your storefront
Build any front-end (website, bot, app) and list the SKUs you want with your markup applied. Start with a focused set, not all 10,000 — curate the products your audience actually buys.
- 3
Automate ordering
On checkout, call POST /api/v2/order from your backend. Use idempotency keys so a retry never double-charges. The reseller balance is debited at wholesale.
- 4
Deliver via webhooks
Subscribe to order.completed / order.failed / order.refunded. Deliver the code/top-up to the buyer on completion; surface failures and refunds automatically.
- 5
Settle in crypto and go live
Keep the balance funded via Binance Pay or USDT (TRC20 / BEP20 / TON / Aptos). No card rails or bank onboarding needed — flip the store live the same day.
What you get
- No inventory, no shipping — pure digital, instant delivery
- One API for catalog + orders + webhooks
- Idempotent orders prevent double-charges
- Crypto settlement — live in a day, no bank onboarding
Watch out for
- Curate the catalog — don't dump all 10,000 SKUs on day one
- Use idempotency keys on every order call
- Cache catalog/prices sensibly and refresh on a schedule
Start in 5 minutes — no card needed
5-day Gold trial: full API, full catalog, no documents.
FAQ
Do I need to build the supply side myself?
No — that's the point of a reseller API. You pull the catalog, place orders and receive webhooks; sourcing, stock and delivery are handled upstream.
How do I avoid double-charging on retries?
Send an idempotency key with each POST /api/v2/order; a repeated request with the same key returns the original order instead of charging again.
Can I use any storefront tech?
Yes — the API is REST/JSON, so any website, bot or app backend can integrate. See the use-case guides for Telegram/Discord/website setups.
How fast can I launch?
Same day for a basic store: trial without documents, fund in crypto, pull the catalog, wire orders + webhooks.