Menu

Qiwi

Note: To learn about the features of Qiwi, there's an overviewhere

How to integrate Qiwi payments:

Direct payment request

We explain the mandatory data for Qiwi payments in the tablebelow. We also recommend that you use thestatement narrative.

Copied!
<?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="YOUR_MERCHANT CODE">
  <submit>
    <order orderCode="YOUR_ORDER_CODE"><!--Use a unique order code each time-->
      <description>YOUR_DESCRIPTION</description>
      <amount currencyCode="RUB" value="5000" exponent="2"/>
    <orderContent>
      <![CDATA[ ]]>
    </orderContent>
      <paymentDetails>
        <QIWI-SSL shopperCountryCode="RU">
          <successURL>http://www.worldpay.com/?successURL</successURL>
          <cancelURL>http://www.worldpay.com/?cancelURL</cancelURL>
          <pendingURL>http://www.worldpay.com/?pendingURL</pendingURL>
        </QIWI-SSL>
      </paymentDetails>
      <shopper>
        <shopperEmailAddress>shopper@worldpay.com</shopperEmailAddress>
      </shopper>
      <shippingAddress>
        <address>
          <address1>Tverskaya Ulitsa 3453</address1>
          <postalCode>74564</postalCode>
          <city>Moscow</city>
          <countryCode>RU</countryCode>
          <telephoneNumber>7987654321</telephoneNumber>
        </address>
      </shippingAddress>
      <statementNarrative>MERCHANT STATEMENT NARRATIVE</statementNarrative>
    </order>
  </submit>
</paymentService>

Mandatory data

Parameter nameDescription
shopperEmailAddressThe email address of the shopper.
telephoneNumberThis field constitutes the identifier of the Qiwi wallet that the shopper wishes to use to make the payment. The wallet identifier is always represented by the shopper’s mobile phone number. The mobile phone number must be presented in standard MSISDN format but without the country code element of the MSISDN. For example, the MSISDN 71234567890 must be presented without the leading '7' (which is the country code for Russia/Kazakhstan). Note that it is possible for the phone number itself to begin with a 7, so it cannot be assumed that a leading 7 always represents the country code.

Merchants can encourage shoppers to enter the correct string by prefixing the data field on their payment page with '+7' as per the example below (the mockup in figure 1 is provided for guidance purposes and does not reflect the current WPG pages).

Ideally, merchants should validate the data to ensure that there are no non-numeric characters (e.g. letters). This will help prevent keying errors by shoppers, which in turn will improve the shopper experience and optimise the payment 'conversion' rate. If merchants do validate the data in this way, it is advisable to ensure that precise validation messages are presented to shoppers so they are made aware of why the data they are entering is incorrect and how they can correct it.

If non-numeric characters are included in the data sent to WPG, these characters will be removed before the data is submitted to Qiwi so as to minimise the possibility of a fatal error occurring.

Merchants are advised to ensure that they label the data field appropriately to indicate that the shopper should enter the mobile phone number associated with their Qiwi wallet (in many countries, shoppers will commonly have more than one mobile phone number, of which possibly only one can be used for making payments via Qiwi). If the shopper does enter the wrong number, they will not be able to complete their payment.

Additionally, only Russian or Kazakhstani mobile numbers are currently valid. If a Russian/Kazakhstani shopper has a phone number from a different country, the shopper will not be able to make a payment using Qiwi. Merchants are advised to set expectations accordingly with their shoppers before the shopper attempts a payment.

Qiwi landing page showing dynamic descriptor

Qiwi landing page showing dynamic descriptor

Qiwi shopper statement showing transaction history

Qiwi shopper statement showing transaction history

Hosted payment request

We explain the recommended databelow.

In this example the merchant has specified that only the Qiwi payment methods should be offered by using the append string:

&country=RU&preferredPaymentMethod=QIWI-SSL

Copied!
<?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="YOUR_MERCHANT CODE">
  <submit>
    <order orderCode="YOUR_ORDER_CODE" installationId="1234567"><!--Use a unique order code each time. Contact Worldpay if you haven't got an installationID-->
      <description>Test order</description>
        <amount value="5000" currencyCode="RUB" exponent="2" />
    <orderContent>
      <![CDATA[ ]]>
    </orderContent>
    <paymentMethodMask>
      <include code="ALL" />
    </paymentMethodMask>
      <shopper>
        <shopperEmailAddress>shopper@worldpay.com</shopperEmailAddress>
      </shopper>
      <statementNarrative>MERCHANT STATEMENT NARRATIVE</statementNarrative>
    </order>
  </submit>
</paymentService>
Parameter nameDescription
telephoneNumberThe merchant should not pass the telephone number unless the merchant is certain that the number is that same as the one that the shopper has registered with Qiwi. If the merchant passes the wrong phone number, the shopper will be unable to complete their payment on the Qiwi landing page.
statementNarrativeThis is explainedbelow.
order
description
You should pass a descriptive text in the language of the shopper to prompt the shopper to enter the phone number associated with his Qiwi wallet (as opposed to another phone number). This will reduce the possibility of the shopper keying the wrong phone number which will cause an error later in the shopper journey.

Statement Narrative

The statement narrative is a string that is:

  • Shown to the shopper when the shopper arrives on the Qiwi landing page as a dynamic descriptor in place of the FI reference.
  • Shown to the shopper on their Qiwi statement (transaction history).

Best Practice: We recommend that you populate the statement narrative for Qiwi because it:

  • Increases shopper confidence as Qiwi provides continuity throughout the shopper journey. Shoppers see the merchant's narrative on both the merchant site and on the Qiwi payment pages.
  • Provides additional information to the shopper on their Qiwi transaction history. This reduces the possibility of the shopper not recognising the transaction, making it less likely that they will query the payment at a later stage.

The narrative can be up to 50 characters long and must be made up of only:

  • Letters (Latin or Cyrillic, upper or lower case).

  • Spaces

  • Underscores

  • Full stop (period)

  • Colon

  • Semi-Colon

  • Numbers

  • Hyphen

A string longer than 50 characters will be truncated to 50 characters.

If you have a compelling need to pass a character not listed above, please contact your Worldpay support representative for advice.

Payment outcomes

Successful

Shopper pays
Event 1:The shopper successfully completes a payment for USD 1.00 on the Qiwi pages using one of the real-time authorisation options (Qiwi wallet, card, mobile phone bill).
Behaviour:success URL is returned
URL:SUCCESS
URL Example:http://www.worldpay.com/successURL?orderKey=ADMINCODE^MERCHANTCODE^Example_Qiwi_Order&paymentStatus=AUTHORISED&paymentAmount=100&paymentCurrency=USD&mac=77fcc8ca4a2a548105b81e252cf15faf
Payment Status:The payment status changes to AUTHORISED.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>AUTHORISED</lastEvent>
        <balance accountType="IN_PROCESS_AUTHORISED">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="AUTHORISED">
        <bookingDate>
          <date dayOfMonth="06" month="12" year="2012"/>
        </bookingDate>
        <accountTx accountType="IN_PROCESS_AUTHORISED" batchId="680">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>
Payment captured
Event 2:The payment is captured in WPG.
Behaviour:The automatic capture job runs in WPG to automatically capture the payment.
URL:No URL is returned to the shopper as the shopper journey is already complete.
URL Example:N/A
Payment Status:The payment status changes to CAPTURED.
Copied!
<!DOCTYPE paymentService PUBLIC "-//WorldPay//DTD WorldPay PaymentService v1//EN" "http://dtd.worldpay.com/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>CAPTURED</lastEvent>
        <balance accountType="IN_PROCESS_CAPTURED">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="CAPTURED">
        <bookingDate>
          <date dayOfMonth="06" month="12" year="2012"/>
        </bookingDate>
        <accountTx accountType="IN_PROCESS_AUTHORISED" batchId="1680">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="debit"/>
        </accountTx>
        <accountTx accountType="IN_PROCESS_CAPTURED" batchId="817">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>
Payment settled
Event 3:The payment is settled internally in WPG.
Behaviour:The payment is successfully settled internally in WPG.
URL:No URL is returned to the shopper as the shopper journey is already complete.
URL Example:N/A
Payment Status:The payment status changes to SETTLED.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>SETTLED</lastEvent>
        <balance accountType="SETTLED_BIBIT_COMMISSION">
          <amount value="3" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <balance accountType="SETTLED_BIBIT_NET">
          <amount value="72" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="SETTLED" description="1 USD = 0.75340 EUR">
        <bookingDate>
          <date dayOfMonth="14" month="12" year="2012"/>
        </bookingDate>
        <accountTx accountType="SETTLED_BIBIT_COMMISSION">
          <amount value="3" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
 <accountTx accountType="SETTLED_BIBIT_NET" batchId="737">
          <amount value="72" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
        <accountTx accountType="IN_PROCESS_CAPTURED" batchId="817">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="debit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>

Invalid data entry

Invalid data
Event 1:The shopper specifies a phone number that does not correspond to a valid Qiwi wallet.
Behaviour:The shopper is redirected to the Qiwi website and is shown a message stating that the mobile phone number is not recognised before being prompted to open a new wallet by following on screen instructions.
URL:No URL is returned as the shopper does not leave the Qiwi website.
URL Example:N/A
Payment Status:The payment status remains at SHOPPER_REDIRECTED.
Notification Example:No notification is generated.
Incorrect password
Event 2:The shopper inputs an incorrect password on the Qiwi website
Behaviour:The password is validated on the Qiwi website. The shopper remains on the Qiwi website until they either enter a valid password, or cancel the transaction on the Qiwi website.
URL:No URL is returned as the shopper does not leave the Qiwi website
URL Example:N/A
Payment Status:The payment status remains at SHOPPER_REDIRECTED.
Notification Example:No notification is generated.

Payment time out

Time out
Event:The shopper does not arrive at the kiosk and complete the payment within the allocated kiosk timeout period.
Behaviour:The shopper cannot complete the transaction and is required to start a new payment.
URL:No URL is returned as the shopper is no longer on the Qiwi website.
URL Example:N/A
Payment Status:The payment status remains at SHOPPER_REDIRECTED.
Notification Example:No notification is generated.

Exception conditions

Error with PSP
Event 1:The payment cannot be processed due to technical issues at the PSP
Behaviour:pendingURL with status=ERROR is returned. This scenario occurs in exceptional circumstances where the payment cannot be processed for technical reasons.
URL:PENDING (ERROR)
URL Example:http://www.worldpay.com/pendingURL?orderKey=ADMINCODE^MERCHANTCODE^ Example_Qiwi_Order &status=ERROR
Payment Status:The payment status remains at SHOPPER_REDIRECTED.
Notification Example:No notification is generated.
Example
Event 2:Worldpay receives the asynchronous authorisation from Qiwi more than 5 seconds after the shopper has completed their journey.
Behaviour:pendingURL with status=OPEN is returned.
URL:pendingURL
URL Example:http://www.worldpay.com/?pending&orderKey=ADMINCODE^MERCHANTCODE^Example_Qiwi_Order_Code&status=OPEN
Payment Status:The payment status changes to AUTHORISED.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>AUTHORISED</lastEvent>
        <balance accountType="IN_PROCESS_AUTHORISED">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="AUTHORISED">
        <bookingDate>
          <date dayOfMonth="06" month="12" year="2012"/>
        </bookingDate>
        <accountTx accountType="IN_PROCESS_AUTHORISED" batchId="680">
          <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>

Refunds

Refund requested
Event 1:The merchant requests a refund of the payment in MAI.
Behaviour:The merchant requests a direct refund of a settled RUB payment in WPG.
URL:No URL is returned as the shopper journey is already complete.
URL Example:N/A
Payment Status:The payment status is set to SENT_FOR_REFUND.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="10000" currencyCode="RUB" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>SENT_FOR_REFUND</lastEvent>
        <balance accountType="SETTLED_BIBIT_COMMISSION">
          <amount value="3" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <balance accountType="SETTLED_BIBIT_NET">
          <amount value="72" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <balance accountType="IN_PROCESS_CAPTURED">
          <amount value="10000" currencyCode="RUB" exponent="2" debitCreditIndicator="debit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="SENT_FOR_REFUND">
        <bookingDate>
          <date dayOfMonth="31" month="01" year="2013"/>
        </bookingDate>
        <accountTx accountType="IN_PROCESS_CAPTURED" batchId="839">
          <amount value="10000" currencyCode="RUB" exponent="2" debitCreditIndicator="debit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>
Refund sent
Event 2:The requested refund is successfully sent to the shopper’s bank.
Behaviour:WPG receives confirmation that the payment has been successfully sent to the shopper’s wallet.
URL:N/A
URL Example:N/A
Payment Status:The payment status is set to REFUNDED.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="10000" currencyCode="RUB" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>REFUNDED</lastEvent>
        <balance accountType="SETTLED_BIBIT_COMMISSION">
          <amount value="3" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="REFUNDED" description="1 RUB = 0.02498 EUR">
        <bookingDate>
          <date dayOfMonth="04" month="02" year="2013"/>
        </bookingDate>
        <accountTx accountType="SETTLED_BIBIT_NET" batchId="749">
          <amount value="250" currencyCode="EUR" exponent="2" debitCreditIndicator="debit"/>
        </accountTx>
        <accountTx accountType="IN_PROCESS_CAPTURED" batchId="839">
          <amount value="10000" currencyCode="RUB" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>
Refund fails
Event 3:The refund fails (e.g. shopper has specified incorrect bank details).
Behaviour:WPG receives confirmation that the payment has not been successfully sent to the shopper’s wallet.

The example below shows an attempt to refund USD to a shopper’s wallet. Direct refunds in USD are not currently supported for this payment method so the refund fails.
URL:N/A
URL Example:N/A
Payment Status:The payment status is set to REFUND_FAILED.
Copied!
<?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="MERCHANT_CODE"><!--Will contain the merchant code used in the request-->
  <notify>
    <orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
      <payment>
        <paymentMethod>QIWI-SSL</paymentMethod>
        <amount value="100" currencyCode="USD" exponent="2" debitCreditIndicator="credit"/>
        <lastEvent>REFUND_FAILED</lastEvent>
        <balance accountType="SETTLED_BIBIT_COMMISSION">
          <amount value="3" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <balance accountType="SETTLED_BIBIT_NET">
          <amount value="72" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </balance>
        <riskScore value="1"/>
      </payment>
      <journal journalType="REFUND_FAILED" description="130219-002880">
        <bookingDate>
          <date dayOfMonth="20" month="02" year="2013"/>
        </bookingDate>
        <accountTx accountType="SETTLED_BIBIT_NET" batchId="758">
          <amount value="72" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
        </accountTx>
      </journal>
    </orderStatusEvent>
  </notify>
</paymentService>

Transfer reports

Settled

The following is an example of a settled transaction in an XML transfer report for RUB 1,997.00 where the Merchants account settles in USD:

Copied!
<orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
  <payment>
   <paymentMethod>QIWI-SSL</paymentMethod>
    <amount value="199700" currencyCode="RUB" exponent="2" debitCreditIndicator="credit" />
    <lastEvent>SETTLED</lastEvent>
    <balance accountType="SETTLED_BIBIT_NET">
      <amount value="6065" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
    </balance>
    <balance accountType="SETTLED_BIBIT_COMMISSION">
      <amount value="204" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
    </balance>
  </payment>
  <journal journalType="SETTLED" description="1 RUB = 0.03139 USD">
    <bookingDate>
      <date dayOfMonth="2" month="5" year="2013" hour="8" minute="9" second="34" />
    </bookingDate>
    <accountTx accountType="SETTLED_BIBIT_COMMISSION">
      <amount value="204" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
    </accountTx>
    <accountTx accountType="SETTLED_BIBIT_NET" batchId="24">
      <amount value="6065" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
    </accountTx>
    <accountTx accountType="IN_PROCESS_CAPTURED" batchId="84">
      <amount value="199700" currencyCode="RUB" exponent="2" debitCreditIndicator="debit" />
    </accountTx>
  </journal>
</orderStatusEvent>

Refunded

The following is an example of a refunded transaction in an XML transfer report for RUB 1,148.00 where the Merchants account settles in USD:

Copied!
<orderStatusEvent orderCode="ORDER_CODE"><!--Will contain the order code used in the request-->
  <payment>
    <paymentMethod>QIWI-SSL</paymentMethod>
    <amount value="114800" currencyCode="RUB" exponent="2" debitCreditIndicator="credit" />
    <lastEvent>REFUNDED</lastEvent>
    <balance accountType="SETTLED_BIBIT_NET">
      <amount value="149" currencyCode="USD" exponent="2" debitCreditIndicator="debit" />
    </balance>
    <balance accountType="SETTLED_BIBIT_COMMISSION">
      <amount value="114" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
    </balance>
  </payment>
  <journal journalType="SETTLED" description="1 RUB = 0.03053 USD">
     <bookingDate>
       <date dayOfMonth="3" month="6" year="2013" hour="11" minute="46" second="37" />
      </bookingDate>
      <accountTx accountType="SETTLED_BIBIT_COMMISSION">
        <amount value="114" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
      </accountTx>
      <accountTx accountType="SETTLED_BIBIT_NET" batchId="33">
        <amount value="3391" currencyCode="USD" exponent="2" debitCreditIndicator="credit" />
      </accountTx>
        <accountTx accountType="IN_PROCESS_CAPTURED" batchId="114">
      <amount value="114800" currencyCode="RUB" exponent="2" debitCreditIndicator="debit" />
      </accountTx>
  </journal>
</orderStatusEvent>