Odoo payment gateways in Qatar
Every payment method and gateway that matters in Qatar, with what each one takes to reach Odoo: shipped with the product, a community module, a paid connector, or a build.
Every payment rail we check for a rollout in Qatar
19 entries, grouped by what each one costs you to reach from Odoo. The badge is the whole commercial question: shipped with the product, a community module, a paid connector, or a build.
In Odoo
4 of 19Ships with Odoo. Configuration, not development.
Qatari shoppers still pay at the door, and Qatar Post supports collection on delivery. It changes the Odoo setup because the sale order confirms before any money exists, so you need the courier to remit and a reconciliation step against the carrier statement.
Amazon Payment Services signs up merchants in Qatar and switches NAPS as a local method alongside Visa and Mastercard. It is one of the payment providers that ships inside Odoo 19, so it is the shortest route from a Qatari merchant account to a working Odoo checkout.
Local transfer in Qatari riyal is normal for B2B invoices and larger baskets. Odoo 19 ships a Wire Transfer method that prints your account details on the order and holds it until you confirm the money arrived.
Stripe ships inside Odoo 19, but Qatar is not on Stripe's list of countries where a business can open an account, so a Qatar registered company cannot collect in riyal through it. Budget for Amazon Payment Services, Tap, MyFatoorah, SADAD or Dibsy instead.
Community module
1 of 19A community module exists. Install, test, and budget for keeping it current across upgrades.
MyFatoorah names Qatar among the eight Middle East countries where it accepts payments and holds central bank licences across the Gulf. It is the only Gulf gateway on this list with a free Odoo 19 payment provider module, published by Cybrosys.
Paid connector
8 of 19A paid connector covers this. Licence cost sits outside our fee and is quoted separately.
NAPS is the debit network Qatari banks issue on, and QPay is the national e-commerce gateway that processes it under Qatar Central Bank. Tap Payments states NAPS carries over 70 percent of online transactions in Qatar, so an Odoo shop taking only Visa and Mastercard turns away most local buyers.
Himyan is Qatar Central Bank's own debit card brand, accepted at POS over NAPS and online through QPay. Noqoody lists Himyan next to NAPS and GCCNET, so you get it by asking your acquirer to enable it, not by adding a separate provider in Odoo.
Tap processes NAPS and QPay in Qatari riyal and covers Saudi, UAE, Bahrain, Oman and Kuwait off the same account. Worth choosing when one Odoo database sells into several Gulf countries.
SADAD is a QCB licensed Qatari payment company and the first fintech to integrate directly with NAPS and QPay, so Himyan and NAPS cards clear through it along with cards and Apple Pay. Several Odoo 19 connectors on the apps store are written for SADAD Qatar specifically.
Dibsy is licensed by Qatar Central Bank under the Payment Service Regulation and aims squarely at Qatari SMEs, taking NAPS, cards, Apple Pay and Google Pay. An Odoo 19 connector exists that lists exactly those methods.
SkipCash is a Qatari provider regulated by Qatar Central Bank, built around QR and NFC payments plus a hosted checkout. Three separate Odoo 19 modules exist for it, including one that drives payment from the point of sale.
Apple Pay is offered by the Qatari acquirers, including Dibsy, SADAD and Noqoody, and Qatari banks support it. You enable it at the gateway rather than as its own provider record in Odoo.
Google Pay sits next to Apple Pay in the Qatari acquirers' method lists, and the Odoo 19 Dibsy connector exposes it at checkout. Like Apple Pay it rides on your gateway contract.
Custom build
6 of 19No connector we would put in production. This is scoped, priced and built.
Fawran is Qatar Central Bank's instant payment service and it now reaches local e-commerce checkouts through QPay, where the buyer pays from a mobile number or alias instead of a card. Merchants have to register for Fawran separately, and Doha Bank was the participating bank when it went live on QPay.
Noqoody holds a QCB payment service provider licence and accepts NAPS, Himyan and GCCNET beside Visa, Mastercard, Apple Pay, Google Pay and Samsung Pay, with payment links and subscription billing. Nothing on the Odoo apps store connects to it, so this one is an API build.
Doha Bank runs its own merchant gateway covering domestic card schemes and bank transfers, with its Doha Pay wallet and QR payments, and it is the bank named for Fawran acceptance through QPay. Relevant when the client already banks there and wants one relationship.
Unconfirmed. Sources agreed, no primary confirmation found.
Ooredoo Money is one of the most used mobile wallets in Qatar and also sells a merchant gateway with QR and mobile payments. There is no Odoo payment connector for it, only an unrelated Ooredoo SMS module, so plan on an API build.
QMP is the mobile payment system regulated by Qatar Central Bank, used to send money, pay bills and pay merchants by QR code. Nothing links it to Odoo today, so it is a build if a client needs it at checkout.
Unconfirmed. Sources agreed, no primary confirmation found.
PayLater holds the first buy now pay later licence Qatar Central Bank issued, and it works with Qatar Islamic Bank on a Sharia compliant instalment product. If a Qatari buyer expects instalments at checkout, this is the locally licensed name, and it needs a custom Odoo integration.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build payments for Qatar
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Start from what buyers already carry. We pick the smallest set of providers that covers the methods your customers use, because every extra gateway is another reconciliation and another support surface.
- 2 Shipped providers first. Anything Odoo already carries is configured before anyone buys a connector. Paid connectors and custom work are priced up front, not discovered mid-project.
- 3 Four tests per provider. Authorization, capture, refund and a deliberate failure, run in sandbox, then repeated once in production with a small live amount.
- 4 Settlement is mapped to the ledger. Payouts, fees and chargebacks post to accounts your accountant agreed, so the bank reconciliation clears instead of leaving a suspense balance.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced payments plan for Qatar instead of a range.
- โ Your current gateway contracts and the fee schedule on each.
- โ A month of settlement reports, so the ledger mapping can be tested against real payouts.
- โ The currencies you collect in, and the entity that receives each payout.
Services behind this work
The rest of the Qatar localization detail
Each topic has its own page with the full item list, the same way this one does.
Payments in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope payments for your Qatar rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.