MobilePay

Overview

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

Before your customers can use MobilePay, they must have installed the correct payment app on their mobile device with one or more payment card(s) added to their MobilePay account. The customer’s account information is connected to their phone number.

When the customer has chosen MobilePay from payment method options on a desktop, they are first directed to MobilePay-hosted page to enter their phone number as registered in the app. After this, a push message will be sent to the customer’s mobile device to open the MobilePay app to complete the payment. When paying with mobile device or in-app, the customer is switched directly to the MobilePay app to approve the payment.

During the approval process, Netaxept authorizes the payment automatically. If the authorization is accepted by the card issuer, the customer receives a receipt in the app showing the approval of the payment.

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 payment card (the one that is linked to their app).

Now the funds get settled to your company bank account in the same settlement batch file and within the same timeframe as your 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 is prompted with a push notification on their mobile device to open the MobilePay app. from MobilePay on the mobile phone. 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 than 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 the payment method name “MobilePay” into this parameter. Also for MobilePay, 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.

• 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

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.

Fees

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.

More information about Callback can be found here.

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 reccuring 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 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. Intial Register call:

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

MobilePay Online can be tested in a test environment. To complete a payment flow within the test environment, you can download a test version of the MobilePay app from here.

Test Credentials for MobilePay

Denmark:

• NIN: 2208840541
• Phone: +45 23784337

Finland:

• NIN: 020580-329K
• Phone: +358 63119202

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.