MobilePay - Send & receive payments

Hello! This message is from MobilePay. You might be familiar with our app that simplifies payments: sending money to friends (or even strangers), making purchases in stores, online, or within other apps. 

There's more you can do with MobilePay:

- Request money

- Receive money

- Settle bills

- Create recurring payment arrangements

- Share expenses among a group

- Use a 'money box' for collecting funds

- Send scheduled money gifts wrapped in digital wrapping paper

And did we mention that sending and paying with MobilePay is completely safe and free of charge? If that doesn't sound very simple, then we don't know what does.

To use MobilePay, all you need (besides parental consent if you're under 18) is a payment card and an account in a Danish bank, as well as a phone number, email address, and MitID.

Please note, MobilePay is designed for personal use only. However, if you wish to utilize it for business purposes, you can easily set up a business agreement. Find more information and details at mobilepay.dk.

Developed in the Nordics with a passion for streamlining processes, MobilePay is available in Danish, English, Swedish, Finnish, and two types of Norwegian.

FAQ

Why do I get "PUSH_MESSAGE flow not allowed" error while creating a payment?

Sales units (i.e., Merchant Serial Numbers) must be especially approved to use this user flow. The merchant must have received the phone number from the customer with their consent for sending a payment request to the user's phone via Vipps or MobilePay app. 

Why do I get "ExpiresAt not allowed" error while creating a payment?

Sales units (i.e., Merchant Serial Numbers) must be especially approved to use this feature. The user experience, including the standard timeout, should be as consistent as possible, so this should only be used in special cases. To request this feature, please contact your key account manager, your partner manager, or customer service.

Why do I get "The parameter PersonalQr is invalid." when initiating payments?

The PersonalQr only accepts the input from the users personal Qr code. This is retrieved by scanning the users Qr code in their Vipps or MobilePay app. If you receive "The parameter PersonalQr is invalid." when initiating payments it means that we cannot recognize the input you are supplying in the request. Double-check the input to ensure that the entire content of the Qr is supplied. And verify that it is the Qr from Vipps or MobilePay app that is scanned and not for example product barcodes or other Qr codes near the scanner.

Can payments be "mixed and matched" between the eCom API and the ePayment API?

You can't use the eCom API to do anything with payments initiated with the ePayment API, but you can use the ePayment API to capture, cancel, query, and adjust payments initiated with the eCom API.