1. Standard Basis
Pix QR codes follow the EMV merchant-presented format, published by the Central Bank of Brazil as BR Code. The payload is a string of tag-length-value fields. While specialized generators exist for Pix, understanding the structure helps with troubleshooting. Test generated codes with a [QR scanner](/qr-scanner) in actual banking apps.
2. Key Fields
*
00: Payload format indicator, 01
*
26: Merchant account information containing the GUI br.gov.bcb.pix and the Pix key
*
52: Merchant category code
*
53: Currency 986 (Brazilian real)
*
54: Amount (optional for static)
*
58: Country code BR
*
59, 60: Merchant name and city
*
62: Additional data such as a transaction reference
*
63: CRC16 checksum
3. Notes
Static codes can omit the amount so the payer enters it. Always generate from the official specification and verify by scanning with a banking app. Check the Central Bank's current manual for field limits before implementing. For general payment QR needs, see our [URL QR code generator](/url-qr-code-generator). Size codes with our [QR size calculator](/qr-size-calculator), position using our [QR placement guide](/qr-placement-guide), and verify with our [printed QR tester](/printed-qr-tester). Understand error tolerance with our [error correction simulator](/error-correction-simulator).
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
