{
  "corpus": "orca-product",
  "format_version": "1",
  "built": "2026-09-26",
  "snapshot": "2026-09-20",
  "commit": "019924ac64ee0aa0742b8f02a04488a83633385d",
  "license": {
    "name": "Creative Commons Attribution 4.0 International (CC BY 4.0)",
    "spdx": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/",
    "attribution": "Data from Orca (https://qstve.com/orca/), CC BY 4.0. Snapshot 2026-09-20.",
    "notice": "Reference material about published payment rules. Not legal, compliance or financial advice. Orca cites rulebooks by section and edition and does not reproduce them; rights in the cited documents stay with their authors."
  },
  "uid": "pix:txn.pix-cobranca",
  "rail": "pix",
  "page": "../../../pix/pix-cobranca.html",
  "product": {
    "uid": "pix:txn.pix-cobranca",
    "id": "txn.pix-cobranca",
    "slug": "pix-cobranca",
    "rail": "pix",
    "rail_name": "Pix",
    "governing_authority": "Banco Central do Brasil",
    "snapshot": "2026-09-17",
    "page": "pix/pix-cobranca.html",
    "file": "data/products/pix/pix-cobranca.json",
    "name": "Pix Cobranca",
    "anchor": "a lifecycle of its own (4 states)",
    "transaction_type": {
      "uid": "pix:txn.pix-cobranca",
      "name": "Pix Cobranca",
      "status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "confidence": "high",
      "tier": {
        "k": "cor",
        "label": "Corroborated (authoritative primary)",
        "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
      },
      "summary": "A 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.",
      "effective_since": "2020-11-03",
      "effective_note": "Drafted 2026-09-22 by the Pix Automatico and Cobranca drafting session from the documents named in basis, each opened and read that day.",
      "source_edition": "Regulamento Pix annexed to Resolucao BCB n. 1/2020, consolidated text as served on 2026-09-22, Chapter V, Section II; Manual de Padroes para Iniciacao do Pix version 2.10.0 of 2026-08-19",
      "directions": [
        "credit"
      ],
      "account_types": [
        "any"
      ],
      "sources": [
        {
          "uid": "pix:src.bcb-resolucao-1-2020-regulamento-pix",
          "name": "Resolucao BCB n. 1/2020 and annexed Regulamento Pix, consolidated text, VersaoNormativo 41",
          "url": "https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Resolução%20BCB&numero=1",
          "source_class": "authoritative_primary",
          "edition": "consolidated text, VersaoNormativo 41, amendments listed through Resolucao BCB n. 559 de 23/4/2026",
          "section": "arts. 11-A, 11-B, 11-C, 11-D and 11-E"
        },
        {
          "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
          "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
          "source_class": "authoritative_primary",
          "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
          "section": "sections 2.4, 2.7 and Annex I section 5.1"
        }
      ]
    },
    "counts": {
      "rules": 8,
      "mandates": 0,
      "states": 4,
      "code_sets": 0,
      "reason_codes": 0,
      "roles": 4,
      "members": 13
    },
    "trust": {
      "members": 13,
      "by_status": {
        "draft": 0,
        "corroborated": 13,
        "verified": 0,
        "superseded": 0
      },
      "strongest_source_class": "authoritative_primary"
    },
    "roles": [
      {
        "uid": "pix:role.payer-psp",
        "name": "PSP do pagador",
        "kind": "institution",
        "via": [
          "binds"
        ]
      },
      {
        "uid": "pix:role.pix-participant",
        "name": "Participante do Pix",
        "kind": "institution",
        "via": [
          "binds"
        ]
      },
      {
        "uid": "pix:role.receiver-psp",
        "name": "PSP do recebedor",
        "kind": "institution",
        "via": [
          "binds"
        ]
      },
      {
        "uid": "pix:role.receiving-user",
        "name": "Usuario recebedor",
        "kind": "party",
        "via": [
          "binds"
        ]
      }
    ],
    "mandates": [],
    "states": [
      {
        "uid": "pix:state.charge-active",
        "name": "Pix charge: active",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "summary": "The charge exists and can be paid. While it is active the business may change it, and a fresh read of its QR code shows the new terms, or remove it.",
        "terminal": false,
        "money_moved": "no",
        "visible_as": "API Pix charge status ATIVA",
        "precedes": [
          {
            "uid": "pix:state.charge-concluded",
            "name": "Pix charge: concluded"
          },
          {
            "uid": "pix:state.charge-removed-by-the-receiver",
            "name": "Pix charge: removed by the receiver"
          },
          {
            "uid": "pix:state.charge-removed-by-the-psp",
            "name": "Pix charge: removed by the payee's bank"
          }
        ],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "Annex I section 5.1 item I and its footnote 79, sections 2.7.1.1 and 2.7.1.2, and Annex I sections 6.5.2 and 6.5.3"
          }
        ]
      },
      {
        "uid": "pix:state.charge-concluded",
        "name": "Pix charge: concluded",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "summary": "A Pix carrying the charge's transaction identifier has been received. The charge now accepts no other payment and can be neither changed nor removed. It says the charge was paid, not that the debt behind it is settled.",
        "terminal": true,
        "money_moved": "yes",
        "visible_as": "API Pix charge status CONCLUIDA",
        "precedes": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "Annex I section 5.1 item I and its footnote 79, sections 2.7.1.1 and 2.7.1.2, and Annex I sections 6.5.2 and 6.5.3"
          }
        ]
      },
      {
        "uid": "pix:state.charge-removed-by-the-psp",
        "name": "Pix charge: removed by the payee's bank",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "low",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "summary": "The payee's bank removed the charge itself. The manual names the state without saying on what grounds a bank does this or whether it can be reversed; terminal here is [Inference].",
        "terminal": true,
        "money_moved": "no",
        "visible_as": "API Pix charge status REMOVIDO_PELO_PSP",
        "precedes": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "Annex I section 5.1 item I and its footnote 79, sections 2.7.1.1 and 2.7.1.2, and Annex I sections 6.5.2 and 6.5.3"
          }
        ]
      },
      {
        "uid": "pix:state.charge-removed-by-the-receiver",
        "name": "Pix charge: removed by the receiver",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "medium",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "summary": "The business asked its bank to remove the charge, for example because the customer gave up the purchase. A payer who reads the code afterwards must be told the charge was deleted. The manual calls only the concluded status final and gives no way to reactivate a removed charge; terminal here is [Inference].",
        "terminal": true,
        "money_moved": "no",
        "visible_as": "API Pix charge status REMOVIDO_PELO_USUARIO_RECEBEDOR; the payer's app says the charge was deleted",
        "precedes": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "Annex I section 5.1 item I and its footnote 79, sections 2.7.1.1 and 2.7.1.2, and Annex I sections 6.5.2 and 6.5.3"
          }
        ]
      }
    ],
    "code_sets": [],
    "reason_codes": [],
    "rules": [
      {
        "uid": "pix:rule.cobranca-a-charge-takes-one-payment-and-an-identifier-is-never-reused",
        "name": "Pix Cobranca: one payment per charge, and a transaction identifier used once",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "A charge is active until paid or removed. When a Pix carrying its transaction identifier arrives it becomes concluded, which is final: it takes no further payment and can be neither changed nor removed. Concluded speaks of the charge, not of the debt behind it. While active, the business may change a charge, and a new read of the QR code shows the change, or remove it, and a payer who then reads it must be told it was deleted. A dynamic QR code may mark itself as single use in BR Code field 01. The transaction identifier of a charge must be unique for that receiver at that bank and is never reused, not even after the charge was removed; it is 26 to 35 letters and digits. So an attempt that did not complete may be retried on the same still active charge, while a new charge always needs a new identifier.",
        "facet": "finality",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "sections 2.7.1.1 and 2.7.2, and Annex I sections 5.1, 5.3.1, 6.5.2 and 6.5.3"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-the-payees-bank-computes-the-final-amount",
        "name": "Pix Cobranca: who computes interest, fines, discounts and rebates",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "The payee's bank computes the amount due on a due date charge, from the terms the business set when it created the charge (how any rebate, discount, interest and fine is calculated) and the payer's municipality and intended payment date. The charge the payer's app fetches always carries the final amount, which is compulsory, beside optional figures for the original amount, rebate, discount, interest and fine; where all of those except the original are zero the app shows only the final amount. So there is no case in which the app has to fall back to the original amount: a charge without a final amount does not meet the standard. A charge may not be built so that its discount could exceed the original amount.",
        "facet": "settlement",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "sections 2.7.1.2 and Annex III sections 1 and 3"
          }
        ]
      },
      {
        "uid": "pix:rule.agendado-and-scheduled-charges-settle-00-to-08-with-an-evening-retry",
        "name": "Pix Agendado and scheduled due date charges: the settlement window and the evening retry",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 2 named sources, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "A Pix the payer schedules for a date, and a charge with a due date that the payer chose to schedule, are sent for settlement on that date between 00:00 and 08:00 if the balance and the limit allow. If the balance is short, or an operational failure intervened, the payer is told and the bank tries at least once more between 18:00 and 21:00, with 21:00 the last moment. If the limit is what is short, the payer is told. The payer can cancel such a scheduled payment up to 23:59 on the day before. The difference from Pix Automatico is who is in charge: here the payer set the date and the amount, and no business sends instructions or retries on later days.",
        "facet": "hours",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [
          {
            "uid": "pix:txn.pix-agendado",
            "name": "Pix Agendado (scheduled Pix)"
          }
        ],
        "parameters": [
          {
            "kind": "time_window",
            "text": "first attempt 00:00 to 08:00 on the chosen date; at least one retry 18:00 to 21:00 if the balance was short; payer may cancel until 23:59 the day before"
          }
        ],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-in-513-2024-pix-automatico-agendado-cobranca",
            "name": "Instrucao Normativa BCB n. 513/2024, operational procedures for Pix Automatico, Pix Agendado and Pix Cobranca, consolidated version 5.0",
            "url": "https://www.bcb.gov.br/api/conteudo/app/normativos/exibenormativo?p1=Instru%C3%A7%C3%A3o%20Normativa%20BCB&p2=513",
            "source_class": "authoritative_primary",
            "edition": "version 5.0, 17 articles including art. 15-A, amended by IN BCB n. 614/2025, n. 634/2025 and n. 743/2026; not revoked",
            "section": "arts. 12 and 14"
          },
          {
            "uid": "pix:src.bcb-resolucao-1-2020-regulamento-pix",
            "name": "Resolucao BCB n. 1/2020 and annexed Regulamento Pix, consolidated text, VersaoNormativo 41",
            "url": "https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Resolução%20BCB&numero=1",
            "source_class": "authoritative_primary",
            "edition": "consolidated text, VersaoNormativo 41, amendments listed through Resolucao BCB n. 559 de 23/4/2026",
            "section": "art. 11-D par. unico"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-a-due-date-charge-rolls-to-the-payers-next-business-day",
        "name": "Pix Cobranca: due date, grace period and the payer's holidays",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "A due date charge must carry its due date, payable at any hour of that day, and a number of calendar days after it during which it can still be paid late. If either date falls on a weekend or on a holiday where the payer is, it moves to the next business day, and every date built on it (the grace period, the discount dates, when interest and the fine start) moves with it. The holidays that count are the payer's state and municipal ones: when the payer's app fetches the charge it sends the payer's IBGE municipality code and the date the payer means to pay, and the payee's bank uses them to price the charge. If the municipality is not sent the payee's bank assumes no state or municipal holiday applies; if the intended date is not sent it assumes the due date, or the day of the query once the charge is overdue. The manual names no list of holidays to consult.",
        "facet": "hours",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "section 2.7.1.2 with footnotes 41, 44 and 45, and Annex III section 3"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-an-immediate-charge-lives-24-hours-by-default",
        "name": "Pix Cobranca: how long an immediate charge stays payable",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "An immediate charge is payable for the number of seconds its creator sets in the expiry field, counted from when it was created, and for 24 hours (86400 seconds) if the creator sets nothing. The receiving end user sets it through its bank's API Pix when it creates the charge. After it expires, the payee's bank may answer a request for the charge with an HTTP status that says so, such as 410 or 404, and the paying bank's reader has nothing to pay.",
        "facet": "hours",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [
          {
            "kind": "time_window",
            "text": "default life of an immediate charge, from its creation, when the creator sets no expiry"
          }
        ],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "sections 2.7.1.1 and 2.7.3"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-a-static-code-leaves-reconciliation-to-the-receiver",
        "name": "Pix QR codes: a static code's identifier is the receiver's to keep consistent",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "The payee's bank cannot stop a transaction identifier repeating on static QR codes, because they are made without the API Pix and it never sees them. Sometimes repeating it is the point, as with a fixed code at a counter with no amount; sometimes it must not repeat, as with a code printed for one sale. Keeping payments on static codes consistent is left entirely to the receiver, and the API Pix only returns the payments that arrived with a given identifier. The identifier reaches the payee's bank on the pacs.008.",
        "facet": "messages",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "Annex I section 5.3.2 and section 2.4.1 footnote 6"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-static-dynamic-and-composite-qr-codes",
        "name": "Pix QR codes: static, dynamic and composite",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "A static QR code carries everything inside the image: a DICT key, which is compulsory, and optionally a transaction identifier, free text, an amount and a withdrawal facilitator. A dynamic QR code carries the key and a URL at the payee's bank; the charge itself, with amount, identifier and the rest, is fetched from that URL when the code is read, so it can change over time and must be validated and queried after reading. A composite QR code adds a second URL pointing at Pix Automatico recurrence terms, with or without a static or dynamic charge alongside it. All three follow the BR Code layout, and a payer's app that cannot fetch the recurrence part must fall back to paying the rest as it would a plain code.",
        "facet": "messages",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [
          {
            "uid": "pix:txn.pix-automatico",
            "name": "Pix Automatico"
          }
        ],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-manual-padroes-iniciacao-pix-2-10-0",
            "name": "Manual de Padroes para Iniciacao do Pix, version 2.10.0",
            "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf",
            "source_class": "authoritative_primary",
            "edition": "version 2.10.0, revision history entry dated 2026-08-19, 123 pages",
            "section": "sections 2.4, 2.6, 2.7, 2.7.2 and 2.8, and footnote 87"
          }
        ]
      },
      {
        "uid": "pix:rule.cobranca-immediate-and-due-date-charges",
        "name": "Pix Cobranca: a charge for immediate payment or for payment by a due date",
        "status": "corroborated",
        "stored_status": "corroborated",
        "source_class": "authoritative_primary",
        "confidence": "high",
        "tier": {
          "k": "cor",
          "label": "Corroborated (authoritative primary)",
          "say": "A validator compared this with 1 named source, the strongest being a publication of Banco Central do Brasil itself. It is not verified: no person has checked it against the current rulebook edition."
        },
        "statement": "Pix Cobranca lets a receiving end user prepare and collect charges through its bank. An immediate charge is for business where payment happens when the charge is issued, such as a till or an online checkout. A due date charge can be paid later and can carry interest, a fine, other additions, a discount and other rebates. Once the payer starts paying a charge it becomes an ordinary Pix. Offering Pix Cobranca to receivers is optional for a participant, apart from the duty to give natural person customers a static QR code, but every account provider must be able to read a Pix Cobranca QR code and start a payment from it, and must let a payer schedule a due date charge for a future date. A payment initiator may choose not to read them. Contactless initiation of a charge is optional and, where offered, follows the manual from 2025-12-01.",
        "facet": "participants",
        "rests_on": "rule",
        "via": "applies_to",
        "also_applies_to": [],
        "parameters": [],
        "part_of": [],
        "sources": [
          {
            "uid": "pix:src.bcb-resolucao-1-2020-regulamento-pix",
            "name": "Resolucao BCB n. 1/2020 and annexed Regulamento Pix, consolidated text, VersaoNormativo 41",
            "url": "https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Resolução%20BCB&numero=1",
            "source_class": "authoritative_primary",
            "edition": "consolidated text, VersaoNormativo 41, amendments listed through Resolucao BCB n. 559 de 23/4/2026",
            "section": "arts. 11-A, 11-B, 11-C, 11-D, 11-DA and 11-E"
          }
        ]
      }
    ],
    "inherited": [
      {
        "facet": "limits",
        "label": "Limits",
        "question": "What limits apply to a payment, and who sets them?",
        "fact_uid": "pix:limits",
        "fact_name": "What limits apply to a Pix, and who sets them?"
      },
      {
        "facet": "return",
        "label": "Return",
        "question": "How does a payment come back, and on what deadline?",
        "fact_uid": "pix:return",
        "fact_name": "Can a settled Pix be returned, by whom and by when?"
      },
      {
        "facet": "recall",
        "label": "Recall",
        "question": "Can the sender ask for a payment back, and who decides?",
        "fact_uid": "pix:recall",
        "fact_name": "Can the payer's side pull a Pix back, and what does asking actually do?"
      },
      {
        "facet": "refund",
        "label": "Refund",
        "question": "Can the payer get the money back, and on what right?",
        "fact_uid": "pix:refund",
        "fact_name": "Does anyone have a right to be refunded, and how does the money get back?"
      },
      {
        "facet": "liability",
        "label": "Liability",
        "question": "Who bears a loss when something goes wrong?",
        "fact_uid": "pix:liability",
        "fact_name": "Who bears the loss when a Pix goes wrong?"
      },
      {
        "facet": "consumer-law",
        "label": "Consumer law",
        "question": "What does the law give a consumer here, beyond the rulebook?",
        "fact_uid": "pix:consumer-law",
        "fact_name": "What protects an end user on Pix, and where does the rulebook stop?"
      },
      {
        "facet": "decision-points",
        "label": "Human decision points",
        "question": "Where does a rule leave the decision to a bank or a person?",
        "fact_uid": "pix:decision-points",
        "fact_name": "Where does Pix hand the outcome to a human or a bank's judgment?"
      }
    ],
    "differs": [],
    "exceptions": []
  }
}
