Automation · 8 min · 2026-11-07

Multibanco payment reminder by SMS: how to recover unpaid orders

Unpaid Multibanco orders hold stock. When to send the SMS reminder, what to write so it does not look like a scam and how not to remind people who paid.

MultibancoMB WAYUnpaid ordersShopify SMSifthenpay

Summary

What matters before moving forward.

  • On Shopify Payments, customers have 7 days to pay a Multibanco reference. If they do not, the order is cancelled and, until then, it shows as Payment pending.
  • With gateways such as ifthenpay, the reference validity depends on the contract and configuration, so reminder timing must follow that validity, not a fixed number.
  • The biggest risk of an SMS reminder is not technical, it is looking like a scam: Banco de Portugal has warned about fake SMS asking for payments by Multibanco reference.
  • A reminder sent to someone who already paid creates distrust and support requests. Payment status must be checked right before each send.
  • MB WAY works differently: customers have 4 minutes to approve and, without approval, the order is not even created on Shopify Payments.

Why Multibanco orders stay unpaid

Multibanco is a deferred payment method: the customer finishes checkout, receives an entity, a reference and an amount, and pays later in online banking, a banking app or at an ATM. Between the order and the payment there is a window where anything can happen.

The usual causes are mundane. The customer closes the tab before copying the reference, the email with the details lands in promotions, the purchase was made on a phone in the middle of something else, or the customer only wanted to hold the item while deciding. None of them gave up on the purchase; they simply did not come back.

For the store, each of these orders has a hidden cost. Stock stays reserved, the order sits in the work queue, and if the item is unique or low in stock, you may be losing another sale while waiting for a payment that never arrives.

How long the customer has to pay

On Shopify Payments the rule is documented: customers have 7 days from the order to pay, and if they do not, the order is cancelled. During that period the payment status in the admin is Payment pending. Shopify itself advises waiting for confirmation before fulfilling, because payment details can expire before the customer pays.

Many Portuguese stores do not use Shopify Payments and receive Multibanco through gateways such as ifthenpay, connected through their own app. In that case the reference validity is set in the contract and the gateway configuration, and it can be hours or days. The reminder has to be calculated from that validity, not from a value copied from a tutorial.

This detail changes everything. A reminder at 48 hours makes sense for a 7 day reference and is useless for a reference that expires in 24 hours.

When to send the reminder

Two moments are a good starting point. The first, a few hours after the order, catches people who forgot while the purchase is still fresh. The second, shortly before the reference expires, creates the real urgency of not losing the order.

Do not send more than that. Three or four SMS about the same payment stop being a service and become pressure, and every SMS has a cost.

Respect the clock as well. A payment reminder at 23:00 or 07:00 reads as debt collection or fraud. A window between 09:00 and 21:00, with a queue for anything outside it, solves the problem.

How to write a reminder that does not look like a scam

Banco de Portugal has warned about fraudulent SMS asking for payments by Multibanco reference, often imitating public bodies or well known companies, and reminds people that legitimate entities do not demand immediate payment by SMS. Your customer has seen these warnings on TV. A poorly written reminder looks exactly like what they learned to ignore.

So the reminder has to be recognisable. Identify the store by the name the customer knows, mention the order number and the items or exact amount, and always use the same entity and reference the customer received at checkout and by email. Never ask for card details or send people to a page that asks for bank details.

Avoid generic link shorteners and aggressive urgency words. Instead of overdue payment or final notice, write something like: Store X. Order 1043 for 49.90 EUR held for another 24 hours. Entity 12345 Ref 123 456 789. Help: storex.pt/contact. In Portuguese, avoid ç and ã so the text fits in a single 160 character SMS.

The most expensive mistake: reminding people who already paid

Multibanco payments do not all arrive at the same time. Some time can pass between the customer paying and the store receiving confirmation, and if the reminder is scheduled in that window the customer receives a request to pay for something they already paid.

The outcome is predictable: an email or a call asking whether they paid twice, or worse, a customer who pays the same reference again just in case. The fix is to check payment status at the moment of sending, not at the moment the reminder was scheduled.

The same applies to cancellations. If the order was cancelled manually or the customer asked to cancel, the reminder has to leave the queue.

What about MB WAY?

MB WAY works the other way round. On Shopify Payments, customers have 4 minutes to approve the payment in the MB WAY app or their banking app, and the order is only created after approval. Without approval there is no order, so there is nobody to send a payment reminder to.

With third party gateways the behaviour can be different, and in some cases the order is created with payment still open. In those cases recovery works by offering another method, such as a Multibanco reference, rather than asking the customer to retry MB WAY.

Before automating, confirm with your gateway how each method appears in Shopify. That answer defines the flow.

How Vokzar sets up payment recovery

We read the real validity of your references in the gateway you use, whether Shopify Payments or ifthenpay, and calculate reminders from it.

We tie SMS sending to payment status, with a check at the moment of sending, a time window and recognisable text that avoids the characters that double the cost. When the reference expires, the order is cancelled and stock goes back on sale, without waiting for someone to remember.

Finally, we deliver a simple record: how many orders were pending, how many were paid after the reminder and how many were cancelled. You see the value recovered in euros, not in open rates.

Related next steps

Next steps.

Proof and validation

  • The 7 day window, cancellation and Payment pending status come from Shopify's official help on Multibanco with Shopify Payments.
  • The 4 minute window and order creation after approval come from Shopify's official help on MB WAY.
  • Third party gateway rules vary by contract and must be confirmed with the gateway before automating.

Official documentation

Validated sources.

Technical strategy should be auditable. These sources link directly to the official documentation behind this guide.

Frequently asked questions

Common questions about this topic.

How long does a customer have to pay a Multibanco reference on Shopify?

On Shopify Payments, 7 days from the order. After that the order is cancelled. With gateways such as ifthenpay, validity depends on the contract and gateway configuration.

When should I send the payment reminder?

One reminder a few hours after the order and another shortly before the reference expires, within a 09:00 to 21:00 window. More than two reminders for the same payment tends to feel like pressure.

How do I stop the reminder looking like a scam?

Use the store name, the order number, the exact amount and the same entity and reference as checkout. Do not ask for bank details, do not use generic shorteners and include a store contact.

Can I send reminders for MB WAY payments?

On Shopify Payments there is no order without MB WAY approval, so there is nothing to remind. With third party gateways that create the order before approval, the best option is to offer a Multibanco reference instead.

Want to apply this to your site?

Next step Technical audit