Message is a service message about a successful payment.
Signature of the post author for messages in channels
Conversation the message belongs to
The domain name of the website on which the user has logged in.
Three-letter ISO 4217 currency code
Date the message was sent in Unix time
Date the message was last edited in Unix time
For forwarded messages, date the original message was sent in Unix time
For forwarded messages, sender of the original message
For messages forwarded from channels, information about the original channel
For messages forwarded from channels, identifier of the original message in the channel
Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
For messages forwarded from channels, signature of the post author if present
Raw user object represent the sender, empty for messages sent to channels
Bot specified invoice payload
The unique identifier of a media message group this message belongs to
Unique message identifier inside this chat
Order info provided by the user
Telegram Passport data
Provider payment identifier
Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
For replies, the original message. Note that the Message object in this field will not contain furth
Identifier of the shipping option chosen by the user
Successful payment information object.
Telegram payment identifier
Total price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
Bot through which the message was sent
Generated using TypeDoc