Vista previa ilustrativaA custom-built WooCommerce payment gateway integrating Xendit for Indonesia and the Philippines
— e-wallets, QRIS, virtual accounts, retail outlet cash, cards and refunds. Built, installed and supported by
ECOSIRE on your own WordPress site.
¿Qué es Xendit Payment Gateway for WooCommerce?
A custom-built WooCommerce payment gateway integrating Xendit for Indonesia and the Philippines — e-wallets, QRIS, virtual accounts, retail outlet cash, cards and refunds. Built, installed and supported by ECOSIRE on your own WordPress site. Built to order by ECOSIRE for WooCommerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Características clave
Hecho a medida, listo para ti
Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.
- 1
Haces el pedido
Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.
- 2
Creamos e instalamos
ECOSIRE la crea, la configura y la instala en tu WooCommerce.
- 3
En marcha + soporte
Sales en vivo en aproximadamente una semana laboral, con dos semanas de soporte tras la puesta en marcha. Los defectos en el código que entregamos se corrigen sin coste.
Sobre este producto
Xendit Payment Gateway for WooCommerce connects your store to Xendit's full Southeast Asian payment stack so Indonesian and Philippine shoppers can pay the way they actually pay — QRIS, e-wallets (OVO, DANA, ShopeePay, GCash, Maya), bank virtual accounts, and retail outlet cash at Alfamart/Indomaret — alongside cards and installments.
This is not an instant download from WooCommerce.com or WordPress.org. ECOSIRE builds, installs and configures the plugin on your own WordPress site using Xendit's Invoice and Payment APIs, then hands you a working checkout. The gateway registers as a proper WooCommerce payment method via the WC_Payment_Gateway class and the woocommerce_payment_gateways filter, so it appears natively under WooCommerce → Settings → Payments with sandbox and live API-key fields.
Under the hood it creates Xendit charges/invoices server-side, redirects or renders the chosen method, and listens for Xendit webhook callbacks to mark orders processing/completed — critical for async methods like virtual accounts and retail cash where the customer pays hours later. We verify the callback token, guard against duplicate notifications, and write to the order via the WooCommerce CRUD layer, so it's fully HPOS / custom order tables compatible. Refunds are wired to the WooCommerce refund button and call Xendit's refund endpoint directly from wp-admin.
Because we build it to order, the integration fits your theme, plugins, currency setup, and edge cases — multi-currency (IDR/PHP), WPML/multisite, subscription renewals, and custom order statuses. You get clean, hook-based code (no core hacks), staging-first deployment, and a real engineer to call when Xendit changes an API or your store grows.
lo que obtienes
- A custom WooCommerce gateway plugin installed and activated on your WordPress site (or staging first, then production)
- Xendit account connection configured — live and sandbox API keys wired into wp-admin, with the callback URL registered in your Xendit dashboard
- Configured payment methods matching your market (Indonesia and/or Philippines): QRIS, e-wallets, virtual accounts, retail outlets, cards
- Verified webhook callback handling with test transactions for each enabled method, including async VA and retail-cash confirmation
- Refund flow tested end-to-end from the wp-admin order screen
- A short handover document covering settings, the callback URL, test vs live switching, and how refunds work, plus a post-launch support window
¿Para quién es esto?
Indonesian D2C / fashion store owner
Runs a WooCommerce store selling to Indonesian customers and is losing carts because checkout only offers cards. Needs QRIS, OVO/DANA/ShopeePay and Alfamart/Indomaret cash so price-sensitive, unbanked, and mobile-first buyers can actually pay.
Philippine marketplace / services seller
Sells in PHP and wants GCash, Maya and bank VA at checkout without juggling several plugins. Needs a single Xendit integration that confirms async payments reliably and reconciles orders automatically.
Agency or store operator who wants it done right
Has a themed, plugin-heavy WooCommerce build (maybe HPOS, WPML or Subscriptions) and doesn't want a generic plugin that breaks on edge cases. Wants ECOSIRE to build, test on staging, and support the gateway as Xendit's API evolves.
Cómo se compara Xendit Payment Gateway for WooCommerce
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Nativo de WooCommerce |
|---|---|---|---|---|
| Full Xendit method coverage (QRIS, e-wallets, VA, retail cash, cards) | Incluido | Apoyo parcial | Apoyo parcial | No incluido |
| Built, installed and tested on your site by the vendor | Incluido | Incluido | No incluido | No incluido |
| Asynchronous webhook callback reconciliation (VA / retail cash) | Incluido | Apoyo parcial | Apoyo parcial | No incluido |
| Instant self-serve download from a marketplace | No incluido | No incluido | Incluido | Incluido |
| HPOS / custom order tables compatibility verified for your stack | Incluido | Apoyo parcial | Apoyo parcial | Incluido |
| Fits your theme, currency, WPML/Subscriptions edge cases | Incluido | Incluido | No incluido | No incluido |
| One-time cost with no per-seat licensing | Incluido | Apoyo parcial | Apoyo parcial | Incluido |
| Direct support from the engineers who wrote the code | Incluido | Apoyo parcial | No incluido | No incluido |
Preguntas frecuentes sobre Xendit Payment Gateway
How long until the gateway is live on my store, and how is it delivered?
This is build-to-order, not an instant download. After purchase we collect your Xendit account access (or guide you to create one), the target market and methods you want, and staging access. Typical delivery is about 3–7 business days depending on how many payment methods and edge cases (multi-currency, WPML, Subscriptions) are in scope. We build on staging, test every enabled method including async virtual-account and retail-cash callbacks, then deploy to production with your sign-off.
What do I need to provide, and does Xendit charge separately?
You provide a WooCommerce store (we recommend staging access), an active Xendit account with live and sandbox API keys, and your business details for whichever methods you enable (some like QRIS or retail outlets require Xendit-side activation). Xendit's own transaction fees and any KYC are between you and Xendit — our one-time fee covers building, installing, configuring and testing the integration, not Xendit's processing charges.
Is it compatible with HPOS, WPML, multisite and WooCommerce Subscriptions?
Yes. The gateway uses the WooCommerce CRUD/order API rather than direct postmeta, so it works with High-Performance Order Storage (custom order tables). Method titles and descriptions are translatable for WPML, and it can run on multisite. Subscriptions support depends on your renewal model — we confirm scope during the build and wire renewal charges where Xendit and your stack allow it.
How does payment confirmation work for virtual accounts and Alfamart/Indomaret, where the customer pays later?
Those are asynchronous. At checkout we create the VA number or retail payment code via the Xendit API and show it on the thank-you page and order email; the order sits in a pending/on-hold state. When the customer pays, Xendit sends a webhook callback to a secure endpoint we register. We verify the callback token, dedupe it, and transition the order to processing/completed automatically. Expired, unpaid codes are cancelled via WP-Cron so your order list stays clean.
What about ongoing support, updates, and changes after launch?
Every build includes a post-launch support window to fix any issue tied to our integration. Beyond that, Xendit's API and WooCommerce both evolve, so we offer ongoing maintenance to keep the gateway current — adapting to Xendit API changes, new payment methods, WooCommerce/HPOS updates, and your store's growth. Because we built it, the same engineers support it; you're not filing a ticket into a generic plugin queue.
Módulos relacionados
WooPayments-style All-in-One Payments Suite
A native WooCommerce payments plugin that keeps cards, Apple/Google Pay, BNPL, multi-currency, payouts and disputes inside wp-admin — built to order, installed and supported by ECOSIRE on your own WordPress site.
WordPress ERP Accounting for WooCommerce (WP ERP Accounting)
A built-in double-entry accounting module that books your WooCommerce sales, expenses, ledgers, and financial statements directly inside WordPress — built, installed, and supported by ECOSIRE.
ZATCA Phase 2 E-Invoicing for WooCommerce
A custom-built WooCommerce plugin that turns your Saudi store's orders into ZATCA Phase 2 (Fatoora) compliant UBL 2.1 e-invoices — QR, cryptographic stamp, clearance and reporting — built, installed and supported by ECOSIRE on your own WordPress site.
ZATCA Phase 2 E-Invoicing for WooCommerce (KSA Fatoora)
A build-to-order WooCommerce plugin that turns your orders into ZATCA Phase 2-compliant UBL 2.1 e-invoices — XAdES-signed, QR-stamped, and submitted to Saudi Arabia's Fatoora platform. ECOSIRE builds, installs, and supports it on your WordPress site.
Xendit Payment Gateway
A custom-built WooCommerce payment gateway integrating Xendit for Indonesia and the Philippines — e-wallets, QRIS, virtual accounts, retail outlet cash, cards and refunds. Built, installed and supported by ECOSIRE on your own WordPress site.
- Registers natively under WooCommerce → Settings → Payments via the WC_Payment_Gateway class and woocommerce_payment_gateways filter, with sandbox/live API-key fields
- QRIS dynamic QR and e-wallet checkout (OVO, DANA, LinkAja, ShopeePay for Indonesia; GCash, Maya, GrabPay for the Philippines)
- Bank virtual account (VA) generation — fixed and closed VAs created server-side via the Xendit API with the number shown on the thank-you page and order email
- Retail outlet cash payments at Alfamart/Indomaret with a payment code and expiry, reconciled automatically on callback