Complaints about problems with QIWI-wallets

QIWI is the most innovative IT company in Russia. Recently, she made a real breakthrough, offering new convenient services and technologies. In any corner of the country you can find a blue or orange terminal with the QIWI logo.

Unfortunately, the flip side of the introduction of new services is the emergence of new errors inevitably arising in advanced products. Security failures in payment systems are particularly sensitive, and the popularity of the system can turn such a crash into a nightmare.
')
On the forum of a specialized provider portal nag.ru , an angry topic of a single user has recently appeared who has a substantial amount of money from a QIWI wallet. It turned out that QIWI experts read the topic, and, after some altercations, the issue was resolved in favor of the victim, which indirectly indicates the company's problem.

However, after some time, the topic got into the search engines and the offended and injured were pulled into it in the hope of help. Below, the original citations of the victims, the grammar and punctuation in them are preserved!

Update
Posted by the official response from QIWI

Update2
My next post will be devoted to the payment system Manibukers.

Update3
At the request of QIWI employees, the post title has been changed. I was also assured of the readiness to discuss the issues raised, and that no one purposefully tries to hide the information. It's good. Thanks to those who supported this post, there was a moment when it seemed to me that there were only a few minutes left and I just would not have time to make an update.

August 15, 2011 - 19:56
, , , ?
, , - , , , .
Fraud@ - , ...

August 20, 2011 - 13:56
17 2011 . , ( ). , , 09.08.2011 . 11.08.2011 . , , QIWI , . 485 126,50 .

, , , , , , ( " "). «QIWI » , , .

, antiqiwi [] yandex.ru QIWI-, ( № ) .
, . .

August 20, 2011 - 14:26
, ... .. 420 ., ...

August 24, 2011 - 03:34
!

... !
1000 , :
, , , , !
. 17- - 325 . 2 ! 19- 1450 ( 1100 - ). -. - ! , . . .

fraud@qiwi.ru. :

.
, . 430 .
. .
" ", , .

, - - , -. . .
3 , .

, QIWI, ???
, .
, , , .
QIWI.

August 27, 2011 - 11:35
, .. 16-.. 1200 .. , ( ) .. , .. - .. , , , - -.. .. .. " ".. , , .. - - ?.. ?..

Complaints in the subject continue to come. Thus, there is every reason to talk about a truly mass problem. In this regard, I appeal to QIWI officials and ask you to clarify the situation. I would like to see a response containing the following:

1. Information about the nature of the failure and its scale, how many subscribers could suffer?
2. Instruction for subscribers with a description of how to check how to hedge and where to call if that
3. Report on measures taken to prevent recurrence of failures

To help the administration assess the scale and take the necessary measures, we open a hotline with QIWI complaints in the comments.

Qiwi official response

sent efads

Good day,

I represent the company QIWI Wallet, which was dedicated to your last post on Habré. The publication of such information does not cause joy.
Information is spread about allegedly massive hacks by a user offended by us, who most likely, alas, used the system to receive payments not for completely legal products.

Regarding your questions:

1. Information about the nature of the failure and its scale, how many subscribers could suffer?

There was no system failure. Viruses, unfortunately, users miss, which sometimes leads to loss of funds.

2. Instruction for subscribers with a description of how to check how to hedge and where to call if that

Write to technical support via the feedback form on the website and applications. At the slightest suspicion of changing the password - this can be done using just an SMS command or on the same site. For an emergency password change, you need to send an SMS with the text pass or password to the number 7494: in response, you will receive an SMS containing the new password.

3. Report on measures taken to prevent a repetition of failures

SMS confirmations and certificates for payment applications that were prepared for release over the last 2 months had to be entered by force, and not voluntarily, as planned. This really caused a flurry of indignation and an influx of calls to technical support.

If you have any questions - write!