Accept Gram and USDT on Your Website: Widgets 2026

TL;DR. You can accept Gram (formerly Toncoin) and USDT-on-TON on a regular website two ways: plug in a hosted gateway/widget (fast, no backend, fees from ~0.3–1%) or build self-hosted on-chain acceptance (full control, but you run the server and verify payments yourself). Match payments to orders via a memo/comment or a per-order address, and confirm status with a webhook. For stable prices use USDT-on-TON; for the network asset use Gram with auto-conversion.

What changed in June 2026

On 15 June 2026 Toncoin officially renamed itself to Gram — a pure ticker-and-logo rebrand approved by community vote (TON Vote). There was no contract change, no swap and no migration: a balance of 10 TON now displays as 10 GRAM at a 1:1 ratio. The network itself stays TON; the asset is now called Gram.

For payments this means one thing: technically nothing broke. Addresses, transactions, memos and APIs work exactly as before — only wallet and exchange labels changed. If your store already accepted TON, there is nothing to rewrite. If you are just starting, account for the new name in button copy and buyer instructions.

USDT is available on TON natively, with no bridge wrappers. That makes the “Gram + USDT-on-TON” pairing convenient: the volatile network asset and a stable dollar in the same network with identical transaction mechanics.

Two ways to accept payments on a website

Hosted gateway or widget

A third-party provider (crypto acquirer) gives you a checkout widget/plugin, generates addresses and memos, watches for incoming transactions and fires a webhook with the order status. Many ship plugins for popular CMS platforms — WooCommerce, for example — and an API for custom sites.

• Pros: fast launch, no blockchain backend needed, auto-conversion of Gram into a stablecoin or fiat, AML screening on the provider’s side.
• Cons: fees (typically ~0.3% to 1%+), reliance on a third party, merchant KYC requirements, possible limits.

Self-hosted on-chain acceptance

You generate addresses, listen to the chain and confirm payments yourself. No intermediary stands between the money and you.

• Pros: no gateway fee, full control over keys and data, no external merchant KYC.
• Cons: you need a server and a reliable indexer/node provider, your own verification and retry logic, and responsibility for key security and Gram volatility.

Stablecoin vs volatile Gram

The key product decision is what you price in.

• USDT-on-TON. The product price in dollars (or converted from local fiat) matches what arrives. No FX risk between order and confirmation. Ideal for a store with fixed prices.
• Gram. Fits if you deliberately hold the network asset or immediately convert it to stablecoin/fiat via a gateway. For retail without auto-conversion the FX risk between checkout and payment is real — even though TON confirms fast, you should “freeze” the price for a short window (say 5–15 minutes).

TON speed and fees

TON settles transactions fast — usually within seconds — at very low network fees. For checkout that means near-instant confirmation: the buyer doesn’t wait minutes as on congested chains, and the network fee doesn’t eat your margin on small payments. This is one of the main advantages over classic crypto acquiring on heavier blockchains.

How to verify a payment

The most common rookie mistake is showing “paid” the moment a buyer sends, instead of on-chain confirmation. The correct flow:

1. Matching. Tie the payment to an order via a unique memo/comment in the transaction, or a dedicated payment address per order.
2. Confirmation. Wait until the transaction lands in a block and reaches the required confirmation depth — not just leaves the wallet.
3. Amount and token. Verify that the right token arrived (Gram or the USDT-on-TON jetton) and the exact amount — not “close enough”.
4. Idempotency. One payment = one order. Protect the webhook against replay and forgery (signature/secret).

Checkout UX: QR and TON Connect

A buyer should pay in one or two taps. Working patterns:

• QR code + deep link. The buyer scans with a wallet or taps a link — a prepared transaction opens with address, amount and memo filled in.
• TON Connect. A “Connect wallet” button links the website to the user’s wallet; the transaction is built on the site side and confirmed in the wallet. This is the most native web flow for TON.
• Real-time status. The payment page should update its status itself (“awaiting payment → received → confirmed”) via webhook or polling, with no manual refresh.

Comparison with familiar crypto acquiring

Classic crypto gateways were built around BTC/ETH and chains with higher fees and slower confirmation. Accepting on TON differs in that:

• confirmation takes seconds, not minutes;
• the network fee is near zero, making micropayments viable;
• USDT-on-TON gives a stable unit of account in the same fast network;
• TON Connect is a built-in, convenient web standard for wallet connection.

That said, the audience and buyer habits outside the Telegram ecosystem are still narrower than Bitcoin’s — worth factoring in when you estimate the share of crypto payments.

Step-by-step launch

1. Choose the model. A hosted gateway for a fast start without a backend — or self-hosted for full control.
2. Pick the settlement currency. USDT-on-TON for stable prices; Gram only with auto-conversion or a deliberate hold.
3. Wire up acceptance. Install the plugin/widget (for a CMS like WooCommerce) or set up address and memo generation on your own backend.
4. Set up verification. Match by memo/address, wait for confirmations, check token and amount, idempotent webhook.
5. Build the UX. QR + deep link and/or TON Connect, live payment status, an exchange-rate lock window for Gram.
6. Test on small amounts. Run the full path: order → payment → webhook → status change → refund, before going live.

What’s next

Accepting on a website is part of a wider shift toward Gram as a payment asset. The market context is shaped by institutional demand (filings for a Gram ETF), infrastructure bridges like TON Teleport for native Bitcoin, and regulatory events — from Coinbase winding down leveraged Gram trading to India’s Telegram ban. And if your funnel lives in Telegram, look separately at in-bot acceptance — that’s a different integration.