I want to test this as well, buy still waiting for the update becoming available on my device.
The 4.1.1 update landed on my Pixel a couple days ago and didn’t fix the MobilePay issues.
3 Likes
It still doesn’t work for me (in DK). MitID authenticates, but MobilePay doesn’t acknowledge it. I use Brave browser. I have tried to switched to ex. Vivaldi but no matter what I do, MobilePay seem to remember Brave… even when other apps don’t. Really weird.
1 Like
Have you tried to remove Brave from your phone and reboot?
Still waiting for the OS update to arrive.
1 Like
No, that I haven’t done. I think I will wait as I haven’t heard that using Vivaldi will definitely help?
1 Like
Well I’m using Vivaldi and the “Open in browser” option works for me. But it still fails on my phone, inside MobilePay after MitID is approved.
1 Like
That’s exactly what happens with brave so no reason to switch browser.
1 Like
/e/ OS 4.1.1 did not fix MobilePay for me, and did not give basic Play Integrity either. Sad.
2 Likes
This may be a silly question. But does this have more to do with MitID than Mobile Pay itself?
MitID works in general. But it seems to be that exact point were Mobile Pay fails?
MitID works everywhere else. Could Mobile Pay fix this issue without compromising their own security when it comes to making payments?
Does that make sense? 
1 Like
Hi Søren.
You could be right, I’m in doubt. I noticed that the MitID authentication process moved from .dk to .no Vipps servers at some point. I don’t know if that is related to this issue, it’s just an observation.
Hi!
I wanted to partake in the topic.
Our Finnish friends at Sailfish OS have also been struggling with MobilePay since the terrible patch, but they have managed to get it working with some older MobilePay version, which didn’t work for me either.
They also use microG so that might help track down the problem?
3 Likes
I have the exact same issue as you all. Thank you Bettina for your efforts, please keep us posted.
1 Like
Martin - I’m guessing, but what I think has changed is that MobilePay has introduced the integrity check from the very beginning. Prevously, it was not checked until after some time, but now they have corrected that “error”.
Of course, this is only a guess, but just like you I wouldn’t be too hopefull - better to be positively surprised.
2 Likes
Well, before the latest update of MobilePay, several of us also had a long period where it actually worked fine.
Could it be that you’re still running on the previous version of MobilePay?
1 Like
I am running v. 10.30.0. I think it is the latest version.
I just recall that I was logged in to microG with a google account for a very short period a while ago but I have removed the account again as I don’t want to use anything from google. I don’t remember if I installed MobilePay during that short period.
Maybe this could be the cause? I am not very technical so I am not in a position to evaluate this myself.
1 Like
I’ve written to MobilePay’s Finnish complaints team to express my feelings regarding the Play Integrity API checks and I’ll write here if there’s a sensible response. In the Sailfish OS forum thread there was a link to a complaint template which I’ve modified slightly to suit my usecase, but the point stands:
It’s dumb to develop a Nordic mobile payment solution as an alternative to Google and Apple if you’re relying on Google’s API anyway.
I’m not exactly holding my breath regarding their response, but complaining is our best way of action at the moment so I’d hope other affected people take the time to do so as well. Also, I tried to specify in my message that I’m not able to make payments with MobilePay as a I can’t log in to the app at all, but let’s see how it goes.
3 Likes
Back in January I mailed a complaint to MobilePay in Denmark, I got this answer:
We completely understand your frustrations — especially with the current global situation.
As it works right now, however, it is a requirement that MobilePay runs on a certified Android or iOS device and is installed from the Google Play Store or the App Store. In section 2.3 of our terms of use, we reserve the right to set requirements for the device’s operating system. We continuously make adjustments to these checks. This is partly for security reasons — it is a combination of our own assessments and assessments that we are required to follow from third parties, such as banks and other payment providers.
That said, nothing is set in stone. We are continuously working to improve the app, and in that connection we will of course pass your thoughts on to the people responsible in this area.
Link to the terms: https://strtermsprod.blob.core.windows.net/terms-and-conditions/2025-11-12-PrivateUser-DK-019a778f-aca4-7657-93d2-8a2cbaf3c7f2.pdf
1 Like
I just now successfully logged into MobilePay!!
Details:
-
I haven’t tried logging in since some weeks.
-
Phone: FairPhone (gen. 6)
-
Current e/os-version:
3.7-a15-20260410607089-official-FP6
(there’s a pending update, I have not yet installed) -
I updated MobilePay from 10.28.? to 10.30.0.
-
When started, I was asked for the usual CPR-number and MitId-login. I chose to change to “Open in Vivaldi” (actually quite fast - before the default mitId login page fully opened).
-
On https://mobilepay.mitid.dk, I entered my MitId credentials and code.
-
Then (back in Mobilepay, no errors shown), I was asked to upload Passport photo, etc. I guess because change of conditions in MobilePay.
-
Note: I’m currently outside Denmark (Spain). Could that be relevant?
After that, I’m in!! Crossing fingers, I’ll stay logged in!
2 Likes
Good news!
But this is strange, because last time I tried I noticed that I was redirected to something like vipps.no or vippsmobilepay.no to enter the MitID credentials. Maybe something changed here?
Yes, I saw you wrote that earlier. Also the fact that I clicked “Open in Vivaldi” quite fast. Maybe before some redirects? Also, I’m in another country. Do you have access to some VPN? Maybe you could try from outside Denmark using a VPN?
1 Like