Pix Instant Payment for Odoo (Brazil)

Name: Pix Instant Payment for Odoo (Brazil)
Brand: ECOSIRE
SKU: odoo-pix-instant-payment

Temel Özellikler

Pix EMV/BR Code QR generation — produces the standard scannable QR image and matching copia e cola string on sale orders, invoices, and the customer portal

Copia e cola (copy-and-paste) payload with correct amount, merchant name, merchant city, txid, and CRC16 checksum encoded per the Banco Central Pix specification

PSP-agnostic architecture — a clean provider abstraction so you can connect Mercado Pago, PagSeguro/PagBank, Efí (Gerencianet), Banco Inter, or another Pix-certified PSP without rewriting the module

Direct bank Pix API connectors (mTLS/OAuth2) for merchants using their bank's Pix API rather than a PSP aggregator

Automatic reconciliation via inbound webhook — the PSP confirmation callback marks the payment.transaction done, posts the account.payment, and reconciles it to the open invoice

Odoo native payment provider record and payment.transaction extension so Pix appears alongside card and bank-transfer methods in Sales, Invoicing, and Website checkout

Dynamic vs static Pix keys — supports per-transaction dynamic QR (unique txid, exact amount) and optional static merchant QR for donations or fixed amounts

Expiry encoding and countdown — sets the QR validity window and auto-expires stale transactions via a scheduled action (ir.cron), releasing reservations

Amount and reference encoding — locks the exact BRL amount and your order reference into the payload to prevent underpayment or mismatched settlements

Webhook signature verification and idempotency — validates the PSP callback signature and dedupes retries so a payment is never double-posted

BRL localization — integrates with the Brazilian chart of accounts (l10n_br), formats currency correctly, and books payments to the right journal

Point of Sale support (optional) — show the Pix QR on the POS screen and confirm payment before the receipt prints, for in-store instant checkout

eCommerce checkout flow (optional) — customer selects Pix on the Website store, sees the QR, pays, and the order confirms automatically on webhook receipt

Audit trail and status timeline — every transaction logs generated, awaiting, paid, expired, or refunded states in the Odoo chatter for support and dispute handling

Configurable multi-company / multi-account setup — record rules keep Pix credentials and transactions isolated per company in a multi-entity Odoo database

Siparişe özel, sizin için baştan sona

Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.

Sipariş verirsiniz

Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.

Geliştirir ve kurarız

ECOSIRE, Odoo ortamınızda geliştirir, yapılandırır ve kurar.

Yayına alma + destek

Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.

Bu Ürün Hakkında

Pix is Brazil's instant payment rail from the Banco Central do Brasil, settling 24/7 in seconds. If you sell in BRL, your customers expect to scan a QR code or paste a "copia e cola" string and pay instantly — not wait on boleto clearance or card fees. Odoo does not ship native Pix support, so this is a custom module that ECOSIRE designs, builds, installs, and supports specifically for your Odoo database.

This is a BUILD-TO-ORDER engagement, not an instant download from the Odoo App Store. After purchase, our Odoo engineers scope your PSP or bank (Mercado Pago, PagSeguro/PagBank, Gerencianet/Efí, Banco Inter, Itaú, Bradesco, Sicoob, or a Pix-certified PSP of your choice), build the module against your Odoo 17, 18, or 19 instance (Community or Enterprise), and hand over a documented, tested, production-ready connector — typically within 2 to 4 weeks.

Under the hood, the module adds a proper Odoo payment provider record and a payment.transaction extension so Pix behaves like any other Odoo payment method across Sales, Invoicing, POS, and the eCommerce Website checkout. It generates the EMV/BR Code QR payload (the copia e cola string) with the correct amount, merchant name/city, txid, and expiry encoded per the Pix specification, renders it on the sale order, invoice, and portal, and — the part that saves your team hours — listens for the PSP's confirmation webhook to automatically mark the transaction paid, post the payment, and reconcile it against the open invoice. No more manually matching bank statements to orders.

Everything is grounded in real Odoo architecture: a versioned __manifest__.py declaring dependencies (payment, account, and optionally website_sale, point_of_sale); ORM models (models.Model) with computed fields using @api.depends; access control via ir.model.access.csv plus record rules for multi-company isolation; secure controller endpoints for the inbound webhook with signature verification; QWeb templates/reports to print the QR on documents; and BRL localization tied to the Brazilian chart of accounts (l10n_br). You get the source, so nothing is a black box.

Ne elde edeceksin

Complete Odoo module source code (models, views, controllers, QWeb templates, security files) delivered to your repository, compatible with your Odoo 17, 18, or 19 version

Configured and connected PSP or bank Pix integration in your instance, including credentials setup, webhook endpoint registration, and a verified end-to-end test payment

ir.model.access.csv access rules and record rules configured for your user roles and multi-company structure

Sandbox/test-mode validation followed by production go-live, with a documented test-payment run captured for your records

Admin and end-user documentation — how to enable Pix, read transaction states, handle expiries, and reconcile edge cases — plus a short setup runbook

A live training/handover session for your finance and sales team, recorded on request

Post-launch support window (typically 30 days) covering bug fixes, webhook/reconciliation issues, and configuration adjustments

Deployment notes and the manifest version so future Odoo upgrades and re-installs are clean and repeatable

Bu kimin için

Brazilian eCommerce merchant on Odoo Website

Runs an Odoo Website/eCommerce store selling in BRL and wants shoppers to check out with Pix instantly instead of abandoning at a slow boleto or high-fee card step. Needs the QR on checkout and orders that confirm themselves the moment payment lands.

Finance / accounts-receivable manager

Spends hours each week matching bank Pix receipts to open invoices in Odoo Accounting. Wants webhook-driven auto-reconciliation so payments post and clear against invoices without manual statement matching, with a clean audit trail per transaction.

Retail / POS operator with in-store Pix

Takes in-person payments and wants to display a Pix QR at the counter, confirm it's paid before printing the receipt, and keep POS sessions reconciling correctly against the right journal.

Multi-entity group or Odoo partner/reseller

Manages several Brazilian companies (or clients) in one Odoo database and needs Pix credentials, journals, and transactions isolated per company via record rules — plus source code they can maintain and re-deploy across instances.

Pix Instant Payment for Odoo (Brazil) Nasıl Karşılaştırılır

Kriter	ECOSIRE	Özel Yapı	Rakip
Native Pix payment support in Odoo	Dahil	Kısmi destek	Kısmi destek
Copia e cola + spec-compliant EMV/BR Code QR generation	Dahil	Kısmi destek	Kısmi destek
Automatic webhook reconciliation to invoices	Dahil	Kısmi destek	Kısmi destek
PSP-agnostic — swap Mercado Pago, PagBank, Efí, or bank API	Dahil	Dahil değil	Dahil değil
Built and tested against your exact Odoo 17/18/19 instance	Dahil	Dahil	Dahil değil
Full source code handed over (no black box)	Dahil	Dahil	Kısmi destek
Post-launch support window + upgrade path	Dahil	Dahil değil	Kısmi destek
Time to production	2-4 weeks, scoped	Unpredictable, months	Fast but may not fit
Multi-company isolation via record rules	Dahil	Kısmi destek	Kısmi destek

Pix Instant Payment for Odoo (Brazil) hakkında Sıkça Sorulan Sorular

How long does delivery take, and is this an instant download?

This is a build-to-order engagement, not an instant App Store download. After purchase, ECOSIRE scopes your PSP/bank, builds the module against your exact Odoo version and instance, and installs it. Typical delivery is 2 to 4 weeks depending on the PSP's API and your reconciliation requirements. You approve a short scope first, then we build, test in sandbox, and go live.

What support and updates do I get after go-live?

Every engagement includes a post-launch support window (typically 30 days) covering bug fixes, webhook/reconciliation issues, and configuration tweaks. Because you receive the full source and a versioned __manifest__.py, the module is yours to maintain. We also offer optional ongoing support and paid version-bump work when you upgrade Odoo (e.g. 18 to 19) or switch PSPs.

Which PSPs, banks, and Odoo editions are supported?

The module is PSP-agnostic by design. We commonly connect Mercado Pago, PagSeguro/PagBank, Efí (Gerencianet), Banco Inter, and direct bank Pix APIs (Itaú, Bradesco, Sicoob, and others). It works on Odoo 17, 18, and 19, on both Community and Enterprise. Tell us your provider at scoping and we build the connector against its API.

How does automatic reconciliation actually work?

When a customer pays the Pix QR, your PSP sends a confirmation webhook to a secure Odoo controller endpoint the module registers. The module verifies the callback signature, dedupes retries, marks the payment.transaction as done, posts an account.payment, and reconciles it against the matching open invoice — using the txid and amount encoded in the QR. Everything is logged in the chatter.

Do you support POS and the Odoo Website eCommerce checkout?

Yes, both are optional add-ons scoped at build time. For POS, we render the Pix QR on the payment screen and confirm settlement before the receipt prints. For Website/eCommerce, Pix appears as a payment method at checkout, the shopper pays the QR, and the order confirms automatically when the webhook arrives.

Is the QR code compliant with the Banco Central Pix specification?

Yes. We generate the EMV/BR Code payload (the copia e cola string) with the correct amount, merchant name and city, txid, expiry, and CRC16 checksum per the Pix standard, so it scans in every Brazilian banking app. Dynamic per-transaction QRs lock the exact amount; static merchant QRs are supported for fixed or open amounts.

What exactly do I need to provide to start?

Your Odoo version and access (or a staging copy), the PSP or bank you use plus API credentials for a sandbox, your Brazilian company/tax setup (l10n_br), and which flows you want — Invoicing, Sales, POS, or Website. We handle the rest, including webhook registration and the end-to-end test payment before go-live.

Pix Instant Payment for Odoo (Brazil)

A build-to-order Odoo module that generates Pix QR codes (copia e cola) and auto-reconciles instant BRL payments via bank/PSP webhooks.

Pix EMV/BR Code QR generation — produces the standard scannable QR image and matching copia e cola string on sale orders, invoices, and the customer portal

Copia e cola (copy-and-paste) payload with correct amount, merchant name, merchant city, txid, and CRC16 checksum encoded per the Banco Central Pix specification

Direct bank Pix API connectors (mTLS/OAuth2) for merchants using their bank's Pix API rather than a PSP aggregator

Temel Özellikler