Build-to-order Paystack gateway for Odoo 17/18/19 — cards, bank, USSD, mobile money, verified webhooks, refunds & recurring billing. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
Build-to-order Paystack gateway for Odoo 17/18/19 — cards, bank, USSD, mobile money, verified webhooks, refunds & recurring billing.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Odoo.
You go live in about 2–4 weeks, with a post-launch support window.
Give your Nigerian and pan-African customers a checkout they already trust. This is a build-to-order Paystack payment provider for Odoo — engineered by ECOSIRE and delivered as installable module code for your specific Odoo 17, 18, or 19 database. It is not an existing apps.odoo.com download; we design, build, configure, and support it around your workflow, then hand over the source.
Under the hood we extend Odoo's native payment.provider and payment.transaction models (models.Model / ORM fields with @api.depends computes where state needs to be derived), so Paystack behaves like a first-class provider everywhere Odoo already renders a "Pay Now" button — the eCommerce checkout, the customer portal for sales orders and invoices, subscriptions, and manual payment links. Customers pay in NGN (and other Paystack-supported currencies) with cards, bank transfer, USSD, and mobile money, using either the Paystack Inline popup or a full redirect flow.
Every transaction is reconciled against Paystack's Verify Transaction API, and inbound webhooks are authenticated by validating the x-paystack-signature HMAC-SHA512 header against your secret key before any state change is written — so a spoofed callback can never mark an order paid. Access is locked down with ir.model.access.csv and record rules so only Accounting/Billing roles can read raw provider credentials and transaction references. Test and Live keys, split codes, and payment-channel toggles are all managed from the standard Odoo provider configuration form (views in XML/OWL), with values held in Odoo's encrypted settings rather than hard-coded.
Because it plugs into Odoo core, reconciliation, invoice registration, refunds, and QWeb receipt reports all keep working the way your finance team expects. We support Community and Enterprise, ship the code with docs and a screen-share training session, and stay on to fix anything during the included support window.
Runs an Odoo-powered online store selling to Nigerian customers and needs the local checkout shoppers already trust — cards, bank transfer, USSD, and mobile money — so carts convert instead of abandoning at an unfamiliar foreign gateway.
Invoices African clients and wants them to pay Odoo invoices and sales orders directly from the customer portal via Paystack, with payments auto-reconciled so the accounts team stops chasing bank confirmations.
Bills recurring plans (SaaS, memberships, retainers) and needs card-on-file renewals through Paystack Plans tied to Odoo Subscriptions, with failed-payment alerts and clean invoice generation each cycle.
Owns reconciliation and refunds and needs verified, signature-checked transactions that post correctly to journals, plus role-restricted access to credentials and a documented refund workflow inside Odoo.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Paystack-native channels (cards, bank, USSD, mobile money) | Built for all your enabled Paystack channels with per-channel toggles | Depends entirely on what your developer implements | Varies by author; often only cards or a subset | |
| Built and configured for YOUR Odoo 17/18/19 database | Included | Included | Partial support | |
| Webhook signature verification (x-paystack-signature HMAC-SHA512) | Enforced server-side before any state change | Only if your developer builds it correctly | Partial support | |
| Server-side transaction verification (Verify Transaction API) | Included | Partial support | Partial support | |
| Full and partial refunds from inside Odoo | Included | Extra build effort | Partial support | |
| Recurring billing via Paystack Plans + Odoo Subscriptions | Included | Significant extra build effort | Rarely offered | |
| Role-restricted credential access (ir.model.access.csv + record rules) | Included | Often overlooked in DIY builds | Partial support | |
| Delivery model | Build-to-order in 2-4 weeks with source handover | Weeks-to-months of in-house dev time | Instant download, then you self-integrate | |
| Support, training, and post-launch fixes | Included support window + live training | You own all maintenance | Author-dependent, often ticket-only |
This is a build-to-order module, not an instant download. Typical lead time is 2-4 weeks from kickoff, depending on scope (for example, whether you need recurring billing or split payments). We confirm your Odoo version, dashboard access, and requirements up front, build and test in a sandbox, then schedule a supervised go-live. You get a delivery timeline in writing before we start.
Every build includes a post-launch support window for bug fixes and configuration adjustments, plus documentation and a training session. If Paystack changes its API or you upgrade Odoo (say 17 to 18 or 19), we can update the module under an ongoing support or a fixed-scope agreement. Because you receive the full source code, you are never locked in — your own team can also maintain it.
We build for Odoo 17, 18, and 19, on both Community and Enterprise. The module extends Odoo's core payment framework (payment.provider / payment.transaction), so it works with the standard eCommerce checkout, the customer portal for invoices and sales orders, and Subscriptions where that app is present.
No. We never trust the browser callback alone. Every payment is re-verified server-side against Paystack's Verify Transaction API, and inbound webhooks are authenticated by validating the x-paystack-signature HMAC-SHA512 header against your secret key before any order or invoice state changes. Handling is idempotent so retried events can't double-post, and credentials are stored in Odoo's encrypted settings with access restricted via ir.model.access.csv and record rules.
All Paystack channels available on your account — cards, bank transfer, USSD, and mobile money — with per-channel toggles on the Odoo provider form. Payments are processed in Paystack-supported currencies (NGN and others your account is enabled for), with amounts handled in the correct minor units so values post exactly.
Yes. Full and partial refunds are issued through the Paystack Refund API and written back onto the Odoo transaction and journal entry. For recurring billing we integrate Paystack Plans and Subscriptions with Odoo Subscriptions/recurring invoices for card-on-file renewals, including alerts on failed or disputed payments via Odoo automated actions.
You get the complete module source — the addon directory with __manifest__.py, Python models, views, security files, and the webhook controller. It's yours to keep, install across environments, and maintain. We recommend a support agreement for updates, but there is no vendor lock-in.
Build-to-order Paystack gateway for Odoo 17/18/19 — cards, bank, USSD, mobile money, verified webhooks, refunds & recurring billing.