Skip to main content

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:

Ways to integrate Multibanco

Payrails SDK

Server-to-server integration

Parse Multibanco from lookup response

Pass Multibanco payment method in request to authorize payment with Payrails

Note on amountsEUR uses 2 decimal places. Amounts should be provided in the smallest currency unit—for example, 2000 for €20.00.
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:

Required meta fields

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

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

Last modified on September 28, 2026