While we work to bring together the best features of both Vipps and MobilePay platforms, some information is still under development and will be updated soon.
For those in need of assistance with MobilePay, we recommend checking out the MobilePay Developer Support page. Here, users can find a wealth of information and resources to help navigate the platform and troubleshoot any issues that may arise.
We help developers with technical issues
We offer a wide range of self-service solutions on our portal at portal.vipps.no. 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 almost all requests we receive are already covered in our searchable technical documentation, which can be found at searchable technical documentation.
To avoid any delays in receiving support, we recommend that users with non-technical questions or inquiries start in the appropriate place:
|Topic||How to get help|
|General questions (including the customer relationship, creating sales units, change of admins, etc.)||See: Contact info on vipps.no.|
|Problems with Vipps services||See: Status pages.|
|Applications for Vipps products (status, follow-ups, etc.)||Check the status on portal.vipps.no.|
|Vipps plugins (WooCommerce, Shopify, Wix, WordPress, Wix, Shopify, Magento, EPiServer, etc.)||See the support info for your plugin: Plugin overview.|
|Vipps through a partner (for merchants)||Please contact your partner.|
|Vipps through a POS (Point of Sale) vendor||Please contact your POS vendor.|
|Vipps through a PSP (Payment Service Provider)||Please contact your PSP.|
|Partner assistance (for partners)||See: Vipps Partners and the Partner API.|
|Settlements, invoices or similar||See: Settlements.|
|Suggestions for improvements to Vipps products||Please use this form.|
For technical issues related to Vipps and the development of services using our APIs, please see the sections below.
Almost all questions are answered in the documentation
Please check the Frequently Asked Questions (FAQ).
Please use the search functionality for the technical documentation.
What to include in the email
If you cannot find the answer: Please send an email with all relevant information to the address below:
- Please: Always include 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 "
- Company details: Organization number (find yours at Brønnøysundregistrene)
- Merchant Serial Number (MSN), found on portal.vipps.no. See the Vipps portal.
- Which Vipps product or Vipps API is this about?
- Environment: Is it a problem in the Test (MT) or the Production environment?
orderId, and preferably also
contextId, to make it possible to search in logs.
- Date: On which date(s) did the problem occur?
- For API issues: We need a complete
response. Plain HTTP from Postman ensures the quickest response. No source code, please. Important: Remove everything except the last four characters from
- Please provide screenshots, if possible.
- Please provide your contact information (if not in your email signature): Name and phone number
- Please include any other information that may be relevant or possibly helpful.
Important: If you do not provide enough information, our first reply will be a request for more details, which will of course cause delays.
The Integration Services email address is email@example.com. If you add your colleagues on CC they will get all updates too.
Keep your colleagues up to date
If you want colleagues to be included in all communication regarding 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.
You will get an auto-reply from us with an issue number like
Subject line. This is the unique number for this specific issue and is
used to connect all communication about this issue in our systems.
The auto-reply is sent from a real e-mail address, which you can reply to.
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, do not quote all the previous messages - we already have them.
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 KAM (Key Account Manager), please contact her/him. If you do not, please reply to the issue, and add any relevant information. Please note that we understand that your problem is important to you, but that we must sometimes prioritize differently.
More than one problem, or a new one?
Please send separate emails for each problem. If you send an email about a new problem by replying to an old issue, it may delay our response. If you reply to an old issue that has been closed, we will not see the reply.
Can I call you?
We do not have a phone number, and we do not have the capacity to help 1:1 on the phone. Most cases involve information that needs to be in written form, such as IDs, API requests/responses, etc.
We do sometimes set up Slack channels for customers, depending on the Partner level.
Sign up for our Technical newsletter for developers.