イメージプレビューBuild-to-order Odoo module for Tap Payments
— one GCC checkout for KNET, mada, Benefit, cards & Apple Pay, with 3DS, refunds & webhooks.
Tap Payments Gateway for Odoo (GCC)とは？
Build-to-order Odoo module for Tap Payments — one GCC checkout for KNET, mada, Benefit, cards & Apple Pay, with 3DS, refunds & webhooks. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
Selling across the Gulf means supporting the payment methods your customers actually trust — KNET in Kuwait, mada in Saudi Arabia, Benefit in Bahrain, plus international cards and Apple Pay — each with its own SCA rules and settlement currency. Wiring all of that into Odoo one integration at a time is slow and fragile. This build-to-order module gives you a single Tap Payments connector that surfaces every Gulf method through one unified checkout in your Odoo store, website, and quotations portal.
ECOSIRE designs, builds, installs, and supports this module specifically for your Odoo instance — it is not an off-the-shelf apps.odoo.com download you install blind. We implement it as a proper Odoo payment provider: a payment.provider record with your Tap credentials, a payment.transaction extension that maps Tap's charge and authorization lifecycle onto Odoo's draft → pending → authorized → done → cancel/error states, and a controller that handles Tap's hosted-payment redirect and JSON webhook callbacks. Amounts, currencies, and references are validated server-side before any transaction is confirmed, so a spoofed redirect can never mark an order paid.
Under the hood it follows Odoo conventions you can maintain: models extend models.Model, computed fields use @api.depends, access is locked down with ir.model.access.csv plus record rules so only accounting and sales users see raw gateway data, and merchant-facing screens are delivered as XML/OWL views with a QWeb payment receipt. Webhook reconciliation matches Tap events back to the originating transaction idempotently, refunds are issued from the Odoo invoice or order, and tokenized cards enable recurring charges for subscription and installment flows. The connector speaks to the rest of Odoo through the standard payment framework, so it works with eCommerce checkout, the customer portal invoice-pay button, sale-order online payment, and your own XML-RPC/JSON-RPC automations without bespoke glue.
Built and tested against Odoo 17, 18, and 19 (Community and Enterprise), on your Tap sandbox first, then promoted to live once you sign off. You get the source, the configuration, documentation, a training session, and a post-go-live support window — a connector your team owns rather than a black box.
得られるもの
- Complete Odoo module source (the addon directory: __manifest__.py, models, controllers, security, views, QWeb receipt and data) targeting your chosen Odoo 17, 18 or 19 line
- Installation on your environment (staging then production, Community or Enterprise) with the payment.provider configured for your Tap merchant account
- Tap sandbox integration end-to-end, followed by supervised go-live with your live API keys and webhook endpoint registered in the Tap dashboard
- Configuration of supported methods (KNET, mada, Benefit, cards, Apple Pay), enabled currencies, 3DS behavior and per-company/per-website routing
- Administrator and finance-team documentation: how transactions, refunds, tokens and webhook reconciliation work, plus a troubleshooting runbook
- A live training / handover session for your finance and store-operations staff, with a recording
- A defined post-go-live support and bug-fix window covering the delivered scope, with a named point of contact
- Source handover to your repository so your team fully owns and can maintain the connector
これは誰のためのものですか
GCC eCommerce retailer
An online retailer selling across Kuwait, Saudi Arabia, Bahrain and the UAE who needs KNET, mada, Benefit, cards and Apple Pay in one Odoo checkout instead of stitching several plugins together, with settlement in the right local currency.
Regional SaaS / subscription business
A subscription or installment business that needs tokenized, recurring Tap charges tied to Odoo invoices and sale orders, so renewals bill automatically without re-entering card details and dunning stays inside the ERP.
Multi-entity Gulf group finance lead
A finance or ERP owner running several storefronts or legal entities on one Odoo database who needs each website routed to its own Tap merchant account, with refunds, reconciliation and role-restricted access all handled inside Odoo accounting.
Tap Payments Gateway for Odoo (GCC) の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| All GCC methods (KNET, mada, Benefit, cards, Apple Pay) in one connector | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Tailored to your Odoo version, edition and workflow | 付属 | 付属 | 含まれていない | 部分的なサポート |
| 3D Secure / SCA with server-side amount & reference verification | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Multi-currency GCC with correct KWD/BHD 3-decimal handling | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Tokenized recurring / subscription charges tied to Odoo invoices | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Idempotent webhook reconciliation + full/partial refunds in Odoo | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Source ownership, docs, training and a support window | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Version-upgrade path (17/18/19) maintained for you | 付属 | 含まれていない | 部分的なサポート | 部分的なサポート |
Tap Payments Gateway に関するよくある質問
How long until the module is live, and what's the process?
Typical delivery is one working week from kickoff, depending on scope (methods, currencies, recurring/subscription needs, multi-entity routing). This is a build-to-order module — not an instant download. We start on your Tap sandbox, build and test the full charge, refund, 3DS and webhook flow, install on your staging environment for sign-off, then do a supervised cut-over to live Tap keys on production.
Which Odoo versions and editions do you support?
We build against Odoo 17, 18 and 19, on both Community and Enterprise. Because it is implemented as a standard Odoo payment provider (payment.provider / payment.transaction) using the framework's own hooks, it works with website eCommerce, the customer portal and sale-order online payment on each of those versions. Tell us your exact version and we target that line.
What support and updates do I get after go-live?
Delivery includes a defined post-go-live support and bug-fix window covering the delivered scope, with a named contact for issues. Because you receive the full source, your team can maintain it independently afterward; we also offer an optional ongoing support/maintenance retainer for Odoo version upgrades, new Tap features or method additions beyond the initial window.
Do I need a Tap Payments merchant account?
Yes. You provide your own Tap merchant account and API credentials (sandbox and live). Tap approves your business and settles funds to you directly; our module is the connector between Tap and Odoo. We help you register the webhook endpoint and configure which methods and currencies are enabled, but the Tap contract and payouts remain between you and Tap.
Is it secure, and does card data touch my Odoo server?
Payment authentication runs through Tap's hosted flow with 3D Secure / SCA, so raw card entry happens on Tap's PCI-compliant pages, not your Odoo forms. Odoo stores only a reusable token for repeat/recurring charges. On our side, every webhook and return is verified server-side for amount, currency and reference, access to gateway data is restricted via ir.model.access.csv and record rules, and secrets live in Odoo's server configuration rather than in any view.
Can it handle recurring subscriptions and installments?
Yes. Cards can be tokenized (as an Odoo payment.token) so you can charge customers again without re-entry — driving subscription renewals, installment schedules or saved-card one-click checkout. Recurring charges are tied to the originating Odoo invoice or sale order, and failed/renewed payments update transaction state so your dunning and reconciliation stay accurate inside the ERP.
関連モジュール
Tap Payments Gateway
Build-to-order Odoo module for Tap Payments — one GCC checkout for KNET, mada, Benefit, cards & Apple Pay, with 3DS, refunds & webhooks.
- Unified Tap Payments provider exposing KNET, mada, Benefit, international cards and Apple Pay through one Odoo checkout
- Odoo payment framework native: a payment.provider record plus a payment.transaction subclass mapping Tap's charge lifecycle to Odoo's draft/pending/authorized/done/cancel states
- 3D Secure 2 / SCA support — Tap's authentication challenge is honored and the transaction only completes on a verified redirect
- Multi-currency GCC handling for KWD, SAR, AED and BHD, including correct minor-unit scaling (KWD/BHD use 3 decimals) so charge amounts match Tap exactly