Click here to search the entire website

About Qiwi

Qiwi is a payment method that shoppers based in Russia and Kazakhstan can use to make payments. Shoppers can use one of the following to complete their payment:

  • Their Qiwi eWallet, split into purses for different currencies
  • A payment kiosk
  • A credit/debit card linked to their Qiwi account
  • The prepay balance on the their mobile phone
  • A Webmoney account linked to their Qiwi account

A Qiwi payment involves raising a Qiwi invoice, which can either be paid in real-time, or paid subsequently at a kiosk. Merchants must be prepared for the following scenarios:

  1. The shopper pays immediately. The payment is in SHOPPER _REDIRECTED status for a short period of time, and then moves to AUTHORISED. The merchant receives real-time notification of payment.

  2. The shopper pays later. The payment remains in SHOPPER _REDIRECTED status for a longer period of time, and then moves to AUTHORISED once the shopper has completed their payment at the kiosk. The merchant receives delayed notification of payment.

  3. If the shopper takes too long to pay for an invoice, you the merchant have the ability to cancel (revoke) this invoice before the payment is authorized.  You use the Revoke Button to do this, see the Revoke Button section below. The ability to revoke a payment is useful if, for example, you sell airline tickets or hotel rooms. In cases like this a quick payment is useful.

The payment options available to the shopper depend on the shopper’s declared country, and the network provider:

Options Notes Country Authorisation

Qiwi Wallet

Always offered as a payment option.

RU, KZ

Real-time

Kiosk

Always offered as a payment option.

RU, KZ

Delayed

Linked card

Conditionally offered as a payment option.

The linked card option is only shown if the shopper has previously linked their card to the Qiwi wallet; if they have not, it will not be shown.

RU, KZ

Real-time

Mobile Phone Prepay Balance

Conditionally offered as a payment option.

Always offered to shoppers whose registered Qiwi number is on provided by the MTS or Megafon mobile networks.

This is not currently available to shoppers whose registered number is on the Beeline network, or shoppers outside of Russia.

RU

Real-time

Webmoney

Conditionally offered as a payment option.

The Webmoney option will only be shown if the customer has previously linked their Qiwi account to their Webmoney account; if they have not, it will not be shown.

RU, KZ

Real-time

Shopper journey overview

To use this method to make a payment:

  1. On the payment page, the shopper selects the Qiwi payment method and is invited to enter their email address and Qiwi account identifier (mobile phone number).

    The shopper is redirected to the Qiwi payment pages.

  2. The shopper chooses the payment option that they wish to use and enters their password to complete the payment.

  3. At the end of the shopper journey, the shopper may return on the successURL.

Note:  The screenshots below are provided for guidance purposes only and are correct as of June 2013. Qiwi may from time to time vary the wording and layout of the payment screens.

Example (mockup) of Qiwi data capture page

Qiwi landing page including payment details

Password entry following payment method selection

Wallet selection after password entry

Wallet selection, including conversion from transaction currency to wallet currency

Integration considerations

Kiosk time out options

If a shopper opts to pay at a kiosk, they must do so within two hours of placing the original order. If the time exceeds two hours, the Qiwi invoice is cancelled; when the shopper arrives at the kiosk they are unable to settle the payment, and you the merchant will not receive payment.

This two-hour timeout works well for merchants with perishable or time-critical merchandise (e.g. airline tickets, hotel bookings). However, it may not be optimal in other lines of business where fulfilment of goods is less urgent.  Merchants may optionally request Worldpay to impose a higher or lower timeout against their merchant code. This time-out must be expressed in whole hours up to a maximum of 240 hours. It is good practice to allow a margin of 15 minutes after the timeout has passed (to allow for communication delays between the Qiwi Kiosk and Worldpay) before you classify an order as expired.

Think very carefully how this timeout is set, and if necessary to discuss your options with your support contact in Worldpay.

Recipient

We advise you, the merchant to make your shoppers aware that:

  • ‘Worldpay' appears as the payment recipient on the Qiwi payment pages
  • ‘Worldpay EnvoyRUB’ appears as the payment recipient on the shopper’s Qiwi statement

If you make shoppers aware of the above information, you  may reduce shopper abandonment.

You can add a field that contains a message during the shopper journey, and you can add another message that appears  on the shopper’s statement. These short messages may help to avoid shoppers getting confused by the ‘Worldpay’ references.

Language

The language setting of Qiwi’s payment pages can vary and the language that Qiwi chooses depends on a number of factors. The logic is :

  1. Examine the shopper's IP address to identify the shopper’s language.

  2. Use the header and browser settings.

  3. Use the prefix of the mobile number the shopper uses to login to their Qiwi wallet.

Maximum transaction value

For payments submitted in RUB, the maximum transaction limit is RUB 15,000.  For payments submitted in USD, it is the USD equivalent of RUB 15,000 calculated with Qiwi’s own exchange rate. This exchange rate may differ from the exchange rate used by the Corporate Gateway. When you submit payments in USD for just under RUB 15,000, Qiwi may disqualify a proportion of these payments if their exchange rate leads to an RUB equivalent amount that exceeds RUB 15,000.

Payment method properties

The properties for this payment method are:

Property Description/ Value

Payment Type

eWallet / Postpay via kiosk

Countries

Russia and Kazakhstan

Acceptance Currencies

RUB and USD

Settlement to Worldpay Currency

USD

Preferred Currency

RUB

Shopper Debit Currency

RUB. Payments authorised in any other currency also have original payment amount shown.

Minimum Amount for a Single Transaction

1 USD

Maximum Amount for a Single Transaction

15,000 RUB

Direct Refunds (Yes/No)

Yes. Refer to WPG Refunds Capability table for limitations.

Direct Refunds Period

See WPG Refunds Capability table

Bank Transfer Refunds (Yes/No)

Yes. Refer to WPG Refunds Capability table for limitations.

Bank Transfer Refunds Period

See WPG Refunds Capability table

Chargebacks (Yes/No)

No. All payments are guaranteed and there is no risk of chargeback to merchants.

Payment Method Mask

QIWI-SSL

Supported Languages

RU, EN

statementNarrative (Yes/No)

Yes

Dynamic Descriptor (Yes/No)

Yes

Payment Traceability

The Payment ID is always shown to the shopper which is searchable in the Backoffice and MAI.

The FI reference is only shown if a dynamic descriptor is not being used. This is viewable in the Backoffice and MAI.

Direct Model (Yes/No)

Yes

Redirect Model (Yes/No)

Yes

Sandbox (Yes/No)

Yes

Service Level

M-Level

Restrictions

None

Payment timetable

The payment status is expected to change according to the following timetable:

Trigger Delay Payment status Notes

Shopper chooses Qiwi method

0

Payment is created in SHOPPER _REDIRECT ED status.

 

Shopper makes immediate payment on the Qiwi website

Typically minutes

 

Most likely if the shopper has chosen to pay by wallet/credit card/phone bill.

OR

 

 

 

Shopper makes delayed payment at the Qiwi kiosk

n hours

 

Where X represents the kiosk timeout in whole hours applicable for this merchant (or the default if no override is specified).

PSP authorises the payment

0 minutes

AUTHORISED

The payment is normally authorised in real time.

For kiosk payments, there may be a short delay (~15 minutes) for the kiosk to relay this information back to Worldpay.

Worldpay capture the payment

< 1 hour

CAPTURED

 

Worldpay clears and settles the payment internally

8 working days

SETTLED

 

Worldpay settles to the merchant

n  working days

 

The settlement to the merchant occurs according to the normal merchant settlement cycle.

Revoke Button

We provide a Revoke button so that you, the merchant, can revoke (cancel) a payment before the payment is authorized. This is useful if you sell things like airline tickets or hotel rooms, where you would like a fast payment.

Examples of Revoke Button Use

A merchant sells airline tickets. A shopper reserves an airline ticket, but after eight hours has not made a payment. In the meantime the aircraft is filling up and the merchant has plenty of other shoppers who want to buy a seat on this flight. The merchant clicks the Revoke button. Worldpay revoke the payment in full, and the merchant can sell the seat on the aircraft to another shopper.

A merchant sells hotel rooms. A shopper reserves a room, but after 24 hours still has not paid for the room. In the meantime the hotel is filling up and the merchant has plenty of other shoppers who want a room in the hotel. The merchant clicks the Revoke button. Worldpay revoke the payment in full, and the merchant can rent the room in the hotel to another shopper.

Note:  ou cannot use the revoke button to revoke payments that have been authorised. The revoke button only works on pre-authorised payments. To revoke an authorised payment, you must cancel the payment or refund the payment  if the payment has been captured or settled.

Example Merchant Screens

The screens below show the Revoke button in action. The screens are all part of your back-office operation on the Merchant Administration Interface; your shoppers never see these screens.

Payment and Order Details page that shows the revoke button in the Revoke Payment section

The revoke button only appears when the payment status is pre-authorised – in the above case the status is SHOPPER _REDIRECTED. The next screen shows what happens when you click the Revoke button.

The 'are you sure?' message appears before the system revokes the pre-authorised payment

When you click OK on the above screen, the payment status changes to REVOKE_REQUESTED

Payment and Order details page shows the REVOKE_REQUESTED payment status

The Payment and Order Details page shows that the new status for this payment is REVOKE_REQUESTED. Notice that the Revoke button and the Revoke Payment section have disappeared. Also, notice that the revoke event appears in the Payment History section.

Payment and Order Details page with the payment status REVOKED

The above page shows the REVOKED payment status in the Event Type column of the Payment History section. The time between the status change from REVOKE_REQUESTED to REVOKED in measured in seconds. If there is a longer period between the status change, this may be due to network problems.

Merchant Channels page with three extra Revoke columns on the far right side of the table

There are three extra columns on the Merchant Channels page. They are REVOKE_REQUESTED, REVOKE_FAILED and REVOKED.  Use them to set the various notifications for each payment status. If a revoke fails, it may mean that the shopper made a payment just before the revoke action was made, or there may be a network problem.

Example Shopper Screens

The revoke action has a minimal effect on shopper web pages. You can use the settings on the Merchant Channels page to send you an automatic e-mail notification when a shopper’s pre-authorised payment is revoked.  

Some Qiwi shopper pages are affected by a revoked payment. Examples of these pages appear below.

Invoices tab in the shoppers VISA Qiwi e-Wallet account – The revoked payments have the red X symbol next to payment date

Two revoked payments appear on the list. They have a red X next to the payment date. This shows they are revoked. The payment at the top of the list with the orange symbol next to the payment date has not been revoked. It is waiting to be paid. It has two options next to it, PAY and CANCEL. Shoppers can either pay, or cancel this payment.

The same screen appears below, but in this case the merchant has revoked the payment at the top of the list. The shopper no longer has the PAY and CANCEL options, and a red X appears next to the Payment date.

Invoices tab in the shoppers VISA Qiwi e-Wallet account with the revoke payment process complete

Order Notifications - Example XML Scripts

The section provides some example XML scripts that start and control the revoke process.

Note:  In all the examples in this section, we assume you have the order notifications feature enabled on your account. If you don’t have the order notifications feature enabled, you won’t receive any order notifications from Worldpay.

Request Revoke

Merchants can submit the revoke request by the Merchant Interface or use their own API system to produce the XML script below. This is called an order modification to request a revoke:

Select

<?xml version="1.0"?>

<!DOCTYPE paymentService PUBLIC"-//WorldPay//DTD WorldPay PaymentService v1//EN" "http://dtd.worldpay.com/paymentService_v1.dtd">

<paymentService merchantCode="MERCHANTCODE”version="1.4">

  <modify>

    <orderModification orderCode="Example_Qiwi_Order">

      <revoke/>

    </orderModification>

  </modify>

</paymentService>

Revoke order modification

Worldpay Response

The response that comes back from the system once it receives the order modification revoke request appears below:

<?xml version="1.0”encoding="UTF-8"?>

<!DOCTYPE paymentService PUBLIC”-//WorldPay//DTD WorldPay PaymentService v1//EN" "http://dtd.worldpay.com/paymentService_v1.dtd">

<paymentService version="1.4”merchantCode="DEMO">

  <reply>

    <ok><revokeReceived orderCode="1233344"/></ok>

  </reply>

</paymentService>

Revoke order modification response

This response tells you that the Worldpay system has received your revoke request.

Sometime later, the Worldpay system processes the revoke request. Once the revoke is made you receive a second notification that appears below: This is called an order notification for a revoked payment.  

<?xml version="1.0”encoding="UTF-8"?>

<!DOCTYPE paymentService PUBLIC"-//WorldPay//DTD WorldPay PaymentService v1//EN" "http://dtd.worldpay.com/paymentService_v1.dtd">

<paymentService version="1.4”merchantCode=“MERCHANTCODE”>

  <notify>

    <orderStatusEvent orderCode="Example_Qiwi_Order">

      <payment>

        <paymentMethod>QIWI-SSL</paymentMethod>

        <amount value="4000" currencyCode="RUB" exponent="2" debitCreditIndicator="credit"/>

        <lastEvent>REVOKED</lastEvent>

        <riskScore value="41"/>

       </payment>

       <journal journalType="REVOKED">

         <bookingDate><date dayOfMonth="11" month="06" year="2014"/></bookingDate>

      </journal>

    </orderStatusEvent>

  </notify>

</paymentService>

Revoked payment order notification

Or if the revoke fails, the notification looks like this. It is called an order notification for revoke failure:

<?xml version="1.0”encoding="UTF-8"?>

<!DOCTYPE paymentService PUBLIC”-//WorldPay//DTD WorldPay PaymentService v1//EN" "http://dtd.worldpay.com/paymentService_v1.dtd">

<paymentService version="1.4”merchantCode=“MERCHANTCODE">

  <notify>

    <orderStatusEvent orderCode=“Example_Qiwi_Order”>

      <payment>

        <paymentMethod>QIWI-SSL</paymentMethod>

        <amount value="3900" currencyCode="RUB” exponent="2" debitCreditIndicator="credit"/>

        <lastEvent>REVOKE_FAILED</lastEvent>

        <riskScore value="1"/>

      </payment>

      <journal journalType="REVOKE_FAILED">

        <bookingDate><date dayOfMonth="22"month="05"year="2014"/></bookingDate>

        <JournalTypeDetail>

          <JournalTypeDetailId>-999</JournalTypeDetailId>

          <Description>Simulated Failure</Description>

        </JournalTypeDetail>

      </journal>

    </orderStatusEvent>

  </notify>

</paymentService>

Revoke failure order notification

The usual reason that the revoke process fails is that the payment is authorised. Check the status of the order if you receive one the these failure messages.

Qiwi: Example XML order