> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# MobilePay via Stripe

> Set up MobilePay payments through Stripe in Payrails, and see the billing and currency rules Stripe applies to MobilePay.

<picture noZoom>
  ![MobilePay logo](https://assets.payrails.io/img/logos/mobilepay/logo-full-bleed.svg)
</picture>

<picture noZoom>
  ![Stripe logo](https://assets.payrails.io/img/logos/stripe/logo-full-bleed.svg)
</picture>

Accept [MobilePay](https://docs.payrails.com/docs/integrations/payment-methods/mobilepay) payments from customers in Denmark and Finland with Stripe as the payment service provider (PSP). The customer selects MobilePay, approves the payment in the MobilePay app and returns to your site.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

Complete these steps before you send your first MobilePay payment through Stripe:

1. Set up a Stripe integration in your workspace. Follow the [Stripe integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/stripe.md) if you don't have one yet.
2. Turn on MobilePay in your Stripe Dashboard payment method settings.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Stripe integration, select **MobilePay** under **Payment methods**, and save.
4. Add MobilePay as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Stripe

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `amount` | Required | Must be in `DKK`, `EUR`, `NOK` or `SEK`, and greater than zero. |
| `returnInfo` | Required | The URLs the customer returns to after the redirect. |
| `meta.order.billingAddress.name` | Required | The customer's first name. Sent to Stripe as the billing name. |
| `meta.order.billingAddress.lastName` | Optional | Added to the billing name, for example `Lars Jensen`. |
| `meta.order.billingAddress.email` | Optional | Sent to Stripe as the billing email. |
| `meta.order.billingAddress.country.code` | Optional | Sent to Stripe as the billing country, for example `DK`. |
| `meta.order.description` | Optional | Sent to Stripe as the payment description. |
| `meta.order.softDescriptor` | Optional | Shown on the customer's bank statement. |

## Authorize a MobilePay payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `mobilePay` as the `paymentMethodCode`. The response includes the redirect to MobilePay.

```json Authorize request theme={null}
{
  "amount": {
    "value": "150.00",
    "currency": "DKK"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "mobilePay",
      "amount": {
        "value": "150.00",
        "currency": "DKK"
      }
    }
  ],
  "meta": {
    "order": {
      "billingAddress": {
        "name": "Lars",
        "lastName": "Jensen",
        "email": "lars.jensen@example.com",
        "country": {
          "code": "DK"
        }
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

After the customer approves the payment, they return to your `success` or `error` URL. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Stripe handles MobilePay

* Stripe accepts MobilePay in DKK, EUR, NOK, and SEK. Payrails checks the currency before calling Stripe.
* Send an amount greater than zero. Payrails checks the amount before calling Stripe.
* MobilePay through Stripe supports customer-initiated transactions (CIT): the customer approves every payment in the app.

## Merchant regions

Merchants based in these countries can accept MobilePay through Stripe:

* Austria
* Belgium
* Bulgaria
* Croatia
* Cyprus
* Czech Republic
* Denmark
* Estonia
* Finland
* France
* Germany
* Greece
* Hungary
* Ireland
* Italy
* Latvia
* Liechtenstein
* Lithuania
* Luxembourg
* Malta
* Netherlands
* Norway
* Poland
* Portugal
* Romania
* Slovakia
* Slovenia
* Spain
* Sweden


## Related topics

- [MobilePay](https://docs.payrails.com/docs/integrations/payment-methods/mobilepay.md)
- [Vipps/MobilePay](https://docs.payrails.com/docs/integrations/data-sources/vippsmobilepay.md)
- [Amazon Pay via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/amazon-pay/stripe.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.