You can accept real money in a Telegram bot without touching Stars, and the main route is Telegram's own Bot Payments API, which connects to more than 20 payment providers across over 200 countries and takes no commission for Telegram itself. You pay your processor and nobody else.
Most guides send you straight to Stars because it's the newest thing and the checkout is one tap. That's the right call for a 30-Star post unlock. It's the wrong call the moment your ticket size passes about $5, because in-app Star purchases carry roughly 30% of app-store overhead. So here are the other five routes, what each actually costs, and when each one is the correct choice.
Does the Telegram Bot Payments API cost anything?
No. Telegram's documentation states plainly that it does not charge any commission on payments made through the Bot Payments API. Your entire cost is whatever your payment provider charges, commonly 2.9% + $0.30 per card transaction in the US if you're on Stripe.
That makes it the cheapest legitimate rail on this list for card payments, with two real caveats. You need someone who can write the integration, and you need a processor that will underwrite your business category. The second one ends more creator projects than the first.
How the Bot Payments API flow works
Worth understanding before you pick, because the mechanics explain the failure modes.
- Your bot calls
sendInvoiceto generate the invoice - The fan taps pay and enters card details in Telegram's native sheet
- Telegram fires a
pre_checkout_queryupdate at your bot - Your bot has 10 seconds to answer with
answerPreCheckoutQueryor the payment fails - The provider processes the charge
- Your bot receives a
successful_paymentupdate and delivers the goods
That 10-second window in step 4 is the detail that bites people. It is not a suggestion. If your server is doing a slow inventory lookup or waiting on a third-party API before confirming, the payment dies and the fan sees an error at the exact moment they decided to buy. Confirm first against cached state, reconcile after.
For Stars specifically the flow is nearly identical, with currency set to XTR and refunds issued through refundStarPayment. Telegram also makes clear that bot developers are solely responsible for handling user disputes, which is a meaningful liability to accept knowingly rather than discover.
The six ways to take money in a Telegram bot
| Method | Real cost | Payout timing | Best for |
|---|---|---|---|
| Bot Payments API (Stripe or similar) | 2.9% + $0.30, Telegram takes 0% | 1–2 business days | Card sales at any ticket size, if you can build and get approved |
| Telegram Stars | Up to ~30% on mobile purchases | 21-day hold per Star | Micro-unlocks and tips under ~$5 |
| Payment link from an external platform | Published platform rate | Depends on platform | Selling now, without a developer |
| Telegram Wallet Pay | Near 0% internally, gas on withdrawal | Instant | Crypto-native audiences |
| Direct crypto transfer | Gas only, $0.01–$1 | Instant on-chain | Technical audiences, low volume |
| Manual PayPal or bank transfer | 2.9% + $0.30 on PayPal | Bank-dependent | Under five buyers, honestly |
Figures for the non-Stripe rails come from GramBase's breakdown of Telegram payment methods.
Which method should you actually use?
If you're technical and Stripe will have you: Bot Payments API, no contest. Zero platform commission is not a marketing claim here, it's the documented arrangement.
If Stripe has already said no: this is where most creators selling coaching, adult content, or high-ticket offers land, and the Bot Payments API stops being an option because the providers behind it are the same processors that declined you. Switching bots doesn't change underwriting, the same way switching funnel builders doesn't change your processor. You need a payment layer underwritten for your category, not a different front end on the same refusal.
If you don't want to write code: a payment link. DROPP's Telegram setup is one link that runs drops, auctions and raffles inside the chat, fans pay without leaving, and the rate is published before you sell: 5% creator with 10% paid by the buyer on the standard tier, weekly payouts. No 21-day per-item hold, no 10-second webhook to get right, no dispute liability sitting on your bot developer.
If your audience is already in crypto: Wallet Pay or direct transfer, and skip the rest of this article.
If you have three customers: take the PayPal payment manually and build nothing. Seriously. Automation below about five buyers a month costs more in your time than it saves.
Who handles refunds and disputes?
You do, and this is underdiscussed. Telegram's Stars documentation states directly that bot developers are solely responsible for processing and rectifying legitimate user disputes. Telegram provides the refundStarPayment method and stops there.
On the card rails it's worse in a different way. A chargeback on a Stripe-processed bot payment behaves like any other chargeback: you pay the dispute fee, you assemble evidence, and a pattern of them puts your processing at risk regardless of how good your bot is. The bot layer offers no protection whatsoever, because the bot is not the merchant of record.
Before you pick a rail, decide who eats that work. If the answer is "me, manually, at 11pm," price your time into the comparison. If a platform absorbs dispute handling inside its rate, that's worth real money on any product with a refund rate above a couple of percent.
What to check before you build
Four questions, in order, and the first one disqualifies more setups than the other three combined.
- Will a processor approve your category? Not "is your product legal," but "will an automated risk model approve it." Coaching, adult content, supplements and anything with fast revenue growth all get flagged routinely.
- What's your average ticket? Under $5, Stars wins on friction. Over $20, the fee math dominates and Stars stops making sense.
- Do you need recurring billing? If yes, you are choosing between building a billing system and buying one. There is no third option on the raw Bot Payments API.
- Where do your fans live? Provider coverage varies by country, and a rail that works beautifully for a US audience can be unusable for a largely Nigerian or Indonesian one.
Answer those honestly and the choice usually makes itself.
What about subscriptions and recurring access?
This is the honest gap in the Bot Payments API. It handles one-off invoices well and gives you no subscription management. Recurring billing, dunning on failed cards, access revocation when someone stops paying, and renewal reminders are all yours to build.
For a paid channel, that's not a small amount of work. It's a billing system. Either use a platform that already has one, or budget properly for building and maintaining it, because the failure mode is subscribers who quietly stop paying and keep their access.
Frequently asked questions
Can I accept payments in a Telegram bot without using Stars? Yes. The Bot Payments API supports over 20 providers in more than 200 countries, and Telegram charges no commission. Payment links, crypto and manual transfer also work.
Does Telegram charge a fee on the Bot Payments API? No. You pay only your payment provider's rate.
Which countries does the Bot Payments API support? Over 200, through more than 20 providers, with per-transaction limits generally in the $1 to $10,000 range depending on provider.
Why did my bot's payment fail at checkout?
The most common cause is missing the 10-second answerPreCheckoutQuery deadline. Telegram cancels the payment if your bot doesn't confirm in time.
What if Stripe won't approve my Telegram business? The Bot Payments API won't help, since it routes to the same processors. You need a payment provider that underwrites your category directly. That's the difference between a flat-rate processor and one built for higher-risk categories.
Pick the rail that matches your ticket size and your approval odds, not the one with the smoothest demo. Full pricing if you want to compare against a published rate.
