FAQ: Other questions
Where do I find the client_id and client_secret?
See:
Can you send us logs, so we can look for errors?
Unfortunately, Vipps MobilePay can't extract logging info for one merchant or one MSN. There are terabytes of data, and it's not trivial to provide data for just one merchant or MSN.
We provide as much information as we can for all API requests that fail, both by using a sensible HTTP status for the response and by including as much relevant information as possible in the response body.
It's important to use this information. If you discard it, it's gone.
The API Dashboard on portal.vipps.no provides a high-level overview of errors in the use of the APIs, but it does in no way replace a proper handling of errors and error messages.
Having said that, it is possible to investigate specific API calls in special cases if you send us enough information. Please do your own investigations before contacting us about this.
How do I perform "testing in production"?
To do this, you need a live Vipps MobilePay account. You can order this on portal.vipps.no.
We recommend testing with 2 NOK, even though 1 NOK is the smallest possible amount. 1 NOK is not reliable, as it gets low priority in some systems.
How can I use Vipps MobilePay for different types of payments?
It's possible to use the eCom API for several types of payments.
Let's say you run a book store. You can then use eCom API in several ways, such as:
- A webshop that sells physical books: eCom API with "reserve capture", since you cannot capture the payment before the book is shipped.
- A webshop that sells digital, downloadable books that are immediately available: eCom API with either "reserve capture" or "direct capture", depending on whether the digital product needs to be generated or not.
- A physical store where customers buy physical books in person: eCom API with "direct capture", possibly integrated with the POS.
- A physical store where customers can buy physical books by scanning a QR code in the window, and have the physical book delivered by mail: eCom API with "reserve capture", since you cannot capture the payment before the book is shipped.
The regulatory requirements are different for different types of purchases. One major difference is if the cardholder is physically present and "can look the seller in the eye" while making the payment.
Vipps MobilePay needs to do more thorough "Know Your Customer" (KYC) and compliance checks for some examples above. This must be done per sales unit. Vipps MobilePay is also required to have the correct MCC (Merchant Category Code) for each sales unit.
Because of this, merchants must use separate sales units for separate types of purchases. This also has some benefits:
- Each sales unit has its own name presented to the user in the app
- Each sales unit has separate transaction logs
- Each sales unit can have its own settlement account. Sharing a single account across multiple sales units is available on request.
How do I set up multiple sales units?
This is typically needed for organization numbers with multiple stores, or offers different ways to pay with Vipps MobilePay. See: How can I use Vipps MobilePay for different types of payments?
The bank account number for a sales unit must belong to the organization number of the company that has the customer relationship with Vipps MobilePay.
A legal entity, the "merchant", may have one or more sales units. It is possible for one merchant to have multiple sales units with a separate bank account number for each one, as long as the bank accounts belong to the organization number that the sales unit belongs to.
If the organization has the required financial regulatory approval to "split"
payments between sales units, it is possible to have only one sales unit and
identify the payments of a store using the orderId - for instance by prefixing the
orderId with the store's ID, name or number.
Alternatively each store, if they each have their own organization number, are set up with their own merchant and sales units.
If all sales units have the same organization number, there are two alternatives:
1: Recommended: Multiple sales units (multiple MSNs): One sales unit per store. Each sales unit will have its
own MSN (Merchant Serial Number), and the orderId may be whatever you want.
Each sales unit gets its own
settlement files.
You will need separate API keys for each sales unit (store).
If you have a Vipps MobilePay platform partner, the partner will use the
Partner keys
for all the sales units.
See: How can I use Vipps MobilePay for different types of payments?.
2: Use only one sales unit (one MSN) for all stores, and use the orderId to identify
which orders belong to which sales units.
All sales units are in the same
settlement report.
You decide what the reference (called orderId in the older eCom API) contains,
and it may be up to 50 characters. See:
Recommendations for reference and orderId.
You will use the same API keys for all stores.
If you have a Vipps MobilePay platform partner, the partner will use the
Partner keys
for all the sales units.
How can I change my organization number?
A company cannot change its organization number.
Companies (merchants) sometimes merge with other companies, are acquired, etc. We sometimes get requests from companies that have "changed organization numbers", but this is not possible in Norway.
The organization number is a unique identifier for a legal entity, and a new legal entity needs a new organization number. The fact that the company has the same name, is owned by the same people, etc. is irrelevant.
Vipps MobilePay is legally required by Finanstilsynet to perform several checks of all companies that have a customer relationship with Vipps MobilePay. This is based on each company's organization number, and the legally binding agreement between the company and Vipps MobilePay. This agreement is signed with BankID.
If a company has "changed organization numbers", it is a new legal entity, and the new company needs a new agreement with Vipps MobilePay. Establishing a new customer relationship for the new company is straight-forward on portal.vipps.no.
What about webhooks?
See: Webhooks API
Can I use Vipps with Klarna Checkout?
Yes. Klarna Checkout (KCO) supports Vipps as an External Payment Method if you have agreement with Klarna for this.
Please note: It's technically possible to use Hurtigkasse on product pages and in the shopping basket for fast and easy checkout, and to let users choose between Vipps and Klarna before they get to Klarna Checkout. With Login (the Login API) it's also possible to let users register and log in without usernames and passwords. Checkout may also be interesting.
Important: Using Vipps as an external payment method requires a direct integration with the eCom API, as Klarna merely redirects the user to Vipps for payment, as the example below shows.
All information about price, shipping, etc. must be done in Klarna Checkout, before the user is sent to Vipps to pay the total amount.
"external_payment_methods": [
{
"name": "Vipps",
"redirect_url": "https://example.com/vipps/ecom-api/initiate/acme-shop-123-order123abc",
"image_url": "https://example.com/images/vipps-logo.png",
"fee": 0,
"description": "Husk: Vipps er alltid gebyrfritt når du betaler til bedrifter."
}
]
Note, the description translates to: Remember: Vipps MobilePay is always fee-free when you pay to companies.
| Field | Description |
|---|---|
name | The name of the payment method. Use "Vipps". |
redirect_url | Merchant hosted URL redirecting to the Vipps payment deeplink URL |
image_url | The logo to be shown for this payment method. See: Vipps design guidelines. |
fee | Should not be applicable because of PSD2 surcharge ban. |
description | The description field should state that there is no fee when paying with Vipps. The Norwegian text above says: "Vipps is without fees when paying businesses". |
Follow Klarna's process to get the External Payment Method activated for your account, described in the Klarna documentation. Using this method will add Vipps as a payment alternative inside KCO.
See: External payment methods & external checkouts.
Please note: We have limited knowledge of Klarna Checkout, and cannot help with all the details.
Important: When using Vipps as an external payment method in Klarna Checkout, the settlements from us will be separate from the settlements from Klarna.
What functionality is included in the Vipps MobilePay API, but not the PSP API?
See Common topics: Benefits of direct integration.
What do we have to do with PSD2's SCA requirements?
Nothing. We will handle everything for you - both BankID and 3-D Secure.
SCA (Strong customer authentication) is a security requirement related to PSD2, to reduce the risk of fraud and protect customer's data.
We use delegated SCA, which makes it easier to users to pay with Vipps MobilePay than with stand-alone card payments. The result is a higher completion rate.
Delegated SCA is our primary way of solving the SCA requirements. For this solution, we have developed an SCA compliant solution that consists of a two-factor authentication featuring either PIN or biometrics in addition to device possession. In addition, we have implemented a Dynamic Linking according to the requirements.
How can I change partner for my Vipps MobilePay integration?
See: How to change partners for a merchant.
Please note: The MSN (the number) does not change when changing partners.