Skip to Content

Get paid the way Portuguese shoppers actually want to pay

This euPago Odoo integration puts MB WAY, cards, Google Pay and Apple Pay behind one checkout option, priced in euro. Confirmed payments mark the matching invoice or sale order paid. Refunds and status checks happen on the Odoo payment record.

  • Odoo 17.0 – 20.0
  • Community & Enterprise
  • Odoo.sh · On-premise
  • Odoo Online

Top seller on the Odoo Apps Store

sales on the Odoo Apps Store
3,000+
apps published
100+
countries running them
100+

Portuguese online payments before and after this euPago gateway

Without the connector by hand

  1. Shoppers who want MB WAY give up on a card-only checkout.
  2. Someone checks euPago, then marks the invoice paid by hand.
  3. Every refund means signing in to the euPago backoffice.
  4. An order sits unpaid when the buyer closes the browser mid-payment.
  5. You search the euPago backoffice when a payment looks wrong.

With the connector automatic

  1. One euPago option covers cards, MB WAY, Google Pay and Apple Pay.
  2. A confirmed payment marks the matching invoice or order paid.
  3. You click Refund on the Odoo payment, for all or part.
  4. A background check settles payments the buyer never came back from.
  5. You click "Refresh from euPago" to pull the current status.

Payments, refunds and status checks between Odoo and euPago

Every object the connector handles, which way it travels and what triggers it.

DataDirectionWhat happens & when
Payment request

Customer picks euPago at checkout and chooses a method.
MB WAY phone number

Customer confirms the number, then approves in the MB WAY app.
Payment confirmation

euPago verifies the payment and notifies Odoo.
Refund, full or partial

You click Refund on the payment in Odoo.
Latest payment status

You click "Refresh from euPago" on the transaction.
Payments with no customer return

A background check runs on a schedule you set.

One checkout option, four ways to pay

Your Portuguese buyers see a single euPago line at checkout instead of four competing buttons. Inside it they pick MB WAY, card, Google Pay or Apple Pay. The same picker appears on your storefront, in the customer portal and on invoice payment pages, so a web order and an emailed invoice offer the same choices.

Odoo checkout with the single euPago option open, showing MB WAY, card, Google Pay and Apple Pay

MB WAY approved with a tap

MB WAY buyers finish without typing a card number. The customer confirms their phone number, which Odoo prefills from the contact record, and euPago sends the request to the MB WAY app for approval. There is no redirect, so the shopper stays on your site while the payment is accepted on their phone.

MB WAY step in the Odoo euPago checkout where the customer confirms a phone number

Cards and wallets on euPago's page

Card, Google Pay and Apple Pay payments open the secure page hosted by euPago. Card authentication is handled there, then the buyer is returned to your order or invoice page. Card details are entered on euPago's side and never reach your Odoo server, so the compliance burden stays with the payment provider.

euPago secure hosted payment page opened from an Odoo checkout for card and wallet payments

Transactions marked Done without you

Nobody has to open the euPago backoffice to find out whether money arrived. euPago sends Odoo a verified notification once a payment clears, and the matching transaction switches to Done. Your sales team sees a confirmed, paid order the moment the buyer finishes, whether the payment came from the shop or an invoice link.

Odoo payment transaction in Done state after euPago confirmed the payment

Invoices reconciled with no data entry

A cleared payment is matched to its invoice or sale order and the document is marked paid. Finance does no retyping for shop and portal payments. For collections work you send an invoice with a euPago payment link, the client pays, and the reconciliation is already recorded when you next open the record.

Odoo customer invoice marked paid and reconciled after a euPago payment

Refund a buyer in one click

Refunds start on the Odoo payment record, not in a second system. Open the payment, press Refund, and choose whether to send back everything or only a share of it. euPago credits the buyer, and the refund is recorded against the original payment so your accounts show it without extra entries.

Refund button on an Odoo euPago payment, used for a full or partial refund

Pull a late status on demand

A slow confirmation does not leave an order in limbo. Each transaction carries a "Refresh from euPago" button that fetches the current status straight away. A background check also runs on a schedule you set and closes out payments where the shopper never came back to your site. Neither needs a developer.

Refresh from euPago button on an Odoo transaction used to pull the latest payment status

Supported Odoo versions

Odoo versionEditionsHosting PriceLatest release
20.0 Community & Enterprise Odoo.sh · On-premise €99 No release notes Buy
19.0 Community & Enterprise Odoo.sh · On-premise €99 No release notes Buy
18.0 Community & Enterprise Odoo.sh · On-premise €99 No release notes Buy
17.0 Community & Enterprise Odoo.sh · On-premise €99 No release notes Buy

Support for Odoo euPago Payment Gateway

The developers who build the app answer your tickets.

Open a ticket Opens our helpdesk with this app already selected
Free app support from purchase
60 days
First response in working hours, typical
4–6 hours
Support hours, 10:00–18:00 IST
Mon–Fri

Support policy Support after 60 days

How to connect euPago to Odoo

  1. Enter your euPago keys

    Open the euPago provider record and paste the API Key so Odoo can request payments. Add the Client ID and Secret too, since refunds and status checks rely on them. Choose Sandbox or Production.

  2. Choose methods and publish

    Switch on only the methods you want shoppers to see, then set the provider to Published. euPago then shows as a payment option in your shop, in the customer portal and on invoice payment pages.

  3. Collect and reconcile

    Customers pay with their preferred method, and cleared payments mark the matching invoice or order paid. The background check and the refresh button on each transaction cover any confirmation that arrives late.

Questions before you buy

Not answered here? Talk to the team.

The gateway runs on Odoo Enterprise, either on your own server or on Odoo.sh, and on Odoo Community installed on your own server. Odoo Online does not allow third-party code, so it cannot be used there. We ship builds for Odoo 17.0, 18.0, 19.0 and 20.0, and each version is bought separately.

euPago bills in euro and the gateway is built for Portugal. MB WAY itself is a Portuguese payment method, so it suits shoppers in that market. Card, Google Pay and Apple Pay also work for anyone holding a card that can be charged in euro.

Visa and Mastercard are supported through euPago, together with Google Pay and Apple Pay wallets. All of them sit inside the same euPago option at checkout rather than as separate providers. MB WAY completes the set for Portuguese shoppers who prefer approving a payment on their phone.

That depends on the method they pick. MB WAY is approved inside the app, so the buyer stays on your pages the whole time. Card, Google Pay and Apple Pay briefly open euPago's secure page, then return the buyer to the order or invoice page they started from.

No. Shoppers type their card details on the page euPago hosts, and those details never arrive on your Odoo server. Security and compliance for the card data sit with euPago. That also keeps sensitive numbers out of your database and your backups.

Yes. The provider settings carry a switch for MB WAY, Google Pay and Apple Pay, so you decide which of them reach your checkout. Anything you leave switched off is not shown to shoppers. You can change the selection later without touching code.

Yes. Put the provider in Sandbox mode, enter the sandbox key from euPago, and run complete payments through your checkout to see how orders and invoices react. When the results look right, paste your live key and move the provider to Production. No code changes are involved.

Talk to the team that built it

Contact us
100%