MobilePay
Intro
In PilotphaseMobilePay is a Danish-Finnish mobile payment app.
With over 6 million users across both countries, native app integration, and server-to-server support, you can let customers pay easily and accept payments efficiently for your business.
You send a standard request to our platform to open the MobilePay app on your customers' mobile device.
The integration is very easy, as you only need to send one additional parameter along with your request.
Integration
Redirect your customers to the MobilePay app via integration methods Hosted Checkout Page or Server-to-server. Find a high level overview in the "Zahlungsablauf" chapter.
Add the following properties to a standard CreateHostedCheckout/CreatePayment request:
{
"cardPaymentMethodSpecificInput": {
"paymentProductId": 340,
"authorizationMode": "SALE",
"redirectionData": {
"returnUrl": "https://yourReturnUrl.com"
}
},
"order": {
"amountOfMoney": {
"amount": 100,
"currencyCode": "DKK"
}
}
}
| Properties | Description |
|---|---|
|
order.amountOfMoney |
amount: The gross amount you want to charge for this order. |
|
cardPaymentMethodSpecificInput |
paymentProductId: The numeric identifier of the payment method on our platform. Find this id in the "Überblick" chapter. For payments requested via CreateHostedCheckout, it instructs our platform to send your customers directly to the MobilePay-branded version of our Hosted Checkout Page. If omitted, our platform sends your customers to the Hosted Checkout Page instead, allowing them to choose this or any other payment method that is active in your account. authorizationMode: Set to either "FINAL_AUTHORIZATION"/"PRE_AUTHORIZATION"/"SALE" depending on whether you want to process payments in authorisation/Direct Sale mode. returnUrl: The URL we redirect your customers to after the payment has been finalised. |
Zahlungsablauf
Depending on your customers' device(s) used, differences apply:
With a desktop and a mobile device
This flow involves both your customers' mobile/tablet and desktop device interacting with each other.
- Your customers finalise an order on their desktop device in your shop and select MobilePay.
- You send this CreateHostedCheckout/CreatePayment request to our platform.
- You redirect your customers on the desktop device via the redirectUrl (For CreateHostedCheckout requests) or merchantAction.redirectData.redirectUrl (For CreatePayment requests) to the MobilePay portal.
- Your customers enter their mobile phone number on the MobilePay portal.
- The mobile/tablet device opens the MobilePay app. Your customers confirm the payment in the app.
- We receive the transaction result.
- The mobile/tablet device displays the transaction result in the MobilePay app.
- We redirect your customers to your returnURL on their desktop device.
- You request the transaction result from our platform via GetPaymentDetails/GetHostedCheckout or receive the result via webhooks.
- If the transaction was successful, you can deliver the goods / service.
With a mobile device
- Your customers finalise an order on their mobile device in your shop and select MobilPay.
- You send this CreateHostedCheckout/CreatePayment request to our platform.
- You redirect your customers via the redirectUrl (For CreateHostedCheckout requests) or merchantAction.redirectData.redirectUrl (For CreatePayment requests).
- The mobile device opens the MobilePay app. Your customers confirm the payment in the app.
- We receive the transaction result.
- The mobile/tablet device displays the transaction result in the MobilePay app.
- You request the transaction result from our platform via GetPaymentDetails/GetHostedCheckout or receive the result via webhooks.
- If the transaction was successful, you can deliver the goods / service.
Testdaten
In unseren Testszenarios finden Sie Testdaten und detaillierte Instruktionen.
Stellen Sie sicher, den korrekten Endpunkt anzusteuern und zurück zum Live-Endpunkt zu wechseln, sobald Sie Ihre Tests abgeschlossen haben