Guide
How to pay for VPN with crypto
This page explains not only the payment step itself, but also the logic of the crypto-first flow in `Single Node VPN`: the site, the Telegram bot for identity, TonConnect, and then the setup of a private VPN on your own VPS.
Quick take
- The payment flow starts on the website after the Telegram bot identity step.
- The supported assets are `USDT` and `TON`.
- Service payment and VPS rental are separate.
Why payment is handled in the website flow
The bot is already part of the core product loop: support, app delivery, and access management happen in one place, while the payment step itself lives on the website and in the cabinet.
That reduces unnecessary transitions and keeps the flow consistent: the site explains the model and accepts payment through TonConnect, while the bot handles identity and operational actions.
What you need before payment
The user needs a clear TonConnect-compatible payment path and an understanding that the VPS is billed separately.
It is better to know what server you plan to use so the setup flow does not stall after payment.
What happens after payment
After payment, the flow does not end: the user provides VPS details, automated setup runs, and then they receive install and activation links for their apps.
That is why payment is not a separate end point here, but one step inside a broader onboarding flow.
FAQ
Can I pay by card?
No, the current product model is built around TonConnect and a crypto-only flow.
Which assets are supported?
The supported assets are `USDT` and `TON`.
Is the VPS included in the price?
No. The VPS is billed separately.
What happens after a successful payment?
The user continues onboarding: connects the VPS, waits for automated setup, and receives app install and activation links.
Single Node VPN does not promise absolute anonymity and does not guarantee that blocking will never happen. The service is built as a more controllable private VPN model on your own VPS.