Build-to-order Xendit connector unifying Indonesia & Philippines payment methods on Odoo checkout — cards, e-wallets, VA, retail. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Xendit connector unifying Indonesia & Philippines payment methods on Odoo checkout — cards, e-wallets, VA, retail.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
A single Xendit connector that brings the full Southeast Asian payment stack into Odoo checkout — cards, e-wallets (OVO, DANA, ShopeePay, GCash, PayMaya), virtual accounts, and over-the-counter retail — without stitching together five separate acquirers.
Unified Xendit payment provider registered natively in Odoo — appears alongside Odoo's built-in acquirers on eCommerce, invoice, sales-order and subscription checkout
Card payments (Visa, Mastercard, JCB) with tokenization for returning customers and support for 3-D Secure authentication
Indonesian e-wallets: OVO, DANA, ShopeePay, LinkAja — with the correct redirect/push flow per wallet
Philippine e-wallets: GCash and PayMaya, presented automatically to PHP-currency and PH-country customers
Virtual Account (VA) bank transfer: BCA, BNI, BRI, Mandiri, Permata and more, with a generated VA number and expiry shown on the Odoo checkout
Over-the-counter retail outlet payments (Alfamart, Indomaret) for cash-preferring buyers, with reference codes surfaced in Odoo
This is a BUILD-TO-ORDER Odoo module. It is not an existing apps.odoo.com download and there is no instant purchase-and-install. After you order, ECOSIRE builds, configures, and installs the module for your Odoo 17, 18, or 19 database (Community or Enterprise), then hands it over with documentation and a support window. Typical delivery is 2–4 weeks depending on which Xendit methods and country flows you need live.
Under the hood, the connector is a proper Odoo payment provider. It extends payment.provider and payment.transaction with Xendit-specific fields (API key, callback verification token, live/test mode) declared in models/ via models.Model and typed fields, secured through ir.model.access.csv plus record rules so only the right roles touch credentials. Payment states are kept consistent using computed fields with @api.depends, and Xendit webhooks post to a controller that verifies the callback token, reconciles the Xendit invoice/charge against the Odoo transaction, and drives the standard _set_done / _set_pending / _set_canceled lifecycle. Checkout templates are rendered with QWeb/OWL so buyers see the right method picker for their country. Refunds are issued from the transaction form and mirrored to Xendit via its API. Everything speaks Odoo's native rails, so accounting entries, sales orders, subscriptions, and eCommerce all reconcile automatically — and you can trigger or read transactions externally over XML-RPC/JSON-RPC.
Because it is built for your instance, ECOSIRE fits it to your chart of accounts, IDR/PHP currency and rounding rules, tax setup, and the exact method mix your Indonesian and Filipino customers expect — rather than forcing you onto a generic one-size listing.
An Indonesian or Philippine online retailer running Odoo eCommerce who wants OVO, DANA, GCash, VA and cards in one checkout — settled through a single Xendit account instead of integrating each acquirer separately.
The controller responsible for matching Xendit settlements to Odoo invoices. Values automatic journal entries, IDR/PHP-correct rounding, refund traceability, and a webhook flow that never double-posts.
Owns the Odoo instance (Community or Enterprise, v17/18/19) and needs a payment provider that installs cleanly, respects record-level security on credentials, and exposes transactions over XML-RPC/JSON-RPC for other systems.
A business selling into IDR and PHP storefronts that wants one connector to present the right local methods per country and currency, rather than maintaining two separate payment stacks.
Buy the license on ecosire.com and download the Xendit Payment Gateway for Odoo (SEA) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Xendit Payment Gateway for Odoo (SEA), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Xendit-native SEA methods (OVO, DANA, GCash, VA, retail) on Odoo checkout | ||||
| Built and installed for your Odoo 17/18/19 (Community & Enterprise) | ||||
| Multi-country IDR/PHP handling with per-country method picker | ||||
| Idempotent webhook reconciliation to the exact payment.transaction | ||||
| Full & partial refunds pushed to Xendit from the Odoo form | ||||
| Credential security via ir.model.access.csv + record rules | ||||
| Fitted to your chart of accounts, tax and rounding rules | ||||
| Sandbox UAT, documentation, training & support window included | ||||
| XML-RPC / JSON-RPC access to transactions |
This is a build-to-order module — there is no instant download. After you order, ECOSIRE scopes your requirements (Odoo version, Community vs Enterprise, target countries and Xendit methods), then builds, configures and installs the connector on your database. Typical delivery is 2–4 weeks, driven mainly by how many methods and country flows go live and by Xendit account/verification readiness. You get sandbox UAT with test transactions before any production cutover.
You receive a post-delivery support window for bug fixes and configuration adjustments, plus a documented handover and a training session for your team. Because you own the module source, ECOSIRE can also provide compatibility updates for future Odoo point releases or new Xendit methods under a support/maintenance arrangement. Security fixes to the callback verification and reconciliation logic are prioritized.
Cards (Visa, Mastercard, JCB), Indonesian e-wallets (OVO, DANA, ShopeePay, LinkAja), Philippine e-wallets (GCash, PayMaya), Virtual Account bank transfers (BCA, BNI, BRI, Mandiri, Permata and more), and over-the-counter retail (Alfamart, Indomaret). The connector adapts the method picker to Indonesia (IDR) and the Philippines (PHP). We enable the exact subset your business is contracted for on Xendit.
Odoo 17, 18 and 19, on both Community and Enterprise. The module is built as a native Odoo payment provider (extending `payment.provider` and `payment.transaction`), so it integrates with eCommerce (`website_sale`), sales orders, invoicing and subscriptions the same way Odoo's built-in acquirers do. We version-pin the `__manifest__.py` to your exact target release.
A dedicated controller receives Xendit callbacks, verifies the callback verification token, and matches each invoice/charge back to the corresponding Odoo `payment.transaction` before driving its state (done/pending/canceled). Handling is idempotent, so Xendit's retried or duplicate webhooks never double-confirm an order or double-post accounting entries. Every transaction keeps an audit trail with failure reasons for finance and support.
Yes. Delivery includes sandbox UAT using Xendit test keys, where we run end-to-end test payments across your selected method mix and share evidence before switching to production keys. Refunds — full and partial — are issued directly from the Odoo transaction form, pushed to Xendit, and reflected in your accounting so settlements and reversals stay reconciled.
Build-to-order Xendit connector unifying Indonesia & Philippines payment methods on Odoo checkout — cards, e-wallets, VA, retail.