MobilePay

Introduction

MobilePay uses a redirect-based payment flow. When a customer selects MobilePay at checkout, they are redirected to the MobilePay app to authenticate and confirm their payment, then redirected back to your website or app upon completion. MobilePay is a single-use payment method where customers must authenticate each payment.

This guide explains the process of integrating MobilePay into your app or website using Payrails via Stripe.

Pre-requisites

Before you start accepting MobilePay payments with Payrails, there are a few requirements you must meet:

  1. Integrate with Payrails using one of our SDKs or our API
  2. Configure a new integration account for MobilePay via Stripe as a Payment Service Provider.
  3. Enable MobilePay as a payment method in your Stripe integration configuration. In the Payrails portal, navigate to Settings → Integrations, select your Stripe integration instance, and enable the MobilePay checkbox under Payment methods, then save the account.
  4. Enable MobilePay as a payment option in your workflow.
  5. Make sure you're sending the MobilePay-specific required meta fields in your requests (see Required meta fields below).

Ways to integrate MobilePay

Payrails SDK

The simplest way to use MobilePay with Payrails is to use our drop-in in your checkout flow. With this integration type, no additional work is required to accept payments with MobilePay except for handling success/failure screens for your users.

For a more flexible implementation using our SDK, you can use our genericRedirectButton element. See special instructions here for your client-side implementation.

Server-to-server integration

You can integrate MobilePay by completely managing your own client-side implementation, and using Payrails APIs with a server-to-server integration to process MobilePay payments.

Parse MobilePay from lookup response

With a server-to-server integration, you can call our lookup payment options endpoint to get available payment options. As shown in the example below, you can see mobilePay returned as an option of the paymentCompositionOptions.

{
  "name": "lookup",
  "actionId": "0bb6413e-cabb-4074-99e6-9e815c69f25b",
  "executedAt": "2026-03-26T12:00:00.000000000Z",
  "data": {
    "paymentCompositionOptions": [
      {
        "integrationType": "redirect",
        "paymentMethodCode": "mobilePay",
        "description": "MobilePay"
      }
    ]
  },
  "links": {
    "execution": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424",
    "authorize": {
      "method": "POST",
      "href": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424/authorize"
    }
  }
}

Required meta fields

MobilePay requires the following fields to be present in every authorize request:

FieldRequiredNotes
meta.order.billingAddress.name✅ YesCustomer's first name
meta.order.billingAddress.lastName✅ YesCustomer's last name
meta.order.billingAddress.country.code✅ YesISO-2 country code (e.g. DK or FI)
returnInfo.success / returnInfo.error✅ YesRequired for all redirect APMs

Pass MobilePay payment method in request to authorize payment with Payrails

You can then make a request to our authorize a payment endpoint with mobilePay as the paymentMethodCode. See an example below:

{
  "executionId": "c0fd1c51-e709-47e5-bfd1-5d1c98f7d990",
  "amount": {
    "value": "15000",
    "currency": "DKK"
  },
  "paymentComposition": [
    {
      "integrationType": "redirect",
      "paymentMethodCode": "mobilePay",
      "amount": {
        "value": "15000",
        "currency": "DKK"
      }
    }
  ],
  "meta": {
    "order": {
      "billingAddress": {
        "name": "Lars",
        "lastName": "Jensen",
        "country": {
          "code": "DK"
        }
      }
    }
  },
  "returnInfo": {
    "success": "https://mysuccessurl.com",
    "error": "https://myerrorurl.com"
  }
}

Note on amounts: DKK uses 2 decimal places. Amounts should be provided in the smallest currency unit — e.g., 15000 for DKK 150.00. MobilePay also supports EUR, NOK, and SEK.


Note: MobilePay is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to the MobilePay app to authenticate and confirm the payment. Once confirmed, the customer will be redirected back to the returnInfo.success URL. Make sure to provide valid returnInfo URLs in your authorization request.

Handle the redirect response

After the customer completes the payment, they will be redirected back to your success or error URL. You should then verify the payment status by checking the workflow execution status via the Payrails API or by listening to webhook notifications.

Supported currencies

MobilePay via Stripe supports the following presentment currencies:

  • DKK — Danish Krone
  • EUR — Euro
  • NOK — Norwegian Krone
  • SEK — Swedish Krona

Supported regions / countries

Customer regions

MobilePay is available to customers based in:

  • Denmark 🇩🇰
  • Finland 🇫🇮

Merchant regions

Stripe accounts across Europe can accept MobilePay payments (AT, BE, BG, CY, CZ, DE, DK, EE, ES, FI, FR, GR, HR, HU, IE, IT, LI, LT, LU, LV, MT, NL, NO, PL, PT, RO, SE, SI, SK).

Supported workflows and services

WorkflowSupported
Available via Payrails SDK✔️
Available via Payrails API✔️
Delayed / Manual Capture✖️
Instant Capture✔️
Cancel / Void✖️
Refund / Reverse✔️
Save Instruments✖️
Merchant Initiated Transaction (MIT)✖️