Network International (N-Genius) Gateway for Odoo

ECOSIRE builds a first-class N-Genius payment provider that plugs directly into Odoo's standard payment architecture. We add a new payment.provider record with its own code, so N-Genius appears alongside every other method on website_sale checkout, the /my customer portal, and any Sales or Invoicing flow that renders the payment form. Under the hood the module implements the provider's _get_specific_rendering_values() and transaction feedback handlers, calls the N-Genius /transactions/outlets/{outletRef}/orders API for order creation, and supports both the hosted redirect and the embedded iframe (Hosted Session) so you choose between sending the shopper to Network's page or keeping them on your domain. OAuth client-credential tokens, outlet references, and the API base (UAT vs production) are stored on the provider record and never hard-coded — switch environments by changing a field, not the source.

The technical core is honest, PCI-conscious Odoo engineering: models/payment_provider.py and models/payment_transaction.py extend the base classes with @api.depends compute fields for state, a signed webhook controller for asynchronous notifications, and idempotent reconciliation so a settlement callback that arrives twice does not double-confirm an invoice. We wire 3DS2 / SCA into the flow so strong customer authentication is handled by N-Genius rather than bolted on, and we support Cards, mada, and Apple Pay through the gateway's payment-method configuration. AED is treated as the base transaction currency with multi-currency capture where your outlets support it. Access is governed by ir.model.access.csv plus record rules so credentials and raw transaction payloads are visible only to accounting/admin, and every gateway exchange is logged for audit. Views are delivered as standard XML/OWL, and where you need a branded settlement or reconciliation summary we add a QWeb report.

Because Network International's exact API contract, your outlet structure, mada/Apple Pay enablement, and whether you want hosted-redirect or iframe differ per merchant, this is a build-to-order engagement, not a shrink-wrapped download. We start from a scoping call, confirm scope in writing, then build against your UAT outlet credentials on a staging database. You receive the installable module source for your exact Odoo version (17.0, 18.0 or 19.0 — Community or Enterprise), UAT on staging, a rollback plan, and a defined post-go-live support window before we hand over the git repository. Typical delivery is 2-4 weeks from confirmed scope.