This repository contains various resources for Vipps developers, including:
- Getting started with Vipps development
- How to contribute to Vipps projects on GitHub
- How to contact us in the Vipps Integration team
- Requirements for foreign companies in order to use Vipps
- Settlements for information about settlements
- API documentation
- Status page
- Postman
- Example code
- The Vipps test environment (MT)
- Vipps test apps
- Vipps design guidelines
- Vipps request servers
- Additional developer resources
See: Getting started.
https://vipps-test.statuspage.io
Postman is a common tool for working with REST APIs. We offer Postman Collections for some APIs. Postman can import Swagger files directly, so collections are not a requirement.
With Postman you can make calls to all the API endpoints and see the full request and response for each call, including headers.
When contacting us about API issues, we are usually able to help faster if you send us the complete request and response.
See our Postman guide or the Postman documentation for more information about using Postman.
| Product | Github Link |
|---|---|
| eCommerce V2 | https://github.com/vippsas/vipps-ecom-api/tree/master/tools |
| Invoice | https://github.com/vippsas/vipps-invoice-api/tree/master/tools |
| Recurring | https://github.com/vippsas/vipps-recurring-api/tree/master/tools |
We have made some example code available, in hope that it may be useful: https://github.com/vippsas/vipps-developers/tree/master/code-examples
The Merchant Test Environment (MT) is available for all Vipps customers.
The environment is suitable for testing most of the Vipps functionality, but some functionality in the production environment is not available in MT. In general, MT does not contain functionality that requires integration with third parties, such as Payment Service Providers, EVRY, Nets, banks, etc.
Functionality not available in MT (a non-exhaustive list):
- Push alerts may be unstable
- Payment of invoices, both for Vipps Regninger and Vipps Faktura
- Limited support for testing card statuses that require connections to Nets, etc
- Limited support for looking up customer information in KAR, etc
To test functionality that is not available in MT, you will have to use the production environment in a controlled manner. One example may be to test Vipps Regninger with real invoices, but with small amounts. We recommend 2 NOK.
Other differences in MT:
- We allow 10,000 incorrect PIN attempts before locking the Vipps user's account
The welcome email contains information about your test user, which has the following dummy data:
- Name
- Phone number
- PIN
- Bank account number
- Credit card number
You can use this test user to in the Vipps test apps.
Important: Do not use the test phone number in production, as the test number may be a real phone number for a real Vipps user.
If you need additional payment cards, you can add it in the Vipps app. See Credit card numbers for more details.
If you have not yet received the welcome email, see the standard reply (in Norwegian) for requests for this.
See also: Vipps Test Data.
Vipps supports using special amounts that are always "rejected in the app", etc - without anyone needing to use the app. This is useful for testing, test automation, etc.
| Amount | Error |
|---|---|
| 1.51 | Not sufficient funds |
| 1.86 | Expired Card |
| 1.87 | Invalid card |
| 1.82 | Refused by issuer |
| 1.83 | Suspected fraud |
| 1.84 | Withdrawal limit exceeded |
| 1.97 | 3D Secure denied |
The test apps for iOS and Android are identical to the production apps, but connects to the Vipps the Vipps test environment (MT) instead of the production environment.
Only test accounts, with random phone numbers, are available in the test environments. Normal Vipps users are not available, so you can not use your own phone number with the test apps.
iOS:
- 2.6.9 or newer
Android:
- Version 2.9.*-MT (2.9-g3100d2-b119922-MT (341) in Appcenter, or any newer -MT suffixed version.)
- Push alerts do not work
- For iOS: There may be conflicts with the production apps, and we recommend to only have one of the apps installed
The iOS test app is available in Apple TestFlight. You do not need an activation code.
- See the information above about which version to install.
- Open the TestFlight link
- Install the "Vipps MT" app
- Open the "Vipps MT" app
- Enter the test phone number, that was sent in the welcome email to the email address used in the registration. Your normal Vipps user is not available in the test environment.
- On the "Verify your number" screen: Use PIN
1236. - On the "Enter your code" screen: Use PIN
1236. - Enable FaceID (or TouchID) and confirm with PIN
1236. - Accept push notifications.
You are now ready to use the iOS test app connected to the Vipps test environment.
Please note: App-switching on iOS uses the same URL pattern for both the
production Vipps app (in App Store) and the MT test app (in TestFlight).
This means that iOS may open either of the apps for a vipps:// URL, as iOS
can not know which of the apps to open. Because of this, we recommend to
only have one of the apps installed on the same device.
Important: Do not use the test phone number in production, as the test number may be a real phone number for a real Vipps user.
The Android test app is available in App Center. You do not need an activation code.
- See the information above about which version to install.
- Open the App Center link. If you get a push message prompting to whitelist the source, you should be able to do this via the "Settings" button.
- Install the "Vipps Android" app
- Open the "Vipps Android" app
- Enter the test phone number, that was sent in the welcome email to the email address used in the registration. Your normal Vipps user is not available in the test environment.
- On the "Verify your number" screen: Use PIN
1236. - On the "Enter your code" screen: Use PIN
1236. - Enable touch id and confirm with PIN
1236. - Accept push notifications.
You are now ready to use the Android test app connected to the Vipps test environment.
Please note: Older versions of the test app using a mobile browser for the landing page will not work in the test environment. This is because it will always redirect to the production Vipps app, not the MT test app. If the production Vipps app is not installed, the redirect will open Google Play to download the production Vipps app.
Important: Do not use the test phone number in production, as the test number may be a real phone number for a real Vipps user.
Guidelines, logos, buttons, etc: https://github.com/vippsas/vipps-design-guidelines
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.
callback-1.vipps.no
callback-2.vipps.no
callback-3.vipps.no
callback-4.vipps.no
callback-dr-1.vipps.no
callback-dr-2.vipps.no
callback-dr-3.vipps.no
callback-dr-4.vipps.no
The disaster recovery environment is as important as the production environment.
callback-mt-1.vipps.no
callback-mt-2.vipps.no
callback-mt-3.vipps.no
callback-mt-4.vipps.no
For API products where Vipps makes requests to your servers, please make sure that these request servers are allowed through firewalls, etc.
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.
- Developer overview: https://vipps.no/developer
- High-level overview of the API documentation: https://vipps.no/developer/documentation/
- Products, personal: http://vipps.no/privat
- Products, business: http://vipps.no/bedrift
The Vipps Integration team Get in touch here