Mobilepay

MobilePay is a digital wallet that allows customers in Denmark and Finland to authorize online payments using the MobilePay app.

Overview

Property	Details
Markets (consumer)	`DK`, `FI`
Consumer currencies	`DKK`, `EUR`
Authentication methods	`REDIRECT` / `APP_AUTHORIZATION`
Authentication timeout	Subject to channel rules
Minimum payment amount	Subject to channel rules
Maximum payment amount	Subject to channel rules
Payment instrument	`DIGITAL_WALLET`
One-time payment	Yes
Recurring payments	No
Separate captures	No
Refund	Full · Partial
Refund validity	Subject to channel rules
Disputes	Subject to channel rules
Supported products	`Checkout Session` · `Hosted Checkout` · `Embedded Checkout` · `API`

Payment Flow

Customer selects MobilePay at checkout.

UseePay creates and confirms the PaymentIntent.

UseePay returns a redirect URL in next_action.redirect.

The merchant redirects the customer to the MobilePay authorization flow.

The customer opens the MobilePay app and reviews the payment information.

The customer authorizes the payment in the MobilePay app.

After authorization, the customer is returned to the URL specified in return_url.

UseePay updates the PaymentIntent and sends a webhook notification containing the final payment status.

Notes

MobilePay is primarily available to customers in Denmark and Finland.

Use:

DKK for customers in Denmark

EUR for customers in Finland

The final currency availability depends on the merchant configuration and enabled channel capability.

MobilePay is a redirect-based payment method. A valid return_url must be provided when creating or confirming the PaymentIntent.

MobilePay only supports automatic capture. Set auto_capture to true or omit it to use the default value.

The browser or application redirect does not represent the final payment result. Always retrieve the PaymentIntent or process the webhook notification before fulfilling the order.

The payment_method_data.mobilepay object currently does not require any MobilePay-specific business parameters. The optional extra_params object is reserved for extended channel parameters and should only be provided when instructed by UseePay.

Integration Guide

Create and Confirm a PaymentIntent

UseePay recommends creating and confirming the PaymentIntent in a single request by setting confirm to true.

Set:

payment_method_data.type to mobilepay

billing.address.country to DK or FI

currency to the currency supported for the customer market

confirm to true

return_url to the merchant result page

Request Example — Denmark

{
  "merchant_order_id": "order_mobilepay_001",
  "amount": 10000,
  "currency": "DKK",
  "confirm": true,
  "auto_capture": true,
  "return_url": "https://merchant.example.com/payment/return",
  "payment_method_data": {
    "type": "mobilepay",
    "billing": {
      "first_name": "Anders",
      "last_name": "Jensen",
      "email": "anders.jensen@example.com",
      "address": {
        "country": "DK"
      }
    },
    "mobilepay": {}
  }
}

Request Example — Finland

{
  "merchant_order_id": "order_mobilepay_002",
  "amount": 1000,
  "currency": "EUR",
  "confirm": true,
  "auto_capture": true,
  "return_url": "https://merchant.example.com/payment/return",
  "payment_method_data": {
    "type": "mobilepay",
    "billing": {
      "first_name": "Matti",
      "last_name": "Virtanen",
      "email": "matti.virtanen@example.com",
      "address": {
        "country": "FI"
      }
    },
    "mobilepay": {}
  }
}

Request Example (Java SDK)

Response Example

When customer authorization is required, the PaymentIntent returns requires_customer_action.

{
  "id": "1012611020000000003",
  "code": "0000",
  "message": "Approved or completed successfully",
  "amount": 10000,
  "currency": "DKK",
  "status": "requires_customer_action",
  "confirm": true,
  "orderType": "sale",
  "mode": "payment",
  "sale": true,
  "merchant_no": "500000000000000",
  "app_id": "merchant.example.com",
  "merchant_order_id": "order_mobilepay_001",
  "refunded_amount": 0,
  "next_action": {
    "type": "redirect",
    "redirect": {
      "method": "GET",
      "url": "https://payment.example.com/mobilepay/authorize",
      "content_type": null,
      "app_url": null,
      "package_name": null
    }
  },
  "return_url": "https://merchant.example.com/payment/return",
  "auto_capture": true,
  "payment_attempt": {
    "billing": {
      "address": {
        "country": "DK"
      }
    },
    "payment_method_details": {
      "type": "mobilepay"
    }
  }
}

When status is requires_customer_action, redirect the customer using the available value in next_action.redirect.

For a browser-based payment, use:

next_action.redirect.url

If an application deep link is returned, use:

next_action.redirect.app_url

At least one supported redirect value should be present according to the client environment and channel response.

Handling the Payment Result

After the customer completes the MobilePay authorization, the customer is returned to the configured return_url.

The merchant must then:

Retrieve the PaymentIntent from the server, or wait for the UseePay webhook.

Check the final PaymentIntent status.

Fulfill the order only when the status is succeeded.

Possible statuses include:

Status	Description	Merchant Action
`requires_customer_action`	Customer authorization is still required	Redirect the customer
`pending`	The payment is pending the final result from the payment provider	Wait for the webhook notification
`succeeded`	Payment completed successfully	Fulfill the order
`failed`	Payment failed or authorization was rejected	Display the failure and allow retry
`canceled`	Payment was canceled or expired	Close or recreate the payment

Always use the PaymentIntent status or webhook event as the source of truth. Do not rely only on the browser or application redirect.

Overview#

Payment Flow#

Notes#

Integration Guide#

Create and Confirm a PaymentIntent#

Request Example — Denmark#

Request Example — Finland#

Request Example (Java SDK)#

Response Example#

Handling the Payment Result#