MobilePay is a mobile payment application developed by Danske Bank. They merged with Vipps in 2022 to become Vipps MobilePay. When selecting MobilePay, customers will be prompted to enter their mobile phone number. While customers new to MobilePay will be guided through a registration process, returning customers will be prompted to open the MobilePay app on their smartphone and approve the transaction. As a digital wallet, MobilePay is responsible for securely storing the customer's card details, enabling them to easily select their preferred card at checkout. The transaction is ultimately processed and authorised by acquiring banks, as with standard card transactions.
| Supported customer countries | DK, FI |
| Supported currencies | DKK, EUR, NOK, SEK |
| Refunds |
Full and partial refunds permitted for up to 365 days. |
| Chargebacks |
Payments may be subject to chargebacks. |
| Zero-authorisation |
Zero-authorisations can performed by enabling Account Checks, if supported by your acquiring bank. |
| Recurring payments |
Not supported. |
Requirements
- MobilePay can only be offered by merchants operating in countries within the European Union (EU) and/or European Economic Area (EEA), and the UK. MobilePay is particularly popular in Denmark and Finland.
- To integrate MobilePay into your checkout, you are required to have a Merchant Id (MID) that will allow you to process e-commerce (ECOM) transactions. This is because, despite the customer approving the payment using MobilePay, ultimately a card transaction is processed and this necessitates you having a relationship with an acquiring bank.
Trust Payments only supports MobilePay transactions processed using Mastercard and Visa-branded payment cards.
Configuration
- To enable MobilePay on your account, please get in touch with your account manager. You will need to provide an image of your company logo that will be displayed to the customer in the MobilePay app when they are prompted to authorise the payment. In turn, we will provide a test sandbox account that you will need when testing your implementation.
- Modify your POST to Payment Pages as needed:
Field name Required during payment session
(Either included in POST by merchant or entered by customer on Payment Pages)
Required in POST Description billingcontactdetailsoverride No No "0" – Uses address details submitted in the POST (this is the default behaviour if the fields are not submitted).
"1" – Uses address details from the customer’s wallet.Value 1 cannot be submitted if no physical goods are being delivered.
customercontactdetailsoverride No No
Notifications
Once a payment has been authorised, funds will be settled using the same process as followed by card transactions.
Before you begin testing, we recommend that you configure notifications that are processed at the following stages of the transaction life cycle:
- URL notification processed on authorisation. Click here to open instructions in a new tab.
- URL notification processed on settlement. You will need to contact our Support Team and request a new rule is configured to be processed on settlement of MobilePay transactions.
We recommend including at least the following fields in your settlement notification:
- Settle Status (settlestatus)
- Settled Timestamp (settledtimestamp)
- Site Reference (sitereference)
- Transaction Reference (transactionreference)
Check the notification
You will need to check the contents of each notification received and respond accordingly by following the processes outlined in our URL notifications documentation. In particular, you will need to look at the updated settlestatus value:
- On authorisation: If the settlestatus is “0”, “1” or “10”, the payment has been authorised and you are not required to take further action at this time. However, values of “2” or “3” indicate funds are not scheduled for settlement (suspended and cancelled, respectively).
- On settlement: If the settlestatus has been updated to “100”, this indicates that the funds have been settled. Alternatively, if this has been updated to “3”, this indicates there has been a problem and the payment was subsequently cancelled.
Testing
You will need to test your solution before you can begin processing live payments. Test transactions are processed through your test Site Reference.
Before you get started, you will need to install the MobilePay testing app to a smartphone in your possession and sign in using one of the test mobile phone numbers provided by MobilePay.
Click here for further details (link to external site).
When performing test transactions, your browser will be redirected to the MobilePay testing environment to simulate a payment, where you will be prompted to enter a phone number to continue. Here you will need to enter the same mobile phone number you used to sign in to the testing app. After signing in, a 5 minute countdown is displayed in the browser.
You will have 5 minutes to open the MobilePay testing app and approve the pending payment. You will be presented with the full transaction amount, the name of your shop and an option to choose your preferred card for payment (these are test cards provided by MobilePay for testing purposes).
Swipe right on the "Authorise" slider to approve the transaction.
EMV 3-D Secure
It is at this point in the checkout process that EMV 3-D Secure is performed to authenticate the transaction.
About 3-D Secure
3-D Secure is a form of Strong Customer Authentication (SCA) designed to reduce fraud and chargebacks during e-commerce transactions. It allows card issuers to provide an extra level of protection, by authenticating cardholders at the point of sale. Click here to learn more.
For enhanced security, the card issuer may force step-up authentication, where the customer is required to take additional steps to verify their identity (e.g. reviewing and approving the order in their banking app). If this occurs, the amount of time the customer is allowed to complete the transaction is increased to 20 minutes.
Otherwise, the transaction will be treated as "frictionless" and the customer will not be interrupted.
If the transaction is ultimately successful, the app will display an "Authorised" response. Meanwhile in the browser, the page will update to show the status of the transaction (e.g. success / decline).
Customers will follow this same process when performing payments in the production environment.
Cancelling/refunding MobilePay transactions
Prior to settlement, you can cancel a pending MobilePay transaction using Portal. Click here to learn more.
The ability to cancel MobilePay transactions is supported for merchants with a Trust Payments acquiring account. If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.
Following settlement, you can instead refund a MobilePay transaction using Portal. Refunds for MobilePay follow the standard settlement flow for card transactions, with funds typically returning to the customer within 24 hours. Click here to learn more.
