Xazum — USDT payments with a wallet per project
USDT payments, per project

One project.
One wallet.
Nothing pooled.

Payments land on addresses derived for your project alone — separated cryptographically, not by a column in someone's database. Your balance is never mixed with anyone else's, and you withdraw to your own address whenever you want.

Create an account → See the API
1:1
a wallet per project
never shared
~1 min
from payment
to webhook
0
pooled balances
anywhere
invoice a3f2·7c19 25.00USDT
Derivation path
m/44'/195'/0'/0/117
Payment address
TUEZSdKsoDHQMeZwihtdoBiN46zxhGWYdH
Confirmations 0/19
Awaiting payment — address issued, no key on the server
Lifecycle

Five steps, and your money is never in a shared pot.

The order matters: each step exists so the next one cannot lose money. Screening sits before any transfer on purpose — a tainted deposit that never moves contaminates nothing, because it is alone on its address.

01

Invoice

Your project asks for an address for an amount. Xazum takes the next index and returns the address with a QR code.

POST /v1/invoices
02

Address

From your project's own hardened branch. No other project can ever be issued this address — the separation is arithmetic, not policy.

m/44'/195'/<project>'/0/i
03

Payment

The scanner walks blocks and waits for finality, then posts a signed webhook. Reconciliation catches whatever the webhook misses.

POST → your /webhook
04

Screening

Every deposit is checked before it can move. Tainted coins stay parked on their own address, where they touch nothing.

verdict = CLEAN
05

Withdraw

You ask, we drain the addresses that cover it and send straight to your wallet. No settlement schedule, no minimum payout.

→ your wallet
Why it matters

Most processors put every merchant's money in one balance.

That is the design decision behind almost every frozen-funds story: when the pot is shared, someone else's problem becomes your withdrawal.

What it decides
A pooled processor
Xazum
Where your money sits
One balance shared by every merchant on the platform
Addresses derived for your project alone
Another merchant investigated
The pot is one address — a freeze reaches your balance too
Nothing — you share no address with anyone
A tainted deposit arrives
Already mixed with everyone's funds by the time it is noticed
Alone on its own address, screened before it can move
Getting paid out
Settlement schedules, minimums, review queues
Your address, when you ask
Getting started
Document upload, KYB, weeks of waiting
An application a person reads
Integration

Four calls, and a project takes payments.

Your app talks to Xazum over HTTP only. It knows nothing about the blockchain, stores no addresses and counts no confirmations — what arrives is “credit this much for customer X”.

  • invoicesIssue an address for an amount and a lifetime
  • statusAsk for state when a webhook goes missing
  • webhookDelivered to you, signed with your secret
  • settlementWhere to sweep — your cold address
# issue an address for a top-up
POST /v1/invoices
X-Api-Key: pg_live_••••••••

{
  "amount": "25.00",
  "currency": "USDT",
  "order_id": "dep-7c19a3f2",
  "ttl": 3600
}

← 201
{
  "address": "TUEZSdKsoDHQMe…hGWYdH",
  "network": "TRON",
  "expires_at": "2026-08-08T21:34:00Z"
}
Ready when you are

Your money, on
your own addresses.

Apply in a minute. A person reads it, and your project gets a wallet of its own.

Create an account → Documentation