mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2025-03-14 04:51:42 +01:00
Update content of files
This commit is contained in:
parent
80e9df038b
commit
577faca3e1
2 changed files with 4 additions and 3 deletions
|
@ -156,7 +156,7 @@ See the <a href="/api/stars#buying-stars">stars »</a> documentation for more in
|
|||
The payment form also contains info about previously saved payment credentials and order information (name, phone number, email, shipping address & so on).</p>
|
||||
<p>The full <a href="/constructor/invoice">invoice</a> contains info about the information required for the order, the price and the currency, and whether this is a <code>test</code> order.
|
||||
The <code>recurring</code> flag will be set for recurring payments, and <code>recurring_terms_url</code> will link to the terms of service of the recurring payment: the user must read and accept them before continuing. </p>
|
||||
<p>A <a href="/constructor/payments.paymentFormStars">payments.paymentFormStars</a> will be returned if the payment is to be made using <a href="/api/stars">Telegram Stars, see here »</a> for more info (note that this constructor is used for payments to bots and peers, it will <strong>not</strong> be returned when <em>topping up</em> the star balance using <a href="/constructor/inputInvoiceStars">inputInvoiceStars</a>). </p>
|
||||
<p>A <a href="/constructor/payments.paymentFormStars">payments.paymentFormStars</a> will be returned if the payment is to be made using <a href="/api/stars">Telegram Stars, see here »</a> for more info (note that this constructor is used for payments in Telegram Stars to bots and peers, it will <strong>not</strong> be returned when <em>topping up</em> the Telegram Star balance of the current account using <a href="/constructor/inputInvoiceStars">inputInvoiceStars</a>). </p>
|
||||
<h4><a class="anchor" href="#23-verifying-information" id="23-verifying-information" name="23-verifying-information"><i class="anchor-icon"></i></a>2.3 Verifying information</h4>
|
||||
<pre><code><a href='/constructor/invoice'>invoice</a>#5db95a15 flags:<a href='/type/%23'>#</a> test:flags.0?<a href='/constructor/true'>true</a> name_requested:flags.1?<a href='/constructor/true'>true</a> phone_requested:flags.2?<a href='/constructor/true'>true</a> email_requested:flags.3?<a href='/constructor/true'>true</a> shipping_address_requested:flags.4?<a href='/constructor/true'>true</a> flexible:flags.5?<a href='/constructor/true'>true</a> phone_to_provider:flags.6?<a href='/constructor/true'>true</a> email_to_provider:flags.7?<a href='/constructor/true'>true</a> recurring:flags.9?<a href='/constructor/true'>true</a> currency:<a href='/type/string'>string</a> prices:<a href='/type/Vector%20t'>Vector</a><<a href='/type/LabeledPrice'>LabeledPrice</a>> max_tip_amount:flags.8?<a href='/type/long'>long</a> suggested_tip_amounts:flags.8?<a href='/type/Vector%20t'>Vector</a><<a href='/type/long'>long</a>> terms_url:flags.10?<a href='/type/string'>string</a> = <a href='/type/Invoice'>Invoice</a>;
|
||||
|
||||
|
@ -365,7 +365,7 @@ Further recurring payments will automatically send <a href="/constructor/message
|
|||
---functions---
|
||||
|
||||
<a href='/method/payments.refundStarsCharge'>payments.refundStarsCharge</a>#25ae8f4a user_id:<a href='/type/InputUser'>InputUser</a> charge_id:<a href='/type/string'>string</a> = <a href='/type/Updates'>Updates</a>;</code></pre>
|
||||
<p>Payments made using <a href="/api/stars">Telegram Stars »</a> may be refunded <em>by the user/bot that received them</em> by invoking <a href="/method/payments.refundStarsCharge">payments.refundStarsCharge</a>, passing to <code>user_id</code> the ID of the user that did the payment, and to <code>charge_id</code> the <code>provider_charge_id</code> from the <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a> of the incoming payment.</p></div>
|
||||
<p>Payments made using <a href="/api/stars">Telegram Stars »</a> may be refunded <em>by the user/bot that received them</em> by invoking <a href="/method/payments.refundStarsCharge">payments.refundStarsCharge</a>, passing to <code>user_id</code> the ID of the user that did the payment, and to <code>charge_id</code> the <code>provider_charge_id</code> from the <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a> service message action of the incoming payment.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
@ -94,7 +94,8 @@ To return all <a href="/constructor/starsTransaction">star transactions »</a> (
|
|||
|
||||
<a href='/method/payments.sendStarsForm'>payments.sendStarsForm</a>#02bb731d flags:<a href='/type/%23'>#</a> form_id:<a href='/type/long'>long</a> invoice:<a href='/type/InputInvoice'>InputInvoice</a> = <a href='/type/payments.PaymentResult'>payments.PaymentResult</a>;
|
||||
|
||||
<a href='/method/payments.refundStarsCharge'>payments.refundStarsCharge</a>#25ae8f4a user_id:<a href='/type/InputUser'>InputUser</a> charge_id:<a href='/type/string'>string</a> = <a href='/type/Updates'>Updates</a>;</code></pre></div>
|
||||
<a href='/method/payments.refundStarsCharge'>payments.refundStarsCharge</a>#25ae8f4a user_id:<a href='/type/InputUser'>InputUser</a> charge_id:<a href='/type/string'>string</a> = <a href='/type/Updates'>Updates</a>;</code></pre>
|
||||
<p>The full flow to follow to make purchases using Telegram Stars is described along the traditional payment flow in the <a href="/api/payments">payments documentation »</a>.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue