payments.sendPaymentForm
payments.sendPaymentForm
Section titled “payments.sendPaymentForm”No description provided by the pinned schema.
Signature
Section titled “Signature”payments.sendPaymentForm#2d03522f flags:# form_id:long invoice:InputInvoice requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;Result type
Section titled “Result type”payments.PaymentResult
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| form_id | long | — | — | No description provided by the pinned schema. |
| invoice | InputInvoice | — | — | No description provided by the pinned schema. |
| requested_info_id | flags.0?string | flags.0 | — | No description provided by the pinned schema. |
| shipping_option_id | flags.1?string | flags.1 | — | No description provided by the pinned schema. |
| credentials | InputPaymentCredentials | — | — | No description provided by the pinned schema. |
| tip_amount | flags.2?long | flags.2 | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| requested_info_id | 0 | Controlled by flags; present when this bit is set. |
| shipping_option_id | 1 | Controlled by flags; present when this bit is set. |
| tip_amount | 2 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import PaymentsSendPaymentFormPublic access: miniproto.raw.functions.PaymentsSendPaymentForm.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import PaymentsSendPaymentForm
# Naming the raw request class is local only; it performs no I/O or network request.request_type = PaymentsSendPaymentFormResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | BUSINESS_CONNECTION_NOT_ALLOWED | This method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we’re a user, and users cannot invoke methods over a business connection; (2) we’re a bot, but business mode was disabled in @botfather or (3); we’re a bot, but this method cannot be invoked over a business connection. |
| 400 | FORM_UNSUPPORTED | Please update your client. |
| 400 | INVOICE_INVALID | The specified invoice is invalid. |
| 400 | MESSAGE_ID_INVALID | The provided message id is invalid. |
| 400 | PAYMENT_CREDENTIALS_INVALID | The specified payment credentials are invalid. |
| 400 | PEER_ID_INVALID | The provided peer id is invalid. |
| 400 | TMP_PASSWORD_INVALID | The passed tmp_password is invalid. |
Accepted types
Section titled “Accepted types”InputInvoice, InputPaymentCredentials
Known selected constructors: inputInvoiceBusinessBotTransferStars, inputInvoiceChatInviteSubscription, inputInvoiceMessage, inputInvoicePremiumAuthCode, inputInvoicePremiumGiftCode, inputInvoicePremiumGiftStars, inputInvoiceSlug, inputInvoiceStarGift, inputInvoiceStarGiftAuctionBid, inputInvoiceStarGiftDropOriginalDetails, inputInvoiceStarGiftPrepaidUpgrade, inputInvoiceStarGiftResale, inputInvoiceStarGiftTransfer, inputInvoiceStarGiftUpgrade, inputInvoiceStars, inputPaymentCredentials, inputPaymentCredentialsApplePay, inputPaymentCredentialsGooglePay, inputPaymentCredentialsSaved
Returned types
Section titled “Returned types”payments.PaymentResult
Known selected constructors: payments.paymentResult, payments.paymentVerificationNeeded
Related methods
Section titled “Related methods”payments.getPaymentForm, payments.sendStarsForm, payments.validateRequestedInfo
Availability evidence
Section titled “Availability evidence”- unauthenticated allowed
- user only
Provenance
Section titled “Provenance”- layer: 228
- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery