- Home
- Skills
- E-commerce
- Pix Static QR (BR Code)
Pix Static QR (BR Code)
Build valid static Pix BR Codes (copia e cola) with the right EMV fields and CRC16, and debug the ones banks reject.
Free
Works with the AI Agents you already use
Pix Static QR (BR Code)
Example session with this skill installed
Gere o Pix copia e cola para a chave +5511988887777, recebedor João da Silva, cidade São José dos Campos, valor R$ 10,50. Só o código final e um resumo.
- Read your context and instructions
- Compiled the pix static qr
Gerei o código e conferi: o CRC está OK.
00020126360014br.gov.bcb.pix0114+5511988887777520400005303986540510.505802BR5913Joao da Silva6015Sao Jose dos Ca62070503***6304B860
Resumo
- Chave: +5511988887777 (telefone)
- Recebedor: Joao da Silva (sem acento, porque alguns apps de banco rejeitam)
Cidade: Sao Jose dos Ca. "Sao Jose dos Campos" tem 19 caracteres e o campo aceita no máximo 15, então truncei. O banco não valida a cidade contra nada, então isso não afeta o pagamento.
- Valor: R$ 10,50, gravado como
10.50 - txid:
***, ou seja, sem identificador
É um Pix estático, que não avisa quando o pagamento chega. Quem recebe precisa conferir o valor no extrato do banco.
Real output from a Claude Code session with this skill installed; the payload was re-checked with pix.py --check (CRC OK).
Connects securely to your tools. The creator never sees your data.
About this skill
Generating valid Pix "copia e cola" payloads by hand is error-prone. One wrong length prefix or a miscalculated CRC16 checksum causes bank apps to reject the payment with a generic error.
This skill provides a Python-based utility to generate and validate static Pix BR Code payloads (EMV Merchant Presented Mode). It strictly enforces field ordering, length constraints, and specific formatting rules for keys, amounts, and transaction IDs to ensure compatibility across all Brazilian banking applications.
What it does
- Payload generation produces compliant static Pix strings from a key, name, city, amount, and TXID.
- Field validation enforces EMV standards including ID prefixes and length headers for every data segment.
- CRC16 calculation computes the required CCITT checksum over the full payload including the mandatory prefix.
- Code debugging parses existing payloads to find invalid length prefixes and bad checksums.
- Data sanitization strips accents from merchant names and cities to prevent common bank app rejection.
How it works
- Input parameters provide the Pix key (CPF, CNPJ, Email, Phone, or EVP), merchant info, and optional amount.
- Standardization applies formatting rules like BRL currency codes and specific TXID character constraints.
- Assembly builds the nested EMV string ensuring field 26 (Merchant Account) stays within the 99-character limit.
- Verification uses the
--checkflag to audit an existing payload for compliance.
Frameworks & tools
The implementation uses a self-contained Python 3.8+ script relying only on the standard library. It targets the BCB (Central Bank of Brazil) BR Code specification for static payments.
Why this beats prompting it yourself
LLMs often hallucinate the CRC16-CCITT algorithm or miscalculate the string lengths for nested EMV fields. This skill uses deterministic logic to ensure the checksum is 100% accurate every time, preventing "Invalid QR Code" errors at the point of sale.
Use cases
- Generate static Pix payloads for printed donation flyers or non-profit signage.
- Embed fixed-price Pix payment options into simple web checkouts without an API.
- Troubleshoot why a customer-provided Pix code is being rejected by a specific bank.
- Create reusable payment templates for small service providers or freelancers.
Known limitations
Does not support dynamic Pix (no expiry, no payment status webhooks). Requires external QR libraries for image rendering. Merchant names and cities must fit strict 25 and 15 character limits.
No support for dynamic Pix, webhooks, or payment confirmation. Requires Python 3.8+. Merchant name and city lengths are strictly limited to 25 and 15 characters respectively.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 16 days ago
- Free with an Agensi account
Requires