pg_status = need_approve.pg_salt and pg_sig.pg_status | Meaning | Next step |
|---|---|---|
ok | The amount is charged from the mobile balance. | — |
process with pg_error_code | The code is wrong, for example 601 «OTP incorrect». The payment is not failed. | Ask the client for the code again and repeat the request, or send a new code with Resend SMS code. |
process without pg_error_code | The mobile operator has not confirmed the charge yet. | Get the result with Get mobile balance payment status. |
error | The request is rejected or the payment failed. | See «Errors» below. |
200; the error is returned in pg_error_code and pg_error_description.pg_error_code | When | What to do |
|---|---|---|
94031 | A parameter is missing or invalid, or pg_payment_id is not found. | Fix the request. |
9998 | The signature is missing or invalid. | Check the signature: see Merchant API Overview. |
9997 | pg_merchant_id is not found. | Check the merchant ID. |
340 | Charge mobile balance was not called for this payment, or the payment is already failed. | Call Charge mobile balance first, or create a new payment. |
9001 | The payment is already paid. pg_error_description is empty. | Do not repeat the request: get the result with Get mobile balance payment status. |
1000 | Internal error. The payment is not failed. | Repeat the request later. |
| Other codes | The mobile operator declined the payment. | See Error codes. |
pg_sig is calculated with the secret key test_secret_key.