OpenSource/telegram-crawler
OpenSource/telegram-crawler
1
0
Fork 0
mirror of https://github.com/MarshalX/telegram-crawler.git synced 2024-12-29 15:59:13 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update content of files

Browse source
This commit is contained in:
GitHub Action 2022-10-27 15:10:44 +00:00
parent 0313849989
commit 510e9f9687
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
data/web/corefork.telegram.org/api/bots/webapps.html
View file

@ -68,7 +68,7 @@
<li><code>status</code> - One of the following values (string):<ul> <li><code>status</code> - One of the following values (string):<ul>
<li><code>cancelled</code> – The user closed the invoice popup without paying, before the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a>.</li> <li><code>cancelled</code> – The user closed the invoice popup without paying, before the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a>.</li>
<li><code>pending</code> – The payment is still processing: the bot will receive a further service message about a successful or failed payment. <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> was successfully invoked, the user completed all additional verification forms returned by the method, the invoice popup was closed but the client hasn't received a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message yet.</li> <li><code>pending</code> – The payment is still processing: the bot will receive a further service message about a successful or failed payment. <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> was successfully invoked, the user completed all additional verification forms returned by the method, the invoice popup was closed but the client hasn't received a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message yet.</li>
<li><code>failed</code> – The user tried to pay, but the payment failed: the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> returned an RPC error (directly or via a deferred <a href="/constructor/updateServiceNotification">updateServiceNotification</a>) and the popup was closed.</li> <li><code>failed</code> – The user tried to pay, but the payment failed: the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> returned an RPC error (via an <a href="/constructor/updateServiceNotification">updateServiceNotification</a>) and the popup was closed.</li>
<li><code>paid</code> – The invoice was paid successfully: the client completed the <a href="/api/payments">payment flow »</a>, the invoice popup was closed and a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message was received by the client.</li> <li><code>paid</code> – The invoice was paid successfully: the client completed the <a href="/api/payments">payment flow »</a>, the invoice popup was closed and a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message was received by the client.</li>
</ul> </ul>
</li> </li>