The release of the new version of the payment application Mobilepay has not gone without problems.
Payment requests that were waiting to be paid in the old Mobilepay application were not transferred to the new application, but disappeared. Adobe Stock / Tiina Somerpuro
Contacted Iltalehti Jani says that updating the Mobilepay payment application caused a surprising problem.
It was known that the old app will stop working when the new one is released. However, what users were not informed about in advance was the fate of payment requests that were waiting for payment in the old application.
According to Jan, he had about fifty requests for a total of about one thousand euros waiting for payment. When the old application stopped working, these pending requests reset and disappeared completely.
Jani is upset that there was no warning.
– Every ethical and possibly legal principle related to the banking industry is violated here, he states.
– No other bank can reset a customer’s debts without warning and not inform about it, he continues.
“We add information to our own channels”
Communications Manager at Vipps Mobilepay Miranda Falk confirms to Iltalehti that unacknowledged payment requests from the old application are not automatically transferred to the new application, but must be entered again in the updated application.
– If our customers need detailed information about old payment requests, we ask them to contact our customer service. If necessary, our customer service will send payment request history information by e-mail.
According to Falk, customer service has received “some contacts” about this. The problem had not yet been reported on the Mobilepay website on Monday morning.
– We will also add information on the subject to our own channels.
On Monday before noon, a warning about the problem was published on Mobilepay’s social media.
– We apologize for the situation, the company wrote on Facebook.
The warning has now also been added to Mobilepay’s website.
Mobilepay’s communication did not answer Iltalehti’s question about whether the problem was already known before the application was updated, and if so, why was it not warned in advance.
If the embed is not visible, check it out here.