Skip to main content

Multibanco

Multibanco References are the Portuguese way of paying by reference. When you create a payment, SIBS issues a payment entity and reference for the exact amount. You show them to the customer, who pays later at any Multibanco ATM, in home banking or in a banking app. Payment can happen minutes or days later, up to the reference's expiry.

There is no hosted page and no browser redirection. The result of the payment is delivered by postback.

Available inNetworksCurrenciesFeaturesIntegrationspayment_type
PortugalMultibanco / SIBSEUR
  • Server-to-Server
  • Checkout Page
  • Pay by Link
  • Payment Page Redirect
multibanco

Payment workflow​

The following diagram explains the Multibanco payment workflow for the Server-to-Server integration.

Multibanco — Server-to-Server
Payer
Merchant (Acceptor)
OneAPI
SIBS (Multibanco)
1. Chooses Multibanco at checkout
2. Create payment (Payment API, payment_type multibanco)
3. Generate a payment reference
4. Response with status pending (2), entity, reference and expiry
5. Shows entity, reference, amount and expiry
Pays later at an ATM, in home banking or in a banking app
6. Pays the reference
7. Payment notification
Status changes to completed (3). An unpaid reference becomes reversed (12) after it expires
8. Postback — completed (3)
9. Confirms the order

Scroll horizontally if the diagram is wider than your screen.

  1. 1
    PayerMerchant (Acceptor)

    1. Chooses Multibanco at checkout

  2. 2
    Merchant (Acceptor)OneAPI

    2. Create payment (Payment API, payment_type multibanco)

  3. 3
    OneAPISIBS (Multibanco)

    3. Generate a payment reference

  4. 4
    OneAPIMerchant (Acceptor)

    4. Response with status pending (2), entity, reference and expiry

  5. 5
    Merchant (Acceptor)Payer

    5. Shows entity, reference, amount and expiry

  6. Payer

    Pays later at an ATM, in home banking or in a banking app

  7. 6
    PayerSIBS (Multibanco)

    6. Pays the reference

  8. 7
    SIBS (Multibanco)OneAPI

    7. Payment notification

  9. OneAPI

    Status changes to completed (3). An unpaid reference becomes reversed (12) after it expires

  10. 8
    OneAPIMerchant (Acceptor)

    8. Postback — completed (3)

  11. 9
    Merchant (Acceptor)Payer

    9. Confirms the order

The transaction moves through the following statuses. The Status Code column is the transaction's status code:

StatusStatus CodeWhen
pending2The reference was issued and is waiting to be paid
completed3The customer paid the reference
reversed12The reference expired without being paid
refunded7There are partial or full refunds for this payment
canceled5The reference was cancelled before it was paid (Reversal API)
error4SIBS could not issue the reference
note

pending means the reference exists, not that it has been paid. Do not ship the order until you receive the completed postback. The reversed postback for an unpaid reference is sent shortly after its expiry time. If SIBS still reports a payment for it afterwards, the transaction becomes completed and a postback is sent.

Integration options​

Choose how you want to accept Multibanco:

Server-to-Server

Create the payment via the Payment API, receive the Multibanco entity and reference in the response, and show them to the customer in your checkout, e-mail or invoice.
Start integrating