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

> Set up Multibanco payments through Stripe in Payrails for customers in Portugal, including the voucher details to show the customer.

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

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

Accept [Multibanco](https://docs.payrails.com/docs/integrations/payment-methods/multibanco) payments from customers in Portugal with Stripe as the payment service provider (PSP). The customer receives a Multibanco voucher and pays it later through online banking or at an ATM.

## 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 Multibanco 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 Multibanco in your Stripe Dashboard payment method settings.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Stripe integration, select **Multibanco** under **Payment methods**, and save.
4. Add Multibanco 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 `EUR` and greater than zero. |
| `returnInfo` | Required | The URLs the customer returns to from the voucher page. |
| `meta.order.billingAddress.name` | Required | The customer's first name. Sent to Stripe as the billing name. |
| `meta.order.billingAddress.email` | Required | Sent to Stripe as the billing email. Stripe sends the voucher payment instructions to this address. |
| `meta.order.billingAddress.lastName` | Optional | Added to the billing name, for example `Inês Costa`. |
| `meta.order.billingAddress.country.code` | Optional | Sent to Stripe as the billing country, for example `PT`. |
| `meta.order.description` | Optional | Sent to Stripe as the payment description. |

## Authorize a Multibanco payment

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

```json Authorize request theme={null}
{
  "amount": {
    "value": "25.00",
    "currency": "EUR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "multibanco",
      "amount": {
        "value": "25.00",
        "currency": "EUR"
      }
    }
  ],
  "meta": {
    "order": {
      "billingAddress": {
        "name": "Inês",
        "lastName": "Costa",
        "email": "ines.costa@example.com",
        "country": {
          "code": "PT"
        }
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

The payment stays pending until the customer pays the voucher. 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.

### Show the voucher

The required action in the authorize response redirects to the Stripe-hosted voucher page. To show the voucher in your own checkout instead, read the voucher details from the required action's provider data:

| Field | Description |
| - | - |
| `entity` | The Multibanco entity number the customer pays to. |
| `reference` | The payment reference the customer enters. |
| `expiresAt` | When the voucher expires, as a Unix timestamp. |
| `hostedVoucherUrl` | The Stripe-hosted voucher page. |

## How Stripe handles Multibanco

* Stripe accepts Multibanco only in EUR. Payrails rejects other currencies before calling Stripe.
* Send an amount greater than zero.
* Each Multibanco payment is a new customer-initiated payment.

## Merchant regions

Merchants with Stripe accounts in Europe and the United States can accept Multibanco through Stripe.


## Related topics

- [Multibanco](https://docs.payrails.com/docs/integrations/payment-methods/multibanco.md)
- [Bancontact via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/bancontact/stripe.md)
- [iDEAL via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/ideal/stripe.md)


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