MobilePay

Overview

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

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

Functionalities

Activation

To be able to use MobilePay as a payment method on your webshop, you need to have a card acquiring agreement with your chosen acquirer. You don't need any additional agreements.

You are responsible for activating this payment method 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 "MobilePay" from the drop down list and click the "Add" button.

• Select the desired currency (EUR or DKK) and enter the name of your webshop which you would like MobilePay to display under the merchant logo and use for a cardholder statement.

• Add merchant logo link. This is to display merchant logo on MobilePay app terminal. If not added, then by default MobilePay logo will be displayed. However, we recommend merchants to add their company logo for better buyer experience.

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

User Journey

This section describes the customer journey for a consumer:

• When your customer chooses MobilePay as a payment method on a desktop they will be forwarded to the MobilePay landing page.
• On the MobilePay webpage customer is asked to enter their phone number (it may be pre-filled) connected to the MobilePay account.
• Once the "Continue" button is clicked, the customer receives a push notification prompting them to open the MobilePay app. The customer has five minutes to approve the transaction.
• Customer approves the payment in the app and receives a receipt in the app showing the approval of the payment.
• The customer will be redirected back to your site and sees the success screen.

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 as with regular card payments.

The following technical requirements apply to MobilePay:

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

• Pre-filled phone number: You can provide a phone number to be pre-filled in the phone number field on the MobilePay webpage by adding “customerPhoneNumber” in the Register call. The phone number should be given in international format +[country code][phone number].

• AutoAuth: After the Terminal phase, Netaxept triggers an automatic authorization for the transaction, therefore you don’t need to run the Process(AUTH) call on MobilePay transactions. We recommend confirming through a Query API call that the authorization is successful before processing capture.

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

• Process(ANNUL) 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.

Callback functionality and Query call

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

Payment Flow (App Switching)

App switching does not require customer to enter phone number but it does require that the MobilePay application is installed on your customer device. It also enables app switch both to the MobilePay 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 MobilePay app).

  • PaymentMethodActionlist = MobilePay
  • ServiceType = M
  • Currency = DKK or EUR
  • 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 MobilePay app.
• Customer authorizes the transaction and MobilePay switches back to your app.

Setting up a MobilePay Recurring payment

Setting up a recurring payment for MobilePay is to most parts described on the page covering card on file payments, but it differs in some small details that are described in this section.

1. For the initial MobilePay transaction that creates the panhash used in subsequent transactions, updateStoredPaymentInfo should not be used, and amount needs to be specified.
2. The parameter paymentMethodActionList needs to be included, with MobilePay as the only entry in the list. Please refer to the paymentMethodActionList page for more details on this parameter.

Here is an example of what the parameters of an initial Register call for setting up a recurring payment with MobilePay can look like. How to set up and process subsequent transactions are described the page covering card on file payments.

1. Initial Register call with a purchase:

merchantId = <your merchant identifier>

token = <your API key>

orderNumber = <an order number>

amount = <an amount>

currencycode = <a currency>

redirectUrl:<a URL to redirect to after the payment has been processed>

serviceType = B

recurringType = S

paymentMethodActionList = [{"PaymentMethod": "MobilePay","Fee": null}]

Testing

Prerequisites

Before testing MobilePay in Netaxept, ensure that:

• You have registered as a MobilePay merchant (you can do it here).
• MobilePay 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 MobilePay test app from the Vipps MobilePay Developer Docs

Example MobilePay 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 MobilePay), and Order number.
• Click Create Link.

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

• Select MobilePay as the payment method.
• Enter the phone number of a test user.
• A payment request is sent to the MobilePay 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.