The non-custodial TON payment gateway — paid straight to your own wallet
Accept Gram (formerly Toncoin/TON) on your own website. Every invoice settles directly to a wallet you control — Zyrvix never holds your funds.
Non-custodial by architecture · per-invoice status ledger · plain REST API · no fund custody, ever. See current pricing
What is a TON payment gateway?
A TON payment gateway is a service that lets a business accept payments in Gram on its website or app — creating invoices, detecting the on-chain payment, and notifying the merchant automatically. Gateways differ in one decisive way: whether the provider takes custody of the money, or it goes straight to the merchant's own wallet. The coin was renamed Toncoin (TON) to Gram (GRAM) on June 15, 2026, after an 81.22% community governance vote; the network itself is still called TON.
Custodial processor, first-party toolkit, or non-custodial gateway?
Businesses accepting Gram today choose between three different shapes of solution — each best at a different thing.
Custodial processors
A provider receives the payment into an aggregated balance it manages for you, then you withdraw later — often above a minimum threshold and behind KYC tiers. Convenient for multi-coin conversion; the money sits with the provider until you move it.
First-party toolkits
A developer SDK — like TON Pay — gives you building blocks: wallet connection, signing, and payment components you assemble into your own checkout. Non-custodial, but you're responsible for the integration, and it's built first for the Telegram Mini App ecosystem.
Non-custodial gateways
A complete hosted service — invoice creation, a checkout page, webhooks, and an auditable payment history — with every payment settling directly to a wallet only you control. Zyrvix is built this way, for any website or backend.
Already decided you want a non-custodial gateway? Read the step-by-step guide to accepting TON payments on your website, or what the Gram rename means for merchants.
How the three compare
| Custodial processors | TON Pay | Zyrvix | |
|---|---|---|---|
| Custody of funds | Processor holds your funds until you withdraw | Non-custodial | Non-custodial |
| Settlement | Aggregated balance; withdrawals above a threshold | Direct to wallet, on-chain | Direct to your own wallet, per invoice |
| Where checkout lives | Varies by processor | Telegram Mini Apps first; broader web rollout expanding through 2026 | Your own website, store, or app — hosted pay page included |
| Integration model | Proprietary APIs and plugins | JavaScript/React SDK (npm package, prebuilt React components) | REST API + HMAC-signed webhooks, from any backend language — no frontend SDK required |
| Payer wallet support | Varies by processor | Wallet-agnostic (via TON Connect) | Wallet-agnostic — any TON-network wallet |
| Invoice lifecycle & audit trail | Varies by processor | Checkout and payment focus | Full invoice lifecycle (paid / expired / canceled / underpaid) with an auditable status history |
| Account requirements | KYC/KYB tiers are common | — | Email sign-up; funds never pass through Zyrvix |
Custodial processors hold your money for you. Toolkits give you parts to build with. Zyrvix is the third option: a complete gateway that never touches your funds — every invoice settles directly to your own wallet, with a full REST API, hosted pay page, and auditable status history built in.
Comparison reflects publicly documented behavior as of July 22, 2026. "Custodial processors" describes a category, not any specific provider.
TON Pay facts sourced from its official SDK documentation: docs.ton.org — TON Pay overview
Built for direct settlement
- 01
Your wallet, not a balance
Funds land per-invoice in your own wallet — no aggregated balance, no withdrawal step, no threshold to clear first.
- 02
Works where you sell
Your own website, store, or app. Customers pay from any TON-network wallet — no specific app or platform required on either side.
- 03
Integration in an afternoon
A REST API, webhooks, and a hosted pay page. Any backend language, no SDK lock-in, nothing to build from scratch.
- 04
Auditable by design
An append-only invoice status history for every payment — verify each settlement on-chain yourself, any time.
How it works
- 1
Create an invoice
One API call creates the invoice — amount and destination wallet, done.
- 2
Your customer pays
They pay from any TON-network wallet, from the hosted pay page's QR code or wallet deeplink.
- 3
Funds arrive in your wallet
The payment lands directly in your wallet, on-chain — a signed webhook confirms it the moment it's detected.
Zyrvix watches the chain and manages invoice state — it never sits between the money and you.
Want the full walkthrough? Read the step-by-step guide to accepting TON payments
See the integration
# replace with the full sk_ key you saved at creationcurl -X POST https://api.zyrvix.com/invoices \-H "Authorization: Bearer YOUR_API_KEY" \-H "Content-Type: application/json" \-H "Idempotency-Key: $(uuidgen)" \-d '{"amount": "5.5","pay_to_address": "EQD_YOUR_TON_WALLET_ADDRESS","expires_in_seconds": 1200}'
{"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6","type": "invoice.paid","created_at": "2026-06-14T12:05:00Z","data": {"invoice": {"invoice_id": "550e8400-e29b-41d4-a716-446655440000","amount": "5.5","currency": "GRAM","pay_to_address": "EQD...","memo": "AB3XP7M","status": "paid","initiated_by": "automatic"}}}
Full reference at the docs.
Evaluating the API on its own? See the crypto checkout API behind it.
Verifiable, not just claimed
- Non-custodial architecture — no deposit or withdrawal endpoints exist for merchant funds.
- Per-invoice on-chain verifiability — check every settlement yourself.
- An append-only status-event ledger for every invoice.
- Open, public API documentation — no account required to read it.
- Self-serve signup — create an account and start integrating in minutes.
TON payment gateway — common questions
Start accepting Gram on your own site
Create an account, connect your wallet, and start taking payments that settle directly to you — non-custodial, from the first invoice.
Last updated July 22, 2026