QIWI Push

Overview

QIWI Push is payment method that allows to process payments by using the QIWI e-wallet. Payment processing by using this method supports crediting of customer accounts in the merchant web service via the QIWI Push service. Whereby crediting of a customer account is considered a purchase (operation type sale) within the framework of the payment platform.

General information

Payment method type e-wallet payments
Countries and regions RU
Payment currencies RUB
Currency conversion
Purchases +
Payouts
Stored credentials payments
Full refunds
Partial refunds
Chargebacks
Special considerations
Obtaining access to the payment method and access fee refer to your ECommPay key account manager

Interaction diagram

Payment processing by using the QIWI Push payment method requires the QIWI Push technical facilities, the ECommPay payment platform, as well as merchant's web service.



Operations support

Payment processing by using the QIWI Push payment method supports the crediting of personal customer accounts. The threshold payment processing time is 1 day (the threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the merchant receives the callback with the payment result). A payment is automatically declined, if its waiting time exceeds the threshold time. For individual setting of the threshold time limit, contact ECommPay technical support.

Processing scenarios

In the QIWI Push method a customer account is credited via the QIWI Push service.

Figure: Account crediting



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

Account crediting

General information

In the QIWI Push method, when crediting a customer account the merchant web service is required to do the following:

  1. Process the request for checking customer account existence, which was sent from the ECommPay URL.
  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.



Figure: Account crediting

  1. Customer selects a web service, the personal account which needs to be credited, and then enters the credentials on the QIWI Push side.
  2. A request for checking customer account existence is sent from the QIWI Push side to the specified ECommPay URL.
  3. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  4. The payment platform sends request for checking customer account existence to the web service.
  5. The request is processed on the web service side.
  6. The web service sends response to the request.
  7. The payment platform sends customer account data to the QIWI Push service.
  8. The QIWI Push payment form is displayed to the customer.
  9. The customer uses the QIWI e-wallet to replenish personal account.
  10. The payment is processed on the QIWI Push side.
  11. The customer receives the payment result on the QIWI Push side.
  12. The QIWI Push service sends the payment result notification to the payment platform.
  13. The payment platform sends request to the web service for payment identifier on the web service side.
  14. The request is processed on the web service side.
  15. The web service sends payment identifier to the payment platform.
  16. Operation is registered on the payment platform side.
  17. The payment platform sends the callback to the web service.

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

Request format

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

  1. The verify request for checking account existence is sent by using the POST HTTP method to the specified web service URL.
  2. The request contains the following required parameters:
    • type—operation type on the web service side, value is alwaysverify
    • customer_id—customer identifier on the web service side
    • project_id—the project ID obtained from ECommPay
    • signature—signature created after you specify all the required parameters (for more information about signature generation, see Signature generation and verification)

    Figure: Example of a request for checking account existence

    {
       "type":"verify",
       "project_id":111,
       "customer_id":"customer@example.com",
       "signature":"lY0LT8AzpRqfYGacOuY...lHG7mdOqRXJnL1kO0lUmkQ0YYLWRg=="
    }
  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 errors.message parameter

    Figure: Example of the response

    {
       "code":0,
       "currency":"RUB"
    }

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 ECommPay
    • amount—purchase amount in minor units
    • currency—currency in the ISO-4217 alpha-3 format
    • payment_method—payment method name, value is always terminal/qiwi-ru
    • signature—signature created after you specify all the required parameters (for more information about signature generation, see Signature generation and verification)

    Figure: Example of a request for payment identifier

    {
       "type":"check_deposit",
       "project_id":111,
       "customer_id":"customer8@example.com",
       "amount":10000,
       "currency":"RUB",
       "payment_method":"terminal/qiwi-ru",
       "signature":"lY0LTSAzpR7zGce5qfYG...R7mdOqRXJnL1kO0lUmkQ0YYLWRg=="
    }
  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 errors.message parameter

    Figure: Example of the response

    {
       "code":0,
       "payment_id":"445",
       "description":"test payment"
    }

Callback format

The QIWI Push method uses the standard format for callbacks to deliver account crediting results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 20.00 RUB account crediting made in the 238 project.

Figure: Example of successful account crediting

{
    "project_id": 238,
    "payment": {
        "id": "21538362",
        "type": "purchase",
        "status": "success",
        "date": "2020-04-24T11:53:19+0000",
        "method": "qiwi-ru",
        "sum": {
            "amount": 2000,
            "currency": "RUB"
        },
        "is_new_attempts_available": false,
        "attempts_timeout": 0,
        "description": ""
    },
    "account": {
        "number": "123456"
    },
    "customer_data": {
        "ip_address": "1.2.3.4"
    },
    "fee": {
        "amount": 1,
        "currency": "RUB"
    },
    "merchant_account_id": 6389,
    "operation": {
        "id": 1000000001,
        "type": "sale",
        "status": "success",
        "date": "2020-04-24T11:53:19+0000",
        "created_date": "2020-04-24T11:53:12+0000",
        "request_id": "a5821969a8538aaef75...c1ff3d0d8e9805b-00000002",
        "sum_initial": {
            "amount": 2000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 2000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 6389,
            "payment_id": "471623",
            "auth_code": ""
        }
    },
    "signature": "mcDPZRhkuYCm+8iiWdOO...6uk8xn0nT6GaEnLiMy1L77tA=="
}

Analysis of payments results

As with other payment methods ECommPay offers, when using the QIWI Push method, you have several options to analyse the information about payments and operations performed by using the method—alone or in conjunction with other methods.

You can load and analyse all the necessary information in Dashboard, for instance you can use the analytic panels on the Analytics tab to this end.

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 and XLS formats—by using the tools on the Payments tab. You can perform export as a one-time download to your local computer or have payment data regularly exported and delivered to email addresses you specify.
  • 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 using the /operations/get queries.

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