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 $249.00 USD; request a quote for a scoped proposal.
Beispielhafte VorschauAccept Filipino cards, GCash, Maya, and GrabPay at Odoo checkout via PayMongo
— built, installed, and supported by ECOSIRE.
Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.
Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.
ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Odoo.
Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.
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 2–4 weeks including your sandbox verification, go-live, and a support window.
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.
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.
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.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo nativ |
|---|---|---|---|---|
| Filipino cards + GCash, Maya, GrabPay in Odoo checkout | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Payment Intents flow implemented server-side | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Signed webhook reconciliation (survives abandoned tab) | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Full and partial refunds from the Odoo transaction | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Built for your exact Odoo 17/18/19 edition, installed and verified | Im Lieferumfang enthalten | Teilweise Unterstützung | Nicht im Lieferumfang enthalten | Nicht im Lieferumfang enthalten |
| Secure credential storage with ir.model.access.csv + record rules | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Im Lieferumfang enthalten |
| Source ownership with no license lock | Im Lieferumfang enthalten | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten | Im Lieferumfang enthalten |
| Dedicated support window + guaranteed version upgrades | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
Typical delivery is 2–4 weeks. 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.
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.
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.
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.
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.
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.

A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.

Automated multi-step abandoned-cart and checkout recovery emails with discounts, resume links, and recovered-revenue reporting — built for your Odoo.

A build-to-order Odoo module that lets you render any accounting report — P&L, Balance Sheet, aged reports, journals, trial balance — in a currency of your choice, with automatic conversion at the rate you define. ECOSIRE scopes, builds, installs and supports it for your Odoo 17/18/19 environment.
Accept Filipino cards, GCash, Maya, and GrabPay at Odoo checkout via PayMongo — built, installed, and supported by ECOSIRE.