Imagine running a digital storefront where the money hits your bank account instantly, but no third-party processor ever holds it. That’s not a fantasy in the traditional web2 world, but it is the reality for merchants on the TON blockchain using TonConnect. This protocol allows businesses to accept cryptocurrency directly into their own wallets, bypassing the custodial middlemen that often delay payouts and freeze accounts.
If you’ve been watching the rise of Telegram Mini Apps or building decentralized applications (dApps) on The Open Network (TON), you’ve likely encountered TonConnect. But what does it actually mean for your business model? Is it just another wallet connector, or does it fundamentally change how you handle revenue? Let’s break down how receiving TON without custody works, why it matters for your cash flow, and how to implement it without needing a team of blockchain engineers.
The Core Concept: Non-Custodial Settlement
In traditional payment processing-think Stripe or PayPal-the customer pays the processor, the processor holds the funds, and then they pay you later. In crypto, many gateways do the same thing: they give you a deposit address, take control of the keys, and manage the balance on your behalf. This creates counterparty risk. If the gateway has an outage, gets hacked, or decides to hold your funds for compliance checks, your liquidity suffers.
TonConnect flips this model. It is a communication protocol that connects a user’s wallet to your application. When a customer buys something, they sign the transaction in their own wallet. The funds move directly from their wallet to yours on-chain. There is no intermediate ledger holding your money. You see the settlement in real-time, typically within one second.
This direct settlement eliminates the "withdrawal" step entirely. You don’t need to log into a dashboard to request a payout. The money is already there, in your wallet, ready to be used, swapped, or held. For small businesses and indie hackers, this means better cash flow predictability and zero platform fees taking a cut of every transaction.
How TonConnect Works with TON Pay
TonConnect handles the connection layer, but you also need a way to structure the payment itself. This is where TON Pay comes in. Launched by the TON Foundation, TON Pay is an SDK designed specifically for merchants to accept TON and Jettons (TON-based tokens like USDT).
The workflow is surprisingly simple for the end-user:
- The customer clicks "Pay" on your site or Mini App.
- TonConnect triggers a popup or deep link to their preferred wallet (like Tonkeeper, MyTonWallet, or Telegram Wallet).
- The customer reviews the amount and confirms the signature.
- The transaction broadcasts to the TON network.
- Your backend receives a confirmation event via webhook or polling.
Because the signing happens client-side in the user's wallet, your server never touches their private keys. This is crucial for security. Even if your website is compromised, an attacker cannot steal the user's funds because they only have access to the public address and the signed transaction data, not the keys required to spend them.
Integration Options: DIY vs. Gateways
You might be wondering if you need to build this entire stack yourself. The good news is that while TonConnect is open-source and free to use, you can choose between a fully custom integration or leveraging existing tools that simplify the process.
| Feature | Direct TonConnect + TON Pay | Third-Party Gateway (e.g., MutoPay) | Custodial Gateway (e.g., NOWPayments) |
|---|---|---|---|
| Custody Model | Non-custodial (Merchant owns keys) | Non-custodial (Settles to merchant wallet) | Custodial (Gateway holds funds) |
| Settlement Speed | ~1 second (On-chain finality) | ~1 second (On-chain finality) | Delayed (Payout schedule) |
| Fees | Network fees only (~$0.01) | Network fees + Provider fee (if any) | Network fees + Processing fee (% of volume) |
| Dev Effort | High (Requires SDK implementation) | Low (API/Plugin based) | Medium (API integration) |
| Risk Profile | Key management responsibility lies with merchant | Low counterparty risk | Platform risk (freezes, delays) |
If you are a developer comfortable with JavaScript or TypeScript, integrating @tonconnect/ui-react or @tonconnect/sdk directly gives you maximum control. You define the manifest file (tonconnect-manifest.json) that tells wallets who you are, and then you construct transactions using helper functions like createTonPayTransfer. This approach is ideal if you want to avoid per-transaction fees charged by third-party providers.
However, if you’re running a WordPress store or a quick prototype, services like MutoPay or CryptoPay Lite offer plugins that handle the heavy lifting. They still respect the non-custodial nature-meaning funds go straight to your wallet-but they provide pre-built UI components and webhook handlers. This saves development time at the cost of potentially higher setup complexity or minor service fees.
Why TON and Telegram Matter for Merchants
You might ask, "Why bother with TON when Ethereum and Solana exist?" The answer lies in distribution. TON is deeply integrated with Telegram, which boasts over 900 million monthly active users. More importantly, over 45 million TON wallets are already activated.
For merchants, this means your potential customers are already on the platform. They don’t need to download a new app or create a new account. They can buy your product directly inside a Telegram bot or Mini App using the wallet they already use for chatting. The friction is near zero.
Consider a scenario: A digital artist sells NFTs via a Telegram bot. With TonConnect, the buyer taps "Buy," signs with their Tonkeeper wallet, and the NFT transfers to their account in seconds. No gas fee anxiety (fees are negligible), no waiting for block confirmations, and no leaving the chat interface. This seamless experience drives higher conversion rates compared to redirecting users to external exchanges.
Managing Volatility and Fiat Off-Ramps
Receiving TON directly solves the custody problem, but it doesn’t solve the volatility problem. If you sell goods priced in USD but receive TON, you face price risk. How do you handle this?
Most merchants adopt one of two strategies:
- Immediate Conversion: Use automated scripts to swap incoming TON or USDT-on-TON into stablecoins or fiat currencies immediately upon receipt. Tools like DeDust or STON.fi allow for atomic swaps with minimal slippage.
- Stablecoin Acceptance: Configure your checkout to accept USDT on TON instead of native TON. Since USDT is pegged to the dollar, you eliminate volatility risk while still enjoying the speed and low costs of the TON network.
It’s worth noting that while TonConnect handles the on-chain movement, moving money back to your bank requires an off-ramp. Services like Bybit, OKX, or specialized fiat on-ramps integrate with TON wallets. You send your accumulated TON/USDT to these exchanges, sell them for EUR/AUD/USD, and withdraw to your bank. This step introduces some centralization, but it’s a necessary bridge between the crypto economy and the traditional financial system.
Security Best Practices for Self-Custody
With great power comes great responsibility. Since you are holding your own keys, losing them means losing your funds forever. Here are three rules to live by:
- Use Hardware Wallets for Treasury: Don’t keep all your business profits in a hot wallet connected to your website. Send large balances to a hardware wallet like Ledger or Trezor, or a multi-sig setup if available.
- Separate Hot and Cold Wallets: Keep a small operational balance in a hot wallet (like Tonkeeper) for daily inflows/outflows. Sweep excess funds to cold storage weekly.
- Verify Addresses: Always double-check the destination address when sending funds out. While TonConnect ensures the *incoming* address is correct (derived from your public key), outgoing transactions are manual.
Some newer gateways, such as TxNod, are exploring ways to make self-custody even safer by allowing merchants to connect extended public keys (xpubs) from hardware wallets. This lets the gateway generate unique invoice addresses for each customer without ever seeing the private key, adding a layer of privacy and organization to your accounting.
Getting Started: A Quick Checklist
Ready to start accepting TON? Here’s your launch plan:
- Create Your Manifest: Host a
tonconnect-manifest.jsonfile on your domain. Include your app name, icon, and terms of service URL. - Choose Your Stack: Decide between React/Vue for web apps, or Python/Go for backend-heavy systems.
- Integrate the SDK: Install
@tonconnect/ui-react(or equivalent) and wrap your app in the provider component. - Test on Testnet: Use the TON testnet (-3 network ID) to simulate transactions before going live.
- Set Up Webhooks: Ensure your backend listens for transaction confirmations to update order status automatically.
- Launch on Mainnet: Switch the network ID to -239 and start accepting real value.
By adopting TonConnect, you aren’t just adding a payment method; you’re aligning your business with a future where ownership and speed are paramount. You remove the intermediary, reduce costs, and tap into a massive, engaged user base. The technology is mature, the fees are low, and the demand is growing. The only question left is whether you’re ready to take custody of your own success.
Do I need a registered company to use TonConnect?
No. TonConnect is a protocol, not a regulated entity. As long as you have a valid TON wallet address and a web presence, you can accept payments. However, local tax laws regarding crypto income still apply to you as an individual or business owner.
What happens if the TON network is congested?
TON is designed for high throughput. Congestion is rare compared to older chains like Bitcoin or Ethereum. Fees remain low even during peak usage. In extreme cases, transactions might take slightly longer than 1 second, but finality is generally very fast.
Can customers get refunds?
Yes, but unlike credit cards, there is no automatic chargeback mechanism. Refunds must be initiated manually by the merchant sending funds back to the customer's wallet address. This puts the control in your hands but requires clear refund policies.
Which wallets are supported?
Any wallet that supports the TonConnect protocol works. This includes popular options like Tonkeeper, MyTonWallet, Telegram Wallet, and OpenMask. The list grows as more developers adopt the standard.
Is TonConnect secure against hacks?
The protocol itself is secure, using end-to-end encryption between the app and wallet. Security risks primarily come from poor implementation by the merchant (e.g., storing keys insecurely) or phishing attacks targeting the user. Following best practices mitigates most risks.
Ashwin Bhandurge
This is the paradigm shift we’ve been waiting for. It’s not just about technology; it’s about reclaiming sovereignty over our own labor and revenue streams. When you remove the intermediary, you remove the friction that stifles creativity and speed. Think about it: every second your money sits in a processor's limbo is a second of potential growth lost. TonConnect isn't just a tool; it's a declaration of independence for digital merchants. Let this be the moment you stop renting your financial life and start owning it. The future belongs to those who build directly on the rails of trust, not the bridges of bureaucracy.