MobilePay stopped working, again

Using /e/OS Applications
1

Since the discussion at MobilePay app has stopped working since app update on Fariphone 4 and subsequent fix, MobilePay has stopped working for me again. I have Fairphone 4, official build that I installed myself to replace the stock ROM. This issue appeared sometime during /e/OS 3.2 and still persists after upgrade to 3.3. I suspect it was caused by MobilePay version upgrade. Am I the only one, or do others see the same?

The error message I see is:

MobilePay-sovellusta ei voida käynnistää. Voit kokeilla MobilePay-sovelluksen poistamista ja ladata sovelluksen uudelleen Play Storesta. Virhe voi joihtua myös siitä, että käytät laitetta, jota on muokattu. Tässä tapauksessa voit ottaa yhteyttä laitteen myyjään.

1 Like
2

Hi there.

Same here on my FP6 since the app was updated to version 9.51.0 yesterday. Fails with the message that “Something went wrong” on the MitID verification step, which is the Danish national digital ID. Using a key generator since the MitID app doesn’t work either. Now looking for a way to downgrade the app, fearing that it will not solve the issue. My guess is that the app is now looking for some Google security components on the phone and fails. This is just too bad.

Update:
I actually managed to solve the issue with the current MobilePay version by using the Microsoft Edge browser. The MitID security step is opening a link via a browser, and the other browsers on my phone all failed this step. So I installed the Edge browser, set it as default browser, rebooted the phone, opened the Edge browser, just jo make sure it was running in the background, and then tried to set up MobilePay again, and this time all steps was accepted. I don’t know if your issue is identical (in Finland?), but it is worth a try mayby? Also this solution would apply to all users in Denmark.

3

No, my issue is not identical. The issue is not with any external identity provider. For me, MobilePay only requires strong auth when setting up for the first time, and I have not had any issues with that step. Probably this depends on which country you are in. And for me, browser is not involved. It all happens within the app itself.

4

It is the same for me, only on the first setup, but somehow changing default browser tricked the app to bypass, what it is it is checking. But unfortunately I just noticed, that after one day with it working as usual, MobilePay once again identifies the phone as “rooted”, the same message that you get. So it is very unfortunate that it has become permanently unusable.

5

So I deleted the app and repeated the steps above, and now the app works again - only for a while probably. Strange.

6

Aha, OK, so exactly the same as it was for me, until it worked without issues for a while. Back then, I interpreted this behavior to mean that Play Integrity results that /e/ OS got did not satisfy MobilePay, but it checked Play Integrity only occassionally and strangely, not as a first thing before allowing usage. But that was guessing based on how things looked, I have not gathered any hard evidence for that.

Indeed, currently my installation fails all Play Integrity checks, even basic integrity. I used Play Integrity API Checker app to check that. I think there was a time when basic integrity passed. So maybe this was just caused by /e/ OS regressing on Play Integrity?

1 Like
7

Ah I was not aware of that tool, but I just checked and mine also fails all three levels. I’m running the official version of e/OS with a re-locked bootloader.

I’m beginning to get second thoughts about this journey. It is getting more and more complicated for non-expert level guys like me. It was hard enough to replace the OS in the first place. And my folder of malfunctioning apps is getting bigger.

I have attempted to find the previous version of MobilePay on APK mirror etc. without any luck, hoping downgrading it would help. Would it change anything if the app was installed via another app store? I’m currently using the native e/OS App Lounge.

8

Was just offered version 10.2.0 and updated. Fingers crossed.

9

Version 10.2.0 unfortunately has the same issue.

10

HI! I’m not sure I follow everything you write here. But my MobilePay app stopped working in June 2025. I have a Fairphone 5, original eOs. However, I just tested it today, and now it works. I’m not sure if it was the fix Murena made in September, because I don’t think I have tested it since August 2025 (according to this thread: MobilePay app has stopped working since app update on Fariphone 4 - #51 by SalmonSnake )

My eOS version is 3.3. I used Brave browser.

1 Like
11

PS - I also found this thread: Danish users of Fairphone E-OS - #26 by Bettina

where DK_murena_user writes this:
”You can make it work if you have the Brave browser installed and defined as standardbrowser and you have a MitID Nøgleviser. We are currently working on a hack to make the MitID app work and I will post if we succeed - but until then you can use the above version to sign in to all apps requiring the MitID sign in.”

1 Like
12

I think that it has to do something with the Revolut fix that was introduced some time ago. Or at least Mobilepay started to work again roughly at the same time.

1 Like
13

@Bettina @SalmonSnake so if MobilePay currently works for you, keeping in mind that in the broken case it may at first seem to work, then fail a day or two later, could you run Play Integrity API Checker or some other Play Integrity checker app and report here. I am just wondering that maybe the difference is that some /e/ OS configs pass Play Integrity, at least the basic level, and others do not. Now we have me and @martinielsen with problems and no Play Integrity, what is the crucial difference to you two?

Note that live in Finland, not Denmark. I do not have, cannot use, do not have to use MitID. So while MobilePay issues mesh with MitID issues for you all in Denmark, this thread is not about MitID. Any issues with that one are separate. I would edit the original post make that clear, but I cannot.

1 Like
14

Hi Otto, I’m sorry, I wasn’t aware that you used MobilePay in Finland without MitID!

Our (Danish) problem is this: MobilePay around June / summer 2025 changed their policies so that you could only authenticate yourself in a chromium / google based browser. However, Murena made some kind of fix in autumn (I think) so that we can authenticate in Brave browser. I only discovered this yesterday, so MobilePay might in fact have worked fro me for several months without me discovering it :slight_smile: I have gotten used to it not working… But this also means that our problem does not as such have to do with MitID but about authentication. And I guess you also authenticate yourself on MobilePay in Finland, just using another method?

As I cannot read your Finnish error message, I don’t know if your problem has to do with authentication in the “wrong” browser? Of whether it’s something else. But if it does have to do with authentification, I would switch your standard browser to Brave and try again.

Regarding your suggestion about running Play Integrity API Checker, I had difficulty downloading it, but managed in the end. I don’t know what the app does but I can tell that it gave a red cross to each of the three criteria. Not sure what that means and if it helps you?

Sorry I couldn’t help more!

PS - you can edit posts using the three dots below the writing and then choose the pencil.

1 Like
15

Hi Otto, I’m sorry, I wasn’t aware that you used MobilePay in Finland without MitID!

No problem, it is easy to do false assumptions if things are not explicitly mentioned!

And I guess you also authenticate yourself on MobilePay in Finland, just using another method?

Correct, when setting the app up for the first time, social security number is asked and then some auth flow ensues. I do not remember the details, but probably the usual one around here, either via your bank or Mobiilivarmenne (a thing tied to your carrier that does not use a browser). I have not had any issues with that, ever.

As I cannot read your Finnish error message, I don’t know if your problem has to do with authentication in the “wrong” browser? Of whether it’s something else. But if it does have to do with authentification, I would switch your standard browser to Brave and try again.

AI translation, seems correct: The MobilePay app cannot be launched. You can try uninstalling the MobilePay app and downloading it again from the Play Store. The error may also be caused by using a modified device. In this case, you can contact the device vendor.

Auth succeeded, the app just refuses to run as you can read.

Regarding your suggestion about running Play Integrity API Checker, I had difficulty downloading it, but managed in the end. I don’t know what the app does but I can tell that it gave a red cross to each of the three criteria. Not sure what that means and if it helps you?

It does, it tells me that the app can work even with Play Integrity totally failing. So it is not about (only?) that, like I previously hypothesised.

16

Hi again!

I notice you write: “Auth succeeded, the app just refuses to run as you can read.”

This was exactly the case with our problem. The authentification succeeded but MobilePay refused to accept it. I would assume your problem might have to do with the authentification. Can you delete the MobilePay app and then authentificate again? And if that takes place in a browser, definitely use Brave.

17

Aha, OK, so it is possible that is a single issue after all, just with different auth provider in different countries, but the same problem. Here is what I did and what happened:

Setup:

  1. Removed existing MobilePay installation
  2. Checked that I have Brave already installed
  3. Installed MobilePay again from App Lounge, started it
  4. MobilePay asked for national ID number, phone number, confirmed phone number via SMS
  5. MobilePay asked for auth, redirected to browser for this.
    1. Brave was automatically selected, even though I think I have not set it as the default for anything. /e/ OS fixing things for me under the hood maybe?
  6. Auth was provided by something called Criipto I think. It gave me the usual Finnish choices of various banks and Mobiilivarmenne. I used Mobiilivarmenne as I always do, it passed
  7. MobilePay asked about notifications, I accepted, and asked me to set a PIN code, which I did
  8. Then presented itself as ready to use

Test:

  1. Sent 1 € via MobilePay. It worked

At this point, things looks just as they have always looked: Initial setup works and MobilePay works initially. So another test:

  1. Reboot phone
  2. Send 1 € again. It worked

So this far, things look good. If it still works after a couple of days, I consider everything good. In the bad case I have seen previously and that prompted this thread, some time quite soon I will see the error in the initial post instead.

2 Likes
18

Glad it worked, for now at least! Let’s both check in in a week or so to see it it still works? We actually had a MobilePay update this morning and mine still worked after the update. Crossing fingers <3

1 Like
19

Yes, let’s compare notes in a week!

1 Like
20

So I discovered that you don’t need to delete the app and then reinstall it. You can just clear the app data and start over. Still pretty annoying.

I also learned from help in another thread that you can rollback the app to the latest working version via the manual install functionality in Aurora Store. Unfortunately you need the specific app version code, the numbers inside the ( ) from the working app version, which I do not know, so it is kind of a dead end unless you write all the codes down before updating your apps.

2 Likes