payments.sendStarsForm
payments.sendStarsForm
Section titled “payments.sendStarsForm”No description provided by the pinned schema.
Signature
Section titled “Signature”payments.sendStarsForm#7998c914 form_id:long invoice:InputInvoice = payments.PaymentResult;Result type
Section titled “Result type”payments.PaymentResult
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| form_id | long | — | — | No description provided by the pinned schema. |
| invoice | InputInvoice | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import PaymentsSendStarsFormPublic access: miniproto.raw.functions.PaymentsSendStarsForm.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import PaymentsSendStarsForm
# Naming the raw request class is local only; it performs no I/O or network request.request_type = PaymentsSendStarsFormResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | BALANCE_TOO_LOW | The transaction cannot be completed because the current Telegram Stars balance is too low. |
| 400 | BOT_INVOICE_INVALID | The specified invoice is invalid. |
| 400 | BUSINESS_CONNECTION_INVALID | The connection_id passed to the wrapping invokeWithBusinessConnection call is invalid. |
| 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_EXPIRED | The form was generated more than 10 minutes ago and has expired, please re-generate it using payments.getPaymentForm and pass the new form_id. |
| 400 | FORM_ID_EMPTY | The specified form ID is empty. |
| 400 | FORM_SUBMIT_DUPLICATE | The same payment form was already submitted. . |
| 400 | FORM_UNSUPPORTED | Please update your client. |
| 400 | GIFT_STARS_INVALID | The specified amount of stars is invalid. |
| 400 | MEDIA_ALREADY_PAID | You already paid for the specified media. |
| 400 | MONTH_INVALID | The number of months specified in inputInvoicePremiumGiftStars.months is invalid. |
| 400 | PEER_ID_INVALID | The provided peer id is invalid. |
| 400 | PURPOSE_INVALID | The specified payment purpose is invalid. |
| 400 | STARGIFT_ALREADY_UPGRADED | The specified gift was already upgraded to a collectible gift. |
| 400 | STARGIFT_NOT_FOUND | The specified gift was not found. |
| 400 | STARGIFT_OWNER_INVALID | You cannot transfer or sell a gift owned by another user. |
| 400 | STARGIFT_SLUG_INVALID | The specified gift slug is invalid. |
| 400 | STARGIFT_USAGE_LIMITED | The gift is sold out. |
| 400 | STARGIFT_USER_USAGE_LIMITED | You’ve reached the starGift.limited_per_user limit, you can’t buy any more gifts of this type. |
| 400 | TO_ID_INVALID | The specified to_id of the passed inputInvoiceStarGiftResale or inputInvoiceStarGiftTransfer is invalid. |
| 400 | USER_ID_INVALID | The provided user ID is invalid. |
| 401 | AUTH_KEY_UNREGISTERED | The specified authorization key is not registered in the system (for example, a PFS temporary key has expired). |
| 403 | BOT_ACCESS_FORBIDDEN | The specified method can be used over a business connection for some operations, but the specified query attempted an operation that is not allowed over a business connection. |
| 406 | API_GIFT_RESTRICTED_UPDATE_APP | Please update the app to access the gift API. |
| 406 | PRECHECKOUT_FAILED | Precheckout failed, a detailed and localized description for the error will be emitted via an updateServiceNotification as specified here ». |
| 406 | STARS_FORM_AMOUNT_MISMATCH | The form amount has changed, please fetch the new form using payments.getPaymentForm and restart the process. |
Accepted types
Section titled “Accepted types”InputInvoice
Known selected constructors: inputInvoiceBusinessBotTransferStars, inputInvoiceChatInviteSubscription, inputInvoiceMessage, inputInvoicePremiumAuthCode, inputInvoicePremiumGiftCode, inputInvoicePremiumGiftStars, inputInvoiceSlug, inputInvoiceStarGift, inputInvoiceStarGiftAuctionBid, inputInvoiceStarGiftDropOriginalDetails, inputInvoiceStarGiftPrepaidUpgrade, inputInvoiceStarGiftResale, inputInvoiceStarGiftTransfer, inputInvoiceStarGiftUpgrade, inputInvoiceStars
Returned types
Section titled “Returned types”payments.PaymentResult
Known selected constructors: payments.paymentResult, payments.paymentVerificationNeeded
Related methods
Section titled “Related methods”payments.getPaymentForm, payments.sendPaymentForm, payments.validateRequestedInfo
Availability evidence
Section titled “Availability evidence”- business supported
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