MobilePay

MobilePay was developed by DanskeBank and it's an application for phones with operating systems iOS and Android being a digital wallet covering all payment needs. It was initially released on May 7, 2013 and the app allows users to connect a credit card and account information to their mobile number. This service is currently available in Denmark, Finland and Greenland.

MobilePay Specific Notes

• Only Danish Krona (DKK) and Euro (EUR) are supported currencies.
• The maximum length of order ID's is 50 characters
• You can use the same shop_orderid up to 4 times.
• Due to the nature of MobilePay, the customer can try multiple credit cards within its wallet to proceed with a transaction. The gateway will return notification for each attempt depending on the result. So there may potentially arrive multiple failure notifications before a successful one. Once a successful notification arrives, it means the payment went through. We advise our merchants to to be aware of this behavior and handle notifications accordingly.
• It is recommended to submit customer_info[cardholder_name] (Select MobilePay acquirer in dropdown) as MobilePay in some cases can provide non authorized credit card and that will require performing additional 3DSecure which requires Cardholder Name.
• Only Denmark and Finland are supported.

MobilePay Subscriptions Specific Notes

MobilePay Subscriptions is available only from Version: 20240508

Integration test cases can be found here

Recurring & Unscheduled Agreements (Subscriptions)

An agreement is a practical way of providing a customer with a service on a subscription basis.

• The customer will see amount, orderLines[0][itemId], orderLines[0][description] and agreement[frequency], agreement[next_charge_date] in the Agreement screen. It's recommended to use them to ensure a good customer experience. See example

Agreement With Initial Payment (Subscription + One-Off Payment)

The merchant can use this feature when he wants to initiate an agreement with a customer, and simultaneously, charge him immediately or allow him paying for additional items. The customer will have to swipe on the MobilePay app only once to approve it. See here an example on how the details are presented to the customer.

• Same parameters are required as for regular agreements. The subscription model order line description will be used for the charge description when it is the only one provided. Otherwise, the description will be computed from the other provided order lines except the subscription-dedicated one.
• The first order line is highlighted in the charges' descriptions, but all of them are shown when the customer opens the details page of it.
• The amount for the agreement will be used from the orderLines[0][unitPrice] where orderLines[0][goodsType] = 'subscription_model'. The payment request amount will be used for the one-off payment.
• Only Denmark and Finland are supported.

Unscheduled Agreements

• The customer will see the same fields as in recurring, however the amount parameter should generally be omitted when creating an Unscheduled agreement in order to not confuse the customer.

Recurring Payments (Subscription Payments)

• MobilePay handles Reservations and Captures.
• Subscriptions payments will be collected automatically, there is no need for customer interaction.
• The payment is executed by MobilePay within 2 days after providing us with the charge request.

Unscheduled Payments (One-Off Payments)

• The Merchant is resposnible for handling the Reservations and Captures.
• The default expiration of a payment is 1 day if it is not accepted or rejected by the customer. This expiration can be modified with `agreement_expiration_timeout` parameter
• Truncated payment reference will be visible in bank statement (30 characters limit).
• It is mandatory for the merchant to Capture or Cancel one-off payment if it was reserved on a customer account.
• The uncaptured unscheduled reservations expire after 7 days.
• Merchant initiated transactions will be automatically attempted to be reserved, however this feature needs to be requested by the merchant in advance.
• Partial captures are not supported. The Merchant can capture only the exact amount that was reserved on a customer account.

Releases

• The Merchant cannot reactivate a released agreement.
• The Customer cannot cancel an agreement that has pending payments on it. Only the Merchant can.
• The Merchant cannot release a recurring payment (Subscription Payment).
• The Merchant can always release an unscheduled payment after initiating it until it's captured, cancelled or expired.

Refunds

• A refund can be made up to 90 days after payment execution.
• Refunds are sent to users receiving bank account, not the card/account the payment was done from.
• Multiple partial refunds are supported as long as the compound amount is less or equal to the original value.