Payment Confirmation Request
Available only when two-stage payments are enabled
To confirm a payment, send a POST request to the following endpoint:
POST {url_system}/acquiring/{Service_ID}/confirm
Where {Service_ID}
is the Partner's ID within the system.
The system will check the incoming request for validity and the correctness of the control signature. If the incoming request is incorrect, the system will respond with:
- HTTP Status 400: for malformed requests
- HTTP Status 401: for validation errors
- HTTP Status 404: if the operation is not found
Request Parameters
Parameter | Required | Type | Description | Example |
---|---|---|---|---|
orderid | Yes | String | Unique transaction identifier within the Partner's system | 123456789 |
dt | Yes | String | Request date and time in yyyyMMddHHmmss format | 2024070123301 |
control | Yes | String | Control signature. MD5-hash generated using the formula: orderid + dt + SecretKey , where + denotes concatenation. | 89f0a1e56ac9b3ba2778a8f445e453f0 |
The system responds in XML format with UTF-8 encoding (Content-Type: application/xml).
Example of a Response
<response>
<paymentStatus>PAY_OK</paymentStatus>
<paymentStatusDesc>CONFIRMED</paymentStatusDesc>
<txnId>100001900441</txnId>
</response>
Response Parameters
Parameter | Required | Type | Description |
---|---|---|---|
paymentStatus | Yes | String | Possible values: - INIT_FAIL : Payment initialization failed- PAY_OK : Successful payment- PAY_FAIL : Failed payment- PROCESSING : Payment is processing- REF_OK : Successful refund- ORDER NOT FOUND : Payment with the specified order ID is not found |
paymentStatusDesc | Yes | String | Description of the payment status |
txnid | Yes | String | Unique transaction ID within the system |
description | Yes | String | Detailed error description |
Updated about 1 month ago