Illustrative previewAccept Filipino cards, GCash, Maya, and GrabPay at Odoo checkout via PayMongo
— built, installed, and supported by ECOSIRE.
What is PayMongo Payment Gateway for Odoo (Philippines)?
Accept Filipino cards, GCash, Maya, and GrabPay at Odoo checkout via PayMongo — built, installed, and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Sell to Filipino customers the way they actually pay. This is a build-to-order Odoo payment provider that connects your Odoo website, eCommerce, invoicing, and Sales quotations to PayMongo — so shoppers can check out with local cards (Visa, Mastercard), GCash, Maya (PayMaya), and GrabPay without leaving your site.
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 one working week including your sandbox verification, go-live, and a support window.
What you get
- Complete, source-available Odoo module (models, views, QWeb templates, security CSV, data XML, __manifest__.py) built for your exact Odoo 17/18/19 edition
- Installation and configuration on your Odoo instance, including the PayMongo provider record, payment methods, and webhook registration
- Sandbox verification pass covering card, GCash, Maya, and GrabPay success, failure, and refund paths before go-live
- Go-live switchover from PayMongo test keys to live keys with a smoke-test of a real low-value transaction
- Admin documentation: how to manage keys, read transactions, trace a Payment Intent, and issue refunds
- A live handover/training session for your finance and store-admin team
- A defined post-launch support window for fixes, questions, and PayMongo API adjustments
- Source code and deployment notes handed to you so your own team can maintain or extend the module
Who this is for
Philippine online store owner
Runs an Odoo Website eCommerce shop and is losing carts because checkout doesn't offer GCash, Maya, or GrabPay. Wants local wallets and cards live without redirecting buyers off-site.
Finance / accounting manager
Needs every payment to reconcile cleanly against Sale Orders and invoices in Odoo, with a traceable PayMongo reference and the ability to issue refunds without leaving the system.
Odoo administrator / IT lead
Owns the Odoo instance and wants a properly built provider that follows Odoo conventions, keeps API keys secure, verifies webhook signatures, and can be maintained in-house afterward.
How PayMongo Payment Gateway for Odoo (Philippines) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Filipino cards + GCash, Maya, GrabPay in Odoo checkout | Included | Partial support | Partial support | Not included |
| Payment Intents flow implemented server-side | Included | Partial support | Partial support | Not included |
| Signed webhook reconciliation (survives abandoned tab) | Included | Partial support | Partial support | Not included |
| Full and partial refunds from the Odoo transaction | Included | Partial support | Partial support | Not included |
| Built for your exact Odoo 17/18/19 edition, installed and verified | Included | Partial support | Not included | Not included |
| Secure credential storage with ir.model.access.csv + record rules | Included | Partial support | Partial support | Included |
| Source ownership with no license lock | Included | Included | Not included | Included |
| Dedicated support window + guaranteed version upgrades | Included | Not included | Partial support | Not included |
Frequently Asked Questions about PayMongo Payment Gateway
How long does delivery take, and what does the process look like?
Typical delivery is one working week. This is a build-to-order module, not an instant download. After purchase we confirm your Odoo version (17, 18, or 19) and edition, gather your PayMongo test keys, build the module, install it on your instance, and run a full sandbox verification of card, GCash, Maya, and GrabPay flows. Once you sign off we switch to live keys and smoke-test a real transaction.
What support and updates are included after launch?
Every build includes a defined post-launch support window for bug fixes, configuration help, and adjustments if PayMongo changes its API. Because you receive the full source, your own team can also maintain it. Beyond the initial window we offer ongoing support and version-upgrade services (for example, when you move from Odoo 18 to 19) as a separate engagement.
Which payment methods are supported?
Local cards (Visa and Mastercard) plus the GCash, Maya (PayMaya), and GrabPay e-wallets — all through PayMongo's Payment Intents flow. If PayMongo enables additional methods on your merchant account, we can extend the module to include them.
Does it work on Odoo Community or only Enterprise?
Both. The module extends Odoo's standard payment framework (payment.provider and payment.transaction), which exists in Community and Enterprise, and we build it against whichever edition and version — 17, 18, or 19 — you run.
What happens if a customer pays with GCash but closes the browser before returning to my site?
The payment still reconciles. Confirmation is driven by a signed PayMongo webhook, not only by the browser redirect. When PayMongo notifies your Odoo endpoint, the module verifies the signature and updates the payment.transaction to done — so the Sale Order confirms or the invoice is marked paid even if the shopper never lands back on your thank-you page.
Do I keep the source code, and can my team modify it?
Yes. We hand over the complete, source-available module along with deployment notes. There's no license lock — your team can read, maintain, and extend it, and we're available to help when you want changes made for you.
Related Modules
Payment Reconciliation & Settlement Matching for Odoo
A build-to-order Odoo module that imports gateway settlement and payout files, matches net payouts back to the underlying orders and fees, and posts the fee, FX, and adjustment entries automatically. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19.
Payment Surcharge & Convenience Fee for Odoo
Automatically add a per-payment-method surcharge or convenience fee to Odoo orders and online checkout, with tax-aware fee lines, country/threshold caps, and refund-safe handling. ECOSIRE scopes, builds, installs and supports it for your Odoo 17/18/19.
Payroll Accounting
A build-to-order Odoo module that ties payroll runs directly to your accounting — every payslip generates a reviewed, balanced journal entry mapped to the right accounts, analytic tags, and cost centers. ECOSIRE builds, installs, and supports it for your chart of accounts.
PayMongo Payment Gateway
Accept Filipino cards, GCash, Maya, and GrabPay at Odoo checkout via PayMongo — built, installed, and supported by ECOSIRE.
- Native Odoo payment.provider and payment.method records so PayMongo appears in Website Payment Providers with the standard test/enabled/disabled state machine
- Card acquiring for Visa and Mastercard through PayMongo, including 3-D Secure authentication redirect handling
- GCash e-wallet checkout via PayMongo's redirect flow, reconciled back to the Odoo order
- Maya (PayMaya) e-wallet checkout support with return-URL and webhook confirmation