Telegram Stars API for B2B: Sell Stars & Premium

If your product already has customers, a checkout, or a Telegram audience, you do not need to build a separate fulfilment operation to sell Telegram digital products. The MyStars Fulfilment API lets your backend create and track orders for Telegram Stars and Telegram Premium delivered to a Telegram @username.

That makes it a practical fit for resellers, Telegram bots and Mini Apps, creator platforms, gifting services, loyalty programs, agencies, marketplaces, and products that want to add a Telegram purchase without sending each customer through a manual support flow.

Who should use a Telegram Stars API?

Use a Telegram Stars API when Stars or Premium are part of the product you sell — not a one-off manual purchase for your own team.

Typical B2B implementations include:

• Reseller storefronts that sell Stars packs or Premium durations alongside other digital goods;
• Telegram bots and Mini Apps that collect a username, show a current quote, and send the order to a backend;
• Creator and community platforms that help an audience top up before a paid post, bot action, or premium experience;
• Gift and loyalty products that turn a campaign reward into Telegram Stars or Premium for a named recipient;
• Agencies and managed services that need a repeatable fulfilment flow instead of manually processing each client request;
• Marketplaces that need an auditable order record and an event when delivery is complete.

The API is a fulfilment layer, not a front-end widget. Your product owns the customer experience, its checkout and commercial rules. Your server uses MyStars to quote, validate, create, pay, and reconcile the Telegram fulfilment order.

What can you sell through the MyStars API?

The current catalog supports two product types:

• Telegram Stars — an order uses a Stars quantity;
• Telegram Premium — an order uses a Premium duration in months.

Stars and Premium solve different buyer jobs, so present them separately in your UI. Stars are a spendable Telegram balance for creators, channels, bots, and digital goods. Premium is a subscription gift for a Telegram account. If your customer is comparing Premium plans rather than integrating an API, point them to the Telegram Premium checkout.

Do not hardcode pack sizes, plan durations, currencies, or prices in a client app. The MyStars API documentation exposes live product, currency, and pricing data so your catalog follows the current API rules.

How to sell Telegram Stars via API: the B2B fulfilment flow

A reliable integration has a short but deliberate sequence. The order is created on your backend; the customer should never see an API key or handle on-chain payment instructions that belong to your service.

1. Load the current catalog and payment currencies. Read the available products and currencies when your integration starts and refresh them on a sensible schedule. This prevents an old app build from offering an unavailable option.
2. Request a live quote. Ask the pricing endpoint for the chosen product, quantity or duration, and payment currency. Use the returned amount as the amount to settle; do not build a price from cached rate assumptions.
3. Check the recipient before charging or creating the order. Send the recipient’s Telegram @username and the chosen product to the recipient-check endpoint. A Stars recipient check and a Premium eligibility check are not interchangeable.
4. Create one idempotent order. Submit the selected product, recipient, payment currency, a callback URL when you use webhooks, and a stable Idempotency-Key generated from your own internal order ID.
5. Settle exactly the returned payment instruction. The order response contains the destination address, amount, memo, chain, and expiry. Your payment service must use those values exactly, rather than a wallet address or memo stored in application configuration.
6. Reconcile the terminal delivery status. Poll the order-status endpoint as a fallback, or receive the terminal status through your webhook. Mark your own customer order complete only after your reconciliation rules are satisfied.

This sequence is what separates a B2B Telegram Stars API integration from a simple purchase link: every step can be stored, retried safely, observed, and supported by your product team.

The data your backend should keep

Your database is the source of truth for the customer-facing order. Store enough information to explain an order to support, retry a safe operation, and reconcile a blockchain payment without exposing secrets.

At minimum, keep:

• your internal order ID and the MyStars order ID;
• the idempotency key used to create that order;
• product type, Stars quantity or Premium duration, and recipient username;
• quoted currency, amount, chain, expiry, and payment memo;
• the on-chain transaction hash after settlement;
• your payment state, MyStars order state, webhook payload or polling timestamp, and final fulfilment outcome.

An Idempotency-Key matters because real systems retry. A network timeout after POST /v1/orders is not proof that nothing happened. Retrying with the same stable key lets your backend recover without creating a second fulfilment order for the same customer purchase.

Webhooks, polling, and the order lifecycle

Your customer may pay your product first, while your service settles the MyStars instruction afterwards. That creates three operational states that should not be confused:

1. the customer paid your product;
2. your service sent the on-chain payment for the MyStars order;
3. MyStars delivered Stars or Premium to the Telegram recipient.

When an order is created, it can be returned as awaiting_payment with a payment block and expiry. Once settlement and fulfilment progress, your system needs a dependable way to receive the terminal result.

Use a webhook callback for normal delivery updates and retain status polling as a recovery path. Verify that incoming webhook requests are handled by your backend, correlate them to the MyStars order ID, and make webhook processing idempotent too. A duplicate callback must not grant a duplicate reward, issue a second receipt, or trigger a second refund workflow.

Payment settlement: GRAM (TON) and USDT on TON

MyStars API orders can be settled in GRAM (TON) or USDT (TON). These are backend payment operations, not fields to copy into a client-side checkout blindly.

For each order, read the returned currency, chain, address, amount, memo, and expiry from the API response. Do not reuse a previous order’s payment details. A payment with the wrong amount, comment, network, or expired instruction can fail reconciliation.

Keep wallet signing and API calls on the server side. Never ship X-Api-Key, a wallet seed, or automated settlement credentials in a browser bundle, Telegram Mini App, public repository, or client log.

No buyer KYC: the precise B2B meaning

“No buyer KYC” is a search term, but it needs precise language. In this flow, the MyStars fulfilment checkout does not require the buyer to upload identity documents. That can reduce friction in a product experience.

Launch checklist for a Telegram Stars reseller API integration

Before making the feature visible to customers, verify the following:

• API key is stored only in server-side secret management and can be rotated;
• product and currency choices come from the live API rather than hardcoded values;
• a recipient check runs before order creation and before your final customer charge;
• every order has a stable internal ID and idempotency key;
• payment uses the exact address, amount, memo, chain, and expiry returned for that order;
• USDT is labelled TON only everywhere it appears;
• webhook handling verifies, correlates, logs, and safely deduplicates events;
• polling covers a missed or delayed webhook;
• your support team can find an order by your ID, MyStars order ID, recipient, and transaction hash;
• refund, fraud, compliance, and customer communication rules are defined before launch.

For request formats, response fields, SDK options, and the live API contract, use the MyStars API documentation as the implementation source of truth.

FAQ

Can I sell Telegram Stars through my own website, bot, or Mini App?

Yes. Your product can collect the customer’s selection and recipient username, while your backend uses the MyStars Fulfilment API to create and track the Stars order. Keep the API key and settlement operations server-side.

Can I sell Telegram Premium through the same API?

Yes. The API supports Telegram Premium fulfilment as a separate product type with Premium duration in months. Check recipient eligibility before an order is created, because Premium gift constraints can differ from Stars recipient checks.

Does the API provide a fixed price list for Stars and Premium?

Use the pricing endpoint for a live quote instead of relying on a fixed list. The API response is the appropriate source for the current amount and settlement currency for the selected order.

How do I avoid duplicate Telegram Stars orders?

Create every order with a stable Idempotency-Key tied to your own internal order ID. If a server worker retries because of a timeout, reuse the same key rather than generating a new one.

Which USDT network is supported?

USDT on TON / The Open Network only. Do not send or present USDT on another network as a compatible settlement method.

Does no buyer KYC mean my business has no compliance obligations?

No. It describes the MyStars buyer checkout experience, not your company’s legal, financial, fraud, tax, sanctions, consumer-protection, or refund responsibilities.

Start your B2B Telegram fulfilment integration

If your product needs to sell Telegram Stars or Premium at scale, build around a verifiable order lifecycle: live quote, recipient check, idempotent order creation, exact on-chain settlement, and a final webhook or status reconciliation.

Open the MyStars API documentation and start the integration →

Sources and evidence

• MyStars FaaS — Fulfilment API documentation: product catalog, live pricing, recipient checks, order creation, API authentication, settlement instructions, status tracking, and webhooks.