AL+

Language: RO (română) EN (English)

Email us: paul@alplustech.com

Looking back at the week of 14–20 August 2024

Telegram subscriptions: distinguish Stars from revenue

Telegram's paid channel links simplified monthly access in August 2024. Separate subscriber payments, Stars balances and usable proceeds before planning income.

Citiți articolul în română

A paid channel can be easier to launch when the platform handles the invitation and recurring payment. That convenience is useful for a small content business. The business case still needs to distinguish what a subscriber spends, what the creator receives in platform currency and what the creator can ultimately use to pay expenses.

Looking back from November 2026, Telegram's 14 August 2024 announcement introduced special invite links for joining a channel in return for monthly payments in Stars. That was a concrete reduction in subscription plumbing. It was not evidence that a Stars balance equaled cash revenue, or that every prospective paid channel had customers waiting.

The subscription feature had a specific job

A paid invite link connects a recurring payment to channel access. For an existing Telegram audience buying content delivered in Telegram, that can fit the product directly. A creator can assess the offer without first commissioning a separate membership website and a custom access integration.

Consider an illustrative publisher offering a paid monthly research channel. The proposed advantage is that payment and joining happen inside the audience's existing environment. The example does not establish demand, a conversion rate or a delivery result. Before deciding whether the feature is sufficient, the publisher must say what subscribers are buying and what happens when access or payment fails.

Do not count every form of support as a subscription. The same August announcement introduced Star reactions, which let users support individual posts and creators. A reaction and a monthly access payment express different commitments. Combining them into one recurring-revenue figure would make forecasting less useful.

The distinction also matters to the offer. A reader supporting one excellent post has not necessarily agreed to pay for next month's publishing schedule. Keep voluntary support separate when deciding how much regular work the subscription can fund.

June explains the payment unit

The 6 June 2024 Stars launch described buying Stars through Apple or Google in-app purchases or PremiumBot and spending them on digital products from bots. It said developers would soon be able to withdraw earned Stars as Toncoin through Fragment. That future-tense statement belongs to June; it should not be described as proof that the withdrawal flow was already available on that date.

By August, the announcement described converting Stars into Toncoin rewards or using them for advertising. That is a documented platform route, not a guarantee that a particular creator can turn any balance into a chosen amount of local currency at any time. The article does not reconstruct exact launch exchange rates, payout waiting periods or withdrawal thresholds.

The distinction is necessary because buyer expenditure and creator proceeds occur at different stages. A buyer acquires a platform unit. The channel receives units. A creator may use an available reward route and may then need another conversion before paying ordinary business bills. A single promotional percentage cannot describe every stage.

Keep three records before forecasting income

For the proposed research channel, keep a record of subscription payments in Stars and the access periods they cover. Separately record the available balance and any restrictions verified for the actual account. Finally record realized proceeds and any costs of making those proceeds usable. These are recommended bookkeeping distinctions, not a tax classification or accounting opinion.

The August announcement's statement about receiving all Stars appeared in its Star reactions section. Do not silently broaden that sentence into a promise that subscription buyers' entire cash expenditure reaches the publisher. Even a full platform-unit credit would not establish the result after acquisition, reward and conversion stages.

For the same reason, this retrospective does not apply current platform terms backward to August 2024. Anyone launching now should inspect the applicable account eligibility, reward terms, refund handling and conversion route before making a current forecast. Those are open business questions to verify, not historical conditions asserted here.

Avoid filling an unknown with a convenient zero. If withdrawal costs or availability have not been established, leave the usable-proceeds estimate conditional. A business can still compare delivery options while acknowledging that it has not yet verified the full path from subscriber payment to spendable funds.

Native access does not define the whole service

A paid channel also needs a promise about its content. Say what will be delivered, how often and where subscribers can get help. If the proposed product includes individual support or access outside Telegram, a paid invite link alone does not explain who is entitled to those additional services.

Before committing, propose a small acceptance check using the actual product configuration: joining through the paid route, understanding the payment period and reaching the promised content. Also establish how a subscriber gets help with an access problem. These checks are suggestions for a future launch, not transactions performed for this article.

Avoid unnecessary custom development if the channel itself is the complete product. Conversely, if the business needs entitlements shared with another application, customer records outside Telegram or a different payment relationship, compare the cost of that integration with an independent subscription system. The simplest visible payment screen may conceal work elsewhere.

The strongest case for staying native

For a creator with an established Telegram audience, building separate infrastructure can be wasteful. A platform-native offer may be enough to learn whether people will pay for a clearly defined publication. Requiring a bespoke billing system before that learning would add cost without proving demand.

That is a good reason to use the feature within its actual scope. Keep the offer narrow, separate reactions from recurring subscriptions and reconcile Stars with realized proceeds before relying on the income. The August launch made monthly access easier to sell. A sound business decision still follows the payment all the way to what the creator can use.