How to sign up merchants

To sign up a new merchant, they must apply for services with Vipps MobilePay and order a product. Once they have a Vipps MobilePay sales unit, they can begin to use a partner.

When a new merchant gets their Vipps MobilePay application approved, an email is sent to both the merchant and the partner with information about:

• The merchant's organization number
• The merchant's name
• The sales unit's MSN
• The sales unit's name

To sign up a merchant that is working with another partner, see How can a merchant change partners.

note

It is not possible to pay the partner instead of the merchant. See also: Can I create a marketplace with multiple merchants?

Signing up merchants with the Management API

Partners that have their own API keys can use the Management API.

Partners that do not have their own API keys can't use the Management API to prefill a product order, must use manual signup.

The Management API enables a partner to "prefill" the product order form on portal.vippsmobilepay.com on behalf of a merchant, so the merchant can log in, check the data, and submit the product order.

See: Prefill a product order.

note

A partner that only rarely needs to onboard a new merchant can have the merchant order a product on portal.vippsmobilepay.com instead of using the Management API's "prefill" functionality. The partner may also log in on there and manually fill in the form, which will be similar to using the Management API's "prefill" functionality.

Sequence diagram for signup with prefill

Signing up with product order templates

For partners who don't use the Management API, it's possible to get custom URLs to the product order form where certain fields have been pre-set, and optionally also locked, so the merchant cannot change them.

These PO templates are made by Vipps MobilePay at the request of the partner, usually through the partner manager.

This allows partners to offer PO templates for different products and prices, for instance both for web/app payments and for physical in-person payments.

These parameters can be set in the PO template:

• Price package - The partner's price package for this product order template. This field may be hidden when there is only one price package available.
  info

  If the price package is specified or the partner only has one price package the price will not be displayed in the product order form.

• Intended purpose - Description and explanation of the product or products that will be sold. This can include hints such as specifying "POS integration in physical store" to indicate that the sales unit needs skipLandingPage activated.
• MCC - The merchant category code is used to determine the risk level of the merchant. Our product order form contains a user-friendly MCC selector, which contains a subset of all MCCs.
• Product use case - Where will sales take place? A website? A website that is not yet launched, so a test website must be used? A native app? Something else?

These fields are a subset of the fields that can be set when you Prefill a product order in the Management API.

The fields can be locked, so the merchant cannot change them when they complete (fill out the rest of) in the PO form.

URLs to a PO template have this format: https://portal.vipps.no/register/template/{templateId}.

Sequence diagram for product order templates

Manually signing up a merchant

We recommend that you use the Management API's prefill functionality to sign up a new merchant, because it is much faster and easier to get all the details correct since you can prefill the product order information.

Otherwise, the merchant can manually sign up as follows:

1. The merchant logs in to portal.vippsmobilepay.com.

   If they don't already have a customer relationship with Vipps MobilePay, they need to register on portal.vippsmobilepay.com and create a merchant agreement as described in Applying for services.

2. Once the merchant has a customer relationship with Vipps MobilePay, they can apply for the relevant Vipps MobilePay product(s) on portal.vippsmobilepay.com.

   It's the partner's responsibility to make sure the merchant has all necessary information to fill out the application correctly.

   When the merchant applies for a product, they must select:

   • The product (or use a direct link as above)
   • The partner
   • The price package, typically "Price 1", "Price 2" or "Price 3". Although it's not ideal to let merchants select the price package, this is needed when not using the Management API. This field may be hidden if there is only one price package available.

3. We process the application and perform customer control (KYC, PEP, AML, etc.). This may take a few days, depending on the information provided and the workload and the quality and completeness of the application. See the Typical reasons for delays.

4. The merchant can check the status of the application on portal.vippsmobilepay.com at any time. We don't have the capacity to answer emails with status inquiries. If the partner wants to know the status, they can check with the merchant.

5. We notify the merchant and the partner by email that the application is approved, with the new MSN, and that the merchant can now use the Vipps MobilePay products. Both the merchant and the partner receive exactly the same information.

   note

   If the application is declined, only the merchant is notified, as we may not be allowed to share the reason for declining.

The partner can now use their partner keys and the merchant's new MSN to make payments. Alternatively, if the partner doesn't want to use partner keys, they can ask the merchant to create a portal user for them, so they can get access to the merchant's MSN.

For information about user permissions, see: Portal: Users.

Typical reasons for delays

• Vipps MobilePay has sent an email requesting additional information, but has not received a reply. Merchants should check their "spam" and try to search their email for "vipps".
• The merchant has signed a merchant agreement, but has not ordered any Vipps MobilePay products.
• The application is not signed by a person that has signatory rights.
• The merchant's website does not meet the regional regulatory terms and conditions.
• The merchant's website does not have the organization number clearly visible.
• The merchant has not provided enough information about what they want to use Vipps MobilePay for.
• If the merchant's website is not the distribution channel, the requirements mentioned above also apply to the partner's platform.
• The application has been declined. Vipps MobilePay only informs the merchant about this, not the partner. The reason for declining may be related to risk and compliance, and thus sensitive.

See the application solution on portal.vippsmobilepay.com for more help and tips.

Related pages

• How to check the status of a product order