inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-payments.paymentForm#a0058751 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long title:string description:string photo:flags.5?WebDocument invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON additional_methods:flags.6?Vector<PaymentFormMethod> saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?Vector<PaymentSavedCredentials> users:Vector<User> = payments.PaymentForm;Typically, payment takes place by opening the url in the specified payment form, which leads to a payment form on the website of the payment gateway.
-Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing data and title JSON fields.
The user can choose to use either the main payment platform, using the url of the payments.paymentForm, or any of the additional payment platforms, using the url of the chosen paymentFormMethod.
+Payment takes place by opening the url of the chosen payment platform in the specified payment form, which leads to a payment form on the website of the payment gateway.
+Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing credentials and title JSON fields.
The title is used by the client app to represent the payment credentials (typically a censored version of credit card information).
-The data is used to generate an inputPaymentCredentials constructor.
+The credentials are used to generate an inputPaymentCredentials constructor.
Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.
Telegram does not have access to your card information. Credit card details will be handled only by the payment system.
Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form.
This is only possible on accounts with 2FA enabled.
The bot then replies to the received precheckout query, finally the user proceeds to checkout.
-Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify his identity by opening the provided url and following instructions.
+
Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify their identity by opening the provided url and following instructions.
Once the user finishes working with the webpage, the client can proceed to checkout.
Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.