This repository contains various resources for Vipps developers. We recommend starting with Getting started.
- Vipps demo store
- API documentation
- Partners
- Plugins
- Status pages
- The Vipps test environment (MT)
- Postman
- API Dashboard
- Vipps API servers
- Vipps request servers
- Vipps API Lifecycle
- Settlements
- Vipps design guidelines
- Questions?
Document version: 2.5.1.
You can test Vipps with a production version of the Vipps app (the normal one in Apple Store and Google Play) here: demo.vipps.no.
Maybe you want to start by scanning this QR code and go directly to Vipps Hurtigkasse (express checkout) and buy a nice VHS cassette?
First of all: See Getting started.
The most commonly used APIs:
All Vipps APIs are available here: https://github.com/vippsas
The API documentation is frequently improved and increasingly extensive. Please use the search functionality in your browser and on GitHub to find what you are looking for.
See our Partner section.
Vipps provides several open source plugins for various web solutions. See our Plugins section.
We have several status pages, and we strongly recommend to subscribe to them (you can also subscribe to updates for specific incidents):
- Test environment: https://vipps-test.statuspage.io
- Production environment: https://vipps.statuspage.io
- BankID production: https://www.bankid.no/status/
- BankID preprod: https://bankidpreprod.statuspage.io
You can use Statuspage's Atom and RSS feeds for integration with other systems.
See The Vipps test environment (MT) for more information about general test functionality, the iOS and Android test apps, etc.
MT is short for Merchant Test.
See our Postman guide or the Postman documentation for more information about using Postman.
All merchants have access to an API Dashboard on portal.vipps.no under the "Utvikler" tab. Keep in mind that the "Utvikler" tab is only available to users with admin or developer roles.
The API Dashboard shows information about your API usage, an overview of errors, etc. Here's an example for one endpoint:
Please note: The API dashboard is not real-time, and events might take up to 10 minutes before they appear. We strongly recommend that you also monitor your Vipps integration yourself.
The test and production environments are separate and require different API credentials:
| Production (Prod) | Test (MT) |
|---|---|
| api.vipps.no | apitest.vipps.no |
The servers are world accessible. Vipps only relies on the API keys, and no requests to our servers are blocked on our side by IP addresses or similar.
Please note: Vipps may change the IP addresses for the API servers. To ensure that you are whitelisting the correct IP addresses please use these hostnames and DNS, and automatically update your firewall rules if there are DNS changes. We can not provide the IP addresses in any other way than DNS.
Requests made by Vipps are made from the servers specified below. Vipps normally only uses one server at a time, and change servers approximately every three months.
| Production (Prod) | Disaster recovery (DR) | Test (MT) |
|---|---|---|
| callback-1.vipps.no | callback-dr-1.vipps.no | callback-mt-1.vipps.no |
| callback-2.vipps.no | callback-dr-2.vipps.no | callback-mt-2.vipps.no |
| callback-3.vipps.no | callback-dr-3.vipps.no | callback-mt-3.vipps.no |
| callback-4.vipps.no | callback-dr-4.vipps.no | callback-mt-4.vipps.no |
The disaster recovery environment is as important as the production environment.
Please note: Vipps may change the IP addresses for the request servers. To ensure that you are whitelisting the correct IP addresses please use these hostnames and DNS, and automatically update your firewall rules if there are DNS changes. We can not provide the IP addresses in any other way than DNS.
For API products where Vipps makes requests to your servers, please make sure that these request servers are allowed through firewalls, etc.
See: Vipps API Lifecycle.
See: Settlements.
Guidelines, logos, buttons, etc is here: vipps-design-guidelines.
And here: brand.vipps.no.
We're always happy to help with code or other questions you might have! Please create an issue, a pull request, or contact us.
Sign up for our Technical newsletter for developers.