I built a paid Telegram bot. Here's what Telegram Stars actually pay.

A few months ago I launched a paid Telegram bot. No Stripe, no checkout page, no app-store account. The whole subscription runs on Telegram Stars — Telegram's own in-app virtual currency. People had questions. The most useful answer was the math, which nobody publishes openly. So here it is.

The setup

PolySignal is a Telegram bot that alerts users when top wallets on Polymarket make a trade. It has a free tier and two paid tiers (Signal 150⭐/month, Pro 750⭐/month). Subscriptions are recurring, billed every 30 days, cancellable in two taps inside Telegram. No payment provider, no checkout flow, no shipping address fields.

If you've never sold anything in Telegram: you're missing one of the cleanest payment surfaces on the internet. There's also one inconvenience hidden in the math. Both worth knowing about.

How users pay

A Telegram user buys "Stars" — Telegram's in-app currency — through Apple IAP, Google IAP, or Telegram's web purchase. They cost roughly $0.02 each at retail (e.g., 75⭐ for $1.49, depending on bundle). The user spends those Stars on paid bots. From the user's perspective: tap, confirm, pay with the Apple/Google account already linked to the phone. No friction. No "I need a credit card." Zero fields to fill.

This is, by some distance, the lowest-friction global subscription payment surface I've shipped on. There are users who pay for PolySignal that I'd never have reached with a Stripe checkout — same Telegram, never typed a card number, in the same flow as buying premium stickers.

How the developer gets paid

Here the math gets specific. The user pays via Apple/Google → Apple/Google take 30% → Telegram takes a cut → what remains lands in your Telegram-bot Stars balance. You then withdraw via Fragment (Telegram's marketplace) into TON, the network coin, and convert from there.

The widely cited dev-side rate: about $0.013 per Star — the value of one Star after Apple/Google and Telegram have taken theirs.

Which means:

• Signal at 150⭐/month → about $1.95 net to me.
• Pro at 750⭐/month → about $9.75 net to me.

If those numbers look small, that's because they are. Two caveats:

1. The 150 / 750 prices are deliberately low. I'm collecting conversion data on an unproven product; I'd rather see whether people convert at all before optimising revenue per user. The Stars rate is what it is, but my retail price is a knob I'll turn once I have churn data.
2. Margin on the dev side is real: ~95% gross. There's no per-user infrastructure cost worth mentioning, no support team, no advertising spend. The question is volume, not unit economics.

The payout side: where Stars-billed gets less convenient

Here's the part nobody mentions when they pitch you on Telegram Stars: how you actually withdraw the money is its own story.

Fragment is the bridge from your Telegram-bot Stars balance to actual currency. It works, but:

• Minimum withdrawal is 1,000 Stars (~$13).
• First-time withdrawals are delayed 21 days — the Stars you earn today won't even be eligible for withdrawal for three weeks.
• Payout is in TON, not USD. Fragment sells your Stars for TON; you then convert TON → fiat through an exchange with its own KYC and fees.
• Fragment requires Telegram login + a connected TON wallet. Identity verification at higher transaction sizes is "not publicly documented," by which I mean: you'll discover it when you cross a threshold.

If you're used to Stripe — daily payouts, direct deposit, no crypto in the chain — this feels archaic. If you're used to running a crypto-native business — TON is fine, this is just another rail.

The honest summary: convenience for the user, friction for the developer. The user gets a payment so low-friction it almost doesn't feel like one. The developer gets paid through a crypto off-ramp that takes three weeks for the first round.

Why I did this anyway

Three reasons:

1. Global reach with zero compliance overhead. I don't have a legal entity. I haven't talked to a payment processor. I haven't filled in a single "tell us your business model" form. Telegram (with Apple/Google) handles consumer VAT collection at the Stars-purchase point. I don't see card data. I don't see banking details. I can't be liable for things I never received.

2. The product lives in Telegram already. PolySignal's whole user surface is Telegram messages. Asking users to leave the app to enter a credit card on a third-party page would have been a substantial conversion tax — and a meaningful chunk of my audience is in countries where Stripe doesn't even land.

3. The bar for "an indie founder can ship this" was unusually low. Telegram's Bot API documents createInvoiceLink clearly. There's a subscription_period parameter for recurring. Auto-renewal is a 30-day-only fixed period (annoying — no weekly, no yearly recurring). The successful_payment update fires once on the initial charge and again on every monthly renewal, with an is_first_recurring flag. About 200 lines of Python total for the whole billing layer. Stripe would have been more.

What I'd tell another indie founder considering this

• If your product lives in Telegram already, Stars are the right rail. The conversion gain from the in-app flow probably outweighs the worse payout mechanics.
• If your product lives in a web app or a mobile app, Stars probably isn't worth the funnel detour.
• Build the withdrawal pipeline (Fragment → TON → fiat) early, before money is on the table. Discovering payout delays after you've earned $300 is unpleasant.
• The 30-day-only subscription period is a real product constraint. Annual plans have to be one-time charges, with manual expiry extension. Plan for it.
• Watch what users are actually charged. Apple/Google can adjust the user-side retail price of Stars without changing your developer rate per Star. The number you see in your Telegram dashboard is the number that matters.

And, finally, the bot

PolySignal is the bot I built around all this. It sends Telegram alerts when top wallets on Polymarket make a trade. Free tier, real-time on Signal, consensus alerts on Pro. The Telegram-Stars subscription mechanic above is the same one running in production.

If you're curious to see the user experience side of "billed in Stars": t.me/PolySignalAlertsBot

If you're building a paid Telegram bot of your own and want to compare notes — leave a comment, I'll answer.