How to Accept Payments on Telegram: Rules and Setup (2026)

Accepting payments on Telegram starts with what you sell and where the sale happens. Digital goods/services sold inside bots and Mini Apps must use Telegram Stars. Physical goods/services have a separate provider route. A bot’s supported crypto switch, an external website or an audience already holding USDT does not exempt an in-app digital sale. Telegram’s official rules answer this first decision.

I built GramBase. This guide explains payment approaches and responsibilities, rather than claiming every method has been independently tested or ranked by a universal fee.

Understand the four commerce jobs

A storefront explains the offer. An order identifies the buyer and intended charge. A payment service confirms the receipt. Delivery grants the item or access. These jobs can be run by several services or one tool, but they remain different states.

For a short first-offer checklist, use can you accept payments through Telegram?. For broader business decisions, read how to sell on Telegram.

Compare payment approaches by sales context

Approach	Where to evaluate it	Additional work
Manual external payment	A separately permitted transaction	Match receipt to buyer, fulfill, record refunds and access
Wallet transfer	A permitted transfer context	Verify exact network/asset/recipient and reconcile the order
Telegram Stars	Digital goods/services inside bots/Mini Apps	Product records, delivery, support and access lifecycle
Telegram provider Payments API	Physical goods/services within supported conditions	Provider setup, order, fulfillment and disputes
Integrated commerce/membership tool	The tool’s supported offer and permitted rails	Configuration, permissions, buyer testing and support
Custom bot	A workflow requiring proprietary behavior	Build and maintain validation, storage, delivery, refunds and access

A manually posted address is not proof of permission for a bot/Mini App digital sale. Do not use this list to route around the Stars requirement.

Manual payments and wallet transfers

A manual flow can be adequate for a controlled small transaction if the context permits it. Keep the actual receipt, order and buyer together. Screenshots are not settlement proof, and two transfers of equal value can still need careful matching.

Network charges and exchange withdrawal charges vary. Use the quote shown to the buyer instead of universal $0.01-$1 or TRON $0.30 claims. Never describe an irreversible transfer as eliminating refunds or customer obligations.

A personal @wallet transfer and Wallet Pay’s merchant service are distinct. Do not infer merchant webhook, API or delivery capabilities from a person-to-person transfer screen. Verify the exact service’s official current merchant documentation and eligibility before selecting it. This guide does not assert that Wallet Pay lacks payment notifications or automatically provides a membership platform.

For supported transfer checks and failure handling, read crypto payments around Telegram.

Telegram Stars for digital purchases

A buyer spends a Stars balance on an invoice. A bot must wait for the successful-payment event, retain the charge identifier and then deliver. Pre-checkout approval alone is not a paid order.

For no-code configuration, create a product and whole-number Stars price; each subscription tier needs its own amount. Use the Stars setup tutorial and the Stars product use case.

The buyer’s Stars acquisition price differs from the merchant reward. Telegram’s developer terms, checked October 3, 2026, state a $0.013-per-Star reward reference which can change, with earned Stars potentially unavailable for rewards for up to 21 days. Withdrawal/conversion and tool usage are separate.

Use the Stars price calculator for a stated buyer quote and gross reward reference. Do not subtract a universal 30%, 35% or 38% from every dollar price. The full Stars guide explains purchase cost, reward conditions and refunds.

Telegram offers recurring APIs, but your commerce tool must implement them. GramBase uses one-time invoices; a member renews by buying again. That is distinct from Telegram’s native paid-channel subscription feature.

Provider payments for physical goods/services

Telegram’s provider Payments API supports a separate physical-goods/services route using external payment providers. Availability and processing rates depend on the provider, region and account. Telegram does not turn every bot into a merchant-of-record or fulfillment service.

If you build this flow, you still need order validation, shipping/fulfillment where relevant, support and disputes. Do not use a Bot API plus Stripe example to suggest card checkout is permitted for in-app digital subscriptions.

GramBase currently has Digital Goods and Paid Community product types, not a separate physical-goods/service product or conventional Stripe/PayPal checkout. Use suitable tooling if those capabilities are essential.

Membership tools: separate fees from custody

A membership tool can integrate a processor account, a platform balance or a wallet route. The label “membership bot” does not tell you who holds funds.

For example, InviteMember’s current pricing uses sales-volume plans. Its integration/provider and transaction terms must be checked separately; a universal $49 + 10% fee or custodial label is inaccurate. Read InviteMember alternatives and payment-bot comparisons.

Custody by a tool, custody by a processor, Telegram Stars balances and a seller-controlled wallet are different dependencies. The custody explainer gives the questions to ask without claiming a service outage automatically destroys funds.

GramBase’s supported workflows and costs

For in-app digital sales, configure Stars in Pricing & Payment. GramBase confirms Telegram’s payment event, records the order and runs the selected file/code/access delivery. For paid communities, test the private invite, renewal and expiry. The current payment documentation and subscriptions explain those flows.

For a separately permitted supported crypto flow, funds go to the configured seller-controlled address and verification waits for the required confirmations. The tool does not hold the private key. This does not create universal availability or eliminate asset, wallet and service risk.

GramBase offers free credits to start. Order processing consumes credits at 2.5% of the internal USD valuation, bounded at 5-2,000 credits per order, with other usage separately billable. The $20 equivalent upper bound applies per order, not per month. Current pricing owns the details.

For an illustrative order-processing calculation, 50 orders each valued at $20 consume $0.50-equivalent each, or $25 total before other usage. This is tool-billing arithmetic, not a comparison of total Stars/card/crypto net revenue.

Set up the first digital purchase

1. Create/control a bot with @BotFather, secure the owner account and keep its token private.
2. Connect the bot in GramBase.
3. Create a Digital Goods or Paid Community product and set its whole-number Stars amount.
4. Configure delivery or group access with the necessary permissions.
5. Open the actual product link with a controlled buyer account and test the full flow.
6. Confirm the order is paid once and the intended buyer receives the correct item or usable invite.

Test a failed/incomplete payment and an unsuccessful delivery as separate branches. A Stars payment cannot use the crypto force-confirm path. For eligible failed delivery, inspect the order record and retry without charging again.

Explain terms, payment support and refunds before taking orders. For membership, explain that GramBase renewal requires another purchase and periodic removal is best-effort.

Frequently asked questions

Can I use crypto instead of Stars for digital goods in my bot?

No. Telegram requires Stars for that in-app digital purchase, regardless of an external website or the buyer’s wallet readiness.

Are Telegram payments risk-free?

No. The risks differ by method: settlement restrictions, account review, wrong transfers, compromised credentials, disputes and failed fulfillment. Choose based on actual controls and obligations.

Is there one Telegram payment fee?

No. Distinguish buyer acquisition cost, merchant reward or processor charges, payout/conversion costs and the commerce tool’s usage. Compare the applicable amounts for the same offer.

Can one receipt prove everything worked?

No. Payment confirmation, delivery and access are separate. Keep order identifiers and inspect each state when a buyer reports a problem.

Create one tested Stars offer, or follow the shop-bot guide when you need a browsable catalog. Keep the payment decision grounded in the permitted sales context.

Questions? DM @Kai, founder of GramBase.