How the tool works
Enter the Pix key, recipient name, and city. Optionally set an amount, description, and alphanumeric TXID. The browser assembles the TLV fields, calculates CRC16, validates the result with the existing decoder, and then renders the QR Code.
Supported input and output
The tool creates static Pix BR Code payloads. Amounts may be fixed or omitted, TXID accepts up to 25 letters or digits, and an omitted TXID is encoded as ***. Name and city are normalized to the permitted merchant text representation.
Practical example
A service provider can enter an email Pix key, business name, city, a fixed invoice value, and an internal TXID, then copy the payload or download its QR Code.
Common use cases
Use static Pix codes for counters, invoices, service charges, printed material, remote payment requests, and reusable codes without integrating a dynamic charge API.
Limits and important checks
Structural and CRC validation do not query DICT, confirm key ownership, identify the actual account holder, or prove payment. The payer must confirm the recipient and amount in the banking application.
Privacy and local processing
Unless the tool explicitly identifies an external lookup, input and generated output are processed in your browser and are not uploaded to CosmoTools. Avoid placing secrets in any web page and review downloaded results before using them in production.
Frequently asked questions
Does this generator confirm the Pix key owner?
No. It creates and validates the BR Code structure but does not query DICT or verify ownership.
Can I leave the amount open?
Yes. If no amount is entered, the payer can usually enter it in the payment application.
Does a valid CRC16 confirm payment?
No. CRC16 confirms payload integrity only. It does not confirm a recipient, charge, or completed payment.