Wallet based payment methods

Enable customers to pay with just one swipe


This page outlines the basics of using payment methods based on the mobile wallet application via Netaxept and gives you instructions needed for a fluent implementation. At the moment you can implement MobilePay, Vipps and Masterpass in your webshop via Netaxept. Read more about:

MobilePay >

Vipps >


Use for the end-customer

The prerequisite is that the consumer has downloaded the correct payment app in their smartphone and added there one or more payment card(s) that can be used for payments when shopping online. Besides card data, the consumers need to register their local mobile phone number into the app and approve which card(s) they want to use for online payment purposes.

When the consumer is shopping online and have chosen the payment method either in your website or in Netaxept payment window, they are asked to enter their mobile phone number registered in the app. After entering the mobile phone number, a push message will be sent to the consumer's smart phone to get a confirmation of the payment. The consumer logs in to their app and approves 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 consumer receives a receipt in the app showing the approval of the payment. Please note that this is not, however, an official receipt. The consumer should receive the official receipt from your webshop as they normally do.

The payment is now authorized and shown authorized also in Netaxept. When the order has been delivered to the consumer or there is certainty regarding its delivery, you can run capture to the payment. After the capture is done, the order amount is withdrawn from the consumer's payment card linked to the app and settled to your company's bank account in the same settlement batch file and within the same timeframe as your regular card payments.



To be able to use mobile wallets as payment methods in your webshop, you need to sign an acquiring agreement with your chosen acquirer with card payments. Besides that, for Vipps you need to sign up with Vipps to get the merchant serial number, read more about Vipps sign up. For MobilePay, you don't need any additional agreements.

After signed all the needed agreements, you need to activate the payment method in question in Netaxept Admin. The merchant is responsible for activating these payment methods in Netaxept Admin and ensuring that all information entered is correct.

  • Log in to Netaxept Admin (test: https://test.epayment.nets.eu/admin or production: https://epayment.nets.eu/admin)
  • Go to "Options" => "Agreement" tab.
  • Choose the correct payment method from the drop down list and click "Add" button.
    • For Vipps, select "NOK" as currency and enter the VippsID you have received when registering with Vipps to the field "Merchant serial number".
    • For MobilePay, select the desired currency and enter the name of your webshop which you would like MobilePay to use for a cardholder statement.
  • Save your changes by clicking "Add" button.

It should be also noted that Vipps and MobilePay are 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.


Performing API integration

Implement the technical API in accordance with the standard Netaxept API instructions. Read more about API >

Transaction flow

Start the payment process by sending the information required for the payment to Netaxept by means of the Register call. If you are sending "Payment method action list" parameter along the Register call, you need to add the name of the chosen payment method into this parameter. Also for MobilePay and 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.

After the successful Register call, perform the Terminal call to send the customer to the checkout for the payment. After the Terminal phase, Netaxept triggers AutoAuth for the transaction, therefore, you don’t need to run the Process(Auth) on MobilePay and Vipps transactions. 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. 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.

If you already have a working Netaxept API integration for card payments, you have been used to run either the Process(Auth) or the Process(Sale) for the transaction after the successful registration and Terminal phase. To be able to implement MobilePay or Vipps without changing this integration, the following workarounds have been implemented in Netaxept. However, we always recommend you to implement MobilePay and Vipps in your webshop in a correct way without the need of the workaround, if possible.

  • If you send the Process(Auth) call, then Netaxept ignores the repeating AUTH.
  • If you send the Process(Sale) call, then Netaxept runs the CAPTURE instead.
  • If you send AutoSale in the Register call, then Netaxept runs the CAPTURE instead.

Callback and Query

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 the Callback function and the Query call as part of the payment process. Through the Callback, you will receive a transaction ID 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. Read more about Callback > and Query >

Other notes

If you have defined fees for different payment methods, please note that charging MobilePay 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.

MobilePay and Vipps can be tested only in production environment due to lack of test environment on service provider side. It means that you need to use your production merchant and own smart phone and payment card for testing purposes.

Payments done via mobile wallets are considered and processed as regular card payments, and as such, the same rules and possibilities apply. For example:

  • 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.
  • However, it should be noted that these payment methods are not supported in Single page payment window, nor they support recurring payments.


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 these will be included in the same settlement batch files as the other card payments. Also, because this kind of payment is equal to card payment, the timeframe when 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 a same way as with the regular card payments. That is, by sending the parameter TransactionReconRef and its value along 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. Read more about transaction reference number >

Identification of transactions

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

In Netaxept Admin,

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

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