Daniil Gentili
e4a326e552
* refactor * Apply fixes from StyleCI * Implement https and http transport, add support for new req_pq_multi, send pending acks and objects in containers along with the next method call, remove dependency on the socket extension. * Apply fixes from StyleCI * Make types with empty constructors optional, fix phar archives (fixes #217) * Apply fixes from StyleCI * Update to layer 75 * Update github pages gemfile.lock
1.7 KiB
1.7 KiB
| title | description |
|---|---|
| payments.validateRequestedInfo | payments.validateRequestedInfo parameters, return type and example |
Method: payments.validateRequestedInfo
Parameters:
| Name | Type | Required |
|---|---|---|
| save | Bool | Optional |
| msg_id | int | Yes |
| info | PaymentRequestedInfo | Yes |
Return type: payments_ValidatedRequestedInfo
Can bots use this method: NO
Errors this method can return:
| Error | Description |
|---|---|
| MESSAGE_ID_INVALID | The provided message id is invalid |
Example:
$MadelineProto = new \danog\MadelineProto\API();
$MadelineProto->session = 'mySession.madeline';
if (isset($number)) { // Login as a user
$MadelineProto->phone_login($number);
$code = readline('Enter the code you received: '); // Or do this in two separate steps in an HTTP API
$MadelineProto->complete_phone_login($code);
}
$payments_ValidatedRequestedInfo = $MadelineProto->payments->validateRequestedInfo(['save' => Bool, 'msg_id' => int, 'info' => PaymentRequestedInfo, ]);
Or, if you're using the PWRTelegram HTTP API:
As a user:
POST/GET to https://api.pwrtelegram.xyz/userTOKEN/payments.validateRequestedInfo
Parameters:
save - Json encoded Bool
msg_id - Json encoded int
info - Json encoded PaymentRequestedInfo
Or, if you're into Lua:
payments_ValidatedRequestedInfo = payments.validateRequestedInfo({save=Bool, msg_id=int, info=PaymentRequestedInfo, })