QIWI Kazakhstan

Interaction diagram

Payment processing by using the QIWI Kazakhstan payment method requires merchant's web service, one of Rocketpay interfaces, and the Rocketpay payment platform, as well as QIWI Kazakhstan service.

Figure: Interaction diagram for purchase by using QIWI Kazakhstan kiosks and e-wallets

Operations support

	Interfaces				Amounts, KZT		Times
	Payment Page	CMS Plug-ins	Gate	Dashboard	minimum	maximum	basic	threshold
Purchases							*	30 days

* Refer to your key account manager at Rocketpay for details.

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.

Processing scenarios

To perform a purchase operation in the QIWI Kazakhstan method, you need to have the customer to pay by using QIWI Kazakhstan kiosk.

Figure: Purchase by using Gate via kiosk or e-wallet

The sections that follow provide detailed information about what you need to perform payments and how you can analyze the information on payments and operations.

General information

In the QIWI Kazakhstan method, when processing a purchase by using Gate, the merchant web service is required to do the following:

1. Process request for checking customer account existence.
2. Send information about customer account existence.
3. Process request for receiving payment identifier on the web service side.
4. Send payment identifier.
5. Get the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.

The sections that follow discuss in more details the request format and the Gate parameters to use in the QIWI Kazakhstan payment method and provide the information on the format of callbacks with purchase results.

Request format

There are several things you must consider when using requests for checking account existence in the QIWI Kazakhstan method:

1. The verify request for checking account existence is sent by using HTTP method POST to the specified web service URL.
2. The request contains the following required parameters:
   • type—operation type on the web service side, value is always verify
   • customer_id—customer identifier on the web service side
   • project_id—the project ID obtained from Rocketpay
   • signature—signature created after you specify all the required parameters

   Figure: Example of a request for checking account existence

   {
      "type":"verify",
      "project_id":111,
      "customer_id":"johndoe@example.com",
      "signature":"lY0LT8AzpR7zGce5qfYGacOuYlHGWqkMcQlqmjlsDDZI2gVcE1qVeWANnkIR7mdOqRXJnL1kO0lUmkQ0YYLWRg=="
   }

3. Response to the verify request must be synchronously sent and contain the following required parameters:
   • code—response code
   • currency—currency in the ISO-4217 alpha-3 format

   Table 1. Allowed response codes

   Code	Description
   0	Successful operation
   400	Signature is invalid
   404	Account does not exist
   500	General error. The reason should be specified in the message parameter

   Figure: Example of the response

   {
      "code":0,
      "currency":"KZT",
      "additional_customer_id": "HFVDW42345"
   }

There are several things you must consider when using requests for payment identifier on the web service side:

1. The check_deposit request for payment identifier is sent by using HTTP method POST to the specified web service URL.
2. The request contains the following required parameters:
   • type—operation type on the web service side, value is always check_deposit
   • customer_id—customer identifier on the web service side
   • project_id—the project ID obtained from Rocketpay
   • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
   • currency—currency in the ISO-4217 alpha-3 format
   • payment_method—payment method name, value is always qiwi-kz;
   • signature—signature created after you specify all the required parameters

   Figure: Example of a request for payment identifier

   {
      "type":"check_deposit",
      "project_id":111,
      "customer_id":"johndoe@example.com",
      "amount":10000,
      "currency":"KZT",
      "payment_method":"qiwi-kz",
      "signature":"lY0LTSAzpR7zGce5qfYGacOuYlHGWqkMcQlqmjlsDDZI2gVcE1qVeWANnkIR7mdOqRXJnL1kO0lUmkQ0YYLWRg=="
   }

3. Response to the check_deposit request must be synchronously sent and contain the following required parameters:
   • code—response code
   • payment_id—payment ID unique within the project

   Table 2. Allowed response codes

   Code	Description
   0	Successful operation
   400	Signature is invalid
   404	Account does not exist
   500	General error. The reason should be specified in the message parameter

   Figure: Example of the response

   {
      "code":0,
      "payment_id":"Asfdsaf3252345"
   }

Callback format

The QIWI Kazakhstan method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks in Gate.

The following is the example of a callback with an information about successful 20.00 KZT purchase made by the user9876 customer in the 238 project.

{
        "project_id": 238,
        "payment": {
            "id": "1554967098",
            "type": "purchase",
            "status": "success",
            "date": "2019-04-11T07:18:20+0000",
            "method": "Qiwi Kz Kiosk",
            "sum": {
                "amount": 2000,
                "currency": "KZT"
            },
            "description": ""
        },
        "account": {
            "number": "user9876"
        },
        "operation": {
            "id": 36425000001206,
            "type": "sale",
            "status": "success",
            "date": "2019-04-11T07:18:20+0000",
            "created_date": "2019-04-11T07:18:19+0000",
            "request_id": "25f3114242a16ab1e010ebab4fe816b9d105ff33b90281",
            "sum_initial": {
                "amount": 2000,
                "currency": "KZT"
            },
            "sum_converted": {
                "amount": 2000,
                "currency": "KZT"
            },
            "provider": {
                "id": 1197,
                "payment_id": "999990000001a1",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "HRcDJN84ghAJL2hPW9yUbVMm7SRPewQJuH+mz4gcipXc8sI
                         dToQunzSUEiy7w5vA3+MVIO8xHSNsQB5qCCm5kXA=="
    }
}

Related topics

The following topics might be useful when implementing payments through Gate:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

General information

In the QIWI Kazakhstan method, when processing a purchase by using Gate, the merchant web service is required to do the following:

1. Process the request to check whether the customer account exists .
2. Respond with the information whether the customer account exists.
3. Process request for payment identifier on the web service side.
4. Respond with the payment identifier.
5. Accept the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.

The sections that follow discuss in more details the request format and the Gate parameters to use in the QIWI Kazakhstan payment method and provide the information on the format of callbacks with purchase results.

Request format

1. The verify request to check for the account existence is sent by using HTTP method POST to the web service URL.
2. The following required parameters must be specified in any request:
   • type—operation type on the web service side, value is always verify
   • customer_id—customer identifier on the web service side
   • project_id—the project ID obtained from Rocketpay
   • signature—signature created after you specify all the required parameters

   Figure: Example of a request to check for the account existence

   {
      "type":"verify",
      "project_id":111,
      "customer_id":"johndoe@example.com",
      "signature":"lY0LT8AzpR7zGce5qfYGacOuYlHG...kIR7mdOqRXJnL1kO0lUmkQ0YYLWRg=="
   }

3. Response to the verify request must be sent synchronously and contain the following required parameters:
   • code—response code
   • currency—currency in the ISO-4217 alpha-3 format

   Table 3. Allowed response codes

   Code	Description
   0	Successful operation
   400	Signature is invalid
   404	Account does not exist
   500	General error. The reason can be specified in an optional message parameter.

   Figure: Example of the response the verify request

   {
      "code":0,
      "currency":"KZT",
      "additional_customer_id": "HFVDW42345"
   }

There are several things you must consider when using requests for payment identifier on the web service side:

1. The check_deposit request for payment identifier in the web service is sent to the web service URL by using HTTP method POST.
2. The request contains the following required parameters:
   • type—operation type on the web service side, value is always check_deposit
   • customer_id—customer identifier assigned by the web service
   • project_id—the project ID obtained from Rocketpay
   • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
   • currency—currency in the ISO-4217 alpha-3 format
   • payment_method—payment method name, value is always qiwi-kz;
   • signature—signature created after you specify all the required parameters

   Figure: Example of a request for payment identifier assigned by the web service

   {
      "type":"check_deposit",
      "project_id":111,
      "customer_id":"johndoe@example.com",
      "amount":10000,
      "currency":"KZT",
      "payment_method":"qiwi-kz",
      "signature":"lY0LTSAzpR7zGce5qfYGacOuYlHGWqkMcQl...Q0YYLWRg=="
   }

3. Response to the check_deposit request must be sent synchronously and contain the following required parameters:
   • code—response code
   • payment_id—payment ID unique within the project

   Table 4. Allowed response codes

   Code	Description
   0	Successful operation
   400	Signature is invalid
   404	Account does not exist
   500	General error. The reason can be specified in an optional message parameter.

   Figure: Example of the response to the check_deposit request

   {
      "code":0,
      "payment_id":"Asfdsaf3252345"
   }

Callback format

The QIWI Kazakhstan method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks in Gate.

The following is the example of a callback with an information about successful 20.00 KZT purchase made in the 238 project.

{
        "project_id": 238,
        "payment": {
            "id": "1554967098",
            "type": "purchase",
            "status": "success",
            "date": "2019-04-11T07:18:20+0000",
            "method": "Qiwi Kz Terminal",
            "sum": {
                "amount": 2000,
                "currency": "KZT"
            },
            "description": ""
        },
        "account": {
            "number": "user9876"
        },
        "operation": {
            "id": 36425000001206,
            "type": "sale",
            "status": "success",
            "date": "2019-04-11T07:18:20+0000",
            "created_date": "2019-04-11T07:18:19+0000",
            "request_id": "25f3114242a16ab1e010ebab4fe816b9d105ff33b90281",
            "sum_initial": {
                "amount": 2000,
                "currency": "KZT"
            },
            "sum_converted": {
                "amount": 2000,
                "currency": "KZT"
            },
            "provider": {
                "id": 1197,
                "payment_id": "999990000001a1",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "HRcDJN84ghAJL2hPW9yUbVMm7SRPewQJuH+mz4gcipXc8sI
                         dToQunzSUEiy7w5vA3+MVIO8xHSNsQB5qCCm5kXA=="
    }
}

Related topics

The following topics might be useful when implementing payments through Gate:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

As with other payment methods Rocketpay offers, when using this method, you have several options to analyze the information about payments and operations.

You can load and analyze all the necessary information in Dashboard (dashboard.rocketpay.kz), for instance you can use the analytic panels in the Analytics section for this purpose.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

• Dashboard allows you to download reports in CSV format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
• Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by means of sending requests to the /operations/get endpoint.

If you have any further questions regarding payment data analysis, contact Rocketpay technical support.