Getting Started Guide MobilePay via Netaxept

Transcription

1 Getting Started Guide MobilePay via Netaxept Version 1.1 MobilePay Online (MPO, MobilePay) is a mobile payment solution launched by Danske Bank for webshops. With MobilePay through your Netaxept integration you can allow your customers to pay their purchases with their payment cards via MobilePay app in your webshop. This document guides you through the process of activating and implementing MobilePay as a payment method via Netaxept. Please forward this guide to the party responsible for the technical API implementation at your webshop, if necessary. For any issues concerning the activation or implementation of MobilePay via Netaxept, please contact your contact person at Nets or Netaxept Customer Support for your country Contents 1 MOBILEPAY VIA NETAXEPT BUSINESS FEATURES AND RESTRICTIONS PAYMENT FLOW SETTING UP NETAXEPT FOR USE WITH MOBILEPAY ACTIVATION OF PAYMENT METHOD REQUIREMENTS FOR API INTEGRATION RECEIVING SETTLEMENTS AND IDENTIFYING TRANSACTIONS SETTLEMENT BATCH AND TRANSACTION REFERENCE NUMBER IDENTIFICATION OF TRANSACTIONS PRICING... 8 Page 1/8

2 1 MobilePay via Netaxept 1.1 Business features and restrictions For the time being the following features and restrictions take place when using MobilePay via Netaxept. ID Feature / Restriction 1 Targeted to Finnish and Danish consumers, which need a local phone number to use the service. 2 Available for webshops, not for merchants using only call centre service. Additional paid payment method available in Start, Advanced and Premium service packages. 3 Supported payment cards for consumers are Visa, Visa Electron, Mastercard and Dankort. The prerequisite is that you have made an acquirer agreement with the acquirer who accepts payments with the particular payment card. Supported cards may differ from country to country. 4 Supported payment currencies are DKK and EUR. 5 Recurring payments for MobilePay via Netaxept are not supported. 6 If you have made both Netaxept and acquirer agreement for Visa, Visa Electron, Mastercard and/or Dankort, you don't need to sign any additional agreement to be able to accept payments via MobilePay. I.e. no separate agreement with Nets, acquirer or Danske Bank is needed. 7 Available for consumers whether or not they are customers at Danske Bank. Also your company doesn't need to be a customer at Danske Bank. 8 When paying with MobilePay, 3D Secure authentication is bypassed and all payments are considered and marked as non 3DS authenticated. 9 Card data which is needed to be able to shop online via MobilePay is stored safely and according to PCI DSS (Payment Card Industry Data Security Standard) requirements in DIBS Payment Services. Any card data is not saved in the consumer's mobile device or Danske Bank. 10 Payments done via MobilePay are considered and processed as regular card payments, and as such, all 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. 1.2 Payment flow Payment flow of the successful MobilePay payment goes as follows. The prerequisite is that the consumer has downloaded the MobilePay app in their smartphone and added there one or more payment card(s) that can be used for payments via MobilePay when shopping online. Besides card data, mobile phone number needs to be registered into the app and the consumer needs to approve which card(s) they want to use for online payment purposes. 1. When the consumer is shopping online and is moving to the payment phase, send the Register call to Netaxept. Depending on your technical API implementation, the payment method will be selected either in your webshop site or in Netaxept payment window. Page 2/8

3 If the consumer chooses the payment method in your webshop site, include "Mobilepay" in "Payment method action list" or "Payment method list" element in the Register call. If the payment method is selected in Netaxept payment window, "MobilePay" option is shown in the payment window together with the other payment methods. 2. After choosing "MobilePay", Netaxept forwards the consumer to the MobilePay site where the consumer is asked to enter their mobile phone number which is registered in the MobilePay app. 3. After entering mobile phone number, a push message will be sent to the consumer's smart phone to get a confirmation of the payment. The consumer has 5 minutes to confirm the payment in the MobilePay app. Page 3/8

4 4. The consumer logs in to their MobilePay app and approves the payment by swiping the "Approve payment" button. 5. During the approval process, Netaxept authorizes the payment automatically. If the authorization is accepted by the Issuer, the consumer receives a receipt in the MobilePay 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. 6. 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 need run capture to the payment either via Netaxept API by doing the Process(Capture) call or manually via Netaxept Admin. After the capture is done, the order amount is withdrawn from the consumer's payment card linked to the MobilePay app and settled to your company's bank account in the same settlement batch and within the same timeframe as your regular card payments. Page 4/8

5 2 Setting up Netaxept for use with MobilePay 2.1 Activation of payment method You can activate MobilePay in Netaxept Admin. The merchant is responsible for activating the payment method and ensuring that all information entered is correct. ID Requirement 1 Log in to Netaxept Admin by using the merchant ID and login password. Production environment: Test environment: 2 Go to "Options" => "Agreement" page. 3 Pick "MobilePay" from the drop down list and click "Add". 4 Select your desired currency (DKK or EUR), and enter the name of your webshop which you would like MobilePay to use for a cardholder statement. 5 Click "Add". If you have already made both Netaxept and acquirer agreement for Visa, Visa Electron, MasterCard and/or Dankort, you don't need to make any additional agreements to be able to accept payments via MobilePay. I.e. no separate agreement with Nets, acquirer or Danske Bank is needed. 2.2 Requirements for API integration If you have a working Netaxept API integration already, you may need to do some small adjustments to your API integration towards Netaxept to be able to take MobilePay in use in your webshop. To be sure everything works as expected check the following technical requirements before going live with MobilePay. If you don t have any Netaxept API integration yet, please visit our technical site at for more information about the general API integration. ID Requirement 1 If you use "Payment method action list" or "Payment method list" in the Register call, then payment method name "Mobilepay" needs to be added inside this element. This element is used if the payment method is selected in your webshop site or if you have wanted to define the order of the payment methods shown in Netaxept's payment window. 2 Generate a unique value in Order number field for each transaction. Re use of order number within same merchant ID not allowed. 3 On MobilePay transactions, Netaxept triggers AutoAuth for the transaction, therefore, you don t need to run the Process(Auth) on MobilePay transactions after the successful registration and Terminal phase. When you want to capture the payment, run the Process(Capture) call. Also, you can cancel the authorization by doing the Process(Annul) call if the purchase is cancelled already before the payment is captured. 4 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) after the successful registration and Terminal phase. To be able to implement MobilePay without changing this integration, the following workarounds have been done in Netaxept when MobilePay is in question: If you send the Process(Auth) call, then Netaxept ignores a repeating AUTH. Page 5/8

6 If you send the Process(Sale) call, then Netaxept runs a CAPTURE instead. If you send AutoSale in the Register call, then Netaxept runs a CAPTURE instead. However, we recommend you to implement MobilePay in your webshop in a correct way without the need of the workaround if possible. 5 Both full and partial refunds, meaning the Process(Credit) call, are supported. 6 In order to verify that the transaction is authorized successfully, 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. 7 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 (country specific and other restrictions may apply). 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. 8 MobilePay is not supported in Single page terminal. 9 MobilePay can be tested only in production environment due to lack of test environment for MobilePay in Danske Bank. I.e. you need to use your production merchant and own smart phone and payment card for testing purposes. Page 6/8

7 3 Receiving settlements and identifying transactions 3.1 Settlement batch and transaction reference number Payments done via MobilePay 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 payment via MobilePay is equal to card payment, the timeframe when the money is settled into your company's bank account will be the same as for regular card payments. Specifying a unique reference number for each MobilePay 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. 3.2 Identification of transactions MobilePay transactions can be identified both in Netaxept Admin and via API by using the Query call. Netaxept Admin In Transaction list you will see MobilePay logo next to the transaction done with MobilePay. In Details page you will see both MobilePay logo and the logo of the underlying card. In Advanced transaction search section, you are able to search payments done with MobilePay by selecting MobilePay as payment method. In the Query call, there is the Wallet element that contains MobilePay if the payment has been done via MobilePay. The underlying card is shown in the CardInformation.PaymentMethod and CardInformation.Issuer. <CardInformation> <Issuer>MasterCard</Issuer> <IssuerCountry>NO</IssuerCountry> <MaskedPAN>541300******0000</MaskedPAN> <PaymentMethod>MasterCard</PaymentMethod> <Wallet> <Issuer>MobilePay</Issuer> </Wallet> Page 7/8

8 4 Pricing MobilePay is additional paid payment method in Netaxept. It means that Nets will invoice the following fees as an addition to the regular Netaxept monthly and transaction fees. The monthly fee for each month you have MobilePay active in Netaxept Admin. The transaction fee for each successful MobilePay transaction. Unless otherwise agreed between Nets and the merchant, the fees will be charged in accordance with the price list in force at each time, or as stated in the Netaxept Admin s Agreement page. The fees will apply only to payments done in Netaxept production environment, not in Netaxept test environment. Also, unless otherwise agreed with your chosen acquirer, because payments done via MobilePay are considered as regular card payments, the acquiring prices remain the same. Page 8/8