Quick answer: Telegram supports Stars payments, subscriptions, paid media and gifts. Implementing payments in a client differs from selling through a bot.
api_idandapi_hashare not merchant accounts and do not replace Bot Tokens, order validation or eligibility.
First decide whether you are building a client's purchasing experience or selling your own product. Those goals use different interfaces and responsibilities.
Select a commercial workflow
| Goal | Integration | Additional checks |
|---|---|---|
| Sell digital goods through a bot | Bot Stars payments | Invoices, successful payments, delivery and refunds |
| Show payments in a client | Client payment interfaces | Confirmation, forms and official requirements |
| Paid channel access or subscriptions | Applicable invitation or subscription features | Periods, renewals, cancellation and access |
| Paid photos or videos | Paid-media interfaces | Purchase state, content access and publishing rights |
| Display or manage gifts | Gift interfaces | Supported actions, costs and eligibility |
Digital goods and services sold inside Telegram bots and Mini Apps must follow the official Stars rules. Application credentials do not bypass those requirements.
Define the complete order lifecycle
Separate order creation, pending payment, a verified successful-payment event, fulfillment, refund and closure. A customer's “paid” message or screenshot is not sufficient evidence for automatic delivery.
Validate order ownership, amount, currency and payment identity on the server. Duplicate updates must not fulfill an order twice. Reconcile uncertain outcomes before issuing another invoice that could charge the customer again.
This is an order-design recommendation, not a payment platform supplied by GetTGAPI. Consult the Bot payments reference for methods and events.
Model subscriptions and purchases separately
Subscriptions grant eligibility over time and require renewal, cancellation and expiry handling. Paid media focuses on the purchase and access state of specific content. A single “has paid” flag cannot safely represent both.
Display the cost and effect of gift-related or other paid actions before confirmation. Avoid hiding spending actions inside automatic synchronization, and do not assume every account can perform every documented operation.
Keep payment and settlement figures distinct
A customer's cost to acquire Stars, a developer reward and an eventual withdrawal amount are different figures. Channels, eligibility and rules can change. A Stars amount should not be advertised as permanently equivalent to a fixed net USDT income.
Show the customer's charge, what will be delivered and the support route separately. Consult current official settlement information rather than promising fixed conversion, zero fees or stable income.
Prepare the right credentials
Standard bot payments start with a Bot Token and payment workflow configuration. Application credentials are needed when the chosen client or integration explicitly requires them.
Follow the application guide for api_id and api_hash. For portal ERROR issues, contact GetTGAPI through gettgapi.com/en/help#contact; use an access code at the application page.
GetTGAPI supplies application assistance, not payment acquiring, currency conversion or custody services.