PayMongo Payment Gateway for Odoo (Philippines)

This is not an existing apps.odoo.com download. ECOSIRE designs, builds, and installs the module for your exact Odoo edition and version, then supports it. Under the hood it registers a native payment.provider record and a matching payment.method, so PayMongo appears alongside your other payment options in Settings → Website → Payment Providers with the standard Odoo test/enabled state machine.

The integration is built around PayMongo's Payment Intents flow. When a customer confirms an order, the module server-side creates a Payment Intent through PayMongo's REST API, attaches the chosen payment method (card, GCash, Maya, or GrabPay), and redirects the buyer to the appropriate authorization or e-wallet redirect page. On return, and independently via a signed PayMongo webhook, the module reconciles the result against Odoo's payment.transaction record — moving it to done, authorized, cancel, or error and letting Odoo's core confirm the linked Sale Order or post the invoice payment automatically.

Because reconciliation is webhook-driven, orders still settle correctly even if the shopper closes the browser tab after paying in GCash or Maya. Every transaction stores the PayMongo Payment Intent ID and reference so your finance team can trace any payment end-to-end. Refunds are supported directly from the Odoo transaction (full or partial), calling the PayMongo refund API and writing the result back to the transaction and its accounting entries.

The module is built to Odoo's own conventions: a clean __manifest__.py declaring dependencies (payment, and website_sale/account as your scope requires), models extending payment.provider and payment.transaction, ir.model.access.csv plus record rules to protect API credentials, QWeb templates for the checkout redirect and any inline form, and data XML that installs the provider in test mode so nothing goes live until you flip it. It ships PHP (₱) localization defaults and the currency/rounding behavior PayMongo expects. Credentials (public + secret keys and the webhook signing secret) live in the provider record, encrypted and hidden from non-admin users.

You keep full ownership of the source. It runs on Odoo Community or Enterprise, and we build it against Odoo 17, 18, or 19 — whichever you run. Typical delivery is 2–4 weeks including your sandbox verification, go-live, and a support window.