​​​MobilePay Developer

Getting started with MobilePay AppSwitch

MobilePay AppSwitch enables merchants to offer in-app payments with MobilePay. This site will guide you through the process of implementing MobilePay as a payment method in your merchant app.


On this site, you can access the Software Development Kit (SDK) for MobilePay AppSwitch as well as APIs for backend-to-backend communication.

You can also find FAQs, information about integration and test as well as example code on GitHub*.

* GitHub is an external site which is not owned by MobilePay. MobilePay is not responsible for technical errors or downtime on GitHub.​​


Learn more about how to implement MobilePay AppSwitch. Get access to the SDK, APIs and other relevant documentation.

Go to Integration​​


Find information on testing, including test IDs, error codes and testing of your app and backend integration.

Go to Test​​​


In the FAQ, you can find the answers to the most frequently asked questions.
MobilePay AppSwitch is currently available in Denmark, Norway and Finland, and supports native apps for iOS, Android and Windows Phone. If you need assistance to implement the solution, or if you want to implement MobilePay AppSwitch in a non-supported language (e.g. PhoneGap, Appcelerator Titanium and Xamarin), we recommend that you contact Trifork or your preferred frontend or backend developer at your own expense.


  • A Danish/Finnish/Norwegian VAT ​identification​ number
  • A MobilePay AppSwitch agreement
  • A native app (MobilePay AppSwitch supports native apps for iOS, Android and Windows Phone)
  • Compliance with the rules and regulation for in-app puchases set by Apple, Google and Windows.
To use MobilePay AppSwitch, all services and products sold through the app need to be consumed outside the app. This means that MobilePay AppSwitch cannot be used for sale of digital products and services that are used in the app. It is your responsibility to make sure that MobilePay AppSwitch can be and is allowed to be used in relation to the merchant app. It is up to the merchant to make sure that the rules and regulations that apply for the merchant app and sales from the merchant app are complied with - including rules which the app stores (e.g. Apple, Google, Windows) at any time put forward for development and use of merchant apps.
At our repository on GitHub you can always find an updated list of operating systems supported by the MobilePay AppSwitch SDK.
MobilePay AppSwitch supports native apps for iOS, Android and Windows Phone. Using the AppSwitch SDK's should be possible on various cross-platforms as well, however we do not test the SDK's on any cross platforms, or provide support for it in any way or form.
Yes, we have developed a Capture Amount API, which allows you to make payment reservations.
​Yes, we have developed a Refund Amount API, which allows you to make either full or partial refunds directly from your own systems.
To ensure a good user experience, you must thoroughly test your app before launching MobilePay. All information related to test is gathered here. We recommend that you read the information on the site and go through the test cases.
The MobilePay AppSwitch backend is based on REST API's and can be used by practically any programming language​.
All information related to test is gathered here. We recommend that you read the information on the site.
When the requested payment has been completed in MobilePay, a signed payment ticket is returned to the merchant app. The signed information contains the original merchant order ID and the MobilePay transaction ID. The MobilePay SDK validates the signature and ensures that the order ID given to the MobilePay SDK by the merchant app matches the order ID received from MobilePay.
Yes, you can create as many ID’s as you need. The IDs can be connected to one or more of your accounts depending on your preferences.
No, MobilePay AppSwitch can be used for person-to-business transactions only.