Skip to content


    This page outlines the basics of using Vipps via Netaxept and gives you instructions needed for a successful implementation.

    Before you start

    Before you start accepting wallet payments, you need to sign an acquiring agreement with the relevant provider and activate that payment option in your Netaxept Admin Account.

    You also need to sign up with Vipps to get the merchant serial number.


    Vipps is a Wallet payment method, enabling users to make mobile payments, authenticate and approve payments via their Vipps payment app.

    Your customers must have downloaded the correct payment app on their smartphone with one or more payment card(s) added. They must register their local mobile phone number into the app and approve which card(s) they want to use for online payment purposes.

    When the customers are shopping online and have chosen the payment method either on your website or on Netaxept's payment window, they are asked to enter their mobile phone number as registered in the app. After entering the mobile phone number, a push message will be sent to the customer's smart phone to give a confirmation of their payment. The customer log into their app and approve the payment by swiping or pressing the corresponding button.

    During the approval process, Netaxept authorizes the payment automatically. 3D Secure authentication is bypassed, and all payments are considered and marked as non 3DS authenticated. If the authorization is accepted by the card issuer, the customer receives a receipt in the app showing the approval of the payment.

    Please note that this is not an official receipt. The consumer should receive the official receipt from your webshop as they normally do.

    The payment is now authorized and shown as authorized also in Netaxept. When the order has been delivered to the customer or there is certainty regarding its delivery, you can capture the payment. After the capture is done, the order amount is withdrawn from the customer's payment card (the one that's linked to their app).

    Now the funds get settled to your bank account in the same settlement batch file and within the same timeframe as your regular card payments.


    Payment typeWallet
    Partial refund
    Update order
    Cancel payment
    Reservation & charge


    To be able to use mobile wallets as payment methods on your webshop, you need to sign an acquiring agreement with your chosen acquirer. You also need to sign up with Vipps to get the merchant serial number.

    Similiar to invoices, you need to activate the payment method in question in Netaxept Admin. You are responsible for activating these payment methods in Netaxept Admin and ensuring that all information is entered correctly.

    For Vipps, select "NOK" as currency and enter the "VippsID" you have received when registering with Vipps to the field "Merchant serial number".

    • Choose the correct currency and enter the third parties credentials. The number of credentials and terminology varies between different providers.

    • Save your changes by clicking the "Add" button.

    Vipps is additional paid payment methods which means that merchant will be invoiced the payment method specific fees as an addition to the regular Netaxept monthly and transaction fees.

    User Journey

    This procedure describes the customer journey and payment flow:

    1. When your constomer chooses Vipps as a payment method in the checkout, they will be prompted to the Vipps app.
    2. From here, they will be redirected to the Vipps app landing page to enter the phone number connected to the Vipps account.
    3. Click on Continue. The customer has five minutes to approve the transaction.
    4. Approve the payment in the app.
    5. They will be redirected back to the checkout and the amount is charged immediately.

    Payment Flow

    The payment flow in general follows the sequence of steps as described in the payment flow outline section.

    In fact, payments done via mobile wallets are considered and processed as regular card payments, and as such, the same rules and possibilities apply:

    • The payment can be captured after the product or service has been delivered to the consumer or there is certainty regarding its delivery.
    • The authorization is valid the same length as regular card authorizations, i.e. depending on issuer rules.
    • The authorization is put on the underlying card.
    • The same liability shift rules apply than with regular card payments.

    Wallet based payment methods are not supported in the single page payment window, nor do they support recurring payments.

    There are a few parameters that are specific for mobile wallet payments:

    • If you are sending "Payment method action list" parameter with the Register call, you need to add the name of the chosen payment method into this parameter. Also for Vipps, you need to generate a unique value in Order number field for each transaction. Re-use of order number within same merchant ID is not allowed.

    • AutoAuth: After the Terminal phase, Netaxept triggers AutoAuth for the transaction, therefore you don’t need to run the Process(AUTH) call on Vipps transactions.

    • Process(CAPTURE): When you want to capture the payment, run capture to the payment either via Netaxept API by doing the Process(CAPTURE) call or manually via Netaxept Admin.

    • CANCEL and Process(CREDIT) Also, you can cancel the authorization if the purchase is cancelled before the payment is captured, or run either full or partial credit if the payment is already captured.

    Query call and callback functionality

    In order to verify that the transaction has the correct status and is authorized successfully, or if you are unsure which payment method the customer used for the payment, we recommend you to implement [Callback functionality] and the Query call as part of the payment process.

    Through the Callback, you will receive a transactionId whenever the transaction has a new status. Based on this, you can do the Query call to get the new status and detailed information about the transaction.

    We always suggest implementing callback functionality. Callbacks will send a transactionId whenever the transaction has a new status. The Query call can be triggered by that event and get detailed information about the payment in question based on the transactionId.


    If you have defined fees for different payment methods, please note that charging Vipps specific fees from consumers are not allowed. However, you may charge the usual card fee associated with the card which the consumer uses (taking into account the other fee and country specific rules and restrictions). In this case, the fee needs to be displayed clearly in your webshop page before the consumer approves the order and continues to the payment phase.

    App Switching (Payment Flow)

    For the best possible UX, we recommend using our mobile SDK.

    Netaxept supports using Vipps M-commerce application. Vipps M-commerce does not require user to enter phone number but requires that the Vipps application is installed on the device. It also enables app switch both to the Vipps application and back to the merchant application or website as described below:

    • If the transaction is performed in app, the Register call should contain the following parameters for the app switch (from your app to Vipps app).

      • PaymentMethodActionlist = Vipps
      • ServiceType = M
      • Currency = NOK
      • Customer phone number = country code and phone number
      • redirectURL as your merchant application URL-scheme ("merchant://") or your full https address.

    The transaction flow is as follows:

    • Initiate the transaction in your app.
    • App switch to Vipps app.
    • Customer pays to authorise the transaction and Vipps switches back to your app.


    Vipps can be tested in test environment. You can download the test APP for Vipps from here:

    Test Credentials for Vipps:

    • Vipps Number: 48059560
    • Enter “1236” as pin

    Settlements and Identifying Transactions

    Settlement batch and transaction reference number

    Payments done via mobile wallet will be processed as regular card payments in Netaxept, and therefore they will be included in the same settlement batch files as the other card payments. The timeframe before the money is settled to your company's bank account will be the same as for regular card payments.

    Specifying a unique reference number for each transaction works in the same way as with regular card payments: The TransactionReconRef parameter must be sent with the Register call to Netaxept.

    As with the regular card payments, the actual support for end-to-end transaction reference number is bound by the limitation of the acquirer that you have an agreement with.

    Identification of transactions

    Mobile wallet transactions can be identified both in Netaxept Admin and via API by using the Query call.

    Netaxept Admin

    • find the mobile wallet logo in "Transaction list" next to the transaction
    • the corresponding "Details" page will show both, the mobile wallet logo and the logo of the underlying card
    • you can search payments done with mobile wallet by selecting the corresponding payment method in the "Advanced transaction search" section

    Query call

    The Query call's Wallet element contains the information about the mobile wallet used for the payment. The underlying card is shown in the CardInformation.PaymentMethod and CardInformation.Issuer parameters.

    Was this helpful?

    What was your feeling about it?