POST /g2g/payment returned pg_status = ok and pg_3ds = 1, after the client's browser has sent MD and PaRes to your TermUrl.pg_status | Meaning | Next step |
|---|---|---|
ok | The payment is authorized. | One-step payment: nothing else is needed. Two-step payment (pg_auto_clearing = 0): capture the amount with clearing or release it with cancel. |
pending | The payment system has not returned the result yet. | Request the status with status_v2 until it is final. |
error | The request is rejected or the payment is declined. | See «Errors» below. |
200; the error is returned in pg_error_code and pg_error_description.pg_error_code | When | What to do |
|---|---|---|
9403 | A parameter is missing or has an invalid value, or a payment with this pg_payment_id does not exist. | Fix the request. |
1100 | The signature is missing or invalid. | Check the signature: see Sync API Overview. |
1101 | pg_merchant_id is not found. The response is not signed. | Check the merchant ID. |
1202 | The payment belongs to another merchant. | Check pg_payment_id and pg_merchant_id. |
110691 | The payment is not waiting for 3DS completion: the method has already been called for it, or the payment was made without 3DS. | Do not repeat the call; get the payment status with status_v2. |
10004 | The 3DS result is not available: the method was called before the client passed the 3DS page. The payment fails. | Call the method only after the client's browser has returned to TermUrl; for this order create a new payment. |
9999 | Internal error, for example a request for this payment is already being processed. | Do not repeat the call at once: wait for the response to the first request or get the payment status with status_v2. |
| Other codes | The payment is declined by the issuer or the payment system. pg_payment_id is returned. | See Error codes. |
pg_sig is calculated with the secret key test_secret_key.