The MobilePay SDK enables your app to receive payments through the MobilePay app.
How it works
-
You initiate the payment from your own app through the SDK.
-
It automatically switches to the MobilePay App where the user is asked to sign in.
-
The user confirms the payment.
-
The receipt is shown and the user can either tap "videre" or wait one second. A counter is showing the time remaining.
-
MobilePay switches back to your own app together with a MobilePay transactionId.
- Check out MobilePay AppSwitch documentation on github.
- Make sure you generate unique order ID’s, otherwise calling Refund endpoint can cause trouble.
- Make sure you do polling on payment status on your backend and do not rely on getting the response from MobilePay through the SDK. If your backend get a status ‘Reserved’ – the user has swiped and the order can be completed and payment can be captured though the MobilePay AppSwitch API.
- Use App code obfuscasion to make it more difficult to do reverse-engineering.
- Make sure you do backend validation of the reservation details from the app, e.g. the amount.
- Testing must be done in production with real money, however you can do testing in the SDK from the app by using a test merchant id to get started.
Latest version is 2.2.0. See the release notes here
For technical questions about the MobilePay AppSwitch SDK or other related questions, please contact us via e-mail at [email protected]
Please look at the MobilePay Developer Portal for further details MobilePay Developer Portal
The MerchantID for testing depends on which country you are targeting. The following IDs can be used:
APPDK0000000000 - Denmark
APPFI0000000000 - Finland
When the test MerchantID is used you are able to complete the payment flow from a user perspective without transferring any money.
Please look at the wiki page for further details wiki site
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent