Skip to main content

Sales units & account setup

Setting up multiple sales units​

Merchants with multiple stores or different payment scenarios typically need multiple sales units. See: Payment scenarios

Bank account requirements: The bank account number for a sales unit must belong to the organization number of the merchant that has the customer relationship with Vipps MobilePay.

A legal entity (the "merchant") may have one or more sales units. Merchants can 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.

Alternative approaches for organizations with the same organization number:

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.

If each store has its own organization number, each store should be set up with their own merchant and sales units.

For all sales units with the same organization number, choose one of these approaches:

  1. (Recommended) Multiple sales units: 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: Payment scenarios.

  2. Single sales unit: Use only one sales unit (one MSN) for all stores, and use the order identifier (e.g., orderId or reference) to identify which orders belong to which sales units. All sales units are in the same settlement report. You decide what the order identifier contains, and it may be up to 50 characters. See: Recommendations for order identifier. 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.

tip

If you have multiple sales units, prefix the reference with the MSN for each sales unit. For example, if the MSN/sales unit ID is 654321, the reference could be 654321-acme-shop-123-order123abc.

Organization numbers cannot be changed.

When businesses merge with other businesses or are acquired, they sometimes request to "change organization numbers". However, the organization number is a unique identifier for a legal entity, and a new legal entity requires a new organization number, regardless of whether the business has the same name, is owned by the same people, etc.

Vipps MobilePay is legally required by the financial authorities to perform several checks of all businesses that have a customer relationship with Vipps MobilePay. This is based on each business' organization number, and the legally binding agreement between the businesses and Vipps MobilePay.

If your business has a new organization number, it is considered a new legal entity. The new business needs a new agreement with Vipps MobilePay. Establishing a new customer relationship for the new business is done on the portal at portal.vippsmobilepay.com.

Cross-border and Nordic expansion​

Implementation compatibility across countries​

Current implementations for Norwegian users work in other countries across the Nordics. See: Offering Vipps/MobilePay in the Nordics.

Signing agreements for other countries​

If you don't have the eID for another country where you want to offer services, you can log in to the business portal with your own eID and then search for the other company in the merchant agreement flow. If this is not possible, contact business support.

Managing your merchant profile​

As a Vipps MobilePay merchant, you can manage your profile in the business portal, portal.vippsmobilepay.com. Be aware that adding services, such as recurring payments, may require extra verifications due to additional risk evaluations that are required. For help logging in, see the portal section.