How to accept TON payments on your website
June 23, 2026
Accepting TON payments means letting people pay you in Toncoin (GRAM) and confirming each payment on-chain. The hard part isn't taking the money — it's knowing, reliably, that a specific payment arrived and tying it back to an order. TONpayment does exactly that, and it never holds your funds.
Two ways to start
You can use the hosted gateway at tonpayment.net, or self-host the open-source engine. Both are non-custodial: payments settle straight into your own wallet, not ours.
1. Hosted — no code
Connect your TON wallet (signing in is a signature, not a deposit), then create a payment gateway or a donation link. Share the link, or point your checkout at it. You get paid in GRAM directly to your wallet and watch each payment settle in your dashboard. You can set a name, an image and your social links per gateway.
2. Self-host the engine
Prefer to run it yourself? The engine is a few thousand lines of Go, MIT-licensed, with no database required to start. It issues invoices and confirms payment by reading the chain — about a minute to try (dev mode uses a mock verifier so you don't need real funds):
git clone https://github.com/aturzone/TONpayment
cd TONpayment
export TON_RECEIVING_ADDRESS=UQ... TON_ENV=dev
go run ./cmd/server
# POST /v1/invoices, then GET /v1/invoices/{id}/statusHow confirmation works
Every invoice gets a unique memo. The payer sends TON with that memo as the transaction comment (via deeplink, QR, or TON Connect). The engine matches the incoming transaction by the (receiving address + memo + amount) triple, and only then marks the invoice paid. It fails closed — any error leaves the invoice pending, never paid — and on payment it can fire a signed webhook so your backend reacts immediately.
Why non-custodial matters
A custodial processor holds your money and can freeze, lose, or gate it. TONpayment never has your private keys and never moves funds: the receiving address is yours, and the service only observesthe public chain. That's also why the whole engine is safe to be open-source — there are no secrets in it to leak.
Start now
Create a link at tonpayment.net, or read the code on GitHub. Either way takes a couple of minutes, and your money stays yours the whole time.