Accept TON (native) payments without KYC
Confirmed in seconds, built for bots and apps
TON is the fastest asset on the platform: a single confirmation lands in roughly five to ten seconds, which makes it the closest thing to a card-like checkout experience in crypto. If your audience lives in Telegram, TON is the native currency of that ecosystem.
Addressing works like TRON: you connect one static address, and live invoices get unique amounts — spaced by 2× your amount tolerance plus one unit — so concurrent invoices never match each other's payments. Native TON transfers are watched via toncenter with a second provider as fallback.
Networks & confirmations
| Network | Asset | Confirmations | Time |
|---|---|---|---|
| TON | TON (native) | 1 | ~5–10 s |
Addressing modes
Transit
ZeroKYC Pay issues payment details from its own pool and auto-sweeps to your payout address after confirmations. 1% + network fee.
Direct (non-custodial)
Payments go straight to your wallet: static address + unique amounts — one TON address for all invoices; amount windows (2×tolerance + 1 unit apart) disambiguate concurrent payments. The address must be used only through ZeroKYC Pay.
Create an invoice for TON
curl -X POST https://api.zerokyc-payments.com/v1/invoices \
-H "Authorization: Bearer pk_test_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{
"amount": 49.00,
"base_currency": "USD",
"payment_currency": "TON",
"order_id": "order-1042"
}'Replace the API key with your pk_test key from the console. Full flow in the quickstart.
TON (native) payment FAQ
Is one confirmation really enough?
On TON, the single confirmation is the network's design: finality is near-immediate thanks to the BFT-style consensus. Five to ten seconds to 'confirmed' is the normal, production-tested behaviour.
How do multiple invoices share one TON address?
By unique amounts: with the default tolerance of 0, each live invoice gets an amount that differs from every other live invoice down to the smallest unit. If you set a tolerance of ±0.1%, invoices are spaced 0.3% apart so payment windows never overlap.
TON vs USDT on TON — which should I enable?
Both take seconds to confirm. TON suits buyers holding the network token (and Telegram Mini Apps); USDT-TON suits buyers who want stable pricing. payment_currency=any lets each invoice pick its own answer.
Do you support TON Connect wallets?
The hosted checkout shows an address and a ton:// QR that all major TON wallets scan natively. Deep wallet-connect integrations are on the roadmap.
Start accepting TON (native) today
Create an account, paste your payout address or connect a wallet, and generate your first TON invoice in minutes. Want to accept TON plus everything else? Set payment_currency=any and let the buyer choose the coin at checkout.