Bot for accepting payments and subscriptions in Telegram: turnkey payment automation

If your bot has a “Pay” button, and then the client sends a check in a personal message, and you manually check the transfer, open access and write down the renewal date in the sign - you do not have a service, but a 24-hour operator change. Telegram bot with subscription and payment relieves the owner of exactly this work: accepts money, issues access and writes off renewals without a single manual action.

We are a globall.dev studio, developing Telegram bots and web services: 17+ bots in production and our own product Globall VPN, which lives exactly on these mechanics. In this article, we’ll take an honest look at how payments are accepted in a bot, how the subscription model differs from a one-time sale, what’s included in turnkey automation, how much it costs and how long it really takes to launch.

Why does a bot need to accept payment and subscribe?

The main value of a payment bot is not a “nice button”, but what happens after payment. A good payment circuit solves four problems at once:

• Accepts money in several ways at once - card, bank transfers, UMoney, cryptocurrency if necessary - without forcing the client to the browser.
• It gives out what you paid for: access to a private channel, key, config, course files, license. In seconds, without you.
• Remembers about renewals: the subscription is automatically debited on the required day, and the defaulter is disconnected without your participation.
• Counts money: each payment is recorded in the database, revenue and active subscriptions are visible in the admin panel.

A one-time sale is “paid → received the goods.” Subscription is more complex and more valuable: it is recurring revenue that grows on its own if the auto-renewal mechanic works reliably. That’s why a subscription bot requires not only accepting payment, but also billing—accounting for periods, recurring charges, and automatically closing access.

What payment systems are connected to the Telegram bot?

The choice of provider determines what methods the client will be able to pay and whether auto-renewal is supported. For Demo cityn business, the set is well-established:

In practice, several providers are often connected at once - for example, payment gateway for the bulk and CryptoPay for those who pay with crypto. The client chooses a convenient method, and the bot processes everything the same way: confirmation of payment is received by a webhook, and then the issuance of access starts.

How does payment acceptance and auto-issuance work technically?

To make it clear what you pay for during development, I’ll break down the payment path step by step - without unnecessary terminology:

1. The client chooses a tariff. The bot shows a fork (for example, 1 / 3 / 12 months) and generates a payment for the required amount.
2. Payment. Payment by card, via bank transfers or digital wallet opens - ideally right inside Telegram via WebApp, without going to the browser.
3. Confirmation. The payment system sends a webhook with status to the bot server. The bot checks the signature and amount - this protects against forgery.
4. Automatic issue. The payment is confirmed - the bot itself performs the action: adds it to a private channel, issues a key or files, activates a subscription in the database.
5. Accounting. The payment and expiration date are recorded in the database. From this moment on, the bot “knows” when the renewal time comes.

For subscription, another circuit is added - recurring auto write-offs. The cron task checks every day who is running out of period and writes off payment for the next one using the saved payment method payment gateway. If the write-off has been completed, access is extended silently; if not, the client receives a reminder, and after a specified period of time, access is closed automatically. The owner does not interfere in this process at all.

The key difference between a production bot and a prototype is error handling. The payment may be stuck in the pending status, the webhook may arrive twice, and the card may not be debited. In each of our bots, these scenarios are processed: a repeated webhook does not grant access twice, an unsuccessful write-off does not crash the service, and disputed payments are visible in the admin panel.

Real example: a VPN service that sells and renews itself

This mechanic is best seen in the studio's own product. We have collected VPN service by subscription to Telegram bot (plus a website with a personal account) - Globall VPN. This is not a demo prototype, but a live service on which we ourselves test what we then build for clients.

How the purchase funnel works. A new user goes through onboarding, selects a device and immediately receives free trial key - this removes the barrier “will it work at all.” Next, select a tariff (1, 3 or 12 months) and pay by card, through bank transfers or digital wallet directly inside Telegram via WebApp. The payment is confirmed by a webhook - and a VLESS key is created via the 3x-ui panel API and issued automatically in seconds.

The heart of the service is renewals. Subscription is made from recurrent auto write-off: cron on the required day itself writes off the fee for the next period using the saved payment gateway method. If a client buys more months, the balances are added up and not burned. The subscription has expired without payment - access is revoked automatically, without the “forgot to disable the non-payer”.

At the top is growth and retention: the referral system awards bonus days for the first payment of the invitee, the middleware of a mandatory subscription to channels gives a bonus for subscription, and the admin panel gives the owner of the newsletter manual issuance/revocation of access and user management - in case you still want to intervene. Stack: Python + AIogram, FastAPI, MySQL, payment gateway, 3x-ui/VLESS. The outline turned out to be exactly what most subscription products need: payment → auto-issue → auto-renewal.

Subscription accounting, renewal and revocation of access apply to different products. The payment scheme depends on the place of sale and the type of product: digital goods inside Telegram are paid for by Stars.

How much does a bot cost with subscription and payment?

The cost depends on whether you need a simple one-time payment or a full-fledged subscription service with auto-renewal. Here are the actual rates and terms in our studio:

The exact figure depends on the payment methods, the number of tariffs, the complexity of issuing access and whether you need a referral system and a web storefront. See the full tariff schedule and cost calculator on the page services and prices — there you can collect an approximate estimate in a couple of minutes.

What should be included in a turnkey payment bot?

A checklist to check any proposal for the development of a subscription bot:

• Accept payment with webhook signature verification (protection against payment forgery)
• Idempotent issuance of access - repeated webhook does not issue the product twice
• Recurrent auto-debits and auto-closing of access for the defaulter
• Tariffs with different periods and correct accounting of balances upon additional payment
• Admin: revenue, active subscriptions, manual issue/review, mailings
• Fiscalization of checks under applicable local rules, if you work with individuals in the Demo city
• Monitoring, backups and error handling Telegram API - included by default

How do we work on such a project?

The approach is simple and without surprises. First, a brief: you tell us what you are selling and to whom, we ask clarifying questions and send fixed estimate and terms in the contract - usually in one day. Next - step-by-step payment and demo every 2-3 days, so that you see progress and do not receive a “black box” at the end.

We are hiring limited number of projects at once — this keeps the deadlines realistic. Billing is designed first because it directly affects revenue and retention: first, what brings in money is automated, then everything else. You own the source code from day one — you are not tied to us and can further develop the bot with anyone.

Frequently asked questions