Represents a Telegram Stars transaction ».
starsTransaction#aa00c898 flags:# refund:flags.3?true pending:flags.4?true failed:flags.6?true id:string stars:long date:int peer:StarsTransactionPeer title:flags.0?string description:flags.1?string photo:flags.2?WebDocument transaction_date:flags.5?int transaction_url:flags.5?string = StarsTransaction;
Name | Type | Description |
---|---|---|
flags | # | Flags, see TL conditional fields |
refund | flags.3?true | Whether this transaction is a refund. |
pending | flags.4?true | The transaction is currently pending. |
failed | flags.6?true | This transaction has failed. |
gift | flags.10?true | This transaction was a gift from the user in peer.peer . |
reaction | flags.11?true | This transaction is a paid reaction ». |
id | string | Transaction ID. |
stars | StarsAmount | Amount of Stars (negative for outgoing transactions). |
date | int | Date of the transaction (unixtime). |
peer | StarsTransactionPeer | Source of the incoming transaction, or its recipient for outgoing transactions. |
title | flags.0?string | For transactions with bots, title of the bought product. |
description | flags.1?string | For transactions with bots, description of the bought product. |
photo | flags.2?WebDocument | For transactions with bots, photo of the bought product. |
transaction_date | flags.5?int | If neither pending nor failed are set, the transaction was completed successfully, and this field will contain the point in time (Unix timestamp) when the withdrawal was completed successfully. |
transaction_url | flags.5?string | If neither pending nor failed are set, the transaction was completed successfully, and this field will contain a URL where the withdrawal transaction can be viewed. |
bot_payload | flags.7?bytes | Bot specified invoice payload (i.e. the payload passed to inputMediaInvoice when creating the invoice). |
msg_id | flags.8?int | For paid media transactions », message ID of the paid media posted to peer.peer (can point to a deleted message; either way, extended_media will always contain the bought media). |
extended_media | flags.9?Vector<MessageMedia> | The purchased paid media ». |
subscription_period | flags.12?int | The number of seconds between consecutive Telegram Star debiting for Telegram Star subscriptions ». |
giveaway_post_id | flags.13?int | ID of the message containing the messageMediaGiveaway, for incoming star giveaway prizes. |
stargift | flags.14?StarGift | This transaction indicates a purchase or a sale (conversion back to Stars) of a gift ». |
floodskip_number | flags.15?int | This transaction is payment for paid bot broadcasts. Paid broadcasts are only allowed if the allow_paid_floodskip parameter of messages.sendMessage and other message sending methods is set while trying to broadcast more than 30 messages per second to bot users. The integer value returned by this flag indicates the number of billed API calls. |
starref_commission_permille | flags.16?int | |
starref_peer | flags.17?Peer | |
starref_amount | flags.17?StarsAmount |
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
Generated invoice of a bot payment
You can accept payments from Telegram users via Telegram Bots.
Content creators can accept Stars by publishing paid photos or videos on their channels. Subscribers will be allowed to view such posts only after paying the author to unlock them.
Telegram Stars are virtual items that allow users to purchase digital goods and services from bots and mini apps inside the Telegram ecosystem, send gifts to content creators on the Telegram platform, and more.
Contains info about a giveaway, see here » for more info.
Telegram channel and supergroup administrators may launch giveaways to randomly distribute Telegram Premium subscriptions and other gifts among their followers, in exchange for boosts.
Sends a message to a chat