Integrating payments in mobile apps

This guide will help you to integrate Mollie in a mobile app for devices such as mobile phones and tables. Several factors should be considered, such as legal, security and technical considerations.

Security considerations

Note that your app is distributed to and executed on mobile devices after being installed from the app store. Since you do not control the mobile device, you should not put Mollie API keys inside the app. If the app is installed on a rooted device, any keys in the app can easily be extracted by an attacker. Even on a non-rooted device, the keys could be stolen by a MITM proxy server.

In principle, you should consider the device your app is installed on untrusted.

To make matters even worse, any API keys shipped with your app cannot be reset, since that will break all installed apps that use the same API key.

Hence, any communication with the Mollie APIs must not be done by the app but by a trusted back end service under your control. This service should authenticate your app, perform any needed API calls with Mollie and forward any information needed by your app such as the checkout URL to the app.

Integrating with other mobile apps

Your customers will expect your app to play nice with the apps they use for making payments from their mobile device, such as the banking apps of iDEAL issuers or the Bancontact app.

These apps will often use custom URL schemes which you will need to take extra precautions with to make sure that any redirects to these custom URL schemes cause the app to open. To make it even more complicated, some apps are not registered to a custom scheme but to the prefix of a regular (HTTPS) URL.

When your customer finishes the payment using the app, the banking app won’t know how to return to your app. You will need to use your custom scheme to return to your app after the payment. Mollie’s API accepts custom URL schemes for the redirectUrl parameters.

Note that this is usually handled correctly if you open the checkout URL in the mobile device’s default browser instead of an embedded WebView inside your app.


Webhooks cannot be sent to mobile devices And since the payment status is not always known when your customer returns to the app, you cannot rely on checking on your customer’s return to your app.

You should set the webhookUrl parameters to and endpoint on your trusted back end service, which then sends a silent push notification to the app. The app can then show the appropriate messages or take appropriate action.