Connect Odoo to a card gateway that works for UAE merchants, so customers pay from the invoice or webshop and your accountant can match every net settlement to the right invoices and fees.
Odoo connects to payment gateways as payment providers linked to a payment journal, so customers pay quotations, orders or invoices online. Standard modules such as Stripe and Adyen can serve UAE-registered merchants, while local acquirers like Network International (N-Genius), Telr, PayTabs, Checkout.com, Tap or Amazon Payment Services usually need a third-party Odoo app or custom module. Settlements are then matched net of fees.
Odoo payment gateway integration in the UAE means configuring Odoo's payment providers so that customers can pay a quotation, sales order or customer invoice online by card, and so that the money that lands in your bank days later is matched to those invoices, net of the gateway's fees. In Odoo the gateway is set up under Accounting or Website as a payment provider, linked to a payment journal, and exposed through payment links, the customer portal and the eCommerce checkout.
The UAE adds a few wrinkles. Some providers that ship as standard Odoo modules, such as Stripe and Adyen, can serve UAE-registered merchants, while local acquirers that many Dubai businesses already use, such as Network International (N-Genius), Telr, PayTabs, Checkout.com, Tap or Amazon Payment Services, usually connect through a third-party app from the Odoo Apps store or a custom module built on the provider's API. Which route fits depends on your Odoo version, your hosting (Odoo Online, Odoo.sh or on-premise) and the acquirer your bank has already approved.
This page is specific to Odoo. For the platform-neutral view see ERP payment gateway integration in the UAE, and for the broader set of Odoo connections see our Odoo integration services. Matching the bank deposit itself is covered on Odoo bank integration.

The products we configure, integrate and support on projects like this one.
Product names and logos are trademarks of their respective owners and are shown only to identify the software we implement.
These are the patterns we find when UAE companies collect card payments outside Odoo or with a half-configured provider.
Sales staff create links in the acquirer's merchant portal and paste them into emails. Finance then has to guess which invoice a payment of a given amount belongs to.
The customer has paid, but nobody registered the payment in Odoo, so the reminder workflow sends a dunning email to a client who paid last week.
The acquirer deposits one net amount covering dozens of transactions minus fees, refunds and chargebacks. Without a clearing account the bank line cannot be reconciled cleanly.
Merchant discount fees are written off as a lump sum at month end, and the input VAT charged on those fees by a UAE acquirer is not claimed or is posted to the wrong account.
Card numbers are taken over the phone and keyed into a terminal or written down. That creates PCI DSS exposure that tokenized online payment avoids.
Monthly retainers and subscriptions are charged by hand each cycle, so missed renewals and failed cards are only spotted when the customer complains.
The flow below is for an invoice paid online. The same provider serves the webshop checkout and portal payments.
One shared database: every step updates stock, finance and reports in real time.
Field names vary by provider module; this is the typical data exchange for a UAE Odoo setup.
| Data | Direction | Trigger / frequency | Notes |
|---|---|---|---|
| Payment request (amount, currency, reference) | Odoo to gateway | Customer clicks pay link or checks out | Reference carries the invoice or order number so the payment can be traced |
| Transaction status | Gateway to Odoo | Real time via redirect and webhook | Authorized, done, cancelled or error; webhook covers customers who close the browser |
| Payment entry | Created in Odoo | On successful transaction | Posted to the provider's payment journal and an outstanding receipts account |
| Saved card token | Gateway to Odoo | When customer opts to save card | Only a token is stored in Odoo, never the card number; used for subscriptions |
| Refunds | Odoo to gateway | On credit note refund, where the provider supports it | Some third-party modules only support refunds from the merchant portal |
| Settlement report | Gateway to Odoo | Daily or per payout, usually by file import | Lists gross, fees, VAT on fees and net; drives the clearing account reconciliation |
| Chargebacks and disputes | Gateway to Odoo | As raised, often manual entry | Booked against the clearing account and the customer balance |
| Currency | Both | Per transaction | AED is typical; foreign currency cards may settle in AED with FX handled by the acquirer |
Availability changes between Odoo versions and app vendors, so we confirm the exact module for your version and acquirer before committing.
A focused gateway project is usually measured in weeks, not months, but acquirer onboarding can add time.
We check which acquirers your bank and business type qualify for, then match them to a maintained Odoo module for your version, or scope a custom provider if none exists.
We set up the payment journal, the outstanding receipts or clearing account, a fees expense account and the input VAT treatment, agreed with your accountant.
Payment links on invoices and orders, portal payments, webshop checkout and, if needed, tokenized payments for Odoo Subscriptions.
We map the acquirer's settlement report to an import format and reconciliation model so the net bank deposit clears the individual payments and fees.
Successful, failed, abandoned, refunded and partially paid scenarios are tested in the provider's test mode before switching to live keys.
Sales learn to send pay links; finance learn the daily clearing routine and how to handle chargebacks and refunds.
These are configuration considerations, not tax or legal advice; confirm the treatment with your tax advisor.
Using the gateway's hosted page or tokenization keeps card numbers out of Odoo and out of your servers, which keeps your PCI DSS responsibility much smaller.
Fees charged by a UAE acquirer normally carry 5% VAT on a tax invoice, which may be recoverable. Fees from a provider outside the UAE may fall under reverse charge. Your advisor should confirm the tax codes we configure.
Online payment does not replace the tax invoice. From the e-invoicing go-live dates, B2B invoices will flow through an Accredited Service Provider in PINT AE format, and the payment simply settles that invoice. See Odoo UAE e-invoicing and check the latest MoF/FTA guidance.
Customer names, emails and payment references are personal data under the UAE Personal Data Protection Law. Limit who can see payment transactions and keep only what you need.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
Benefits our clients look for, described without invented percentages.
Customers can pay the moment they receive the invoice instead of arranging a bank transfer or cheque.
Payments are posted against the right invoice automatically, so statements and reminders reflect reality.
Every settlement is broken down into payments, fees and VAT, so the gateway clearing account returns to zero.
Tokenized cards let Odoo charge subscriptions on schedule and flag failed renewals for follow-up.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertStripe and Adyen have standard Odoo modules and can serve UAE merchants, subject to their onboarding. Local acquirers such as Network International, Telr, PayTabs or Checkout.com typically connect through a third-party app or a custom module. We confirm what is maintained for your Odoo version before recommending one.
Yes. Once a provider is active, Odoo can add a pay-now link to the invoice email and the customer portal. The customer pays on the gateway's page and the invoice is marked paid when the transaction is confirmed.
Individual payments post to an outstanding receipts or clearing account. When the net deposit arrives, we import the settlement detail and use a reconciliation model to clear the payments and book the fees and VAT on fees, as described on our Odoo bank integration page.
Standard provider modules work on all hostings. Third-party or custom provider modules need Odoo.sh or on-premise, because Odoo Online does not allow custom Python modules.
Orders paid on Shopify or a marketplace are collected by that platform, not by Odoo's provider. Their payouts are reconciled differently; see Odoo Shopify integration and Odoo ecommerce integration.
No. Odoo stores a token issued by the gateway, and the gateway holds the card data. Renewals are charged with the token, which is the standard approach for PCI DSS.
Related Solutions
Related Industries
Related ERP Platforms
Tell us your acquirer, Odoo version and hosting, and we will map the provider, accounting and settlement routine for you.
Dubai, United Arab Emirates