How to create a static PIX QR Code for your business
Build a static BR Code PIX charge with key, optional amount, and payer-friendly payload.
Step-by-step
- Choose transaction type and validate key format.
- Fill receiver data and optional amount with proper decimal format.
- Generate payload and QR code in BR Code-compatible format.
- Test payment in banking apps before publishing to end users.
- Store reference payload for support and reconciliation.
When to use this PIX workflow
static pix qr code is useful in in-person sales and fast checkout, especially when you need fast payment confirmation and fewer manual steps.
A standard workflow reduces friction for customers and avoids invalid charge payloads.
Required fields and validation
Validate key type, receiver name, city, amount format, and description length before generating the final payload.
When a field is optional, keep defaults explicit so downstream systems behave predictably.
Operational sequence
Generate the payload, validate integrity, render the QR code, and test in at least two banking apps before publishing.
Store a reference of the generated payload for support and reconciliation.
Common failure points
Invalid key type, malformed amount separators, and inconsistent merchant identifiers are recurrent issues.
A final pre-publish checklist prevents most production incidents in PIX flows.
Quick practical example
In a in-person sales and fast checkout process, generate PIX payload + QR, perform a real low-value test payment, then release to users.
This confirms compatibility and avoids checkout failures after launch.