Auto-generate dynamic UPI QR codes at Odoo checkout and POS with amount, VPA and order reference pre-encoded for instant collection. One-time license from $199.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Auto-generate dynamic UPI QR codes at Odoo checkout and POS with amount, VPA and order reference pre-encoded for instant collection.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
UPI Dynamic QR Payment is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports specifically for your business — this is not an instant download from apps.odoo.com. After purchase, our Odoo engineers scope your collection flow, build the module against your Odoo 17, 18 or 19 database (Community or Enterprise), and hand you production-ready code within a typical 2-4 week lead time.
Dynamic UPI QR generated per order/invoice, encoding your VPA, exact amount, transaction note and a unique order reference (upi://pay deep-link spec)
Interoperable across every major UPI app — Google Pay, PhonePe, Paytm, BHIM and any NPCI-compliant PSP — no app lock-in for your customers
Auto amount and reference encoding eliminates mistyped payments and mismatched receipts
Registered as a native Odoo payment.provider ('upi_dynamic_qr') so it slots into the standard checkout, sales and POS payment flow
Website eCommerce checkout support — customer scans the QR on the payment page and the order confirms on payment
Point of Sale support — cashier displays a dynamic QR on the POS screen for face-to-face UPI collection
The module turns every order into a payable UPI intent. At website checkout and in Point of Sale, it generates a dynamic QR code that already encodes your Virtual Payment Address (VPA), the exact amount, the transaction note and a unique order reference — so your customer simply scans with GPay, PhonePe, Paytm or any BHIM/UPI-compliant app and pays the right amount, first time, with no manual typing. Because the payload follows the standard UPI deep-link spec (upi://pay?pa=...&am=...&tn=...&tr=...), the QR is interoperable across every UPI PSP app your customers already use.
Under the hood we ship a proper Odoo payment provider. A new payment.provider record ('upi_dynamic_qr') plugs into Odoo's native payment flow, so sales orders, eCommerce checkout and POS all recognise UPI as a first-class method. The QR image is generated server-side and rendered in the payment page and POS screen via OWL/QWeb, and a payment.transaction is created and linked to the source order. Confirmation is flexible: run it manually (staff marks the transaction paid after seeing the UPI credit) or automatically via a secured webhook / bank-statement reconciliation route that flips the transaction to 'done', validates the order and triggers Odoo's standard invoicing and delivery logic.
Everything is modelled the Odoo way. Compute fields (@api.depends) derive the encoded payload and expiry from the order amount, currency and reference. Access is locked down with ir.model.access.csv plus record rules so cashiers, salespeople and accountants each see only what they should. Automated actions (base.automation / ir.cron) can expire stale QR codes, retry reconciliation and notify staff. A QWeb report renders a branded UPI receipt with the QR for print or PDF. And because Odoo exposes XML-RPC/JSON-RPC, your other systems can create UPI-payable transactions or poll payment status programmatically.
You are not buying a black box. ECOSIRE hands over the full module source under your control, configuration in your database, written documentation, a training session for your team, and a post-go-live support window — with compatibility maintained across Odoo 17, 18 and 19. If your requirements evolve (multi-outlet VPAs, split settlements, deeper PSP webhook integration), it is your codebase to extend, and we are here to extend it with you.
A shop or multi-outlet retailer collecting most sales via UPI at the counter. Wants cashiers to show a dynamic QR with the exact amount already filled so payments are fast, correct and reconciled against the POS order automatically.
Runs an Odoo website storefront and wants low-cost UPI collection at checkout instead of high card MDR. Needs the QR to encode the order reference so paid orders confirm and invoice without manual matching.
Responsible for reconciling UPI credits against Odoo orders and invoices. Wants every payment.transaction linked to its source order, a clear audit trail, and either manual or webhook-driven confirmation that triggers Odoo's standard invoicing.
Owns the Odoo instance and integrations. Wants a proper payment provider (not a hack), role-based security via ir.model.access.csv and record rules, and XML-RPC/JSON-RPC access so other systems can create and check UPI payments.
Buy the license on ecosire.com and download the UPI Dynamic QR Payment for Odoo 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 UPI Dynamic QR Payment for Odoo, 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 |
|---|---|---|---|---|
| Dynamic QR with amount + order reference pre-encoded | Possible, but you build and test the UPI deep-link payload yourself | Varies — many generate static or amount-only QR | ||
| Native Odoo payment provider + POS + website integration | You must wire payment.provider, POS and checkout by hand | Usually one channel (checkout OR POS), rarely both cleanly | ||
| Interoperable across GPay/PhonePe/Paytm/BHIM | Depends on getting the NPCI spec right | Often tied to one PSP/aggregator | ||
| Webhook / reconciliation auto-confirmation to payment.transaction | Significant effort to build and secure the endpoint | Sometimes, often PSP-locked | ||
| Role-based security (ir.model.access.csv + record rules) | Only if you design it deliberately | Inconsistent quality | ||
| Built, installed and supported for you (2-4 wk lead time) | You own all build and maintenance | |||
| Full source handover + you can extend it | Often encrypted/obfuscated or license-restricted | |||
| Compatibility maintained across Odoo 17, 18 and 19 | Your responsibility on every upgrade | Depends on vendor keeping it updated |
No. This is a build-to-order module that ECOSIRE develops, installs and supports specifically for your Odoo database. There is nothing to download and self-install — after purchase our engineers scope your collection flow, build the module against your Odoo 17, 18 or 19 instance, and deliver it ready to run.
Typical lead time is 2 to 4 weeks from the kickoff call, depending on complexity (single VPA vs multi-outlet, manual vs webhook confirmation, custom PSP integration). We build in a staging database first, validate the full checkout and POS flow with you, then deploy to production. You'll get a delivery schedule during scoping.
Every build includes written documentation, a team training session, and a post-go-live support window for bug fixes and configuration tweaks. Because you receive the full module source, your codebase is yours to keep and extend — and we maintain compatibility across Odoo 17, 18 and 19. Ongoing support or new features can be arranged as a follow-on engagement.
The QR follows the standard NPCI UPI deep-link format (upi://pay), so it is interoperable with Google Pay, PhonePe, Paytm, BHIM and any UPI-compliant app. Customers scan with whatever app they already use — there is no lock-in to a single PSP.
Two modes. Manual: staff mark the payment.transaction as paid once the UPI credit is seen, and Odoo validates the order. Automatic: a secured webhook or bank-statement reconciliation route flips the transaction to 'done', matches it to the order via the encoded reference, and triggers Odoo's standard invoicing and delivery. Every transaction is linked to its source sale.order or pos.order.
Yes. The module is built as a native Odoo payment provider and supports Odoo 17, 18 and 19 on both Community and Enterprise. It covers website eCommerce checkout and Point of Sale, and the QWeb receipt and role-based security (ir.model.access.csv + record rules) work the same across editions.
Yes. Odoo exposes XML-RPC and JSON-RPC, so external systems can create UPI-payable transactions and poll their status. We can also expose the webhook confirmation endpoint to your bank/PSP or an intermediary during the build.
Auto-generate dynamic UPI QR codes at Odoo checkout and POS with amount, VPA and order reference pre-encoded for instant collection.