This website is designed to help developers with creating payment and login solutions for their websites. If you are a customer who needs help with using the app, please see:
For help with the Vipps app, see vipps.no.
For help with migrating from MobilePay
If you are a developer migrating to Vipps MobilePay, start with the MobilePay migration guides.
If you have an integration that was built by your partner, talk with them next.
For questions about the apps or pricing changes, see vippsmobilepay.com.
How to get help quickly
We offer a wide range of self-service solutions on our merchant portal at portal.vippsmobilepay.com. We encourage you to check there first to see if your question or issue has already been addressed.
For technical questions and inquiries related to API usage, our Integration Services team is available to assist. Please note that most information can be found in our searchable technical documentation.
For non-technical question, the fastest way to get help is to start in one of the places listed below:
|Questions relating to:
|How to get help:
|General questions (e.g., customer relationship, creating sales units, change of admins)
|See Contact info on vippsmobilepay.com.
|Problems with Vipps MobilePay services
|Check the status on the Status pages.
|Applications for Vipps MobilePay products (status, follow-ups, etc.)
|Check the status on portal.vippsmobilepay.com.
|Vipps MobilePay plugins (e.g., WooCommerce, Shopify, Wix, etc.)
|Check the support info for your plugin in the Plugin documentation.
|Vipps MobilePay through a partner (for merchants)
|Contact your partner.
|Vipps MobilePay through a POS (Point of Sale) vendor
|Contact your POS vendor.
|Vipps MobilePay through a PSP (Payment Service Provider)
|Contact your PSP.
|Partner assistance (for partners)
|Check the Partner and Management API documentation.
|Settlements, invoices or similar
|Check the Settlements documentation.
|Suggestions for improvements to Vipps MobilePay products
|Please contact us at vippsmobilepay.com.
For technical issues related to using our APIs, please see the sections below.
If you can't find the answer, please send an email as described below.
What to include in the email
Please email us at firstname.lastname@example.org and include all the following information:
- A detailed description of the problem with a step-by-step description of what you do and what happens.
- A concise, self-explanatory
Subjectline, such as "
- Business/organization details: Organization number (If you are in Norway, find yours at Brønnøysundregistrene, the Norwegian business registry).
- Merchant Serial Number (MSN), found on portal.vippsmobilepay.com. See the portal documentation for a description of how to find your MSN and your other API keys.
- The name of the product or API that you're having a problem with.
- Environment: Is it a problem in the Test (MT) or the Production environment?
orderId, and preferably also
contextId. This makes it possible to find your API request in our logs.
- Date: On which date(s) did the problem occur?
- For API issues, include a complete
response. Plain HTTP from Postman ensures the quickest response. No source code, please. Important: Remove everything except the last four characters from
- Screenshots, if possible.
- Contact information, including name and phone number.
- Other relevant or helpful information.
For the fastest resolution, provide all the above information.
Keeping your colleagues up to date
To include your colleagues in all the communication for this issue,
add them in the
CC: field of the email.
You can add more recipients to an existing issue by adding them as recipients to the email, you are sending.
All updates to the issue will be sent to every recipient of the previous email.
When you email us, we will create a case and assign a case number. For instance
Case 123456 in
Subject line. This is the unique number for the specific case and is
used to connect all communication about this issue in our systems.
Adding additional information
If you want to send additional information about the same issue,
please reply to the email, without changing the
Please remove previous communication when replying to an email. It is also not necessary to quote the previous messages, because we can see them in the case.
For a new problem, please send a separate email.
We will help as quickly as possible, usually in a few hours during normal working hours.
But, due to large variations in the number of requests and the varying complexity of resolving them, we cannot guarantee response times.
If you have a Key Account Manager (KAM), please contact them. If you do not have a KAM, please reply to the issue and add all relevant information.
Reporting multiple problems
For the fastest response, please send separate emails for each problem.
It may result in a delay to add details about new problems into an old case. If you reply to an old issue that has been closed, we will not see the message.
Contact by phone or slack?
Unfortunately, we don't have the capacity to answer by phone. Please send all the above information by email, and we will respond as quickly as we can.
For partners at Partner Plus level or above, it may be possible to set up a Slack channel to assist with communication.
Sign up for our Technical updates for occasional updates relating to the API platform or other technical tools.