Online Banking, E-Wallet, Virtual Account and QR Payments

Acquiring Interaction Diagram

Acquiring Interaction Diagram Description

1. The user initiates a payment using a payment method available through the Partner's service.
2. The Partner's service sends a payment request to the System using a specific System URL.
3. The System verifies the request by checking the required parameters and the validity of the request signature.
4. The System responds with either a confirmation that the request is correct and accepted or an error message if the request doesn't meet the System's requirements.
5. The System processes the request further and forwards the data to the payment method.
6. The payment method's service continues processing the payment request.
7. The System provides a redirect link, QR code, or operation identifier, which the User must use to confirm the payment.
8. The Partner redirects the User to the provided link or displays the QR code or operation identifier for completing the payment.
9. The User completes the necessary actions to finalize the payment according to the selected payment method.
10. The payment method's service continues processing the payment after the User's confirmation.
11. The payment method informs the System of the payment result.
12. The System sends a callback message with the payment result to the Partner’s service.
13. The Partner communicates the payment result to the User.

Payment Request

To initiate a payment, send the following request:

POST request to: {{url_system}}/alt

(for Uzum Bank (Uzbekistan) and ELQR (Kyrgyzstan) Payment Methods use /inverse)

Where {{url_system}} is:

• Testing environment: https://secure-test.8b.world
• Production environment: https://secure.8b.world

Request Parameters:

The data parameter is formed using the basic (required) parameters for each request to the System.

Additional parameters may be used if the selected payment method requires further payment details. Requirements for using additional parameters are detailed in the List of Available Payment Methods.

Basic Data Parameters Description

Note: > denotes depth for nested parameters.

* If parameters are present - User will be redirected to passed success_url/failure_url. Otherwise User will be redirected to URL specified in Shop settings.

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

Signature Formation Procedure (sign parameter)

The signature is created based on the data parameter (a base64-encoded parameter string) using the hash_hmac function. The "md5" algorithm is used to generate the signature:

hash_hmac('md5', $data, $secret_key)

Where:

• $data – MIME base64-encoded JSON document
• $secret_key – Partner’s Secret key

Request Examples

You can view request examples for this method at this link

API Reference

You can view a Reference API implementation for this method at this link

Payment Callback Message

Whenever a payment is confirmed or there is a change in the status of a payment transaction, the System sends a callback message to the Partner’s system (Webhook). This message is transmitted via an HTTP POST request to the Partner’s system (Callback URL) and includes the following parameters:

It is recommended to verify the callback request signature to ensure data integrity and validity using the following algorithm:

hash_hmac('md5', $_POST['data'], $secret_key) === $_POST['sign']

Where $secret_key is the Partner’s Secret key.

Callback Request Data Parameter Description

In response to a callback message, the Partner’s system is required to return a string containing the value OK.

If the Partner’s system does not return OK in response, the Gateway will send repeat callback requests.

Request Examples

You can view request examples for this method at this link

API Reference

You can view a Reference API implementation for this method at this link

Refund Request

To initiate a refund, make the following request:

POST request to {{url_system}}/alt/refund

Where {{url_system}}:

• For testing environment - https://secure-test.8b.world
• For production environment - https://secure.8b.world

Request Parameters

The following parameters are used to form the data parameter:

* - optional parameter. If amount is not present, the full original transaction amount will be refunded.

Request Example

You can view request examples for this method at this link

API Reference

You can view a Reference API implementation for this method at this link

Transaction Information Request

To receive detailed transaction information, make the following request:

POST request to {{url_system}}/alt/get_orders_data

(for Uzum Bank (Uzbekistan) and ELQR (Kyrgyzstan) Payment Methods use /inverse/get_orders_data)

Where {{url_system}}:

• For testing environment - https://secure.8b.world
• For production environment - https://secure-test.8b.world

Request Parameters

The following parameters are used to form the data parameter:

Request Examples

You can view request examples for this method at this link

API Reference

You can view a Reference API implementation for this method at this link

List of available Banks for Bank Transfer methods

List of available Banks in Argentina

List of available Banks in Brazil