30.05.2026
White-Label Crypto Payment Gateway for PSPs
Read article
If you sell access to a private channel, a bot subscription or anything else the buyer receives inside Telegram, the platform's own rules leave you one method: Telegram Stars. Crypto isn't singled out and banned here. Everything except Stars is — cards and bank transfers included.
If you sell a physical product or a real-world service — a consultation, a delivery, equipment, development work — Telegram doesn't process that payment at all. Its terms for bot developers let you choose a third-party payment provider, and they put no restriction on the currency that provider settles in. Nothing there rules a crypto gateway out.
So the opening question isn't which gateway. It's which side of that line your product sits on. And once you're on the second side, accepting crypto payments in Telegram turns out to mean one small thing: a payment link sent into a chat. No bot, no code, no integration to start.
The Bot Platform terms are unusually blunt about this. For digital goods and services, Telegram's terms for bot developers state that "all transactions pertaining to digital goods and services must be executed exclusively through the exchange of Telegram Stars". Exclusively — not "preferably", and not "unless you use crypto".
The reason is borrowed, and the document says so: "Since Telegram must adhere to Apple and Google's definitions of digital goods and services". Telegram's apps ship through the App Store and Google Play, so those stores' in-app purchase definitions reach all the way down to your channel subscription.
The other half of the rule is the half that decides your case if you sell anything tangible: "Telegram does not process payments for physical goods and services. Instead, Bot Platform provides a set of APIs that allow developers to interface solely and directly with third-party payment providers." If you want to sell physical goods and services on Telegram, the terms say, you can choose a third-party payment provider. That's the door. The terms name no permitted currency and rule none out, so a crypto payment gateway for Telegram is a third-party provider like any other processor.
Stars side — the buyer receives it inside Telegram:
Outside-provider side — the buyer receives it in the real world:
One test settles most edge cases: where does the buyer actually receive the thing? Inside Telegram, treat it as digital and price it in Stars. Outside, the payment is yours to route.
One narrow rule gets misfiled here. A Mini App that builds token issuance or distribution into itself is "required to be based exclusively on The Open Network (TON) blockchain" and may not promote non-TON assets — a rule about crypto functionality inside your app, not about sending a customer a USDT invoice from an outside gateway; if that's your territory, TON and Telegram Mini App payments covers it properly.
You're not stuck, you're just on a fixed track. Here's what the track looks like.
How the sale runs. The buyer taps a price inside your bot or channel, pays with Stars he already holds or tops up in-app, and your bot grants the access. There's no outside processor to sign up with and no settlement account to open — Telegram's documentation on Stars payments is what a developer builds the invoice flow against. For a paid channel, the checkout is Telegram's own.
What actually reaches you. Developers receive the equivalent of 0.013 USD of rewards per Telegram Star. Do the pricing arithmetic in that direction rather than the other: if you want about 10 dollars a month per subscriber, you're pricing near 770 Stars, not near "10 dollars' worth". Set the number before you announce it, because moving a subscription price after launch costs you subscribers.
What the balance is. Stars sitting on your balance "are owned by Telegram and have no inherent value beyond our good-faith commitment to advertisement credits and rewards", in the terms' own words. Read that as it's written: the balance is a claim on Telegram, not money in an account you control. Unused Stars are valid for three years from the date they were received.
What you can do with it. Two routes exist — spend the balance as advertising credit inside Telegram, or take it out as rewards. The thresholds, timing and conversion mechanics for taking it out are set by Telegram and get revised; check the current terms before you plan cash flow around a payout date, and don't budget on a number you read in an article, this one included.
What of your business is still on the crypto side. Most channel operators sell more than the channel. The one-to-one consulting call, the offline workshop, the printed workbook, the done-for-you service, anything shipped — none of those are digital goods delivered inside Telegram, and none of them are Stars-bound. You can invoice for them in USDT this afternoon using the link route below. Splitting your catalogue that way isn't a loophole; it's what the two categories already are.
The flow has four moves. You agree a price in the chat. You create an invoice — an itemised payment request with a fixed amount, currency and expiry date. You paste its link into the conversation or pin it in the channel. The customer opens it, pays from whatever wallet he already uses, and you get a notification.
That's the whole mechanism. The customer installs nothing. You need no website. The link is an ordinary URL, so it works in a private chat, a channel post, a bot menu button or your profile bio, and Telegram doesn't process the payment at all — by its own terms — because the payment happens on the gateway's page.
Everything else is automation of those same four moves. Which is why the four options below separate on two questions: how much code do they need, and what happens to the money once it lands.
Each card carries the same four lines — who it suits, what it takes to start, what acceptance costs, and what becomes of the money afterwards.
Best for: selling in DMs, in a channel or on a call. Consultations, custom orders, small batches of physical goods, anything where you quote a price and then get paid.
What it takes: an account with a crypto payment gateway. You create an invoice in the console — amount, currency, description — and copy the link. Nothing is installed on Telegram's side and there's no bot to maintain. The settings that matter later, like expiry windows and what happens when someone pays the wrong amount, are covered in how crypto payment links and QR invoices work.
What acceptance costs: published gateway rates for a plain payment sit between 0.5% and 1% — and check the figure for your actual scenario, because multi-currency acceptance and passing the fee to the customer are often priced separately. The CryptumPay gateway, for example, charges 1% per successful payment, from 0.5% at volume, and the fee can be passed on to the customer.
What happens to the money: this varies far more than the percentages. Some gateways price both ends of the deal; many publish only the acceptance rate and leave the payout unpriced — pin the payout terms down inside the account before real money runs through. CryptumPay converts incoming funds to USDT the moment they arrive, so the balance doesn't sit in a coin that can move overnight, and withdrawal to your own wallet is available at any time with no minimum amount.
Best for: small, occasional sales where speed of setup outweighs knowing your costs in advance — and where the money doesn't sit around.
What it takes: almost nothing. You talk to a bot, create an invoice, send it. Crypto Pay handles USDT, TON, BTC, ETH, LTC, BNB, TRX and USDC, with per-invoice limits running from roughly 1 to 25,000 USD.
What acceptance costs: not published, and that's the deciding fact about this option. The Crypto Pay API reference documents a `fee_amount` field — "amount of service fees charged when the invoice was paid" — and a `fee_asset` field naming the coin it was taken in. Both arrive only once the invoice has been paid. No percentage appears in that reference, on help.crypt.bot or on pay.crypt.bot. You learn your rate by reading it off a completed sale.
What happens to the money: it lands in a wallet inside Telegram, not in a merchant account. That's the structural point here — it's a consumer wallet with an invoicing API bolted on. The documentation describes invoices and balances, not settlement-currency rules or merchant reporting, and the funds sit under a Telegram account, so account recovery is the whole of your recovery story. Fine for pocket money. Uncomfortable once the numbers get real.
Best for: anyone whose bot already takes the orders and whose orders arrive in a steady stream — course access, subscription renewals, a catalogue of dozens of items.
What it takes: a developer, or a weekend if you are one. Your bot asks the gateway's API for an invoice when the customer picks a product, then waits for a webhook — a callback the gateway fires at your server the second payment confirms — and grants access, releases the order or updates your CRM without you touching it. The questions to ask an API before integrating is worth an hour before you commit to a provider.
What acceptance costs: the same rate as the link route with the same provider — API access isn't usually priced separately. Your extra cost is development and maintenance — a build plus a small tail, counted in hours.
What happens to the money: identical to the link route with that provider, which is exactly why this is a build decision and not a money decision. On CryptumPay, the API covers orders, deposits and payouts with instant notifications through callbacks and webhooks and a Node.js SDK, and settlement behaves the same whether the invoice came from the console or from your bot.
Best for: person-to-person transfers and informal sales between people who both already use it. Inside the app it genuinely is the smoothest thing here.
What it takes: nothing to set up. That's the appeal, and it's a real one.
What acceptance costs: the consumer wallet has no merchant rate to compare — you pay transfer and conversion costs as a user, which is a different pricing model from everything above. Wallet does run a separate merchant product on its own domain; it's a different thing from the wallet in your Telegram app, it isn't what people mean when they say "just send it to my Wallet", and its terms aren't published where the wallet's help pages are. If you want it, price it with the vendor directly.
What happens to the money: three things to weigh. Availability is restricted in a published list of territories, and Telegram Wallet's restricted access page names the United States and associated territories — American Samoa, Guam, the Northern Mariana Islands, Palau, Puerto Rico and the U.S. Virgin Islands — among them, so American buyers quietly fall out of this route. The main balance is held for you by the service rather than by you — the help pages don't say so in as many words, but they offer a self-custody TON address, one whose keys are yours alone, separately as a "DeFi Account", which tells you what the ordinary balance is. And the wallet in your app is a wallet: order statuses and reconciliation are not what it's for.
Selling in conversation and want money today: take the link. Bot already doing the selling: give the bot the API. Testing whether anyone will pay at all, in small amounts you'll move out quickly: @CryptoBot works, as long as you accept that you'll learn the fee afterwards and that the balance lives under your Telegram account. Considering Wallet as a checkout: it isn't one — use it for what it is.
If the shortlist is still long after that, how to choose a crypto payment platform has the questions that separate providers once the headline rates look alike.
The no-code path, for the physical-goods-or-real-service side of the line.
Four things set your real cost. The acceptance percentage is only the first of them, and usually the smallest.
The coin it sits in. If a customer pays in a volatile asset and your balance holds it, you're carrying market risk between payment and withdrawal — the sum you booked and the sum you withdraw are different sums. Conversion to a stablecoin at the moment of arrival ends that. Ask any provider whether conversion happens on arrival or only when you request it; the gap between those two answers is where surprise losses live.
Whether you can get it out. Ask for the payout rules in writing before you sign up: minimum amount, processing time, manual or automatic mode, and whether payouts go to any address you name or only to a whitelisted one.
What moving the money costs. Sending USDT out over TRON costs roughly 6.5 TRX if the receiving address already holds USDT and about 13 TRX if it doesn't — the first USDT ever to arrive at an address costs more to deliver. With TRX near $0.33 that's about $2.10 and $4.30. Not fractions of a cent, and what USDT transfers really cost on TRON walks through why.
Now put the pieces together on a real month. Say you take €2,000 across twenty invoices.
The other two lines of the bill answer a different question — not what the month costs, but whether a small balance is worth moving at all.
A minimum withdrawal decides whether the money is stuck. A €50 floor is invisible at €2,000 a month, where every weekly sweep is around €495. It is decisive for someone closing €30 sales who wants the cash the same week: one sale, and the balance sits there until a second one arrives.
The network fee is charged per withdrawal. Four TRON sweeps cost about $8.50 a month where one costs about $2 — the line shrinks when you batch and grows when you sweep daily, whatever your acceptance rate. The layers underneath the headline number are unpacked in how crypto payment fees are built.
Whether the money is clean. Funds that arrive from mixers or sanctioned addresses can sour your relationship with an exchange months after the sale closed. Providers differ on when they look, so ask where the screening sits: a filter that holds suspicious funds before they reach your balance is the difference between one rejected payment and a compliance conversation later. If you take money from strangers at any volume, AML checks on incoming crypto is the background worth having.
Two separate rulebooks apply to you, and mixing them up is expensive in both directions.
Telegram's rules are platform rules. The Stars requirement, the third-party provider clause and the TON rule for Mini Apps come from a terms-of-service document that changes when Apple's and Google's store policies change. Break them and what you risk is your bot, not a court date.
Whether you may legally accept cryptocurrency at all is a question of law where you live. The answers diverge sharply between countries: some treat crypto as ordinary payment with ordinary tax consequences, some require registration or a licence, some prohibit domestic businesses from taking it for their own goods and services. Check your own jurisdiction before your first invoice, and check the tax treatment separately from the legality — they're often decided by different rules. This article is not legal advice.
If what you're collecting is tips or support rather than payment for a specific thing, the tooling and the rules both look different; accepting crypto donations as a creator covers that case.
For physical goods and real-world services, yes. Telegram doesn't process those payments, and its bot developer terms let you choose a third-party payment provider, with no restriction on the currency that provider settles in. For digital goods and services delivered inside Telegram, no: the terms require those transactions to run exclusively through Telegram Stars.
No. A gateway invoice is a link, and a link works in a DM, a pinned channel post or a bot button. You can accept crypto in a Telegram bot without a website, and you can accept it with no bot at all.
Create it in your payment provider's console — amount, asset, network, description, expiry — and send the resulting link into the chat. The customer pays from any wallet he already has. You act on the provider's notification.
The rate isn't published. The Crypto Pay API returns a `fee_amount` field showing what was deducted, but only after an invoice has been paid, and no percentage appears in the public documentation. If knowing your margin before the sale matters, use a provider that publishes its rate.
They don't compete, because they don't apply to the same sales. Stars are compulsory for digital goods inside Telegram, at 0.013 USD of developer rewards per Star. Gateways handle physical goods and real services at published rates of roughly 0.5% to 1%, plus whatever conversion and withdrawal cost you. Your product decides the column; the arithmetic only starts after that.
Look at what you sell before you look at what you'd like to use. Digital, delivered inside Telegram: Stars, with no route around it, so price in Stars and move your non-digital products onto a separate rail. Physical goods or a real service: Telegram steps aside, a crypto gateway is a provider like any other, and the whole thing starts as a link in a chat — upgraded to a bot with an API when the order flow makes the automation worth building. Then read the payout side of the price list as carefully as the acceptance side. On the €2,000 month above the percentage still decides most of the bill — but the minimum withdrawal and the per-sweep network fee decide something the percentage never touches: whether a small balance is worth moving at all.
Checked against primary sources in August 2026.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.
