How to prepare MB WAY and Multibanco payments for your online shop
To accept MB WAY or Multibanco payment references in a shop, you need a compatible provider, an appropriate contract and an integration that updates orders correctly. Adding logos to checkout does not implement payments. Plan order creation, provider confirmation, stock and failure cases. Use a test environment and confirm current commercial conditions before enabling customer charges.
By the end, you can:
- Distinguish a request from confirmed payment
- Define stock rules and reference expiry
- Prepare failure, duplication and refund tests
Choose the provider for your operation, rather than the brand alone
List the payment methods your audience needs and compare providers supporting them on your chosen platform. SIBS presents solutions for MB WAY, Multibanco references and cards, with integration documentation. Other providers may offer different journeys. Confirm specific compatibility, registration documents, support, refunds and test environments, without assuming a generic integration covers everything.
Request written confirmation of commissions, monthly fees, settlement conditions, limits and additional-operation costs applicable to the account. Distinguish the payment service from integration work and shop maintenance. Do not publish a commission taken from an old promotion. A contract should be assessed by someone authorised to make that commitment for the company; this guide organises requirements and tests, rather than recommending a financial product.
Design statuses corresponding to real events
Separate order created, payment pending, confirmed, failed, expired and refunded. Someone may close the browser after paying, or return to the shop without completing the operation. The return page therefore informs the customer, while the commercial status needs reliable confirmation according to the provider’s integration. Ask the developer to explain the source of that confirmation.
Determine the communication accompanying each status. An order-received message should explain whether payment is still needed. Payment confirmation should identify the order and next stage without promising dispatch before preparation. Record status changes using the minimum data needed for reconciliation. Avoid including credentials, sensitive codes or complete payment information in support messages and shared screenshots.
- Create the order
Fix the items, variants, amount and internal reference.
- Start payment
Request the operation from the provider and show appropriate instructions.
- Receive confirmation
Verify the notification according to the technical contract and link it to the order.
- Update once
Confirm payment and trigger preparation without duplicating actions.
Requirements diagram. Event names and checks depend on the provider and integration version.
Define what happens while payment is pending
A pending reference may hold the last unit for some time. Choose whether stock is reserved, for how long and how the customer is informed. Confirm the provider’s and shop’s capabilities: payment expiry and stock-reservation expiry are related rules, but should not be confused. Document behaviour when availability changes.
Consider confirmation arriving after the reservation ends. The shop must have a procedure for checking the operation and contacting the customer, rather than automatically marking an impossible order as ready. If the integration cannot support a suitable policy, adjust the offer or deadline. Do not create a silent cancellation rule that leaves the team unsure whether a payment actually occurred.
Test ordinary cases and those often forgotten
Use the test data and procedures supplied by the provider. Perform a successful payment, a declined one and an interrupted one. Send the same notification again where the test environment permits, and confirm it does not duplicate orders, emails or stock reductions. Do not make real charges merely to produce a convincing screenshot. Production activation requires a controlled, authorised check of the contracted process.
Include payments started on a mobile phone, switching to the app and returning to the shop. Observe messages, the retry button and recovery of an order already created. Customers should not be encouraged to pay a second time just because the page has not yet shown the updated status. Support should be able to consult the internal reference and reconcile the operation with the provider.
| Case | Expected result | Evidence |
|---|---|---|
| Confirmed payment | One updated order | Reference and status match |
| Customer closes the page | Confirmation continues to be processed | Status updates independently of the return |
| Repeated notification | No duplicated commercial effect | Only one email and stock movement |
| Expired reference | New instructions or support, according to the rule | Previous order remains identifiable |
| Refund | Status and communication match the operation | Amount and reference reconciled |
Fictional scenario: a shop’s last backpack
A fictional shop has only one blue backpack. A buyer chooses a Multibanco reference and the system reserves the unit according to the defined policy. Another buyer sees current availability and cannot buy that same unit as though it were free. The team checks both the displayed text and internal status; a page label without a stock block would not suffice.
The first order expires without confirmation. The reservation is released and the record retains the reason for the change. During the test, the team also tests delayed confirmation and contact from a buyer claiming to have paid. The procedure requires reconciliation before requesting another payment. This is an illustrative scenario and does not describe capabilities automatically included in a template-based website or Lyntev results.
Prepare support and refunds before the first sale
Define which reference buyers should provide and who consults provider operations. Separate viewing access from permissions to refund or change settings. Decisions about returns and cancellations depend on the conditions and rules applicable to the sale, rather than just a dashboard button. Keep the procedure link and the list of authorised people.
Test a refund in the appropriate environment and confirm whether the shop receives the update or needs it recorded. Consider the distinction between a refund initiated and completed. Customers should receive information faithful to the status, with the correct support channel. During incidents, preserve necessary identifiers without sharing technical secrets. An integration is operationally complete only when the team can resolve a request that did not follow the expected journey.
Use an activation and reconciliation worksheet
Complete the worksheet with the shop supplier and the person monitoring orders. Mark each case as demonstrated, pending or outside scope. Do not turn a commercial feature list into technical evidence. Request the integration version and record dependencies so the next update can repeat essential tests.
Before promoting the shop, also confirm the journey without payment: view a product, learn the total and decide whether to proceed. Conditions and charges should be clear before commitment. The payment experience adds confidence when it matches an operation the business can monitor; the presence of a popular method alone cannot predict sales or eliminate every incident.
Worksheet for your project
Payment-method activation Provider, platform and integration version: Approved commercial conditions and date: Methods actually active: Payment confirmation source: Pending-stock and expiry policy: Handling repeated notifications: Normal, failed, interrupted and return tests: Late confirmation and reconciliation: People responsible for viewing and refunds: Outstanding issues before activation:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
