Guides to buying from us

How to open an account and start selling

What happens between opening your account and your first delivered code: signing up, confirming your email address, funding the wallet, then the first order.

2026/09/17 4 min read

How to fund your wallet in USDT

One wallet buys everything, and it is funded one way: in USDT. You choose a package, see what is credited and what you pay before you confirm, send the amount to the address shown, and the credit appears by itself in a ledger nothing edits.

2026/09/17 5 min read

Connecting to the REST API, step by step

From issuing a key to your first delivered order: reading the catalogue at your price, placing an order with an Idempotency-Key, following it, and subscribing to webhooks.

2026/09/17 4 min read

How your price is decided

Two forms and no third: an agreed rate off every list price, or an exact figure on one package. And what does not exist: volume tiers, monthly thresholds, promo codes.

2026/09/17 4 min read

Direct top-ups and code products: the two kinds of order

Every denomination here is one of two shapes, and your integration has to tell them apart: one hands you a code to pass on, the other credits an account and hands you nothing.

2026/09/17 6 min read

Idempotency: retrying an order without buying it twice

A timeout tells you nothing about whether the order was placed. An Idempotency-Key of your own turns "send it again and hope" into a safe, exact repeat of the first request.

2026/09/17 5 min read

Webhooks: verifying the signature and handling every event once

Check the signature against the raw body before you parse it, answer quickly, and key your processing on the event id — because a retry is not a second event.

2026/09/17 5 min read

Reconciling your wallet against your own sales

The balance is the sum of the ledger and nothing edits a line of it, so reconciling is matching entries to your own records — and knowing what the three ordinary discrepancies mean.

2026/09/17 7 min read

Every API error, and what your integration should do about each one

Branch on the stable code, never on the message. Which errors charged you and which did not, which are safe to retry, and which need a person rather than a retry loop.

2026/09/17 7 min read

Rate limits, and building a shop that stays inside them

Sixty a minute per key by default, read from a header rather than hard-coded — and a 429 that carries no Retry-After, so your client has to have been watching on the way down.

2026/09/17 6 min read

Storing and handing over codes safely in your own system

One endpoint serves a code and nothing else does. Encrypt it, hand it to one buyer, keep it out of every log — and know that there is no reissue to fall back on.

2026/09/17 7 min read

Building a checkout that collects the right account id

We check that the field is present, never that it is right, and a credit that lands in the wrong account cannot be pulled back. So the correctness of that field is your checkout.

2026/09/17 7 min read