I can't find MobilePay in App Store or Google Play

• MobilePay is a Danish app and can only be used on Danish mobile phones. Your phone's country settings and language determine the content you see in the App Store and Play Store. Therefore, make sure your phone is set to Danish and Denmark as the country.
• If you still cannot find MobilePay, it may be because your phone uses an operating system that we do not support (e.g., Windows).

Jailbreaked/rooted devices

Please note that MobilePay does not work on phones that are jailbroken/rooted or if "unsafe" apps are installed on the phone. If you have a jailbroken/rooted phone and did not do it yourself, we recommend contacting the person you bought the phone from or who helped you set it up. In some cases, the solution may be to completely restore the phone. If you have installed an "unsafe" app, you must uninstall it before you can use MobilePay.

Operating system requirements

Our goal is for MobilePay to work on as many devices as possible, including Android variants that differ from the standard configuration. At the same time, we must comply with strict security, privacy, and regulatory requirements arising from agreements with banks and card schemes, as well as the audits and certifications we are subject to.

Currently, MobilePay requires Google Play Integrity verification, and we also rely on Google Play Services for other critical functionality, including push notifications. This means that MobilePay does not function on devices that lack these components. At present, this dependency is a prerequisite for meeting our security requirements.

As of now, MobilePay works on GrapheneOS under specific conditions:

• The bootloader must be locked
• Google Play Services and the Play Store must be installed in sandboxed mode
• MobilePay must be installed via the Google Play Store

This makes it possible to use MobilePay on a security-hardened and partially de-Googled operating system. At the same time, we recognize that this is not sufficient for all users. It is also not guaranteed that this configuration will continue to work unchanged in the future, although we are not actively attempting to block such setups.

We want to be clear that we are not opposed in principle to de-Googled devices. The challenge is that, in practice, it is demanding to ensure both broad device support and compliance with the requirements we are bound by.