Bezant Merchant
ReferenceGetting startedOTC desksDashboard

Getting started

Change notice · 2026-10-05

TRX, ETH and BNB payments now work like the exchange-custodied coins (BTC, XRP, SOL, …): the customer pays a shared deposit address and must send exactly the quoted amount_crypto before expires_at (60 minutes). The per-payment-address flow, where any amount is accepted, remains for USDT on Tron (USDT), Ethereum (ETH-USDT) and BNB Smart Chain (BNB-USDT). Asset codes and endpoints are unchanged; if your checkout shows these coins, make sure it displays the exact amount and the expiry. Addresses issued for USDT must only receive USDT on that network.

Change notice · 2026-10-06

Network fee on Tron USDT raised to 4 USD (from 1.50) for deposits and withdrawals, to match what a TRC20 transfer actually costs on the Tron network today. It is added on top of the amount, so amount_crypto on new USDT payments is 4 USDT higher than the merchant amount, and USDT withdrawals on Tron hold 4 USDT more. Nothing else changed; always read the live figures from GET /v1/quote.

Fees at a glance

ChargeWho paysHow much
Network fee on an on-chain depositthe customer, on top of the amountTron USDT 4 USD · Ethereum USDT 4 USD · BNB Smart Chain USDT 0.10 USD, converted to the asset at quote time (network_fee_crypto)
Deposit feededucted from what is credited1 % of the amount, minimum 0.50 USD (custodial mode; none in direct-to-wallet mode)
Withdrawalheld from your balance with the amountnetwork fee as above (exchange coins: the exchange's withdrawal fee) + 0.5 % + 1 USD
Buy & deliver ordercharged in USDTreal exchange cost + 0.5 %
Direct-to-walletfrom your USDT balance50 USDT per asset per year
Top-up of your own balance—no deposit fee; network fee still applies

Per-merchant rates may differ by agreement; GET /v1/quote always returns the figures that apply to you.

1. Authenticate

Every request carries your API key in the X-Bezant-Api-Key header. Base URL: https://api.bezant.cc.

2. Quote, then create a payment

Always read GET /v1/assets for what you can accept; today that is USDT on three networks (USDT = Tron, ETH-USDT = Ethereum, BNB-USDT = BNB Smart Chain) plus the exchange-custodied coins, including USDC (on Solana), BTC, ETH, TRX, BNB, XRP, SOL, GRAM (Gram, previously Toncoin, on TON; added 2026-10-06) and more. Optionally price first: GET /v1/quote?asset=BTC&amount=1000&currency=USDT returns our rate, the fiat equivalent and the fees that would apply. Then ask for an address and amount when the customer checks out. amount is in currency: USD by default, USDT, or the asset code itself for an exact crypto amount ({"asset":"ETH-USDT","amount":"100","currency":"ETH-USDT"} means "send exactly 100 USDT on Ethereum").

curl -X POST https://api.bezant.cc/v1/payments \
  -H "X-Bezant-Api-Key: $KEY" -H "Content-Type: application/json" \
  -d '{"asset":"USDT","amount":"25","currency":"USD","external_id":"order-123","callback_url":"https://shop.example/bezant"}'

{"status":"success","payment":{"id":"pay_…","address":"T…","memo":null,"amount_crypto":"25","status":"PENDING", … }}

Show address, amount_crypto and, when present, memo to the customer (XRP and GRAM deposits are only credited when the memo is included). For on-chain assets amount_crypto already includes the network fee the customer pays on top of your amount (network_fee_crypto); your amount in crypto is amount_crypto_net. For KuCoin-custodied coins (BTC, XRP, SOL…) the amount is unique and must be sent exactly; the reservation expires at expires_at.

3. Receive the webhook

When the payment confirms we POST to your callback_url (or the merchant default). Verify the signature, then mark the order paid. Respond with any 2xx; we retry with back-off otherwise.

# Python
import hmac, hashlib, time
def verify(secret, body: bytes, headers) -> bool:
    ts, sig = headers["X-Bezant-Timestamp"], headers["X-Bezant-Signature"]
    if abs(time.time() - int(ts)) > 300: return False
    expected = hmac.new(secret.encode(), f"{ts}.".encode() + body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, sig)

# Node
const crypto = require("crypto");
function verify(secret, rawBody, headers) {
  const ts = headers["x-bezant-timestamp"], sig = headers["x-bezant-signature"];
  if (Math.abs(Date.now()/1000 - Number(ts)) > 300) return false;
  const expected = crypto.createHmac("sha256", secret).update(`${ts}.`).update(rawBody).digest("hex");
  return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(sig));
}

Payload: {"event":"payment.updated","merchant_id":"…","created_at":…,"data":{…payment…, "credited":[{"txid","amount_crypto","fee_crypto","net_crypto"}]}}. Events: payment.unconfirmed, payment.updated, withdrawal.completed, withdrawal.failed. Handle duplicates: the same event can be delivered more than once.

4. Balances and withdrawals

curl https://api.bezant.cc/v1/balances -H "X-Bezant-Api-Key: $KEY"
curl -X POST https://api.bezant.cc/v1/withdrawals -H "X-Bezant-Api-Key: $KEY" -H "Idempotency-Key: wd-2026-09-19-1" \
  -H "Content-Type: application/json" -d '{"asset":"USDT","amount":"500","address":"T…"}'
curl -X POST https://api.bezant.cc/v1/transfers -H "X-Bezant-Api-Key: $KEY" -H "Idempotency-Key: mv-2026-10-06-1" \
  -H "Content-Type: application/json" -d '{"from_asset":"USDT","to_asset":"BNB-USDT","amount":"500"}'

Fees are added on top of the amount and returned on the withdrawal. Use Idempotency-Key on every POST you might retry. Your USDT is held per network (USDT = Tron, ETH-USDT = Ethereum, BNB-USDT = BNB Smart Chain) and a withdrawal spends its own network's balance. POST /v1/transfers (added 2026-10-06) moves USDT between those balances 1:1 and instantly, with no fee, so you can receive on one chain and pay out on another without keeping a float per chain. Also on the dashboard under Withdrawals.

5. Long-lasting addresses (one per customer)

Instead of a new payment per invoice, give each of your users a permanent deposit address per asset. Every transfer that ever lands on it is credited to your balance and reported with your reference — ideal for services that bill the same customer repeatedly. Two flavours, same endpoints:

POST /v1/payments  {"asset":"BTC","amount":"100","currency":"USDT","address_id":"addr_…","external_id":"inv-42"}
GET  /v1/payments?address_id=addr_…
POST /v1/addresses   {"asset":"USDT","customer_ref":"user-1694","label":"Alice","callback_url":"https://shop.example/bezant"}
→ {"address":{"id":"addr_…","asset":"USDT","address":"T…","customer_ref":"user-1694","status":"ACTIVE", … }}

GET  /v1/addresses?customer_ref=user-1694      GET /v1/addresses/{id}      GET /v1/addresses/{id}/deposits
PATCH /v1/addresses/{id} {"status":"DISABLED"}  (hides it; anything still sent there is credited anyway)

Calling POST /v1/addresses again with the same customer_ref and asset returns the existing address, so you can call it on every page load. Each incoming transfer fires deposit.received: {"event":"deposit.received","data":{…address…, "deposit":{"txid","amount_crypto","network_fee_crypto","fee_crypto","net_crypto","credited_at"}}}. Because no amount is quoted up front, the network fee is deducted from each transfer (not added on top) before the deposit fee; net_crypto is what reached your balance. Match the customer by customer_ref, the amount by net_crypto.

6. Buy & deliver (OTC desks)

Keep USDT on your balance and let Bezant source other coins: GET /v1/orders/quote?asset=BTC&amount=0.01 shows the cost, then POST /v1/orders {"asset":"BTC","amount":"0.01","address":"bc1…","external_id":"deal-42"} buys the coin on the exchange and delivers exactly that amount to the address. You are charged the real cost plus the order fee; the unused part of the hold comes straight back. Webhooks: order.completed, order.failed. Set a USDT reserve minimum with Bezant to get reserve.low alerts before you run dry. Quotes and payments also accept currency=USDT.

7. Direct-to-wallet (optional)

Subscribe an asset (POST /v1/subscriptions, 50 USDT/year from your USDT balance), then PUT /v1/settlement-policies/{asset} with {"mode":"DIRECT","address":"…"}. Every confirmed deposit is then paid to your address with no Bezant fee. Address changes must be confirmed from the e-mail we send.