Build-to-order Odoo 17/18/19 PayTabs gateway: on-page tokenized card & local-method checkout across 7 MENA countries. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo 17/18/19 PayTabs gateway: on-page tokenized card & local-method checkout across 7 MENA countries.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
This is a build-to-order Odoo payment provider module that ECOSIRE designs, develops, installs, and supports for your specific environment — it is not an instant apps.odoo.com download. After purchase we scope your PayTabs profiles, currencies, and target countries, then deliver a production-ready module for Odoo 17, 18, or 19 (Community or Enterprise) within a typical 2–4 week lead time.
On-site tokenized card capture rendered inside Odoo checkout via PayTabs's PCI-scoped fields — no redirect to a hosted page, card data never stored in Odoo
mada (Saudi Arabia) and KNET (Kuwait) local-scheme acceptance routed through your PayTabs profiles
Apple Pay and STC Pay wallet checkout wired into the Website eCommerce flow
Registered as a native Odoo payment.provider — appears in Website checkout, Sales/Invoicing Pay-Now links, customer portal, and Subscriptions
Multi-currency MENA support: each PayTabs profile ID mapped to the correct Odoo currency and account.journal (e.g. SAR, AED, KWD, EGP, OMR, JOD)
Server-to-server IPN/webhook controller with signature validation that reconciles transactions even if the shopper drops off before redirect
The module registers PayTabs as a first-class payment.provider in Odoo, so it appears natively in Website eCommerce checkout, the Sales/Invoicing "Pay Now" links, the customer portal, and Subscriptions. Instead of bouncing shoppers to a hosted page, we integrate PayTabs on-site card capture so the card form renders inside your Odoo checkout and returns a reusable token — card PAN and CVV are collected by PayTabs's PCI-scoped iframe/fields and never touch your Odoo database, keeping your PCI-DSS scope minimal (SAQ A style) while preserving your branded, single-page flow.
Beyond raw cards, we wire the local rails your MENA customers actually reach for: mada in Saudi Arabia, KNET in Kuwait, Apple Pay, and STC Pay, all routed through your PayTabs merchant account across its seven supported markets (Saudi Arabia, UAE, Egypt, Oman, Jordan, Iraq, and the wider GCC footprint your profile covers). Multi-currency is handled by mapping each PayTabs profile ID to the right Odoo currency and journal, so an AED cart and an SAR cart settle correctly and reconcile against the matching account.journal.
Reliability is built on PayTabs's server-to-server IPN/webhook. We expose a secured controller route in Odoo that validates the signature, matches the transaction reference back to the originating payment.transaction, and moves it through Odoo's standard _set_done / _set_pending / _set_error state machine — so an order confirms even if the shopper closes the browser before the redirect completes. Refunds and partial refunds are issued directly from the Odoo transaction or the related invoice via PayTabs's refund API, keeping accounting and the payment provider in sync without logging into a separate dashboard.
Everything ships as a clean, upgrade-safe Odoo addon: a proper __manifest__.py, models extending payment.provider and payment.transaction, ir.model.access.csv plus record rules for least-privilege access to credentials, backend and website QWeb/OWL views for the checkout widget, and server-action/automated-action hooks for reconciliation alerts. You get the full source — no obfuscation, no per-transaction lock-in — so your team (or ECOSIRE on a support retainer) can maintain it across future Odoo upgrades.
Runs an Odoo Website store selling across Saudi Arabia, the UAE and beyond, and needs one PayTabs integration that accepts mada, KNET, Apple Pay and cards without sending shoppers off-site — while keeping order confirmation reliable.
Wants payments, refunds and multi-currency settlement to reconcile automatically against the right Odoo journals, and to issue full or partial refunds from the invoice instead of logging into a separate PayTabs dashboard.
Needs a clean, source-available, upgrade-safe addon with proper security rules and webhook handling that their team can maintain across Odoo 17/18/19 upgrades, rather than a black-box connector with per-transaction lock-in.
Buy the license on ecosire.com and download the PayTabs Payment Gateway for Odoo (MENA) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for PayTabs Payment Gateway for Odoo (MENA), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| On-site tokenized card capture (no redirect) | Yes — PayTabs fields embedded in your Odoo checkout, token stored, single-page branded flow | Possible but you build and PCI-scope the iframe integration yourself | Often redirect/hosted-page only; on-site capture varies by add-on | |
| mada, KNET, Apple Pay, STC Pay local methods | Yes — enabled per country via your PayTabs profiles | Only if you implement each scheme against the API | ||
| IPN/webhook reconciliation (confirms on drop-off) | Yes — signed controller route ties callbacks to payment.transaction | You must build and secure the webhook handler | ||
| Refund & partial refund from inside Odoo | Yes — issued from the transaction or invoice via PayTabs refund API | Requires custom API wiring to the refund endpoint | ||
| Multi-currency MENA profile-to-journal mapping | Yes — each profile mapped to the right currency and account.journal | You design the mapping and journals yourself | ||
| Full source, upgrade-safe across Odoo 17/18/19 | Yes — clean addon, ir.model.access.csv + record rules, no lock-in | You own it but also own all maintenance from scratch | Source often obfuscated or license-locked | |
| Least-privilege access to API credentials | Yes — record rules restrict key visibility to finance/admin | Depends entirely on your implementation discipline | ||
| Built, installed & supported for your exact environment | Yes — scoped build, supervised go-live, defined support window | Your internal team's time and risk |
This is a build-to-order module, not an instant download. After purchase we hold a short scoping call to confirm your Odoo version (17/18/19), edition, target countries, PayTabs profiles and currencies. We then build, test in sandbox, and deliver a production-ready addon within a typical 2–4 week lead time depending on how many local methods and currencies you need. Go-live includes a supervised real test transaction and refund before we hand over.
Every build includes a defined post-launch support and warranty window covering bug fixes and compatibility with Odoo point releases on your version. You receive the full source code, so your team can maintain it, and ECOSIRE offers an optional ongoing support retainer for Odoo major-version upgrades (e.g. 18→19), new PayTabs methods, or additional country/currency rollouts.
No. Card PAN and CVV are captured by PayTabs's PCI-scoped fields/iframe and exchanged for a token — the sensitive data never lands in your Odoo database. This on-site tokenized approach keeps your checkout branded and single-page while holding your PCI-DSS scope to the minimal SAQ-A tier. Only the transaction reference and token metadata are stored on the payment.transaction record.
The module works with your PayTabs merchant account across its seven MENA markets (including Saudi Arabia, UAE, Egypt, Oman, Jordan, Iraq and the surrounding GCC coverage on your profile). It supports mada, KNET, Apple Pay, STC Pay and international/local cards, and maps each PayTabs profile to the correct Odoo currency and journal for multi-currency settlement. We enable methods per the countries you actually sell into.
Yes. We rely on PayTabs's server-to-server IPN/webhook, not just the browser redirect. A secured Odoo controller validates the callback signature, matches it to the originating payment.transaction, and drives Odoo's standard state machine (_set_done / _set_pending / _set_error) — so a successful payment confirms the order and invoice even when the shopper drops off before returning to your site.
Both. The module registers PayTabs as a standard payment.provider, which exists in Odoo Community and Enterprise for versions 17, 18 and 19. We tailor the build to your exact edition and version at scoping time; Enterprise-only touchpoints (like certain Subscriptions or accounting automations) are wired only when your edition includes them.
Build-to-order Odoo 17/18/19 PayTabs gateway: on-page tokenized card & local-method checkout across 7 MENA countries.