Introducing Paysell: accept USDT and TON on the TON network

Paysell is a payment processor built for one network: TON. If your customers already hold Toncoin or USDT, or you simply want to accept crypto without juggling a dozen chains and wallet formats, Paysell gives you a merchant cabinet, an API, a hosted checkout page, and webhooks — all designed around TON from the ground up.

What Paysell is#

Paysell processes two assets: Toncoin (TON) and USDT on TON, the USDT jetton that lives on the TON blockchain. There's no fiat, no card processing, and no other chains — this is a focused tool for merchants who want to accept TON-network payments reliably and move funds to a wallet they control.

Every invoice you create becomes a unique TON address. When a payment arrives, Paysell waits for the transaction to be included in the TON masterchain plus three additional blocks, cross-checks it against a second data source, and only then marks the invoice paid and calls your webhook — about a minute from payment to notification.

Who it's for#

Paysell suits merchants who already sell online — SaaS, e-commerce, digital goods, services — and want a straightforward way to add USDT and TON as payment options. It's also a natural fit for businesses whose customers are already in the Telegram/TON ecosystem, where wallets like Tonkeeper and MyTonWallet are common.

You don't need to run a TON node, manage private keys for every customer, or write blockchain-indexing code yourself. Paysell handles address generation, confirmation tracking, and reconciliation; you handle order fulfillment.

What you get#

Merchant cabinet#

The cabinet is where you create stores, generate API keys, watch invoices and balances, request withdrawals, and manage account security. It's protected by email and password, with optional TOTP two-factor authentication and recovery codes, plus a list of active sessions you can revoke individually.

API#

The Paysell API lets you create invoices, check their status, and list past payments programmatically. It's a small, predictable REST API — see the documentation for the full reference. A typical integration is a single call to create an invoice plus a webhook handler to react when it's paid.

Hosted payment page#

Every invoice comes with a payment_url — a hosted checkout page where the buyer scans a QR code or opens a deep link into Tonkeeper, MyTonWallet, or another TON wallet. You don't need to build your own payment UI unless you want to; the hosted page shows the amount, address, and time left before the invoice expires.

Webhooks#

When a payment is credited (or rejected), Paysell sends a signed webhook to your endpoint so you can mark the order as paid automatically, without polling. Webhooks are retried on a backoff schedule if your endpoint is unreachable, and every event carries a signature you can verify. See the webhooks section of the docs for headers and the retry schedule.

Support#

If something looks off — a payment that hasn't confirmed, a question about a withdrawal — you open a support ticket from the cabinet, and a person answers it. There's no bot standing in for support.

Pricing#

Paysell charges 0.2% of each received payment, deducted at the moment it's credited to your balance. That rate is fixed for your store when you register, so it won't change later. There's no setup fee and no monthly subscription.

Withdrawals cost 0.7 USDT or 0.52 TON, depending on the asset, with a minimum withdrawal of 19 TON or 25 USDT. Paysell covers the network gas for incoming payments; that flat withdrawal fee already covers the cost of sending a withdrawal. Full details live on the fee schedule.

Note: Payouts are protected by several layers — a required TOTP code, automated anti-fraud checks, and an isolated signing service the application has no access to. How that works, and what makes a withdrawal go through faster, is covered in a separate post.

How to start#

1. Register and create a store.
2. Generate an API key from the cabinet — it's shown once, so save it somewhere safe.
3. Create your first invoice with a single API call, or send customers straight to a hosted payment page.
4. Point a webhook URL at your backend so paid orders update automatically.

Your store starts accepting payments immediately after you create it. A background review process runs alongside normal operation, but it only affects withdrawals — it won't stop you from receiving payments on day one.

If you sell physical or digital goods online, our e-commerce solutions page walks through a typical setup, from creating a store to going live.