Vipps

Overview

Vipps is a wallet payment method that enables customers to authenticate and approve payments using the Vipps app.

Customers initiate the payment during checkout and approve it in the Vipps app. Netaxept automatically authorizes the transaction, and payments can be captured and settled in the same way as regular card payments.

Functionalities

Pre-Auth Vipps

Vipps supports Netaxept’s pre-auth functionality as described on this page Please note that for Vipps the pre-authorization needs to be initialized using the Register API call. For details, see "Step 1: Initiating a pre-authorization payment" -> "1. Register Call" in this section

Activation

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.

• Log in to Netaxept Admin:

  • test: https://test.epayment.nets.eu/admin
  • production: https://epayment.nets.eu/admin

• Find the "Agreement" tab under "Options".

• Choose the correct payment method from the drop down list and click the "Add" button.

• 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.

User Journey

This procedure describes the customer journey and payment flow:

1. When your customer 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:

3D Secure authentication is bypassed for Vipps transactions, and payments are considered and marked as non-3DS authenticated.

• 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.

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

We recommend implementing [Callback functionality] together with the Query call as part of your payment integration.

Callback: Netaxept sends a transactionId whenever a transaction status changes.

Query call: Use the transactionId received through the Callback to retrieve the updated status and detailed transaction information.

Together, the Callback and Query call help ensure that your system receives accurate and up-to-date information about the payment throughout its lifecycle.

Fees

Merchants may not charge consumers additional fees specifically for using Vipps. However, the standard card fee associated with the underlying payment card may apply, subject to local regulations and restrictions.

Any applicable fee must be clearly displayed in the webshop before the customer approves the order and proceeds to payment.

App Switching (Payment Flow)

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.

Testing

Prerequisites

Before testing Vipps in Netaxept, ensure that:

• You have registered as a Vipps merchant (you can do it here).
• Vipps has been activated in Netaxept.
• You have created a test user in the Vipps MobilePay Business Portal. (Test User PIN: When creating a test user, choose a PIN code and make a note of it. The PIN will be required when completing test payments.)
• You have downloaded the Vipps test app from the Vipps MobilePay Developer Docs

Example Vipps activation in Netaxept Admin.

Perform a Test Payment

• In Netaxept Admin, navigate to Help and Tools > Link Payment.
• Enter Amount, Currency (ensure to use a valid currency for Vipps), and Order number. Use a different order number for each test transaction.
• Click Create Link.

• Open the payment link generated by Netaxept by clicking Preview.

• Select Vipps as the payment method.
• Enter the phone number of a test user.
• A payment request is sent to the Vipps test app.
• Open the app and approve the payment.

Verify the Result

Verify that:

• The payment was completed successfully.
• The transaction is visible in Netaxept Admin under Approved transactions.

Navigate to Manage Transactions to view an overview of transactions. Select a transaction to view its details.

Next Steps

With the completed Terminal phase, you are now ready to process the transaction and do financial operations such as authorization Process(AUTH), authorization and capture Process(SALE) or account verification Process(VERIFY). You can read more about it here.

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.