A made-to-order Odoo payment provider that brings pay-in-2x/3x/4x and deferred installment plans into your Website checkout, with real-time eligibility, on-page schedules, and payment confirmed only after the provider validates it. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19 environment. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A made-to-order Odoo payment provider that brings pay-in-2x/3x/4x and deferred installment plans into your Website checkout, with real-time eligibility, on-page schedules, and payment confirmed only after the provider validates it. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19 environment.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
French and EU B2C retailers running Odoo Website checkout consistently lose orders at the payment step when the only options are card and bank transfer. Shoppers who want to split a 400 EUR cart into three payments abandon rather than pay in full up front. Odoo core ships payment, account_payment, sale, and website_sale, but out of the box it has no concept of a BNPL provider that quotes an installment plan per cart, exposes eligibility in real time, or reconciles multi-installment settlement back into your accounting. You can bolt on a generic redirect provider, but it will not show shoppers a p2x/p3x/p4x schedule on the product page, will not gate plans by amount or market, and will not confirm the sale order strictly on a validated callback — which is exactly where conversion and reconciliation both break down.
Dedicated `payment.provider` record for the BNPL service with live/test API keys and merchant ID stored as provider fields
Real-time eligibility call to the provider REST API that returns available `p1x`/`p2x`/`p3x`/`p4x` and deferred plans keyed to the cart amount
Installment-schedule widget rendered on product and cart pages via QWeb/OWL, showing exact due dates and per-installment amounts
Redirect to the provider's hosted payment page with a signed, per-transaction payload
Webhook/IPN controller mapping provider states (`in_progress`, `paid`, `refused`, `expired`) onto `payment.transaction` and the linked sale order
Sale order confirmed strictly on a validated `paid` callback, with idempotent handling so retried callbacks never double-confirm
We build a dedicated payment.provider record for the BNPL service as a proper Odoo module. The provider model carries live and test API keys plus the merchant identifier, and a sandbox toggle that routes every call to the test endpoint with verbose transaction logging so your team can trace an order end to end before go-live. When a cart is priced, the module makes a real-time eligibility call to the provider's REST API and returns the plans available for that amount — pay-in-2x, 3x, 4x, and deferred options — which we render as an installment-schedule widget on both product and cart pages using QWeb/OWL templates, so the shopper sees the exact dates and amounts before committing. Plan availability is governed by per-plan minimum and maximum amount rules and by EUR / French-EU market gating, all editable from Odoo through fields on the provider and dedicated configuration models secured with ir.model.access.csv and record rules.
At checkout the customer is redirected to the provider's hosted payment page, and here we enforce the critical rule: the Odoo sale order is confirmed only after the provider validates the payment. A webhook/IPN controller handles every payment state the provider reports — in_progress, paid, refused, expired — updating the payment.transaction and driving the linked sale order accordingly, with idempotent handling so a retried callback never double-confirms. Because BNPL callbacks can be delayed, a status-reconciliation ir.cron job polls pending transactions and closes the loop when a webhook is late or lost. Refunds — full and partial — are issued through the provider's API from the Odoo backend and post the matching accounting entries, and merchant fees are surfaced on the transaction and booked so your finance team sees the true net. The module is built clean-room against the provider's public REST eligibility and hosted-page API, works across Odoo 17.0, 18.0, and 19.0, and runs on Community or Enterprise.
Because this is build-to-order, nothing is downloaded from an app store — we scope your exact requirements, build the module for your Odoo version and edition, test it on a staging instance against the provider sandbox, and hand over installable source and a git repository. Typical delivery is 2 to 4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); multi-company checkout, additional localization depth, extra accounting or reconciliation integrations, and non-standard checkout customizations increase the quoted scope. You receive a fixed quote after the scoping call.
Runs an Odoo Website store and wants to add a split-payment option shoppers already recognize, to lift average order value and cut checkout abandonment without leaving Odoo.
Owns conversion on the storefront and needs eligibility and schedules shown on product and cart pages, plus plan gating by amount and market, all configurable without a developer.
Needs every BNPL payment reconciled cleanly — validated capture, merchant fees booked, full and partial refunds posted as proper accounting entries, and no orders confirmed on unvalidated callbacks.
Implements Odoo for retail clients and wants a supported, source-delivered BNPL provider they can deploy across Community or Enterprise on 17/18/19 rather than maintaining a fragile in-house bridge.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة Alma Buy-Now-Pay-Later for Odoo ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن Alma Buy-Now-Pay-Later for Odoo، ثم اضغط على تثبيت.
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Delivery model | Built to order for your Odoo version and edition, source handed over | Built in-house or by a freelancer from scratch | Generic pre-built download, one-size-fits-all | |
| Real-time eligibility | Live REST call returning plans keyed to cart amount | Possible but must be designed and maintained yourself | Often static or limited plan display | |
| On-page installment schedule | QWeb/OWL widget on product and cart pages with dates and amounts | Requires custom front-end work | Basic badge or no schedule | |
| Validated capture | Order confirmed only on validated paid callback, idempotent | Risk of confirming before validation if built hastily | Varies; not always strict | |
| Refunds and accounting | Full/partial refunds via API with posted account.move entries and fee booking | Must be implemented and reconciled manually | Refund support inconsistent, fees rarely booked | |
| Delayed-callback reconciliation | Dedicated ir.cron polling pending transactions | Rarely built; orders can hang | Usually absent | |
| Plan and market gating | Per-plan min/max and EUR / French-EU rules editable in Odoo | Hard-coded unless designed for config | Limited configuration | |
| Support and ownership | Post-go-live support window, git repo and source ownership | Depends entirely on the developer's availability | Vendor-dependent, no source access |
No. This is a build-to-order module. ECOSIRE builds it for your specific Odoo version and edition, tests it against the provider sandbox on staging, and hands over installable source and a git repository. It is not a pre-built apps.odoo.com download.
Typical delivery is 2 to 4 weeks from confirmed scope. The exact timeline is set after the scoping call, based on your Odoo version, edition, multi-company needs, and any custom checkout or accounting requirements.
Pricing starts from $299 as an indicative single-company base-scope figure. After a short scoping call we assess drivers like multi-company, localization depth, extra integrations, and reconciliation complexity, then issue a fixed quote. You approve the fixed quote before any build work begins.
You get a post-go-live support window for defect fixes and configuration adjustments, and because you receive the full source and git repository you own the code. Compatibility work for future Odoo versions or provider API changes is quoted separately as needed.
No. The order is confirmed strictly on a validated paid callback from the provider's webhook, with idempotent handling. A status-reconciliation cron also polls pending transactions so delayed or lost callbacks are closed out reliably rather than leaving orders in limbo.
Yes. The module is built against Odoo core payment, account_payment, sale, and website_sale, so it runs on both Community and Enterprise across 17.0, 18.0, and 19.0. We build and test for the exact version you run.
Yes. Per-plan minimum and maximum amount rules are managed from Odoo, and plan availability is gated by EUR / French-EU market rules, so shoppers only see plans that are actually eligible for their cart and region.
A made-to-order Odoo payment provider that brings pay-in-2x/3x/4x and deferred installment plans into your Website checkout, with real-time eligibility, on-page schedules, and payment confirmed only after the provider validates it. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19 environment.