Skip to main content
Midtrans Payment Gateway for Odoo (Indonesia) — Indonesian cards, e-wallets, and VA bank transfer via Midtrans Snap on Odoo — — 1/1Illustrative preview

Indonesian cards, e-wallets, and VA bank transfer via Midtrans Snap on Odoo

— built, installed and supported by ECOSIRE.

What is Midtrans Payment Gateway for Odoo (Indonesia)?

Indonesian cards, e-wallets, and VA bank transfer via Midtrans Snap on Odoo — 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

Midtrans Snap integration in two modes — embedded popup (Snap.js) rendered over your Odoo checkout, or full redirect to Midtrans-hosted Snap, selectable per your UX preference
Full Indonesian payment-channel coverage through one integration: credit/debit cards, GoPay, ShopeePay, QRIS, virtual-account transfer (BCA, BNI, BRI, Mandiri, Permata) and over-the-counter retail (Alfamart, Indomaret)
Native Odoo payment provider implementation: a real payment.provider record (code 'midtrans') and payment.transaction extension mapping Midtrans states to Odoo's draft/pending/authorized/done/cancel/error lifecycle
Server-side webhook controller that receives Midtrans HTTP notifications and treats them as the authoritative payment source — browser redirects are never trusted to confirm payment
SHA-512 signature_key verification (order_id + status_code + gross_amount + Server Key) on every notification to reject spoofed or tampered callbacks
IDR zero-decimal handling: gross_amount rounded and formatted to whole rupiah, fractional-tax rounding drift guarded, and the exact settled amount reconciled back to the Odoo transaction
In-Odoo refund support that calls the Midtrans refund/cancel API on captured transactions, writes the outcome back to the payment.transaction, and logs it in the chatter for audit
Sandbox and production toggle with separate Client Key / Server Key config fields stored on the provider record, so you validate in Midtrans sandbox before going live
Works across all Odoo payment surfaces: Website/eCommerce checkout, customer-portal invoice payment, and online quotation payment — one provider, every flow
Security-scoped via ir.model.access.csv and record rules so only Accounting/Payment managers can edit credentials or issue refunds; credentials are never written to logs
3-D Secure / card-authentication and installment channels supported where enabled on your Midtrans account, surfaced through Snap without extra Odoo code
Idempotent order-id strategy and transaction-state reconciliation to prevent double-charging on retries or duplicate notifications
Compatible with Odoo 17, 18 and 19 on both Community and Enterprise, delivered as a versioned addon with a documented __manifest__.py for clean upgrades
Optional automated action / scheduled reconciliation hook to re-query Midtrans transaction status for pending VA/retail payments that settle hours later

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

  1. 1

    You order

    Start with a one-time build price. We scope it with you at kickoff.

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your Odoo.

  3. 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 Indonesian customers the way they actually pay. This is a build-to-order Midtrans payment provider for Odoo — ECOSIRE designs, builds, installs and supports it for your specific Odoo environment; it is not an off-the-shelf apps.odoo.com download and there is no instant-download link.

Midtrans is one of Indonesia's most widely used payment aggregators, and its Snap product exposes a single hosted checkout that covers credit/debit cards, e-wallets (GoPay, ShopeePay, QRIS), virtual-account bank transfer (BCA, BNI, BRI, Mandiri, Permata), over-the-counter retail outlets (Alfamart, Indomaret), and installment options — all behind one integration. This module wires that Snap experience into Odoo's native payment framework so it works consistently across the eCommerce checkout (Odoo Website / Sales), the customer portal for invoice payment, and quotation online payment.

Under the hood we implement a proper Odoo payment provider. A new payment.provider record (code = 'midtrans') carries your Client Key, Server Key and sandbox/production toggle as encrypted config fields; a payment.transaction extension maps Odoo's transaction lifecycle to Midtrans order and transaction states. On checkout the customer either sees the Snap popup rendered over your Odoo page (via the Snap.js client) or is redirected to Midtrans-hosted Snap, then returned to Odoo's standard confirmation route. Server-to-server confirmation is authoritative: a controller endpoint receives Midtrans's HTTP notification (webhook), verifies the SHA-512 signature_key (order_id + status_code + gross_amount + Server Key) before trusting any status, and moves the payment.transaction to done / pending / cancelled / error accordingly — so a closed browser tab or a spoofed callback can never mark an order paid.

Amounts and currency follow Indonesian rules: IDR is a zero-decimal currency at Midtrans, so we round and format gross_amount to whole rupiah, guard against fractional-tax rounding drift, and reconcile the exact settled amount back to the Odoo transaction. Refunds are supported from within Odoo — an authorized user triggers a refund on a captured transaction and the module calls Midtrans's refund API, then writes the result back to the transaction and posts a message in the chatter for audit.

Security is modeled the Odoo way: ir.model.access.csv grants and record rules keep gateway credentials and transaction actions restricted to Accounting/Payment managers, the webhook controller is auth='public' but validated by signature (never by trust), and no secret is ever logged. The module ships tested against Odoo 17, 18 and 19 and works on both Community and Enterprise (Enterprise adds nicer accounting reconciliation UX, but the gateway itself does not require it). Everything is delivered as a clean, versioned addon with a documented __manifest__.py, so it upgrades cleanly and your team can read exactly what it does.

Because it's build-to-order, you get a gateway tuned to your catalog, tax setup, multi-company/multi-currency layout and preferred Snap payment channels — not a generic binary you have to bend your workflow around.

What you get

  • Complete, production-ready Odoo addon (the Midtrans payment provider module) with clean __manifest__.py, models, controllers, views and security files, versioned for Odoo 17, 18 and/or 19 as required
  • Installation and deployment on your Odoo instance (or a staging copy first), including addons-path placement, module install and payment.provider record setup
  • Midtrans account configuration guidance: Client Key / Server Key placement, sandbox validation, and correct webhook (payment notification URL) registration in the Midtrans dashboard
  • End-to-end sandbox test pass covering card, GoPay/QRIS, virtual-account and retail-outlet flows plus a refund, with results shared before go-live
  • Written documentation: configuration guide, webhook/signature explanation, refund procedure, and a short runbook for common failure states (pending VA, expired transaction, signature mismatch)
  • A live handover / training session for your finance and web team on taking payments, reading transaction states in Odoo, and issuing refunds
  • A defined post-launch support and warranty window for bug fixes and Odoo/Midtrans compatibility issues (see FAQ), plus source-code ownership so your team can extend it
  • Go-live checklist and switch-to-production support to move from sandbox keys to live keys safely

Who this is for

Indonesian eCommerce merchant on Odoo Website

Runs an Odoo Website/eCommerce storefront serving Indonesian shoppers and needs GoPay, QRIS, virtual-account and card checkout that local customers trust — without cobbling together a fragile custom integration.

Finance / accounting manager

Owns reconciliation and refunds. Wants every payment confirmed by a verified webhook (not a browser redirect), exact IDR amounts matched to invoices, and refunds issued from inside Odoo with a clear audit trail in the chatter.

B2B seller invoicing via the customer portal

Sends Odoo quotations and invoices and wants Indonesian buyers to pay online through the portal using their preferred local method, with the payment automatically registered against the right invoice.

Odoo partner or in-house developer

Needs a properly structured, readable addon — real payment.provider/payment.transaction extension, signature verification, ir.model.access.csv security — that installs cleanly on Odoo 17/18/19 Community or Enterprise and is safe to maintain and extend.

How Midtrans Payment Gateway for Odoo (Indonesia) Compares

CriterionECOSIRECustom BuildCompetitorOdoo Native
Indonesian payment methods (GoPay, QRIS, VA, retail, cards) in one checkoutIncludedPossible but you build and maintain every channel yourselfVaries — many cover only cards or a subsetNot included
Webhook + SHA-512 signature verification as the source of truthIncludedOnly if you implement it correctly — easy to get wrongOften relies on browser redirect; signature check inconsistentNot included
IDR zero-decimal amount handling and exact reconciliationIncludedYour responsibility to handle rounding driftNot always handled — a common source of mismatchesPartial support
In-Odoo refunds via Midtrans API with chatter audit trailIncludedExtra work you scope and buildSometimes; often manual in the Midtrans dashboardNot included
Tested on Odoo 17, 18 and 19 (Community + Enterprise)IncludedYou test and maintain across versionsDepends on vendor's version supportPartial support
Built for your catalog, tax, multi-company and preferred channelsIncludedIncludedNot includedNot included
Source-code ownership + defined support/warranty windowIncludedYou own it but support yourselfUsually license + vendor support onlyNot included
Delivery modelBuild-to-order, one working week, installed + supported by ECOSIREFull internal project timelineInstant download, self-install and self-configureAlready in Odoo but no Midtrans support

Frequently Asked Questions about Midtrans Payment Gateway

How long until it's delivered, and how does the build-to-order process work?

Typical delivery is one working week from kickoff, depending on your Odoo version, hosting and how many Snap payment channels you want tuned. This is not an instant apps.odoo.com download — ECOSIRE builds the module for your specific environment. The flow is: requirements + access, development, a full sandbox test pass (card, e-wallet, VA, retail, refund), then production go-live with your live Midtrans keys.

What support and updates do I get after launch?

You receive a defined post-launch support window (two weeks) covering bug fixes and Odoo/Midtrans compatibility issues, plus the training handover; defects in the code we deliver are fixed free of charge. Because you own the source code, your team can extend it freely. Ongoing maintenance beyond the warranty window — including forward-porting to a new Odoo major version or adapting to Midtrans API changes — is available as an optional support retainer.

Does it work on Odoo Community, or only Enterprise? Which versions?

It works on both Community and Enterprise, and is built and tested against Odoo 17, 18 and 19. The Midtrans gateway itself doesn't require Enterprise; Enterprise simply gives you a richer accounting/reconciliation UX. Tell us your exact version and edition at kickoff and we target that.

How does the module make sure a payment is really paid before confirming the order?

Confirmation is server-side and authoritative. Midtrans sends an HTTP notification (webhook) to a dedicated Odoo controller endpoint; the module recomputes the SHA-512 signature_key from order_id, status_code, gross_amount and your Server Key and rejects anything that doesn't match. Only a verified notification moves the payment.transaction to done. A closed browser tab, a page refresh, or a forged callback can never mark an order paid.

Can I issue refunds, and does IDR's lack of decimals cause rounding problems?

Yes to refunds — an authorized Accounting/Payment manager triggers a refund on a captured transaction from within Odoo, the module calls the Midtrans refund API, and the result is written back to the transaction with a chatter log for audit. On IDR: Midtrans treats rupiah as a zero-decimal currency, so the module rounds and formats gross_amount to whole rupiah, guards against fractional-tax rounding drift, and reconciles the exact settled amount to the Odoo transaction so your books match Midtrans to the rupiah.

Which Midtrans payment methods are covered, and can I limit them?

Through Midtrans Snap you get cards, GoPay, ShopeePay, QRIS, virtual-account transfer (BCA, BNI, BRI, Mandiri, Permata) and over-the-counter retail (Alfamart, Indomaret), subject to what's enabled on your Midtrans account. You choose which channels to surface at checkout, and we configure Snap accordingly during the build.

Request a quote

Midtrans Payment Gateway

Indonesian cards, e-wallets, and VA bank transfer via Midtrans Snap on Odoo — built, installed and supported by ECOSIRE.

  • Midtrans Snap integration in two modes — embedded popup (Snap.js) rendered over your Odoo checkout, or full redirect to Midtrans-hosted Snap, selectable per your UX preference
  • Full Indonesian payment-channel coverage through one integration: credit/debit cards, GoPay, ShopeePay, QRIS, virtual-account transfer (BCA, BNI, BRI, Mandiri, Permata) and over-the-counter retail (Alfamart, Indomaret)
  • Native Odoo payment provider implementation: a real payment.provider record (code 'midtrans') and payment.transaction extension mapping Midtrans states to Odoo's draft/pending/authorized/done/cancel/error lifecycle
  • Server-side webhook controller that receives Midtrans HTTP notifications and treats them as the authoritative payment source — browser redirects are never trusted to confirm payment

Request a Quotation

Tell us about your Midtrans Payment Gateway requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.