イメージプレビュー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 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. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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 one working week.
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.
得られるもの
- 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 (two weeks) 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
これは誰のためのものですか
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) の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Native Pix payment support in Odoo | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Copia e cola + spec-compliant EMV/BR Code QR generation | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Automatic webhook reconciliation to invoices | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| PSP-agnostic — swap Mercado Pago, PagBank, Efí, or bank API | 付属 | 含まれていない | 含まれていない | 含まれていない |
| Built and tested against your exact Odoo 17/18/19 instance | 付属 | 付属 | 含まれていない | 部分的なサポート |
| Full source code handed over (no black box) | 付属 | 付属 | 部分的なサポート | 付属 |
| Post-launch support window + upgrade path | 付属 | 含まれていない | 部分的なサポート | 部分的なサポート |
| Time to production | one working week, scoped | Unpredictable, months | Fast but may not fit | N/A — not available |
| Multi-company isolation via record rules | 付属 | 部分的なサポート | 部分的なサポート | 付属 |
Pix Instant Payment に関するよくある質問
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 one working week 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 (two weeks) 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.
関連モジュール
Point of Sale Order Discount
A build-to-order Odoo Point of Sale extension that lets cashiers apply fixed-amount or percentage discounts to the whole order or to individual lines, with configurable limits and permissions. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17, 18, or 19.
Poland Accounting Localization Base
A build-to-order Polish accounting foundation for Odoo: the plan kont chart of accounts, full VAT tax set, sales/purchase VAT registers, split payment, and Ministry of Finance whitelist verification. ECOSIRE builds, installs, and supports it after you confirm scope.
Pix Instant Payment
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
- 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