telegram api constructor · layer 229 · #405fef0d

inputMediaInvoice

Generated invoice of a bot payment

definition

inputMediaInvoice#405fef0d flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:flags.3?string provider_data:DataJSON start_param:flags.1?string extended_media:flags.2?InputMedia = InputMedia;

parameters

nametypedescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
invoiceInvoiceThe actual invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerflags.3?stringPayments provider token, obtained via Botfather
provider_dataDataJSONJSON-encoded data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
start_paramflags.1?stringUnique bot deep links start parameter. If present, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter. If absent, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice.
extended_mediaflags.2?InputMediaDeprecated

type

InputMedia · 19 other constructors

history

present in layers 65–229 · constructor id changed 4×

idlayers
#9215368565–72
#f4e096c373–126
#d9799874127–145
#8eb5a6d5146–180
#405fef0d181–229