イメージプレビューA build-to-order Telr payment provider for Odoo 17/18/19
— accept cards, mada & Apple Pay with 3DS and webhook reconciliation.
Telr Payment Gateway for Odooとは？
A build-to-order Telr payment provider for Odoo 17/18/19 — accept cards, mada & Apple Pay with 3DS and webhook reconciliation. 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+
この製品について
This is a build-to-order Odoo module — not an instant download. ECOSIRE designs, builds, installs, and supports a native Telr payment provider for your Odoo 17, 18, or 19 instance (Community or Enterprise), then hands over the full source. Once live, your customers pay through Telr directly inside Odoo eCommerce, the Customer Portal invoice-pay flow, and Sales Order online payment links.
Under the hood we extend Odoo's payment.provider and payment.transaction models so Telr behaves like any first-class provider (Stripe, PayPal) in your database. The module ships a proper __manifest__.py declaring payment as a dependency, a provider record with your Telr Store ID and API credentials stored on encrypted config fields, and QWeb templates that render Telr's hosted payment page or embedded iframe at checkout. We wire Telr's server-to-server IPN/webhook to a controller route that verifies the signature, matches the transaction reference, and moves the payment.transaction state to done, cancelled, or error — so your accounting entries and sales orders reconcile automatically instead of by hand.
Because it is purpose-built for your setup, we align it to your exact currencies, your Odoo Accounting journals, your tax configuration, and your storefront theme. You get MENA-relevant methods — Visa/Mastercard, mada, and Apple Pay — behind Telr's PCI-compliant hosted page, full 3D Secure authentication, multi-currency support (AED, SAR and the rest of Telr's MENA set), and refunds triggered from the Odoo invoice/transaction without logging into a separate dashboard.
You keep the code. It is real Odoo — models/ORM with @api.depends computed fields, security via ir.model.access.csv and record rules so only authorized users touch provider credentials, XML/OWL views, and (where useful) automated actions for post-payment follow-ups. Delivery is typically one working week depending on scope, and every build ships with documentation, an admin walkthrough, and a support window.
得られるもの
- Full Odoo module source code (models, controllers, QWeb templates, ir.model.access.csv, record rules, __manifest__.py) — you own it, no per-transaction lock-in from us
- Installation and configuration on your Odoo 17/18/19 instance, including the Telr provider record wired to your Store ID and API credentials
- Webhook/IPN endpoint configured and verified end-to-end against your Telr merchant dashboard
- Sandbox-mode test transactions covering card, mada, Apple Pay, 3DS challenge, decline, refund and reconciliation before switch to live
- Admin & finance documentation — how to read transaction states, issue refunds, reconcile, and rotate credentials
- A live handover / training session for your team on operating and troubleshooting the gateway
- A defined post-launch support & bug-fix window with agreed response times
- Compatibility notes and a lightweight upgrade path for your target Odoo version(s)
これは誰のためのものですか
UAE / MENA SME merchant on Telr
A growing online seller in the UAE, Saudi Arabia, or wider MENA already using (or onboarding to) Telr who wants payments to run natively inside Odoo eCommerce instead of bolting on a hosted checkout or manual payment links.
Odoo administrator / finance controller
The person responsible for reconciliation and month-end. They want captured payments to auto-confirm sales orders and post against invoices, refunds handled from Odoo, and provider credentials locked down by security rules — not spreadsheets matching Telr statements by hand.
Multi-currency regional retailer
A business selling across AED, SAR and other MENA currencies that needs 3D Secure, mada and Apple Pay to reduce cart abandonment and satisfy local buyer expectations, with each currency mapped correctly to Odoo pricelists and accounting journals.
Telr Payment Gateway for Odoo の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Native Telr support in Odoo checkout | Purpose-built payment.provider — Telr appears natively in eCommerce, portal & SO pay links | Possible but you design the whole provider integration yourself | Depends on the listing; many are generic or region-limited | 含まれていない |
| mada + Apple Pay + regional cards | Configured for your MENA methods via Telr | Only if you build and test each method | 部分的なサポート | 含まれていない |
| 3D Secure enforced | 付属 | Must be implemented and verified by you | 部分的なサポート | 含まれていない |
| Webhook signature verification & auto-reconciliation | IPN controller verifies signature, matches transaction, posts against invoice | You write and secure the webhook + matching logic | Varies; some rely on redirect-only, missing async confirmations | 含まれていない |
| Refunds from inside Odoo | Full & partial refunds pushed to Telr API, state written back | Build the refund call and state sync yourself | 部分的なサポート | 含まれていない |
| Multi-currency MENA mapped to journals | AED/SAR/etc mapped to your pricelists & accounting journals | 付属 | 部分的なサポート | 部分的なサポート |
| Credential security (record rules + encrypted fields) | ir.model.access.csv + record rules gate credential access | Depends on your implementation discipline | Usually standard provider security only | 部分的なサポート |
| You own the source & it fits your setup | Full source handover, aligned to your version, theme & taxes | 付属 | Vendor-controlled; limited fit, upgrade at their pace | 含まれていない |
| Delivery model | Built, installed, tested & supported by ECOSIRE (one working week) | Your own dev time & risk | Instant download, then self-integrate/support | Already present but no Telr |
Telr Payment Gateway に関するよくある質問
How long until the Telr gateway is live on my Odoo?
This is a build-to-order module, not an instant download. Typical delivery is one working week from kickoff, depending on scope — number of currencies, iframe vs hosted-page checkout, and any custom reconciliation or theme work. We confirm a firm timeline after a short scoping call, build against your Telr sandbox credentials first, validate every flow, then schedule the switch to live.
What support and updates come with it?
Every build includes documentation, a team training/handover session, and a defined post-launch support window with agreed response times for bug fixes. Because you receive the full source, your team (or ECOSIRE on a support plan) can maintain it. We provide compatibility notes and an upgrade path so the module keeps working when you move between Odoo 17, 18 and 19; ongoing support and version-upgrade retainers are available on request.
Which Odoo versions and editions does it support?
It is built and tested for Odoo 17, 18 and 19, on both Community and Enterprise. It uses only standard payment framework extension points (payment.provider, payment.transaction, controller routes, QWeb) so it does not depend on Enterprise-only apps. We build specifically against the version you run.
Do I need a Telr merchant account, and where does card data live?
Yes — you need an active Telr merchant account; we integrate with your Store ID and API credentials, we don't resell payment processing. Card data is entered on Telr's PCI-compliant hosted payment page (or embedded iframe), so sensitive card details never touch your Odoo server, keeping your PCI scope minimal. 3D Secure is enforced for issuer-side authentication.
How do payments reconcile and how do refunds work?
Telr sends a server-to-server webhook/IPN back to a controller route in the module. We verify the signature, match it to the Odoo payment.transaction by reference, and move it to done, cancelled, or error. A successful capture confirms the sales order and posts the payment against the invoice automatically. Refunds — full or partial — are triggered from the Odoo transaction or invoice and pushed to Telr's API, with the refund state written back into Odoo.
Can I customize methods, currencies, or the checkout experience later?
Yes. You own the source code, so mada, Apple Pay, card schemes, supported currencies, and hosted-page-vs-iframe behavior can all be adjusted. Because it's native Odoo (ORM models, XML/OWL views, security via ir.model.access.csv and record rules, XML-RPC/JSON-RPC accessible), your developers or ours can extend it — for example adding automated post-payment actions or custom QWeb receipts.
関連モジュール
Telr Payment Gateway
A build-to-order Telr payment provider for Odoo 17/18/19 — accept cards, mada & Apple Pay with 3DS and webhook reconciliation.
- Native Odoo payment provider — extends payment.provider and payment.transaction so Telr appears alongside Stripe/PayPal in eCommerce, Customer Portal, and Sales Order pay links
- Telr hosted payment page redirect flow for full PCI SAQ-A scope reduction (card data never touches your Odoo server)
- Optional embedded iframe checkout so shoppers pay without leaving your storefront theme
- Card acceptance — Visa, Mastercard and regional card schemes routed through your Telr merchant account