Multi-type Pix Key Generator

Brazilian PIX in depth: instant payments, recurring debit and 2025 roadmap

PIX is the instant payment rail run by the Central Bank of Brazil (BACEN) since November 2020. It settles funds account-to-account in under 10 seconds, operates 24x7x365 (including Sundays and holidays) and is mandatory for every bank, fintech and payment institution licensed in the country. PIX surpassed credit and debit cards combined in 2023 and now processes peaks above 2,500 TPS (transactions per second) during Black Friday and salary days. An "extra" or "out-of-band" PIX code is a one-off PIX Copia e Cola payload generated by the payer or beneficiary for a single transaction — typical for invoices, ad-hoc transfers or test environments.

There are several PIX modalities. PIX Cobrança binds a payload to a specific invoice (with TXID, payer name and due date — equivalent to a bank slip). PIX Devolução reverses a transfer for up to 80 days after the original payment when fraud or error is reported under the MED (Mecanismo Especial de Devolução, Resolução BCB 103/2021). PIX Saque and PIX Troco, live since 2021, let consumers withdraw cash at ATMs or merchants up to R$ 500 per transaction and 8 withdrawals/month. PIX Garantido (approved by BACEN in 2024, launched in 2025) brings installment payments to the rail and is expected to replace domestic credit-card transactions in the next 3-5 years.

PIX Automático and Open Finance integration

PIX Automático, rolled out in 2025, replaces traditional debit autorization (débito automático). Unlike legacy DDA, the customer can cancel the recurrence directly from their banking app with a single tap — no need to contact the merchant. Open Finance complements this with the Payment Initiation Service Provider (PISP) role: a licensed PISP can trigger a PIX on behalf of the customer after explicit consent, bypassing the bank's app. This is the foundation for embedded finance flows like in-app checkout in marketplaces and super-apps.

Costs, limits and night-time caps

PIX is free for individuals (PF) on personal transfers and purchases. Legal entities (PJ) pay according to their bank contract — typically R$ 0.01 to R$ 0.50 per inbound transaction, dramatically cheaper than the ~3% MDR of credit cards. Daily limits are set by each bank and risk profile: a common policy is R$ 1,000 between 20:00 and 06:00 (the "noturno" window introduced after a wave of express kidnappings in 2021) and up to R$ 20,000 during daytime. Customers can request higher limits with KYC review.

Common pitfalls and security gotchas

• Random keys (EVP) can be revoked by the owner, breaking inbound payments — always re-validate the key before paying a recurrent supplier.
• Social engineering is the dominant fraud vector: scammers convince victims to authorize a PIX themselves. The bank cannot reverse it without MED proof.
• QR Code estático vs dinâmico: static codes are reusable but reveal the key; dynamic codes embed a TXID and amount and are signed by the bank's PSP.
• CRC16 checksum at the end of the BR Code payload — a single wrong character invalidates the entire payload.

FAQ

Can I receive PIX as an individual without paying fees? Yes. By BACEN rule, PF receiving PIX from any source — including PJ paying a freelancer — pays zero. Fees only apply to PJ on the receiving side.

Does a random key last forever? Yes, until the owner explicitly revokes it. A revoked key returns "chave não encontrada" and stops accepting funds; the inbound payment is rejected at the SPI (Sistema de Pagamentos Instantâneos) layer before any debit.

What is the difference between PIX Automático and traditional débito automático? PIX Automático gives the customer single-tap cancellation in the bank app, transparent consent, and the option to set per-cycle limits. Legacy débito automático required calling the merchant and often took weeks to cancel.

Is this generator producing real PIX codes? No. The output follows the EMV BR Code format and validates the CRC16, but the embedded key is fictitious. It is meant for QA, unit tests and UI mockups — never paste these payloads in a real banking app.