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

# Multibanco

> Accept Multibanco voucher payments from customers in Portugal, and check the PSPs that process Multibanco through Payrails.

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

Multibanco is a voucher payment method widely used in Portugal. After checkout, the customer receives payment details with an entity number and a reference, and pays through online banking or at an ATM.

Payrails processes Multibanco through two payment service providers (PSPs). The voucher flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

## How a Multibanco payment works

Multibanco is a delayed notification payment method:

1. The customer selects Multibanco at checkout.
2. Payrails returns a redirect URL from the PSP, and the customer sees the voucher with the payment details.
3. The customer pays later through online banking or at an ATM.
4. The PSP confirms the payment, and Payrails updates it from the PSP webhook.

The payment stays pending until the customer pays, and confirmation can take several days, particularly over weekends. Fulfill the order only after you receive the confirmed result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status. Don't treat the customer's return to your site as proof of payment.

Each voucher is single-use. Payrails captures Multibanco payments when they're confirmed, so a successful payment is final. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

Multibanco supports EUR (euro) as its only presentment currency.

Multibanco 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 Multibanco

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

> [card]
>
> Stripe logo
>
> StripeMultibanco via Stripe
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/stripe.md)

> [card]
>
> Worldpay logo
>
> WorldpayMultibanco via Worldpay
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/worldpay.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Stripe](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/stripe.md)</th><th>[Worldpay](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/worldpay.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</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></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></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</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></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</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></tr>
  </tbody>
</table>

## Ways to integrate Multibanco

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Multibanco when your workflow returns it as a payment option, and redirects the customer to the voucher. To control how the redirect opens, 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 `multibanco` as the `paymentMethodCode`. Each PSP guide lists the `meta` fields that PSP requires.


## Related topics

- [Multibanco via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/stripe.md)
- [Multibanco via Worldpay](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/worldpay.md)
- [Worldpay](https://docs.payrails.com/docs/integrations/payment-providers/worldpay.md)


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