Good to hear, Henrik! Let me know what you hear back, if anything? Not sure what to expect, but I haven’t heard anything yet… it’s been two weeks now.
For me, it at least works better than before, because now I can just delete the app, and then reinstall it and login again. It usually is logged out again with some hours, but at least once, it worked for 2 days 
It’s not optimal, but it’s better than not working at all… And for me, it’s not an option to go back to Google surveillance.
Good to see more people gathered here. Hopefully there will be enough some day to make a difference.
I the meantime I almost stopped using MobilePay as I got tired of the endless re-setup cycle real quick.
Before the app was destroyed I was a weekly, sometimes a daily user, now I barely use it twice a month. I’ve slowly moved back to using cash again (yes I’m that old) and now building up a list of my friends, colleagues and family members bank account numbers. I realized that it is much faster just to make a bank account transfer, than to go through the tiresome setup process, that becomes extra troublesome, because mitID app isn’t working either, and I need to get my key generator fob (kodeviser) to set it up again.
It is a shame, but just a new reality for me. I’ve made a decision, not to go back to Googles version of Android. I try my best to keep this promise to myself. And I’m in the slow process of leaving the tech bosses and migrate to alternative solutions as well. Deleted my 17 years old Apple account last week moving to my 22 years old Google account next. This issue with MobilePay is just a minor bump on the road for me.
You don’t have to reinstall the app. Just go settings - apps - Mobilepay - storage & cache and clear storage. That will activate the login process and Mobilepay will work again for.few times.
thanks, but I think what I do is less or the same clicks and it works
Nah, it actually fixed the issue when i locked the bootloader
@Intherasion - that’s superb. So you can in fact lock the bootloader again. Thanks for letting me know about that 
Ok, so more people suggested that instead of deleting the app and reinstalling it, I should rather clear the storage and then authenticate again. So I did that on Monday morning, and just now - even after a new update from Murena /e/ OS AND an update from Mobilepay, I could still login to Mobilepay without problems. This is the first time it’s lasted 5 days - and counting!
I can confirm that MobilePay (fi) is working as of now.
yeah, mine stopped working again when I checked this evening…
And now it stopped working for me also. Lets see if I can manage without it then.
It is a bit sad, that these kind of hard dependencies to services outside of Europe exist even in European apps and services.
We have national elections in Denmark on March 24, and our national media, DR (Danish Radio), har taken up the topic (in Danish):
First, on Sunday, asking “specialists”: Frustrerede danskere: Essentielle apps fungerer kun hos 2 tech-giganter | Teknologi | DR
And then, they “suddenly” found seven politicnas who “definitely” thought “something” should be done…: Politikere fra 7 partier enige: MitID bør fungere uden big tech-giganter | Folketingsvalg 2026 | DR
We were also a group of volunteers who wrote to the Danish Digitisation department on Sunday, and asked a lot of questions about their addiction to, sorry no (!), their reliance on Google Android: (in Danish, but ask me if you need a translation): Spørgsmål til Digitaliseringsstyrelsen vedr. det offentliges fokus på Google & Apple: https://www.hartmannconsulting.dk/wp-content/uploads/2026/03/20260308-til-DIGST-om-alternative-smart-phone-styresystemer-vs2.pdf
Hi Bettina.
I have been writing with the journalists behind the first article on dr.dk that you mention. Initially just thanking them for their article. I mentioned the issue with MobilePay, which they were not aware. I told them about this discussion here and the fact that a complaint has been filed to Finanstilsynet in Norway. I don’t know if they have any intention on following-up on that, but in that case they might contact me or maybe you, who knows. I hope it is okay?
BW
Martin
of course, it’s great if the media will take an interest! Thanks for being active, Martin!
And by the way: I haven’t heard from the Norwegian Finanstilsynet…
Someone just alerted my attention to this intiative, which is a Google API alternative - apparently Murena is also supporting it? Does anyone know anything about it? https://uattest.net/
here’s an english lang. article linked in this thread, and some french discussion: ARTICLE: Paying without Google
This is really interesting @Bettina, and it may very well be the open source alternative to Google Play Integrity that leaves no arguments for app developers like Vipps/Mobile Pay (or MitID for that matter).
Hi all, lurker here.
I was wondering, how many of you are using the hide “Real IP Adress” function in advanced privacy? It runs via TOR, and that fact might get you in trouble with some services…
I am using mobilepay on a daily basis on my FP4 with /e/OS 3.6 (I install updates asap), and I have had no issues since about january of 2025 (/e/OS 2.6 maybe).
I have disabled the built in browser, and am switching in chromium as default browser when mitid does not work with iceraven/firefox.
My partner is running a FP6 with Vivaldi as fallback, and again no issues with mobilepay. 
Hi stefdk_the
That is really interesting, for my part especially your partners FP6 since I have the same one. Was it purchased directly from Murena? Does it run MitID app? I wonder if I should run another build on my phone, I have replaced the OS myself, with the official build, but re-locked the boot loader, and still get all red on an integrity check (attached), so I must have ruined something bad, since it doesn’t even pass basic integrity. I didn’t expected that result. I don’t use the build-in feature to hide my IP address. Could I ask you, to ask your partner, to run an integrity check on the PF6 and come back with the results here? I know it is much to ask - sorry.
Hi Martin
I run /e/OS on a FP6 that I bought from Fairphone.
I flashed e/OS/ at FP6 launch, before there was an official installer. I flashed the official e/OS/ build and relocked the bootloader.
I have not enabled the private settings Geolocation and Real IP address.
I get the same result as you. Three red X’s.
do you use a google account in microg and app lounge? that is necessary for getting basic integrity.
