> ## 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.

# MB WAY

> Accept MB WAY wallet payments from customers in Portugal, and check the PSPs that process MB WAY through Payrails.

<picture noZoom>
  ![MB WAY logo](https://assets.payrails.io/img/logos/mbway/logo.svg)
</picture>

MB WAY is a digital wallet widely used in Portugal. Customers pay with the phone number linked to their MB WAY account, then approve each payment in the MB WAY app. MB WAY supports payments from 0.50 EUR to 5,000 EUR, and each customer has a daily limit they set in the app.

Payrails processes MB WAY through three payment service providers (PSPs). The customer approves the payment in the app with each one, but the required request fields and the way the result reaches you differ. Pick a PSP below for its setup steps and request examples.

## How an MB WAY payment works

MB WAY is an app approval payment method:

1. The customer selects MB WAY at checkout and enters their phone number.
2. Payrails sends the payment to the PSP with the customer's phone number.
3. The customer receives a notification in the MB WAY app and approves the payment.
4. Payrails receives the final result from the PSP and updates the payment.

Depending on the PSP, the customer either stays on your checkout while they approve in the app, or follows a redirect first. Each PSP guide describes its flow.

Payrails captures MB WAY payments immediately, so a successful payment is final. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md). Each MB WAY payment is a new customer-initiated payment.

## Supported currencies and countries

MB WAY supports EUR (euro) as its only presentment currency.

MB WAY is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Europe**</td><td>🇵🇹 Portugal</td></tr>
  </tbody>
</table>

## Integrate MB WAY

Choose the PSP that processes MB WAY for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Adyen logo
>
> AdyenMB WAY via Adyen
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/adyen.md)

> [card]
>
> Checkout.com logo
>
> Checkout.comMB WAY via Checkout.com
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/checkout-com.md)

> [card]
>
> Stripe logo
>
> StripeMB WAY via Stripe
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/stripe.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Adyen](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/adyen.md)</th><th>[Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/checkout-com.md)</th><th>[Stripe](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/stripe.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td><td>✔</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><td>✖</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><td>✔</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td><td>✖</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate MB WAY

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows MB WAY when your workflow returns it as a payment option. With Adyen, and with Checkout.com in the direct flow, the SDK collects the customer's phone number and shows a screen that asks the customer to approve the payment in the app. To control any redirect, listen for the [`actionRequired` event](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `mbWay` as the `paymentMethodCode`. Each PSP guide lists where to send the phone number and the other fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.


## Related topics

- [MB WAY via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/stripe.md)
- [MB WAY via Adyen](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/adyen.md)
- [MB WAY via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/checkout-com.md)


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