How money moves on this rail, in 12 sourced records: what is final, what can be returned, recalled or refunded, who decides, and what the limits are. A profile belongs to the rulebook, so no reason code list is published on this page.
On a rail fact, every detail line names the section or instrument it rests on and whether that is a rule, a law, operator guidance, or observed practice.
A product is built on this rail and has an object of its own: an authorisation, a lifecycle or a code set. Each view below is derived by the build from records already in the corpus; see products.json for the rule.
Pix AutomaticoA recurring Pix for paying a business. The payer authorises it once, at their own bank, before the first charge; after that the business's bank sends a payment instruction for each charge, from 2 to 10 days before it is due, and the payer's bank schedules it and sends the payment itself on the due date between 00:00 and 08:00, retrying that evening if funds or limit fall short. Every collection is a credit push from the payer's bank, not a debit taken by the business, and it settles as an ordinary Pix. Only a legal person whose CNPJ has been active for at least six months can be offered it as the receiver; every participant holding accounts must offer it to its customers as payers, though one may ask the BCB to be excused for business accounts.28 rules, 1 authorisation, 5 states, 3 code sets; 1 draft, 37 corroborated Pix CobrancaA Pix paid against a charge the receiving end user prepared through its bank, rather than one the payer keys in. A charge is either for immediate payment, as at a till or an online checkout, or for payment by a due date, where interest, a fine, a discount or a rebate may change what is owed. Once the payer starts paying it the payment runs as an ordinary Pix.8 rules, 0 authorisations, 4 states, 0 code sets; 13 corroboratedOne other transaction type holds rules on this rail but no authorisation, lifecycle or code set of their own, so each is a transaction type and not a product: Pix Agendado (scheduled Pix) (5 rules).
Not yet covered: no fact describes Pix Automatico or Pix Cobranca end to end; since 2026-09-22 the authorisation, its journeys, timetable, retries, cancellation and refusal code sets, and the charge and QR code rules, are Core records (mandate.pix-automatico-authorisation and the rule.automatico, rule.agendado and rule.cobranca Rules) that no rail fact lists yet, so they reach agents through core.json and the MCP server but not this page; the Requisitos Minimos para a Experiencia do Usuario manual, the Manual de Resolucao de Disputas and the Manual de Penalidades were not read; consumer-law and liability name the routes without describing what happens along them; no Brazilian consumer statute was read, so what a defrauded user can recover from their own bank is stated as outside the rulebook and not answered; the DICT tracing and prioritization algorithm is not published, so decision-points cannot say why a given account is frozen; catalog 5.13.1 enters SPI production 2026-10-25 and changes the pacs.002 reason list and the Pix Automatico code families; the messages fact describes 5.12.1 and will need a dated successor; reason code records for this rail live in corpus/pix-reject and corpus/pix-return and are not drafted yet.