Moyasar Payment Gateway for Odoo

ECOSIRE builds a first-class Moyasar payment provider for Odoo. Technically, it extends the payment.provider model (_inherit = 'payment.provider') with a new code selection value and Moyasar-specific credential fields (publishable/secret keys, webhook secret) stored on the provider record, plus a payment.transaction extension that implements _get_specific_rendering_values, _send_payment_request, and _process_notification_data for the Moyasar lifecycle. The embedded Moyasar.js form is rendered through a QWeb/OWL template so the customer pays without leaving your Odoo checkout, and the payment method list (mada, Apple Pay, STC Pay, cards) is driven by payment.method records so you control exactly what appears. All amounts are handled in SAR with correct minor-unit (halalah) conversion to match Moyasar's API expectations.

Reconciliation is the part most DIY builds get wrong, so we make it the backbone. A public JSON controller receives Moyasar webhooks, verifies the signature against the stored webhook secret, and idempotently maps events onto the Odoo payment.transaction state machine (_set_pending, _set_done, _set_canceled, _set_error) — so a paid order is confirmed, the invoice/SO is advanced, and duplicate or replayed callbacks never double-post. Refunds are handled inside Odoo through the standard refund action, calling Moyasar's refund endpoint and writing back a linked refund transaction. Access is locked down with ir.model.access.csv and record rules so only authorized users touch provider credentials, and every gateway call is logged for audit. The module ships as a proper Odoo addon with a versioned __manifest__.py, targeted for your line — Odoo 17.0, 18.0, or 19.0, Community or Enterprise.

Because this is build-to-order, you're not downloading a generic zip and hoping it fits. We start with a short scoping call to confirm your Odoo version, edition, which Moyasar methods you need live, your SAR tax/invoice setup, and whether you use the eCommerce checkout, the customer portal invoice-pay flow, or both. We then build against your requirements, run UAT on a staging copy of your database, and only cut over to production with a documented rollback. Typical delivery is 2-4 weeks from confirmed scope. You receive the full installable source, technical and user documentation, a training session, and a post-go-live support window — plus the git repository so the module is yours to keep.