> ## 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 via Adyen

> Set up MB WAY payments through Adyen in Payrails, where the customer approves in the app without leaving your checkout.

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

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

Accept [MB WAY](https://docs.payrails.com/docs/integrations/payment-methods/mb-way) payments from customers in Portugal with Adyen as the payment service provider (PSP). The customer enters their phone number at checkout and approves the payment in the MB WAY app. The customer stays on your checkout, with no redirect.

## 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 MB WAY payment through Adyen:

1. Set up an Adyen integration in your workspace. Follow the [Adyen integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/adyen.md) if you don't have one yet.
2. Ask Adyen to enable MB WAY on your Adyen merchant account.
3. Configure Adyen webhook notifications for your integration. The payment completes only when Adyen sends the authorization result.
4. In the Payrails Portal, go to **Settings → Integrations**, open your Adyen integration, select **MB WAY** under **Payment methods**, and save.
5. Add MB WAY as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Adyen

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.currency` | Required | Must be `EUR`. Payrails rejects other currencies. |
| `paymentComposition[].paymentInstrumentData.payerFields.phoneCountryCode` | Required | The dialing code of the customer's phone, digits only, for example `351`. |
| `paymentComposition[].paymentInstrumentData.payerFields.phoneNumber` | Required | The customer's mobile number without the dialing code. Must be exactly nine digits. |
| `meta.customer.phone.number`, `meta.customer.phone.countryCode` | Optional | Used only when the payer fields carry no phone number. Payrails then requires `meta.customer.phone.number`. |
| `meta.customer.email` | Optional | Sent to Adyen as the shopper email. |
| `meta.customer.country.code` | Optional | Sent to Adyen as the country code, for example `PT`. |

## Authorize an MB WAY payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `mbWay` as the `paymentMethodCode`. Send the customer's phone number as payer fields.

```json Authorize request theme={null}
{
  "amount": {
    "value": "25.00",
    "currency": "EUR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "mbWay",
      "amount": {
        "value": "25.00",
        "currency": "EUR"
      },
      "paymentInstrumentData": {
        "payerFields": {
          "phoneCountryCode": "351",
          "phoneNumber": "912345678"
        }
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "ines.costa@example.com",
      "country": {
        "code": "PT"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

The response is pending and includes a wait action instead of a redirect. Show the customer a message that asks them to approve the payment in the MB WAY app. Then 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 Adyen handles MB WAY

* Payrails sends the phone number to Adyen in international format, for example `+351912345678`, and checks the payer fields before it calls Adyen.
* The wait action gives the client a 15-minute window to poll for the result, which matches the Adyen MB WAY approval time.
* Adyen captures MB WAY payments automatically. When Adyen confirms the authorization, Payrails also records the capture, so the payment completes in one step.
* MB WAY through Adyen supports customer-initiated payments only. Payrails rejects an MIT, or a request with a stored PSP token, before it calls Adyen.
* The Payrails SDK collects the phone number through payer fields when the amount is in EUR or isn't known yet.


## Related topics

- [MB WAY](https://docs.payrails.com/docs/integrations/payment-methods/mb-way.md)
- [MB WAY via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/mb-way/stripe.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.