Shadow fight 2 freedom verification error. Errors when checking Android-iOS internal payments and their solution

Visa Qiwi Wallet is a popular payment system that offers users a wide range of financial services. An electronic account is opened for each Qiwi client, access to which is carried out using branded terminals, the official website qiwi.com and the application.

Sometimes Qiwi wallet holders find that the payment system is not working and it is not possible to access personal funds. How to find out what happened to Qiwi and how quickly will the problems be fixed?

Why does Qiwi wallet not work?

Despite the fact that Qiwi Visa Wallet rarely upsets its customers with technical errors, sometimes users are unable to log into the wallet or complete the desired transaction. At the same time, the payment system or its developers are not always to blame.

There can be several reasons for breakdowns:

  • customer problems;
  • failures of intermediaries;
  • failure of the terminal;
  • technical errors on the part of the Qiwi payment system.

To fill out and send an application, it is not necessary to log in to your account, but you will have to attach documents to the application:

  • copies of all pages of the passport;
  • an agreement to connect to the operator's network or a certificate stating that the applicant is the owner of the SIM card linked to Qiwi;
  • a note with comments on the situation;
  • additional information if needed.

Documents are attached to the online application on the website.

Payment error

If an error is displayed during the operation, you should make sure that the details entered are correct. This also happens in cases where the user has not taken into account the amount of the commission or there are not enough funds on the debit account.

The “History” section will help clarify the situation, where the reason for the payment error is indicated and recommendations are given for correcting it.

Intermediary failures

Qiwi failure may mean technical errors on the part of intermediaries: Internet providers, mobile operators and other service providers.

Possible problems and solutions

  1. The Qiwi page does not open - there is no connection to the network or the speed has decreased. You should make sure that all cables are connected correctly and that nothing has changed in the network settings of the computer. Otherwise, it remains to contact the provider to resolve the issue remotely or call a specialist at home.
  2. Technical error when paying for services via Qiwi. Providers need time to verify the data and accept the payment. If the details were entered correctly and there was enough money on the client's account, you should contact the service provider for crediting funds.
  3. I don't receive SMS to confirm my payment. Most likely, the network of the mobile operator is overloaded, and there are a large number of subscribers in the queue. The Qiwi system will definitely offer to resend the SMS in a few seconds. More about problems with SMS -.

Terminal malfunctions


Select the question you are interested in regarding the operation of the terminal and fill out the application.

20% of Qiwi malfunctions are associated with branded payment terminals. Each such device is used daily by hundreds of people who want to access their wallets. There is nothing surprising in the fact that sometimes the device does not work or fails.

Access to terminal services can be limited in several cases:

  • interruption of the Internet connection;
  • failure of their equipment;
  • update or error in the operation of the terminal operating system.

Only specialists can solve any of these problems. If the device generated an error at the time of payment for services by the user, he should check the status of the payment on the qiwi.com website and contact technical specialists.

In the "Help" - "Contact support" - "Qiwi terminals" section, possible problems are listed. Having chosen the right question, the client needs to fill out an application and wait for a response from the Qiwi technical service. You can contact support by calling 8 800 707-77-59. When the Priority service package is connected, the operator will answer within 10 seconds.

Errors on the part of the payment system


Problems with the Qiwi wallet can be tracked on the monitoring site.

Today, there are fewer and fewer situations when the payment system and the Qiwi website really do not work.

Possible errors should be divided into two groups:

  1. Scheduled. Users cannot log into the Qiwi wallet on days when system updates or maintenance are being carried out. As a rule, customers are warned in advance of temporary inconveniences, and backup servers are connected, which minimize potential problems.
  2. Unplanned. They occur due to system failures, which are the result of software flaws. In such a situation, you can try to enter the wallet a little later.

In order not to get lost in conjectures and make sure that problems with the Qiwi wallet are indeed fixed today, you can visit the special monitoring of technical errors downdetector.ru. It analyzes the schedule of failures in the operation of the site and Qiwi terminals, as well as official comments from representatives of the payment system.

If necessary, site customers can familiarize themselves with the card and find a valid device for making payments.

Video: Why QIWI does not work.

Disclaimer. This post is based on a report at SQADays'15. You can also browse through the presentation. I draw your attention to the fact that the report was of an initial level, that is, the post will be of interest mainly to managers and novice testers. And also the fact that the author is not a real welder and in some places makes rather rough roundings.

My name is Alena and I'm a release manager. The department of the i-Free company where I work is mainly engaged in applications for iOS and Android. We also support Tizen, Windows Phone, alternative stores, but this post will focus on the Apple iOS Appstore and Google Play.
In both markets, in addition to paid and free applications, it is possible to make internal payments - in-apps (In-App Purchases).

Why am I talking about in-app testing? Because I can!
As a release manager, I usually participate in projects at the beginning of development and at the end of those iterations that end up in the store. Before the start of the project, I issue the keys and certificates to the developers, and by the end of the work on the version, the developers give me the builds for the release. But between these points there is a moment when you need to start internal payments - in-apps and issue test accounts to testers. And at this stage, sometimes something strange happens when the developers think that everything is fine with them, and the testers think that everything is bad.

General information about testing in-apps

To begin with, let me briefly remind you about how payments work in mobile applications and what is needed to test them.

So, in one form or another, both markets have:

  • Sandbox for testing payments
  • Test account mechanism to avoid wasting money
  • Test builds and test devices
The standard scheme for buying in-apps in mobile stores:
  1. First, the user clicks on the "buy" button and enters the password. The purchase itself is taking place, the platform mechanisms are working
  2. Purchase information is sent to the application
  3. Purchased in-app consumption (consume)
  4. In-app becomes available for repurchase
Points 3 and 4 are relevant only for reusable purchases - they should be, but this does not always happen. Details will be below.

Specifics of testing Google Play In-App Purchases

How to test and what is needed for this

Let's start with the fact that in the case of Google Play, we are dealing with a semi-sandbox. We will use real accounts that are marked as "test" in the developer account. At the same time, a bank card must be linked to the account, but in fact there will be no debits from it. Well, thanks to the openness of the platform itself, we have full-fledged logs and easy installation of builds.
So what is needed:
  • Developer account with test accounts declared in it
  • A test account with a card linked to it and participating in a beta test
  • Application build published in beta test
  • A test device logged into a test account. We download the build from the beta test on it.

What it looks like when everything is fine:

When you click on the in-app, we see a window with the caption "this is a test payment." The purchase takes place almost instantly and is completed successfully, money is not debited from the card.
In the application, we are credited with the required benefits

What can happen when everything is bad?

Error -#1 build version mismatch


Payments can only be tested on a build of the same version as in the admin panel. But since testing was introduced not with the help of draft builds, but through a beta test, this error should be much less common.
What to do:

  • check if the versions on the device and in the admin panel match
  • wait - the newly downloaded version may not be visible to the application for two to four hours.

Mistake #2 - Bad Connection:



If in fact everything is fine with the Internet, it is almost always treated by switching from 3g to wi-fi or from wi-fi to another wi-fi.

Mistake No. 3 - buy purchased:


Promised retreat. In many markets there is a distinction between disposable and reusable in-apps. It was also on Google Play, but since February 2013 billing version 3 has been introduced. Since then, in-apps have been “Google-managed” and “developer-managed”, and whether they can be bought multiple times depends on how the developer processes them (consumer or not).

In fact, the user should never see this error. If this happens, or the developer refers to one-time in-apps as reusable, or Google has turned the purchase between Google Checkout and Google Play, you have to wait a couple of hours and / or reboot.

Mistake #4 - [letters and numbers in square brackets]



This is usually a problem for buyers due to incorrectly configured Google Checkout.
What to do:
  • standard rituals: reboot and wait a bit
  • last resort is to clear your Google Services data

Everything seems to be fine, but the in-app has not been credited



Or Google said that the payment was successful, but the application said that it was not.
It is important to understand that in this case the problem is on the application side. That is, if Google replied that the payment was successful, it always unambiguously sends just such a response. But the application must still be able to process it!
  1. What to do? Wait for programmers to fix
  2. This is critical, such in-apps disappear without a trace!
  3. This is most likely a server error related to the signature
You can also remember the words license key. The fact is that a small string of numbers and letters that certifies in-apps, paid applications and the download of additional content is now unique for each application. And if for some reason you make two versions of the application (for the Russian and international markets, or paid and free versions, for example), there is a chance that someone somewhere will forget to change this line. Timely spoken words “are we all right with the license key?” can save a few claps with one palm on the forehead.

iOS testing specifics

How to test

But Apple has a full-fledged sandbox waiting for us. But does this mean that it will be easier for us?
So, no real cards and real accounts. In this case, the test account is tied to the store of a certain country, this is important. There is no need to upload builds to the admin panel yet, so with the exception of issuing test accounts, this part goes without my participation.
But it's not so simple - advanced! Roughly speaking, these are lists that list which developers have the right to build an application with a certain identifier, and on which devices the resulting build can be installed.
Well, two admin panels - Tunes Connect for promotional materials, Member Center for developers.

What you need for testing:

  • "Skeleton" application in iTunes Connect, only after that you can start in-apps
  • Test account of the country where the application is installed
  • Test device entered in Member Center
  • Correctly assembled build, installed on the correct device

What happens when all is well:


When you click on the in-app, a window appears with the signature.

What to do when something is wrong?


First of all - important information about iOS test accounts

This is a completely non-existent account, but the e-mail must be unique among both test and real accounts. It does not need to enter credit card information, and the date of birth is entered once when created in the admin panel. If the test account on the device asks you to enter something other than your username and password, you have broken it. At all. We have to make a new one.

Mistake #1 - You need to enter payment information


If you press the “continue” button on such a plate, you will be asked to enter information about the payment instrument. This means that you have linked your test account incorrectly. It can be bound to a device in only one way:
  1. It is necessary to untie all real accounts from the device
  2. Login to the app
  3. Tap on in-app
  4. And enter your username and password
All other methods will not work and will break the account, you will have to make a new one.

Mistake #2 - You can't complete this purchase


It's also an account related issue. What does this mean:
  1. Launched application is not available in the country of the test account
  2. The app and the test account belong to different developer accounts
  3. You are using a real account

Mistake No. 3 - limit on the number of purchases


Very strange error, there is no such restriction. But you can come across a similar one when testing subscriptions hard. I have not personally met, the only advice is to be careful when testing iOS subscriptions :)

Mistake #4 - you're not a test user!


May appear on a jailbroken device or with an extremely poor internet connection. I have not personally met, advice - if possible, do not test on devices with a jailbreak. Unless, of course, this is not part of your target audience.

The report was read on April 18, since then the situation has not changed much, with the exception of the way builds are laid out on Google Play for testing. Previously, it was enough just to start a build as a draft, but now you need to

Now is the digital age. It is difficult to meet a person who does not have a bank card. They are different - different payment systems, credit and debit, profitable, chipped and not.
Payment by credit card via the Internet - this service is now offered by almost any online store. For example, you can buy a train ticket by paying with a bank card, make a purchase on ozon.ru.

I have always ordered and paid for tickets with a bank card via the Internet (I only use debit cards, I don't have one). The most interesting thing is that this service sometimes fails - the money hangs on the card, the payment does not go through.
But I had a case where the payment simply did not go through. Robokassa wrote a message - payment cancelled. I didn't know what was the reason. I couldn't find the error in my account.
Now I will try to talk about the main reasons why an error occurs when paying with a bank card

The main causes of errors when paying with a bank card

First reason, which is the most common - the lack of the required amount on the card. It is recommended to check your balance - for this you need to call the bank or enter the Internet bank. Sometimes a card has a monthly or daily spending limit. To check this, you need to call the bank.
This reason may not be immediately clear - if you refuse to pay, your balance may not be displayed. The 3D secure authentication error may also be related to the incorrect entry of card details in the previous step. In this case, simply repeat the payment and enter the correct data.

The second reason- on the side of the payment system. For example, the Russian Railways payment terminal does not allow you to pay with MasterCard cards. Only Visa cards can be used.
The specified store may not support this payment method. For example, a robokassa, which is connected to many stores, offers various payment rates.


At first I wanted to pay for webmoney, but I called the store. It turned out that you can not pay for webmoney. They don't have this option enabled. Although the payment method via webmoney is offered on the payment page.

Third reason Your card may have been blocked. Again, you can call the bank and check it out. Blocking can be carried out by the bank automatically in case of suspicious transactions with the client.

Fourth reason— you do not have the 3d Secure option enabled (MasterCard SecureCode in case of MasterCard).
The 3D Secure technology is as follows: when paying, you receive an SMS from the bank, which you must enter in a special window. Only you and the bank know this SMS. Fraud in this case is quite difficult, it will require your phone.
You need this option to pay more than 3 thousand rubles. This is just my case. I bought a Bosch gas stove from an online store. When paying for goods in the amount of 22 thousand rubles, I received the following message:


I was confused, didn't know what to do. At first I thought it was a store problem. But first I still called the bank. In my case, it was Promsvyazbank and a profitable card.
Calling Promsvyazbank support, I was offered to first go through the authentication procedure

  1. Say the last 4 digits of the card number
  2. Give the last name, first name, patronymic in full
  3. State the code word.

Further, in order to connect the 3d Secure service, they demanded 2 numbers from the table of one-time keys from me. It seems like the service was connected, but after half an hour the payment failed again. I called the bank - they said wait when it connects - the service does not connect immediately. You need to wait.
I decided to check if the service is connected. I logged into the Internet bank - I saw that there is such a service (in PSB retail, you can see this on the card page by clicking on the card number)


Once again, an attempt to pay - a window popped up for me where I had to enter a confirmation code. After filling in the card details, I received an SMS with a payment code


Then voila - the order is finally paid. I received the following window and the status of the order in the store changed to "Paid"
My order was delivered to the destination, where I will pick it up within a month. The main payment went through.

Most Common Error 11070: 3dsecure Authentication Error - Causes

The most common error that occurs when paying with a card is 11070: 3dsecure authentication error. There are 2 possible reasons for this error

  1. An invalid one-time code was entered. You received a code, but when entering you made a mistake in the number. As a result, we got an error
  2. The one-time code is rotten. The time that you are given to enter a one-time code when paying is no more than 5 minutes. Then you will have to repeat the payment.

Table with payment error codes.

Few people know that when paying with a card, the system usually issues an error code. For example, E00 upon payment. Sometimes by mistake you can understand what the problem is

Error code and description
Code 00 - a successful operation.
Code 01 - refuse, call the bank that issued the card.
Code 02 - refuse, call the bank that issued the card (special conditions).
Code 04 - withdraw the card without giving a reason.
Code 05 - refuse without giving a reason.
Code 17 - refuse, rejected by the card user.
code 19 - technical error on the side of the bank
Code 41 - withdraw, lost card.
Code 43 - withdraw, stolen card.
code 50 - ?
Code 51 - refuse, there are not enough funds on the account.
Code 55 - refuse, incorrectly entered PIN code.
Code 57 - refuse, invalid operation type for this card type
(for example, an attempt to pay in a store with a card intended only for cash withdrawal).
Code 61 - refuse, exceeding the maximum transaction amount for this card.
Code 62 - refuse, blocked card.
Code 65 - refuse, exceeding the maximum number of transactions for this card.
Code 75 - refuse, exceeding the maximum number of incorrect PIN codes for this card.
Code 83 - refuse, network error (technical problems).
Code 91 - refuse, it is impossible to send a request (technical problems).
Code 96 - refuse, it is impossible to contact the bank that issued the card.
Code Z3 - online does not work, and offline the terminal rejected the transaction.

What should I do if everything is OK with the card, but the payment does not go through?

The most typical problem when payment does not go through is a failure in the banking system. There may be interruptions in the work of the bank. This may not necessarily be your bank, but the bank that accepts the payment on the client side (who owns the terminal). In this case, you can give 2 tips

  1. Wait and pay later. Failures in work are quickly resolved and in an hour the payment can go through without problems. Usually you can find out about failures by SMS messages or by calling your bank's hotline.
  2. Use another card. If you can't pay with one card, try paying with another card. If the payment with another card does not go through, then this is most likely a failure on the side that accepts the payment. Here it remains only to wait.

Firstly- Get yourself a special card. Do not use a salary card for payment, on which you have all the money. The best is a credit card. It allows in some cases to return part of the purchase amount (CashBack). Usually this is an amount up to 5 percent of the purchase. Be careful, some services charge commissions when paying with kata. And of course, the address of the payment page should always start with https and next to the address there should be a padlock icon (https connection).

Secondly- do not keep a lot of money on the card. The card should have a little more than the amount you need for the purchase. Approximately plus 10% of the total purchase price. The logic is simple - nothing can be removed from the zero card.
When you make a purchase, you simply replenish your card in the Internet bank and receive the required amount.

Thirdly- Make card payments in well-known stores. Read reviews about stores on Yandex.Market. If you pay by card, be prepared for the fact that if you cancel an order, it may not be returned to your card immediately.
The last time I made a payment for an order and then returned the order and money, the return to the card went within 7 days. Remember - no one will immediately return the money to you. Be prepared to wait.

Regardless of whether you use the Qiwi payment system for the first time, or make financial transfers in it every month, there is always the possibility of encountering a problem in the face of various technical errors. In our article, we will talk about the most common Qiwi errors and talk about all the available methods for solving them.

Technical errors in the Qiwi payment system most often occur during account login. In practice, there are several options for dealing with this situation. To get started, simply check your login details and make sure they are entered correctly. If the attempt to enter was interrupted even after carefully checking the password and login, then in this case you should wait a few hours. There is a high probability of carrying out technical work on the side of the payment system. However, if even after several hours of waiting, you still cannot log in to the system, then there is a reason to contact the support service to find out the reasons for the error.

Qiwi wallet certificate error

If you see a Qiwi wallet certificate error before your eyes, then you should not be nervous again, as everything can be fixed without contacting the support service. To get started, look at the bottom left corner of your screen where the clock is located. To work in the Qiwi system, the obligatory coincidence of the date inside the computer and inside the system is required. The fact is that the difference in time zones can lead to confusion in automatic reports, and this is just fraught with errors.

If changing the date and time did not help you, try restarting your computer after clearing the browser cache. It is worth noting the possibility of infecting your computer with viruses, so without special antivirus software you will not be able to solve the problem.

Error making a payment in the Qiwi system

In some cases, errors may also occur during the payment process. In practice, the text of all such errors is different, but the essence always comes down to one thing - the incorrect operation of the payment system. In this case, the most reasonable solution would be to wait - leave attempts to replenish an account or transfer funds to a relative for a few hours. Believe me, the system staff is aware of all the existing problems, so it would be better to wait a bit and make the transaction again.

Qiwi error codes

List of additional Qiwi error codes and how to fix them:

  • Qiwi error 155 - try again later.
  • Qiwi error 200 - please try again later.
  • Qiwi error 400 - please try again later.
  • Qiwi connection error - please try again later.
  • Qiwi undefined error - try again later.
  • Qiwi error incorrect account ID - check the correctness of the entered data.
  • Qiwi authorization error - check the correctness of the entered data.
  • Qiwi gateway error - please try again later.
  • Qiwi unexpected token error - try again later.
  • An error occurred while sending a payment to MTS - try again a little later.
  • Qiwi server error - please try again later.
  • Insufficient funds error - top up your e-wallet balance.

Conclusion

If a Qiwi error occurred during the operation, you should not be nervous and worried - your money will not go anywhere from you. It would be better to just wait and try to repeat the payment a little later. Maintenance work can be carried out on the servers of large financial companies, so no one is immune from instability in making or receiving payments.