Telegram subscriptions start with what the bot actually sells
Telegram supports recurring Stars payments. Digital-product rules, confirmed payments and entitlement expiry determine how a paid bot should work.

Telegram already supports recurring payments in Stars. The first decision for a paid bot is what the customer is buying, because Telegram applies different payment rules to digital products and physical purchases.
That distinction can change the whole integration. A bot selling access to generated reports has different constraints from a bot taking an order for a delivered meal. Choosing a payment provider before identifying the product can send the implementation down the wrong route.
Start with the product being sold
Telegram's digital-goods payment documentation requires Stars for digital goods and services sold inside its apps through bots or mini apps. That requirement also applies when the business has an external website. Cryptocurrency is not an alternative payment method for those in-app digital sales.
For a report-generating bot, the relevant purchase is digital access. Calling it a membership changes the description on the button, with no change to what the customer receives. The payment design has to follow the actual product.
Telegram has a separate payment flow for physical goods and services. It uses third-party payment providers. The provider handles sensitive payment details, while the merchant remains responsible for fulfilling the order. Provider availability depends on the merchant's situation; an old integration example cannot guarantee that a particular provider is available to a new account.
A sensible implementation brief therefore names the product first. State where the customer buys it, what they receive after payment and how long their access lasts. Those details determine which technical flow needs testing.
Recurring Stars payments are native
Telegram's subscription documentation covers subscriptions for bots as well as channels. Bot subscriptions can automatically renew using the customer's Star balance. Channel administrators can also create paid invite links for recurring access to a private channel.
The supported period in the documentation checked on 14 November 2026 is 30 days. A 30-day renewal interval can land on a different calendar date after a shorter month. The purchase description should say what interval is being sold so the customer knows when the next charge is due.
For bots, the createInvoiceLink method accepts the subscription period with the Stars currency code XTR. The documented period is 2,592,000 seconds. The same API exposes payment information needed to identify a subscription's paid-through date.
This makes a recurring bot product technically possible without building a reminder-only renewal system. It still needs an application-side definition of access. A successful payment should extend the customer's entitlement according to the product they bought. Cancellation should leave a consistent record of when that entitlement ends.
Payment confirmation belongs on the server
A customer returning to a mini app after checkout is a navigation event. The entitlement should depend on the payment notification your backend has actually processed. The Bot API's successful-payment data provides the relevant payment identifier.
Store that identifier with the customer and the purchased entitlement. If the same update arrives again, processing it a second time should leave the entitlement unchanged. This is an implementation requirement you can test by replaying a recorded test event.
A paid membership also needs an explicit expiration rule. A subscription may be cancelled after a successful payment, with access continuing until the paid period ends. A failed renewal needs its own outcome. Decide whether the service stops immediately at expiry or includes a stated grace period, then make the interface match that decision.
Use a test account to follow the full path through renewal. Check the backend record at each step. A payment button that works once leaves most of a subscription product untested.
Support is part of the payment flow
Telegram's bot developer terms place responsibility for legitimate payment disputes on the developer. Digital-product bots must handle the /paysupport command. The API supports returning Stars for a purchase that the bot cannot fulfil.
Design the refund path before customers need it. A support record should connect the reported problem to the payment and the delivery state. If a purchase is refunded, define what happens to the access it created. A refund that leaves the entitlement active can turn a support correction into a recurring accounting error.
The same terms make reward availability a separate consideration. A Star balance is not a bank balance in the merchant's chosen currency. Receiving rewards through Fragment has its own conditions and geographic limits. Any revenue calculation needs to use the merchant's actual eligible route, with its current terms.
That is a reason to test the business process at a small scale. Record what the buyer spent, what was delivered and what the merchant can actually receive. Keep those amounts in their original units until there is a documented conversion.
Ship one complete entitlement cycle
A first release can have one paid product with one renewal interval. The useful scope limit is the number of products, with the whole payment lifecycle still present. A buyer needs to understand the charge before paying and be able to resolve a failed delivery afterward.
For a channel membership, start with the supported paid-invite flow. For a bot product, connect a Stars subscription to a backend entitlement that you can inspect. Physical purchases need a suitable third-party provider and an order-fulfilment process.
The payment choice becomes easier once the product is specific. The release is ready when a test customer can buy the intended access, reach its expiry and get a consistent outcome after cancellation or a refund.