Brazilian Localization QR Code EMV (Pix)
The Pix BR Code is the Brazilian profile of the EMV merchant-presented QR standard. account_qr_code_emv already builds that payload: TLV serialization, CRC16 and the common tags. What it cannot know is the country part, tag 26, which for Pix carries the br.gov.bcb.pix GUI and the addressing key.
This module fills that gap, so a customer invoice can be paid by scanning the QR code with any Brazilian bank app.
The addressing key is not duplicated here: it is read from res.partner.pix, which l10n_br_base already validates for the four key types the Central Bank defines.
Table of contents
Configuration
Register the Pix key on the company partner, under Sales & Purchase > Pix Keys, and link it to the bank account that should receive the payment.
On the bank account, set QR Code to EMV Merchant-Presented QR-code.
On the journal of that bank account, enable QR Code so the payment link and the invoice report offer it.
Usage
The QR code is offered wherever Odoo already offers one: on the customer invoice report and on the payment page. Nothing else changes.
A Pix key must exist on the bank account, otherwise Odoo falls back to the next available QR method and reports why.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Ygor Carvalho <ygcarvalh@gmail.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/l10n-brazil project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-l10n-br-qr-code-emv 18.0.1.0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_l10n_br_qr_code_emv-18.0.1.0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_l10n_br_qr_code_emv-18.0.1.0.0.5-py3-none-any.whl
| Download URL | odoo_addon_l10n_br_qr_code_emv-18.0.1.0.0.5-py3-none-any.whl |
|---|---|
| Size | 28.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04a553c6eea9e7ee39cb477439dc8fe9db521915f89ac0f588d0da7fc30af870
|
|
BLAKE2b-256 checksum How to use checksums |
57612e3ba0d05c01777f0a2c4042e05f7a9e53a2db9774684cb853aadab816bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-l10n-br-qr-code-emv 18.0.1.0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
