You want to accept TON on your website or Telegram Mini App, but you don't want a third party holding your funds. That is exactly why TonConnect exists. It is the standard protocol that lets users connect their wallets to your app so they can sign transactions directly. For merchants, this means money moves from the buyer's wallet straight to yours, with no middleman taking a cut or freezing your account.
In mid-2026, the landscape has shifted. The TON Foundation now maintains TonConnect, making it the official connection layer for the ecosystem. When combined with tools like TON Pay, you get a checkout flow that settles in roughly one second. You keep full control of your private keys, and the customer never leaves their trusted wallet interface.
What Is TonConnect and Why Does It Matter for Business?
TonConnect is not just a login button. It is an end-to-end encrypted session between your application and a user’s wallet. Originally built by the team behind Tonkeeper in 2022, it was handed over to the TON Foundation to become an open standard. Today, it supports dozens of wallets, including MyTonWallet, OpenMask, and the native Wallet Bot inside Telegram.
For a merchant, the value proposition is simple: non-custodial settlement. Traditional payment gateways often hold your crypto in a pooled balance before paying you out. With TonConnect, the transaction happens on-chain immediately. You receive the tokens in the address you control. There is no platform-side ledger to reconcile later, and no risk of the provider going insolvent with your money.
| Feature | Custodial Gateway | TonConnect (Non-Custodial) |
|---|---|---|
| Fund Control | Provider holds keys until payout | Merchant holds keys permanently |
| Settlement Speed | Depends on provider schedule | ~1 second (on-chain finality) |
| Counterparty Risk | High (platform insolvency) | None (direct transfer) |
| Fees | Often includes markup + network fee | Network fee only (near-zero) |
How the Checkout Flow Works Step-by-Step
Integrating TonConnect doesn't require you to build a complex backend from scratch. The process is designed to be lightweight. Here is what happens when a customer clicks "Pay" on your site:
- Connection: The user sees a modal powered by the TonConnect UI SDK. They scan a QR code or click a deep link to open their preferred wallet (like Tonkeeper or Telegram Wallet).
- Verification: Your app sends a request to the wallet. The wallet displays the exact amount, the destination address (yours), and any optional payload data.
- Signing: The user confirms the transaction inside their secure environment. Their private key never leaves their device.
- Broadcasting: The wallet broadcasts the signed transaction to the TON mainnet. This takes less than two seconds.
- Confirmation: Your frontend listens for the transaction hash and status updates via Server-Sent Events (SSE) through the bridge. Once confirmed, you update your order status.
The entire experience feels similar to buying coffee with Apple Pay, but instead of a card number, you are moving assets on the blockchain. Because the protocol uses a public bridge endpoint by default, you don't need to run your own infrastructure to relay messages between the app and the wallet.
Technical Setup: Manifests and SDKs
To start accepting payments, you need two things: a manifest file and the SDK. The manifest file, named tonconnect-manifest.json, tells the wallet who you are. It must be hosted on a public HTTPS server without CORS restrictions. Inside this JSON file, you define your app name, icon URL, and universal link. This ensures that when a user connects, they see your brand logo, not a generic placeholder.
On the code side, most developers use @tonconnect/ui-react if they are building with React or Next.js. If you are using vanilla JavaScript, @tonconnect/ui works just as well. These packages handle the heavy lifting-managing connection states, opening modals, and formatting transaction requests.
When constructing a payment, you will typically use helper functions provided by the TON Pay SDK, such as createTonPayTransfer. This function ensures you format the destination address correctly (converting user-friendly formats to raw base64) and set the network ID to -239 for mainnet. Getting these details wrong is the most common mistake beginners make, so relying on the SDK helpers saves hours of debugging.
Direct Integration vs. Third-Party Gateways
You have two main paths for implementation. The first is direct integration using the official TON Pay SDK. This gives you maximum control and zero fees beyond the network gas. However, you are responsible for handling webhooks, reconciling payments, and managing your own wallet security.
The second path involves third-party providers like MutoPay or CryptoPay Lite. These services wrap TonConnect in a more familiar checkout interface. For example, MutoPay allows you to configure settlement settings where payments land directly in your wallet as USDT-on-TON or native TON. They emphasize that they do not custody funds, but they provide additional features like invoice generation and currency conversion at the point of sale.
If you are a solo founder or running a small project, a wrapper service might save you time on frontend development. If you are building a high-volume platform and want to minimize overhead costs, direct integration is usually the better long-term play. Both methods remain non-custodial, so your funds are safe either way.
Security and Key Management Responsibilities
Because TonConnect is non-custodial, the security burden shifts entirely to you. There is no password reset button if you lose access to your merchant wallet. You must store your private keys securely, ideally using a hardware wallet or a multi-signature setup for larger operations.
The protocol itself is secure because it uses end-to-end encryption for all communication between your app and the user's wallet. Even the bridge server cannot read the contents of the messages. However, you must ensure your manifest file is served over HTTPS and that your frontend code is free from injection attacks. A compromised frontend could theoretically send a transaction to a different address than displayed, though the user would still see the correct address in their wallet before signing.
Always verify the destination address in your code logic before sending the transaction request. Double-check that the address matches your verified merchant wallet. Since there are no chargebacks on the blockchain, a mistaken transfer is permanent.
Why Choose TonConnect Over WalletConnect?
You might notice that some TON apps also support WalletConnect. While TonConnect does offer optional WalletConnect compatibility for institutional platforms, it is not recommended for standard merchant use cases. WalletConnect exposes only a subset of capabilities-basic connect, disconnect, and send transaction.
TonConnect’s native bridge provides a richer feature set, including better support for Jettons (TON-based tokens), faster state synchronization, and deeper integration with Telegram Mini Apps. If your customers are primarily in the Telegram ecosystem, sticking to the native TonConnect protocol ensures the smoothest experience. WalletConnect is better suited for cross-chain treasury management rather than everyday retail checkouts.
Real-World Performance Metrics
Merchants care about speed and cost. On the TON mainnet, block times are approximately one second. This means a payment is effectively final almost instantly. Network fees are negligible, often fractions of a cent, even during high traffic periods. This makes microtransactions viable, which is difficult on networks like Ethereum or Bitcoin.
As of July 2026, the TON ecosystem has activated over 45 million wallets. A significant portion of these users are active within Telegram, accessing services via Mini Apps. By integrating TonConnect, you tap into this massive, ready-made audience. Users already have their wallets funded and connected, reducing the friction of onboarding new customers.
Do I need to register a company to use TonConnect?
No. TonConnect is an open protocol. You can integrate it into any website or app regardless of your legal structure. However, if you use a third-party gateway like MutoPay, check their specific terms. Direct integration requires no registration at all.
Can I accept USDT along with TON?
Yes. TON supports Jettons, which include stablecoins like USDT. The TON Pay SDK allows you to specify the token type in the transaction request. Many merchants prefer USDT-on-TON to avoid volatility while keeping the same fast, low-cost settlement.
Is TonConnect free to use?
The TonConnect SDK and protocol are completely free and open-source. You only pay the standard TON network gas fees, which are extremely low. Third-party wrappers may charge service fees, but direct integration has no platform costs.
What happens if a transaction fails?
If a transaction fails, the funds remain in the user's wallet. Your app receives a failure event via the SSE connection. You should prompt the user to retry or choose a different payment method. No partial charges occur.
Does TonConnect work with Telegram Mini Apps?
Yes, it is natively optimized for them. Telegram Mini Apps can invoke the TonConnect modal seamlessly, allowing users to pay without leaving the chat interface. This is one of the fastest-growing use cases for the protocol in 2026.