At the latest app update I have now been completely kicked out of MobilePay on my FP6.
The “Open in browser” bypass trick doesn’t work anymore on the initial MitID authentication (using kodeviser key), when trying to login for the first time or after the usual clearing app data when the app tries to authenticate with Google Services and fails, shutting me out.
First I thought it was browser dependent, I usually use Vivaldi, buy it fails as well on the OS build-in browser and on Brave as well unfortunately.
So - has anyone managed to successfully logging in and getting past MitID authentication?
Otherwise I guess I must finally accept defeat and look for other payment solutions (cash cough cough).
Martin, thanks for the heads up and for creating a new thread here!
I have now tried and get the same result as you. Only, It’s not possible for me to make MobilePay forget Brave as browser. I have deflagged Brave as standardbrowser, I have deleted mobilepay app and reinstalled it, and also restarted the phone, but to no effect.
I have also tried to force open the MitID authentification in the Murena-browser which it did but I couldn’t authenticate, the process stopped after the second step of three.
The MitID authentification went fine in Brave browser but MobilePay just didn’t recognise it (similar to the old error we had last year).
They have one week to answer me. (They wrote to me after two days, wanting to have “a dialogue” but I replied that I wanted to see the records first and then we can have a dialogue…).
It’s like the world of decision-makers has collectively gone mad and is completely fact-resistant…
Well, right - it’s the exact same situation for me. I used the Vivaldi browser for the MitID verfification, but got the same result as you.
It seems like MobilePay has changed the Google Play verification making it the first thing that happens when you have gone through the MitID verification process.This means that we don’t even a short time period where it works.
@Bettina - it’s really great that you keep fighting. I’m looking forward to hear what’s stated in the records.
I read your letter again, really good questions. I’m curious about what that will lead to. I wish they would solve the issue with MitID app, but I guess that is not likely to happen. However I’m really surprised that AltID is working, so maybe they are beginning to wake up after all.
I had the same problem a couple of weeks ago. I was able to install MobilePay on my FP6 using Chrome as a default browser. MobilePay worked for 2 days just fine.Then, it just stopped working. The same problem - although Mit ID authenticates me just fine, MobilePay does not register it and refuses to continue the installation. No solution so far…
I am sorry if my question sounds stupid, and I might be not fully into the picture of what’s happening, but have you all checked with your bank or whatever payment provider if no re-set or de-linking of old set-up needed for the new registration to be succesful?
I know, it might be a bit lame to ask, as someone said it worked for a couple of days and stopped, then my question is entirely obsolete. But I wonder what the service provider(s) say?
Normally customer service agents do not know much really, but you might be lucky to get a clever one fingers crossed.
I work for a bank and quite often something may go wrong at bank’s end where some re-set, or unblocking might ne necessary. I speak to people with iphones, android devices and also odd fairphone user or came across graphene one - all of them could use our banking app, which does not guarantee your bank provides equally flexible solutions, but still I just wonder if it’s not their end at fault. I hope not to wind you up
P.S. Some banks support only one linked device per user and linking more can cause problems - I mean if they still see old device/system version linked and the new one on the top of it, that sometimes causes problems but in fact it’s a mine field.
If you search this platform for the word “MobilePay” you will realise that this is a deliberate dicision from the monopoly of Danish, now Nordic Mobilepay - they have made a decision to use Google Play Integrity API which blocks out phones other than Google Android. We have complained for more than a year now, and it has only worked fairly OK from April to now (2026). They couldn’t care less.
Bad news indeed . Just a thought, but maybe the complaint should go to the EU as well, since Vipps MobilePay merged and became an international company?
I am having the exact same problem. Thanks to Bettina and Martin for putting in work!
Does anyone have experience with spoofing google API, and getting access through that? It seems like that requires rooting your phone, which isn’t a viable option.
It is hard to live in Denmark without google API access, apparently.
Count me among the people with the same issue. I’ve just spent a couple of hours, trying to uninstall/install MobilePay, clearing cache, using different browsers, etc. No luck…
and yes @martinielsen , EU would probably be a good idea! Do you know who the proper institution would be?
(I never got a reply from the Norwegian Finanstilsynet which MobilePay referred me to). I will also contact the Danish Ombudsman, but first I am waiting for the records which DIGST should send me this week.
I’m a little curious. Is MobilePay considered “samfundskritisk” (critical to society). Could the Danish “ombundsmand” and DIGST not just say that MobilePay is private owned and therefore it’s up to Vipps MobilePay to decide what kind of mobile phones (and mobile OS’s) they want to support?
I am certain that Mobile Pay is not considered “critical infrastructure”. It may be widely used but it is just a private payment solution. You can always choose to pay in cash or using VISA, Mastercard or your trusty old Dankort
I think the more important aspect here is the monopoly part, because when you de facto have a monopoly (which MobilePay more or less has), the responsibilily for inclusion becomes bigger: Mobilepay i monetariseringsmodus - hvor er Monopoltilsynet?
If it isn’t considered critical infrastructure, I don’t think it would make sense taking the complaint to the EU. Then there is no other options than complaining to Vipps directly unfortunately. But I agree with @Bettina, the more contact the better, no matter what useless answer they can deliver.
However, I can try to figure out which EU institution that can be contacted.
fingers crossed.
. Just a thought, but maybe the complaint should go to the EU as well, since Vipps MobilePay merged and became an international company?