Payment Request

To initiate a payment, you should send the following request:

POST /acquiring/{paymentSystem}/pay

where {paymentSystem} can be applepay, googlepay, or samsungpay.

Request Parameters

Some optional parameters may need to be included, depending on your specific configuration. To obtain a list of mandatory parameters for your account, please contact technical support.

The system verifies the validity and correctness of the control signature in the incoming request. If the request is incorrect, the system will respond with HTTP Status 400. In the case of a validation error, the response will be HTTP Status 401.

If the request parameter value is set to check or get-status, the response will return the current transaction status. If the request parameter value is set to pay, is empty, or has any other value, the response will include a payment link.

Example of a Payment Request

POST
{{url_system}}/acquiring/{paymentSystem}/pay

HEADERS
Content-Type: application/x-www-form-urlencoded

BODY

{
  "orderid": "123456789",
  "goodphone": "1001",
  "ctn": "79012345678",
  "smstext": "1001 123456789 300.00",
  "dt": "20240701123301",
  "control": "36a02d89974fd0efa9d7bc8036d8983c",
  "merchant_site": "https://123abc.org"
}

Where the control value is generated using SecretKey = Qwerty123

Signature generation string:
1234567891001790123456781001 123456789 300.0020240701123301Qwerty123

The system responds in XML format, with UTF-8 encoding:
Content-Type: application/xml

Successful Response Example

<response>
    <result>OK</result>
    <txnid>20004410</txnid>
    <url>https://{{url_system}}/user/url/Z2Rlc1A2aU85OVQ0N3NtajdIK2VqLzdQMGtONEp0MXpzQ1czUHh0h4Nm9YaHQ3ZVBIQjNCSHJHNjNHpMTQ</url>
</response> 

Unsuccessful Response Example

<response>
    <errorCode>1</errorCode>
    <txnid>20004410</txnid>
    <description>Something went wrong, please try again or contact support</description>
    <paymentStatus>PAY_FAIL</paymentStatus>
</response> 

In the event of a repeated request with request=pay or if the request parameter is absent, the system will generate the following response:

<response>
    <errorCode>9712</errorCode>
    <description>Operation 123456789 already exists</description>
    <paymentStatus>DUPLICATE TRANSACTION</paymentStatus>
</response>

A List of Main Possible Errors and Their Descriptions

Parameters Description

• Result=OK: Indicates successful transaction initialization. If initialization fails, an errorCode will be provided.
• txnid: A unique request identifier within the system (required for Result=OK).
• url: The URL of the payment form to which the user will be redirected (required for Result=OK).

After the user follows the redirect URL and confirms the payment, the system sends a callback request to the partner containing the transaction status. The user will be redirected to one of the URLs provided by the partner in the initial request: either url_success or url_fail, depending on the payment result.

Callback Example

POST {{partner_url_for_notification}}?
id=20476210
&phone=79012345678
&result=1
&cmd=status
&control=15727abca9b3b1eccf69672aa708f04b

Callback Parameters

Callback Response

In response to an HTTP request, the partner should provide a response in XML format with UTF-8 encoding. The Content-Type can be set to either text/plain or application/xml.

<response>
         <result>0</result>
         <description>success</description>
</response> 

Callback Response Parameters