QIWI Wallet

Overview

QIWI Wallet is a payment method to process payments by using QIWI e-wallets. You can perform purchases through this method by using Payment Page and Gate, payouts and refunds by using Gate.

General information

Payment method type	digital wallet payments
Payment instruments	digital wallets
Countries and regions	All countries
Payment currencies	EUR, RUB, USD
Currency conversion	–
Purchases	+
Payouts	+
Stored credentials payments	–
Full refunds	+
Partial refunds	–
Chargebacks	–
Notes	If the pre-selected payment method is selected on the Payment Page and the customer_phone parameter is sent in the request, a customer is redirected to his QIWI Wallet account page immediately
Onboarding and access fee	Refer to your key account manager ecommpay

Interaction diagram

Payment processing by using the QIWI Wallet payment method requires merchant's web service, one of ecommpay interfaces, and the ecommpay payment platform, as well as provider's the technical facilities.

Operations support

	Interfaces					Amounts		Times**
	Payment Page	Mobile SDKs	CMS Plug-ins	Gate	Dashboard	minimum	maximum	basic	threshold
Purchases	+	+		+	–	*	*	*	*
Payouts	–	–	–	+	–	*	*	*	*
Full refunds	–	–	–	+	–	*	*	*	*

* Refer to your key account manager ecommpay.

** The basic and threshold times are defined as follows:

The basic time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the initiator. The basic time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from customer is required). Use the basic time to estimate when to react to the absence of payment result notifications or when to check payment status.
The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the initiator 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 Wallet method, purchases, refunds, and payouts follow different processing procedures. To perform a purchase operation, you need to redirect customer to the QIWI Wallet service, while to initiate a payout or refund, you need to notify customer via merchant's web service .

Figure: Purchase by using Payment Page procedure diagram

Figure: Purchase by using Gate procedure diagram

Figure: Refund by using Gate procedure diagram

Figure: Payout by using Gate procedure diagram

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.

Purchases by using Payment Page

General information

In the QIWI Wallet methods, when processing a purchase by using Payment Page, the merchant web service should send a request with all the required parameters and signature to the ecommpay URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with one of the QIWI Wallet methods selected. For more information about preselecting payment methods, see in Preselecting payment methods. The full sequence and particularities of the purchase process are provided below.

Figure: Purchase sequence in the Payment Page method:

A customer initiates a purchase on the merchant's web service.
The web service sends the request for Payment Page opening to the specified ecommpay URL.
The request for opening is redirected to the payment platform.
The payment platform performs the initial request processing that involves validation of the required parameters and signature.
Requested Payment Page is generated into the ecommpay payment platform as specified in the project settings and the request parameters.
Payment Page is displayed to the customer.
The customer selects the QIWI Wallet method.
The payment platform receives the purchase request for payment processing from Payment Page.
The payment platform performs the internal purchase request processing and sends it to the QIWI Wallet service.
The purchase request is processed on the QIWI Wallet service side.
The QIWI Wallet service generates the data for redirecting the customer to its website form and sends it to the payment platform.
The payment platform sends the customer redirection data to Payment Page.
The customer is redirected to the QIWI Wallet website.
The customer confirms the purchase by using login and password to the QIWI Wallet account.
The payment is processed on the QIWI Wallet side.
The result is displayed to the customer on the QIWI Wallet website.
The customer is redirected to Payment Page.
The QIWI Wallet service sends the result notification to the payment platform.
The payment platform sends a callback with the payment result to the web service.
The payment platform sends the result to Payment Page.
A page with the payment result information is displayed to the customer on Payment Page.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the QIWI Wallet payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.

Request format

There are several things you need to consider when using the QIWI Wallet method:

You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
- project_id—the project ID obtained from ecommpay
- payment_id—payment ID unique within the project
- payment_currency—payment currency in ISO-4217 alpha-3 format
- payment_amount—payment amount in minor units
- customer_id—customer ID unique within the project
The currency of payment can be one of the following: EUR, RUB, USD.
If you need to have payment form displayed with the QIWI Wallet method selected, set the force_payment_method parameter to qiwi. For the straight redirection to the customer account also pass the customer_phone parameter in the request for opening Payment Page.
If required, you can also add any other additional parameters Payment Page supports.
After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Thus, a correct payment request in the QIWI Wallet method must include project, customer, and payment IDs, the currency and the amount of a payment in the appropriate currency, as shown in the following example:

EPayWidget.run(
    { project_id: 0, 
      payment_id: 'X03936', 
      customer_id: 'user123',
      payment_amount: 100, 
      payment_currency: 'USD', 
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y1Y4HASCQ9vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

For information about all parameters available in the QIWI Wallet method, see Parameters for opening payment form.

Callback format

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

The following is the example of a callback with an information about successful 50.00 EUR purchase on account 79503239672 made in the 481 project.

Figure: Example of a successful purchase callback

{
        "project_id": 481,
        "payment": {
            "id": "1207007",
            "type": "purchase",
            "status": "success",
            "date": "2019-09-10T09:54:45+0000",
            "method": "qiwi",
            "sum": {
                "amount": 5000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79503239672"
        },
        "operation": {
            "id": 44932000002349,
            "type": "sale",
            "status": "success",
            "date": "2019-09-10T09:54:45+0000",
            "created_date": "2019-09-10T09:54:14+0000",
            "request_id": "66e7615d7658a741a09858e2c82868eac3e571dc78fcf164a50",
            "sum_initial": {
                "amount": 5000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 361650,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "44932000002349",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "liDM865/azvMYLt3PHGQ06sJ1636giqSMtMmF6cybmWupmDksqdIBruH
                                             8x2dHcv5bPgE4rfgXPpz21Osvj3+8w=="
    }
}

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

{
        "project_id": 477,
        "payment": {
            "id": "2496584",
            "type": "purchase",
            "status": "decline",
            "date": "2019-09-10T08:43:10+0000",
            "method": "qiwi",
            "sum": {
                "amount": 15000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79500232022"
        },
        "operation": {
            "id": 46483000002283,
            "type": "sale",
            "status": "decline",
            "date": "2019-09-10T08:43:10+0000",
            "created_date": "2019-09-09T07:10:08+0000",
            "request_id": "9f4fa47f818c7ba46fc1815580c464878772ace205da8d36b7",
             "sum_initial": {
                "amount": 15000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1084950,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "46483000002283",
                "result_code": "0",
                "result_message": "expired",
                "auth_code": ""
            },
            "code": "20105",
            "message": "Insufficient funds on customer account",
            "description": "Operation was declined due to insufficient funds on the customer account"
        },
        "signature": "no/72vXyh8gWwUOUtBC2yAAgJ49CUkwlaz25k0btVRc7+0xLOluAICLpw
                                               4hPyZcnoOYbNY4uzSKhJHNjgRGIDQ=="
    }
}

Purchases by using Gate

General information

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

Send a request with all the required parameters and signature to the ecommpay URL.
Perform the redirection of a customer to the QIWI Wallet service.
Get the callback with the payment result from the payment platform.

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

Figure: Purchase by using Gate

A customer initiates a purchase through QIWI Wallet on the merchant's web service side.
The web service sends the request for processing the purchase by using Gate to the specified ecommpay URL.
The payment platform receives the request for processing the purchase from Gate.
The payment platform performs the initial request processing that includes validation of the required parameters and signature.
The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response format.
The payment platform performs the internal payment request processing and redirects the request to the QIWI Wallet service.
The request is processed on the QIWI Wallet side.
The QIWI Wallet service sends the data for redirecting the customer to the QIWI Wallet service to the payment platform.
The payment platform sends the callback with the redirection data in the redirect_data object to the web service.
The customer is redirected from the web service to the QIWI Wallet service.
The customer confirms the purchase by using login and password to the QIWI Wallet account.
The payment is processed on the QIWI Wallet side.
The result is displayed to the customer.
The customer is redirected to the merchant's web service.
The QIWI Wallet service sends the payment result notification to the payment platform.
The payment platform sends a callback to the web service.
The customer receives the payment result on the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the QIWI Wallet 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 purchase requests in the QIWI Wallet method:

You send purchase requests by sending the /v2/payment/qiwi/sale request by using HTTP method POST.
The following objects and parameters must be specified in any request:
- general—general purchase information:
  - project_id—project identifier
  - payment_id—unique purchase identifier
  - signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
- customer—customer information:
  - id—the ID of the customer within the merchant project
  - ip_address—customer IP address
- account—customer account information:
  - number—phone number associated with the QIWI Wallet account, must be specified using a country code and without punctuation or special characters, for example 79031234567, you can read more about the format in the FAQ section
- payment—purchase information:
  - amount—purchase amount
  - currency—payout currency in the ISO-4217 alpha-3 format.
The currency of purchase can only be one of the following EUR, RUB, USD..
If required, you can also add any other additional parameters Gate supports.
After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Thus, a correct payment request in the QIWI Wallet method must include project and payment IDs, customer ID and IP address, QIWI Wallet number, currency and amount of the purchase, as shown in the following example:

Figure: Example of a purchase request

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0UPE8euD+2AbrQgJguu0BQjXWH6naCA9Ts6o4EV
                                                           Pjlyfboq+9ajAteg5lPk96Q=="
  },
    "customer": {
        "ip_address": "1.1.1.1",
    "id": "123"
},
    "account": {
        "number": "79039999999"
  },
    "payment": {
        "amount": 10000,
        "currency": "EUR"
  }
}

Formats of the customer redirection data

To redirect a customer from the web service to the QIWI Wallet site, you must receive a callback from the payment platform containing the URL for redirection in the redirect_data.url parameter and data to be sent in the request body in the redirect_data.body parameter, and use these parameters when opening the HTML page using the method specified in the redirect_data.method parameter.

The following is the callback fragment containing the token for purchase.

"redirect_data": {
    "body": {
      "shop": "12345",
      "transaction": 34700000003226,
      "iframe": "false",
      "successUrl": "test.com/success",
      "failUrl": "test.com",
      "target": "iframe"
    },
    "method": "GET",
    "url": "https://bill.qiwi.com/order/external/main.action"
  }

In the result you should get the following link for the redirection https://bill.qiwi.com/order/external/main.action?shop=12345&transaction=34723000002456&iframe=false&successUrl=http://test.com/success&failUrl=http://test.com /fail&target = iframe.

Callback format

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

The following is the example of a callback with an information about successful 50.00 EUR purchase on account 79503239672 made in the 481 project.

Figure: Example of a successful purchase callback

{
        "project_id": 481,
        "payment": {
            "id": "1207007",
            "type": "purchase",
            "status": "success",
            "date": "2019-09-10T09:54:45+0000",
            "method": "qiwi",
            "sum": {
                "amount": 5000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79503239672"
        },
        "operation": {
            "id": 44932000002349,
            "type": "sale",
            "status": "success",
            "date": "2019-09-10T09:54:45+0000",
            "created_date": "2019-09-10T09:54:14+0000",
            "request_id": "66e7615d7658a741a09858e2c82868eac3e571dc78fcf164a50",
            "sum_initial": {
                "amount": 5000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 361650,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "44932000002349",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "liDM865/azvMYLt3PHGQ06sJ1636giqSMtMmF6cybmWupmDksqdIBruH
                                             8x2dHcv5bPgE4rfgXPpz21Osvj3+8w=="
    }
}

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

{
        "project_id": 477,
        "payment": {
            "id": "2496584",
            "type": "purchase",
            "status": "decline",
            "date": "2019-09-10T08:43:10+0000",
            "method": "qiwi",
            "sum": {
                "amount": 15000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79500232022"
        },
        "operation": {
            "id": 46483000002283,
            "type": "sale",
            "status": "decline",
            "date": "2019-09-10T08:43:10+0000",
            "created_date": "2019-09-09T07:10:08+0000",
            "request_id": "9f4fa47f818c7ba46fc1815580c464878772ace205da8d36b7",
             "sum_initial": {
                "amount": 15000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1084950,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "46483000002283",
                "result_code": "0",
                "result_message": "expired",
                "auth_code": ""
            },
            "code": "20105",
            "message": "Insufficient funds on customer account",
            "description": "Operation was declined due to insufficient funds on the customer account"
        },
        "signature": "no/72vXyh8gWwUOUtBC2yAAgJ49CUkwlaz25k0btVRc7+0xLOluAICLpw
                                               4hPyZcnoOYbNY4uzSKhJHNjgRGIDQ=="
    }
}

Refunds by using Gate

General information

QIWI Wallet supports full refunds processing. In the QIWI Wallet method, any refund follows the usual procedure which is common to Gate: merchant's web service sends a request with all the required parameters and signature to ecommpay URL, Gate accepts the request and redirects to the payment platform for further processing. The full sequence of the payout process is provided below.

Figure: Refund sequence by using Gate

A customer orders a refund on the merchant's web service side.
Merchant's web service sends the request for the refund processing by using Gate to the appropriate ecommpay URL.
Gate redirects the request to the ecommpay payment platform.
The payment platform performs all the necessary checks and processes the request.
The reply with the request processing results is sent to the merchant's web service. For more information, see Response format.
The payment platform redirects the refund request to the QIWI Wallet service.
The payment is processed on the QIWI Wallet side.
QIWI Wallet sends the result notification to the payment platform.
The payment platform sends a callback with the payment result to the web service.
The customer receives the refund result from the web service.

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

Request format

There are several things you must consider when using refund requests in the QIWI Wallet method:

You send payout requests by sending the /v2/payment/qiwi/refund request by using HTTP method POST.
The following objects and parameters must be specified in any request:
- general—general refund information:
  - project_id—project identifier
  - payment_id—unique refund identifier
  - signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
- payment—refund information:
  - description—comment to the refund.
If required, you can also add any other additional parameters Gate supports.

Thus, a correct refund request in the QIWI Wallet method must include project and payment IDs, signature, and description of the payout, as shown in the following example:

Figure: Example of a refund request

{
  "general": {
    "project_id": 35,
    "payment_id": "Payment 12",
    "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0UPE8euD+2AbrQgJguu0BQjXWH6naC
                                     A9Ts6o4EVPjlyfboq+9ajAteg5lPk96Q=="
  },
  "payment": {
    "description": "Refund"
  }
}

Callback format

The QIWI Wallet method uses the standard format for callbacks to deliver refund results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 9.88 USD refund for the account 79165354204 of the 1 customer in the 135 project.

Figure: Example of a successful refund callback

{
        "project_id": 135,
        "payment": {
            "type": "purchase",
            "sum": {
                "amount": 0,
                "currency": "USD"
            },
            "status": "refunded",
            "method": "qiwi",
            "id": "ECT_TEST_1566292942896",
            "date": "2019-08-26T10:52:04+0000",
            "description": "ECT_TEST_1566292942896"
        },
        "customer": {
            "id": "1"
        },
        "account": {
            "number": "79165354204"
        },
        "operation": {
            "id": 47003000001425,
            "type": "refund",
            "status": "success",
            "date": "2019-08-26T10:52:04+0000",
            "created_date": "2019-08-26T10:52:02+0000",
            "request_id": "b6f322b36fec4a35264c652bacd73695a2e970a9287faee7cf",
            "sum_initial": {
                "amount": 988,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 65025,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "5jxuu8dut",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "ls/fOKQSg4YT/FcheW5X+HV1VE/ZH/fgTHDvGTeZy5s97U2YFSL8EqVHVc6P4
                                                       GT5hubvKybMqdyYzDvwaObYzA=="
    }
}

The following is the example of a callback for a refund declined due to customer account is no longer available.

Figure: Example of a declined refund callback

{
        "project_id": 460,
        "payment": {
            "id": "Demo_zqw1",
            "type": "purchase",
            "status": "success",
            "date": "2019-03-02T09:33:42+0000",
            "method": "qiwi",
            "sum": {
                "amount": 988,
                "currency": "USD"
            },
            "description": "Test"
        },
        "account": {
            "number": "9088889977"
        },
        "customer": {
            "id": "Demo"
        },
        "operation": {
            "id": 26740000000119,
            "type": "refund",
            "status": "decline",
            "date": "2019-03-02T09:41:08+0000",
            "created_date": "2019-03-02T09:41:07+0000",
            "request_id": "724a9bffdd63f5e61e73d78f517d85a51075b589fee38002",
            "sum_initial": {
                "amount": 988,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 65025,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": ""
            },
            "code": "20106",
            "message": "Customer account is no longer available"
        },
        "signature": "hE0T4t2cONjWo5XsXDnO8eZqPVwvnYldS2bfrweP0JxXIOTMWwZBmFMiI3IDvX
                                                         FQKxACF9MtawyxEG1EZfc4rw=="
    }
}

Payouts by using Gate

General information

To perform a payout through the QIWI Wallet method, merchant's web service sends a request with all the required parameters and signature to ecommpay URL, and receives a callback with the payment result. The full sequence of the payout process is provided below.

Figure: Payout by using Gate

A customer orders a payout through the QIWI Wallet system.
Merchant's web service sends the request for the payout processing by using Gate to the appropriate ecommpay URL.
Gate redirects the request to the ecommpay payment platform.
The payment platform performs all the necessary checks and processes the request.
The reply with the request processing results is sent to the merchant's web service. For more information, see Response format.
The payment platform redirects the payout request to the QIWI Wallet service.
The payout is processed on the QIWI Wallet side.
QIWI Wallet sends the result notification to the payment platform.
The payment platform sends a callback with the payment result to the web service.
The customer receives the notification about the payout result from the web service.

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

Request format

There are several things you must consider when using payout requests in the QIWI Wallet method:

You send payout requests by sending the /v2/payment/qiwi/payout request by using HTTP method POST.
The following objects and parameters must be specified in any request:
- general—general payout information:
  - project_id—project identifier
  - payment_id—unique payout identifier
  - signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
- customer—customer information:
  - id—identifier
  - ip_address—customer IP address
- account—customer account information:
  - number—phone number associated with the QIWI Wallet account, must be specified using a country code and without punctuation or special characters, for example 79031234567, you can read more about the format in the FAQ section
- payment—payout information:
  - amount—payout amount
  - currency—payout currency in the ISO-4217 alpha-3 format.
The currency of purchase can only be one of the following EUR, RUB, USD..
If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the QIWI Wallet method must include project and payment IDs, signature, customer identifier and IP address, account number (for crediting), currency and amount of the payout, as shown in the following example:

Figure: Example of a payout request

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0UPE8euD+2AbrQgJguu0BQjXWH6n
                                     aCA9Ts6o4EVPjlyfboq+9ajAteg5lPk96Q=="
  },
    "customer": {
        "id": "321"
        "ip_address": "1.1.1.1"
  },
    "payment": {
        "amount": 10000,
        "currency": "EUR",
        "description": "Test payout"
  },
    "account": {
        "number": "79039999999"
  }
}

Callback format

The QIWI Wallet method uses the standard format for callbacks to deliver payout results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 50.00 EUR payout to the iy280590@gmail.com customer in the 1483 project.

Figure: Example of a successful payout callback

{
        "project_id": 1483,
        "payment": {
            "id": "852af08d-1ff0-46a4-af4b-c4f3e9664d5b",
            "type": "payout",
            "status": "success",
            "date": "2019-09-12T10:23:43+0000",
            "method": "qiwi",
            "sum": {
                "amount": 5000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79610818551"
        },
        "customer": {
            "id": "iy280590@gmail.com"
        },
        "operation": {
            "id": 46266000002521,
            "type": "payout",
            "status": "success",
            "date": "2019-09-12T10:23:43+0000",
            "created_date": "2019-09-12T10:23:30+0000",
            "request_id": "0cc015ea0cfaf822ad8f0d0bf4ebf5aa02659d23940db61fd718",
            "sum_initial": {
                "amount": 5000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 361650,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "16401320435",
                "date": "2019-09-12T13:23:32+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "AYjholAnDB4f0+GnlaVnzXweILICE/f+mJxR73+fbbcFv+wYC8IPFoWEaEgE8T
                                                         McQi7CohSKh38y7fBu+y+Mgw=="
    }
}

The following is the example of a callback for a payout declined due to customer account is no longer available.

Figure: Example of a declined payout callback

{
        "project_id": 1483,
        "payment": {
            "id": "852af08d-1ff0-46a4-af4b-c4f3e9664d5b",
            "type": "payout",
            "status": "decline",
            "date": "2019-09-12T10:23:43+0000",
            "method": "qiwi",
            "sum": {
                "amount": 5000,
                "currency": "EUR"
            },
            "description": ""
        },
        "account": {
            "number": "79610818551"
        },
        "customer": {
            "id": "siy280590@gmail.com"
        },
        "operation": {
            "id": 46266000002521,
            "type": "payout",
            "status": "decline",
            "date": "2019-09-12T10:23:43+0000",
            "created_date": "2019-09-12T10:23:30+0000",
            "request_id": "0cc015ea0cfaf822ad8f0d0bf4ebf5aa02659d23940db61fd718",
            "sum_initial": {
                "amount": 5000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 361650,
                "currency": "RUB"
            },
            "provider": {
                "id": 416,
                "payment_id": "16401320435",
                "date": "2019-09-12T13:23:32+0000",
                "auth_code": ""
            },
            "code": "20106",
            "message": "Customer account is no longer available"
        },
        "signature": "AYjholAnDB4f0+GnlaVnzXweILICE/f+mJxR73+fbbcFv+wYC8IPFoWEaEgE8T
                                                         McQi7CohSKh38y7fBu+y+Mgw=="
    }
}

Testing

General information

For the QIWI Wallet method the testing of purchases by using Payment Page and Gate, refunds, and payouts by using Gate are available..

Testing can be performed within a test project, to enable and disable the testing availability, contact ecommpay technical support via support@ecommpay.com.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests, the currency can be only RUB, and the interfaces of the payment forms emulator of Payment Page and QIWI Wallet differ from the production environment.

Test payments statuses

When testing purchases, the final payment status is determined by the amount specified in the request:

decline status with 40000 or 40400 amount
success status with any other amount

When testing refunds, the final payment status is determined by the amount specified in the request:

decline status with 50000 or 50500 amount
success status with any other amount

When testing payouts, the final payment status is determined by the amount specified in the request:

decline status with 40000 or 40400 amount
success status with any other amount

Purchases by using Payment Page

To perform a test purchase by using Payment Page, do the following:

Send a correct test request for Payment Page opening to the payment platform.
If the qiwi method was not specified in the request—select the method on the emulator page.
Specify a random phone number in the data entry field (it is enough to specify at least one digit for testing).
Click the Success or Decline button (depending on the amount specified in the request).
Accept a callback with information about the payment result.

The full information about purchase process by using QIWI Wallet through Payment Page is provided in the section Purchases by using Payment Page.

Purchases by using Gate

To perform a test purchase by using Gate, do the following:

Send a correct test request for purchase to the payment platform.
Accept a callback with redirection data.
Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
Accept a callback with information about the payment result.

The full information about purchase process by using QIWI Wallet through Gate is provided in the section Purchases by using Gate.

Refunds by using Gate

To perform a test refund by using Gate, send a correct test request for refund of previously performed test purchase to the payment platform and accept a callback with information about the payment result.

The test refund performing is possible only within a day after the initial purchase. The full information about the refund process by using QIWI Wallet through Gate is provided in the section Refunds by using Gate.

Payouts by using Gate

To perform a test payout by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. The full information about payout process by using QIWI Wallet through Gate is provided in the section Payouts by using Gate.

Analysis of payments results

As with other payment methods ecommpay offers, when using the QIWI Wallet 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.

Overview

General information

Interaction diagram

Operations support

Processing scenarios

Purchases by using Payment Page

General information

Request format

Callback format

Related topics

Purchases by using Gate

General information

Request format

Formats of the customer redirection data

Callback format

Related topics

Refunds by using Gate

General information

Request format

Callback format

Related topics

Payouts by using Gate

General information

Request format

Callback format

Related topics

Testing

General information

Test payments statuses

Purchases by using Payment Page

Purchases by using Gate

Refunds by using Gate

Payouts by using Gate

Analysis of payments results