GetQRMaker

Pix QR Code Generator

  • Free
  • No sign-up
  • Never expires

Make a static Pix code with your Pix key, name and an optional amount that any Brazilian bank app can pay in one scan.

  1. Pick a type(done)
  2. 2Add content(current step)
  3. 3Save

Type

Pix (Brazil)

A static Pix code (BR Code) with your Pix key, name and an optional amount. Any Brazilian bank app reads it.

Read by Brazilian bank and wallet apps (Nubank, Itaú, Bradesco, PicPay, Mercado Pago…) as a static Pix code.

This code is for receiving money. The site does not process payments and never sees them — the transfer happens in the payer's bank app.

Preview

Waiting

Fill in the form above and your QR code appears here.

Size
Margin

Output 512 × 512px · 4-module margin

Add some content to turn on the save buttons.

Style

Optional · Frame, color, background, error correction, logo

Frame shape

Adds a colored border and a one-line caption around the code. Included in the saved PNG, SVG and the print sheet.

Center logo

More optionsCode color · Background · Error correction

Code color

#111111

Background

Error correction

Maximum keeps the code readable when part of it is covered or damaged, but makes it denser.

How a Pix QR code works

The code holds a BR Code: the text format defined by the Banco Central do Brasil for Pix, built on the EMV standard for merchant-presented QR codes. Every item is written as an id, a two-digit length and the value. The merchant account block carries the identifier br.gov.bcb.pix and your Pix key; then come the merchant category 0000, the currency 986 for the real, the optional amount, the country BR, your name (up to 25 letters), your city (up to 15) and the transaction id. A CRC-16 checksum closes the string, so a damaged or edited code is rejected by the bank app rather than paid to the wrong person.

This is a static code, the same kind a bank gives you to print at the till. It does not call an API or a payment service, so the transaction id is set to *** when you leave it empty, exactly as the Banco Central manual shows for static codes. If you type one (letters and digits, up to 25), it travels with the payment and appears in your statement, which helps with reconciliation.

The payer opens their bank or wallet app (Nubank, Itaú, Bradesco, Caixa, PicPay, Mercado Pago and every other Pix participant), chooses Pix and scans. The app looks up the key in the central directory and shows the account holder's registered name, not the name in the code, so the payer can confirm who receives the money. With an amount in the code it is filled in; without one, the payer types it. The same string is also the Pix copia e cola text shown under the form, which you can paste into a message.

Where it helps

  • A street vendor or market stall prints a code with no amount, so each customer scans and types what they owe.
  • A small shop puts a code with a fixed price next to a product, for example a R$ 25.00 lunch plate.
  • A condominium or club sends a code with the monthly fee and a transaction id such as COTA2026MAR, so payments are easy to match.
  • A church, school fair or charity shows a donation code on a poster or on the screen of a live stream.

Tips before you print

  1. Phone keys must start with +55, for example +5511912345678. Eleven plain digits are read as a CPF, which is a different key.
  2. Keep the name and city short and without accents. The standard allows 25 and 15 characters, and accents are removed for you; bank apps show the name registered with the key anyway.
  3. Test the code with your own bank app before printing. The app shows the registered name of the key holder; if it is not yours, the key has a typo.
  4. For prices that change, leave the amount empty and write the price next to the code. A code with an amount has to be regenerated every time the price changes.

Questions

Is this an official Pix code?
It follows the Banco Central do Brasil's BR Code standard for static Pix codes, the same format your bank uses. Any Pix-enabled app reads it. The site is not a payment institution and does not take part in the transfer.
Does the code expire?
No. A static Pix code works for as long as the key stays registered to your account. If you delete the key or move it to another bank, make a new code.
Can I see who paid?
Payments arrive in your bank account like any Pix transfer, with the payer's name. Adding a transaction id (txid) to the code helps you tell payments from one code apart from others in your statement.
Why does the app show a different name from the one I typed?
Bank apps display the name registered with the Pix key in the central directory (DICT) and ignore the name inside the code. The name in the code is still required by the standard, so type yours; the payer will see your registered name.

Guide: Pix QR codes

What Pix is and why the key matters

Pix is the instant payment system operated by the Banco Central do Brasil. It launched in November 2020 and settles transfers within seconds at any hour, weekends included. Instead of typing a branch and account number, the payer addresses a Pix key: a CPF or CNPJ, a mobile number, an email address, or a random key (chave aleatória, also called EVP) that the bank generates for you.

Whatever key you choose is visible to anyone who decodes the code, so for anything printed in public the random key is the sensible choice. A CPF is a personal tax number, and a phone number or email invites spam, while a 36-character random key points at the same account and reveals nothing about you.

Static codes and dynamic codes

A static code carries the key, the merchant details and optionally an amount, and the string never changes, so it can be printed once. A dynamic code is created by your bank or payment service for a single charge: it embeds a URL that the payer’s app queries, and the bank keeps a transaction record that can expire or be marked paid.

This generator produces static BR Codes only, which suits a stall, a donation poster or a recurring fee but gives no per-order tracking: payments through the same code look alike in your statement, and a txid is one id for all of them, not one per sale. For a reference per customer, make one code each or ask your bank for dynamic codes; the static vs dynamic article covers the general trade-off.

What the payer can and cannot change

When the amount field is empty, the bank app asks the payer to type a value. When an amount is present, most apps lock it, so the customer cannot pay less by mistake; a few apps still allow editing, so treat a fixed amount as a convenience rather than a guarantee. The CRC16 at the end of the payload rejects any edited string.

  • Print the registered name of the key holder next to the code, so the payer can compare it with what the app displays.
  • Check your statement weekly; a sudden drop in payments usually means the code was swapped or damaged.

Sticker swapping and other risks

The most common fraud against static codes is physical: someone pastes their own code over yours and collects your customers’ payments until you notice. The CRC does not help here, since the attacker’s code is internally valid. The defence is the payer checking the name shown in the app, which is why your trade name belongs in sight of the code.

Export the finished code as SVG for a sign or banner (see PNG vs SVG) and check the size guide for printing before it goes on a wall. Businesses with customers in India will find the same static approach on the UPI QR code page.