Payment QR Code Generator (SEPA, Swiss QR-bill, Pix)

About the Payment QR Code Generator (SEPA, Swiss QR-bill, Pix)

Make the QR code that a payer’s banking app reads to fill in a bank transfer for them: the EPC QR code (often called GiroCode) for a SEPA credit transfer in euro, the Swiss QR-bill with its receipt and payment part, or a static Pix QR code for Brazil. Enter the payee, the account and, if you like, the amount and the reference; the code is built to the official specification, then read back and checked field by field — check digits, lengths, character sets and the size limit — before it is shown.

With a pass you download the code as a sharp PNG or SVG, the QR-bill as a print-ready PDF, and in bulk mode one code per invoice row of a CSV file, as a ZIP or added to your own invoice PDFs. The free preview shows your code marked and blocked so it can’t be scanned, with the fields it holds. Everything runs in your browser: no account details are uploaded, and no money ever passes through MySmartCoPilot.

Common uses

• A payment code on every invoice, so customers pay the right amount to the right account with the right reference.
• Swiss QR-bills for a small business, an association or a landlord without accounting software.
• A Pix code for a shop counter, a delivery or a one-off charge.
• Hundreds of codes at once from an invoice export, added to the invoice PDFs you already have.

What a SEPA EPC QR code holds

The European Payments Council’s guidelines EPC069-12 define the code: the service tag BCD, version 001 or 002, a character set (1 is UTF-8, 2 is ISO 8859-1), SCT for a SEPA Credit Transfer, the payee bank’s BIC (needed in version 001; in version 002 it may be left out for payments within the EEA), the payee’s name (up to 70 characters), the IBAN, an amount in euro from 0.01 to 999,999,999.99, an optional four-letter purpose code, then either a structured reference (up to 35 characters; an ISO 11649 RF reference may be used) or an unstructured text (up to 140) — never both — and a note to the payer (70). The elements are separated by line feeds, nothing follows the last element present, the whole code holds at most 331 bytes, and it is printed with error correction level M, QR version 13 at most. See the EPC guidelines.

Swiss QR-bill rules this generator follows

• Only structured addresses (address type S): name, street, building number, postcode, town and country in separate fields, for both the payee and the payer.
• A QR-IBAN (its bank code is 30000–31999) always goes with a QR reference: 26 digits and a modulo 10 recursive check digit. An ordinary IBAN goes with an ISO 11649 creditor reference (RF…) or with no reference.
• Version 2.4 of the guidelines makes a QR-IBAN with a QR reference CHF only; in EUR use the IBAN with an RF reference or none. This generator already applies that rule.
• The message and the billing information share 140 characters; billing information is coded and starts with “//”.
• The PDF puts the 62 mm receipt and the 148 mm payment part at the foot of an A4 page with dashed separation lines and the scissors symbol, the code 46 × 46 mm with the 7 × 7 mm Swiss cross, headings in the language you choose (German, French, Italian, Romansh or English), and blank fields with corner marks when the amount or the payer is left open — as the Implementation Guidelines and the Style Guide require. More on SIX’s QR-bill page.

Pix: what goes into a static BR Code

A static Pix code is a chain of “ID, length, value” objects (the EMV merchant-presented format the Banco Central do Brasil adopted): the Pix account template with br.gov.bcb.pix and your key (CPF, CNPJ, phone number, e-mail address or random key, written the way the DICT directory stores it), an optional description, the currency 986 (real), an optional amount, the name (25 characters) and city (15), the transaction id (txid, up to 25 letters and digits, or for none) and a CRC16* check over everything. Names are written without accents, as the format expects. The payer’s app shows the name registered for the key, not the one typed here. See the Manual de Padrões para Iniciação do Pix and the Manual do BR Code.

Bulk mode: one code per invoice

• Download the template CSV for the scheme, or use your own export with an invoice column; amount, reference and message columns are optional, and QR-bills also read the payer’s payer_name, payer_street, payer_building, payer_postcode, payer_town and payer_country.
• Rows without a reference can get one made from their invoice number: an RF reference, a QR reference (digits only) or a Pix txid.
• Every row is built and read back like a single code; rows with problems are listed with the reason and left out.
• With a pass you get a ZIP of PNG or SVG files with an index CSV, one PDF with a QR-bill page per invoice, or your own invoice PDFs with the code added: EPC and Pix codes in a corner of the last page, a QR-bill as an extra page. Files are matched by the invoice number in their file names. The free preview makes the first codes of the file and counts the rest.

Before you send or print a code

• Scan it with your own banking app and check the payee name, the IBAN and the amount the app fills in.
• Keep the white border around the code (the quiet zone): the downloads include it. Print the QR-bill at 100% (“actual size”), never “fit to page”, so the payment part stays 148 × 105 mm and the code 46 mm.
• A payment code is only a pre-filled transfer: the payer still confirms the payment in their own app, and money goes straight from their bank to yours.

Limitations

• Singapore PayNow and Thailand PromptPay are not offered: their payload specifications could not be checked against a publication of the scheme owners.
• Codes are static: no merchant account, payment confirmation or dynamic Pix (a Pix code that points to a payment record on your bank’s server).
• The QR-bill’s alternative procedures (eBill and similar) and the “DO NOT USE FOR PAYMENT” notice are not offered; billing information is written exactly as you type it.
• The account and references are checked for their format and check digits. Whether the account exists and belongs to the payee only their bank can confirm.
• Invoice PDFs that are password-protected or whose last page is rotated are refused rather than stamped in the wrong place.

Privacy

On this device: nothing is sent

Everything happens in your browser. What you enter or open here is not uploaded or stored by MySmartCoPilot.