Multibanco

Introduction

Multibanco uses a redirect-based payment flow. When a customer selects Multibanco at checkout, they are redirected to a Stripe-hosted voucher page where their payment instructions are displayed. The customer then pays using their bank's online portal or at an ATM using the reference details provided. Multibanco is a single-use payment method.

This guide explains the process of integrating Multibanco into your app or website using Payrails via Stripe.

Pre-requisites

Before you start accepting Multibanco payments with Payrails, there are a few requirements you must meet:

1. Integrate with Payrails using one of our SDKs or our API
2. Configure a new integration account for Multibanco via Stripe as a Payment Service Provider.
3. Enable Multibanco as a payment method in your Stripe integration configuration. In the Payrails portal, navigate to Settings → Integrations, select your Stripe integration instance, and enable the Multibanco checkbox under Payment methods, then save the account.
4. Enable Multibanco as a payment option in your workflow.
5. Make sure you're sending the Multibanco-specific required meta fields in your requests (see Required meta fields below).

Ways to integrate Multibanco

Payrails SDK

The simplest way to use Multibanco with Payrails is to use our drop-in in your checkout flow. With this integration type, no additional work is required to accept payments with Multibanco except for handling success/failure screens for your users.

For a more flexible implementation using our SDK, you can use our genericRedirectButton element. See special instructions here for your client-side implementation.

Server-to-server integration

You can integrate Multibanco by completely managing your own client-side implementation, and using Payrails APIs with a server-to-server integration to process Multibanco payments.

Parse Multibanco from lookup response

With a server-to-server integration, you can call our lookup payment options endpoint to get available payment options. As shown in the example below, you can see multibanco returned as an option of the paymentCompositionOptions.

{
  "name": "lookup",
  "actionId": "0bb6413e-cabb-4074-99e6-9e815c69f25b",
  "executedAt": "2026-03-26T12:00:00.000000000Z",
  "data": {
    "paymentCompositionOptions": [
      {
        "integrationType": "redirect",
        "paymentMethodCode": "multibanco",
        "description": "Multibanco"
      }
    ]
  },
  "links": {
    "execution": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424",
    "authorize": {
      "method": "POST",
      "href": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424/authorize"
    }
  }
}

Required meta fields

Multibanco requires the following fields to be present in every authorize request:

Pass Multibanco payment method in request to authorize payment with Payrails

You can then make a request to our authorize a payment endpoint with multibanco as the paymentMethodCode. See an example below:

{
  "executionId": "c0fd1c51-e709-47e5-bfd1-5d1c98f7d990",
  "amount": {
    "value": "2000",
    "currency": "EUR"
  },
  "paymentComposition": [
    {
      "integrationType": "redirect",
      "paymentMethodCode": "multibanco",
      "amount": {
        "value": "2000",
        "currency": "EUR"
      }
    }
  ],
  "meta": {
    "order": {
      "billingAddress": {
        "name": "Maria",
        "lastName": "Silva",
        "email": "[email protected]",
        "country": {
          "code": "PT"
        }
      }
    }
  },
  "returnInfo": {
    "success": "https://mysuccessurl.com",
    "error": "https://myerrorurl.com"
  }
}

Note on amounts: EUR uses 2 decimal places. Amounts should be provided in the smallest currency unit — e.g., 2000 for €20.00.

Note: Multibanco is a delayed notification payment method. Unlike card payments, the customer is not redirected to your success_url immediately after submitting the form — they are redirected to the Stripe-hosted voucher page. Payment confirmation may be delayed by several days due to the bank transfer process, particularly over weekends. Use webhooks to monitor payment status and fulfill orders only after receiving a confirmed payment notification.

Handle the redirect response and webhooks

Because Multibanco is a delayed notification payment method, use webhooks to monitor payment status. The key events to listen for are:

Supported currencies

Multibanco via Stripe supports the following presentment currency:

• EUR — Euro

Supported regions / countries

Customer regions

Multibanco is available to customers based in:

• Portugal 🇵🇹

Merchant regions

Stripe accounts in Europe and the US can accept Multibanco payments.

Supported workflows and services