Vipps/MobilePay is a leading mobile payment solution in the Nordic region, formed through the merger of Norway’s Vipps and Denmark’s MobilePay. The platform enables individuals and businesses to send and receive money instantly using a mobile phone number, without the need for bank account details. 

This payment provider allows you to integrate with a Vipps/Mobilepay merchant account and allow customers to pay using a MobilePay/Vipps app on their phone.

To set up this payment provider you need to obtain the following from your Vipps/MobilePay account:

  • Client ID
  • Client Secret
  • Subscription key
  • Merchant serial number
  • Webhook Secret (unless Enable Automatic Webhook Registration is enabled)

Add these values to the checkout handler settings:

Figure 1.1 Vipps/Mobilepay settings

As a part of setting this up, you need to think about webhooks, as Vipps/MobilePay sends webhook notifications after every transaction to ensure the system receives payment updates even if the normal payment flow fails. These notifications are validated using a Webhook Secret.

You can either:

  • Specify a webhook secret manually
  • Check the 'Enable Automatic Webhook Registration' option to register a new webhook if the field is empty
  • Check the 'Force Webhook Registration' option to delete all existing webhooks for the current site URL and create new ones

Next, consider the payment parameters:

  • Use Card Payment – Enables standalone card payments instead of the default Vipps wallet payments through the Vipps mobile app (not available in test mode)
  • Auto Capture – Automatically captures the payment immediately after authorization so the customer is charged right away
  • Support Split Capture – Allows capturing the payment in multiple parts instead of capturing the full amount at once (may require activation by Vipps)

Test mode switches the provider between the test endpoint (apitest.vipps.no) and the production endpoint (api.vipps.no)

Debug logging enabled detailed logging of all http requests and responses - they are stored under the Log tab in the order details view.