{
  "corpus": "orca-upcoming",
  "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."
  },
  "counts": {
    "dated": 21,
    "mentioned": 60,
    "passed": 0,
    "expected": 0
  },
  "dated": [
    {
      "date": "2026-09-30",
      "kind": "stops_applying",
      "uid": "rtp-return-request:UAPA",
      "rail": "rtp-return-request",
      "name": "Fraudulently induced payment",
      "record_url": "data/records/rtp-return-request/UAPA.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2026-03-31",
      "effective_to": "2026-09-30",
      "successor": null,
      "note": "UAPA fraud reporting required from 2026-03-31 (section 1.b). This record's statement stops applying 2026-09-30: from that date, under section 1.d.ii of the rules interpretation dated 2026-09-14, a Sending Participant of IDS Payments must also send UAPA for an IDS Payment found to have been fraudulently induced, whether the IDS Originating Institution passes that determination on or the Sending Participant reaches it through its own processes (note 8). UAPA stays in use with that wider scope; once the date has passed the RTP watch drafts the successor under the dated-id procedure in docs/watch.md. Later dates for the successor, not asserted by this record: the two business day reporting deadline (section 1.c) and OBO reporting (section 1.d.i), both 2027-03-01. Found by the RTP watch 2026-09-17; the end date was typed after a later reread of the interpretation (see basis).",
      "updated": "2026-09-26"
    },
    {
      "date": "2026-10-01",
      "kind": "replaced_by",
      "uid": "pix:rule.consumer-law-the-limit-panel-must-be-where-the-customer",
      "rail": "pix",
      "name": "The limit panel must be where the customer already is",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-22"
        }
      ],
      "effective_since": "2024-11-01",
      "effective_to": "2026-10-01",
      "successor": {
        "uid": "pix:rule.consumer-law-the-limit-panel-must-be-where-the-customer-from-2026",
        "name": "The limit panel must be where the customer already is, from 2026-10-01",
        "effective_since": "2026-10-01",
        "status": "corroborated"
      },
      "note": "Split out of pix:consumer-law by the 2026-09 Orca Core migration; no rule change identified. effective_since is the fact's. Stops applying 2026-10-01, when IN BCB n. 746 de 16/6/2026 (arts. 1 to 3) takes the contactless item out of the limit panel (IN 512 art. 10 par. 2 VI revoked); the draft successor is pix:rule.consumer-law-the-limit-panel-must-be-where-the-customer-from-2026.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-01",
      "kind": "replaced_by",
      "uid": "pix:rule.limits-contactless-and-initiation-without-redirection",
      "rail": "pix",
      "name": "Contactless and initiation without redirection",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-12-01",
      "effective_to": "2026-10-01",
      "successor": {
        "uid": "pix:rule.limits-contactless-and-initiation-without-redirection-from-2026",
        "name": "Contactless and initiation without redirection, from 2026-10-01",
        "effective_since": "2026-10-01",
        "status": "corroborated"
      },
      "note": "Split out of pix:limits by the 2026-09 Orca Core migration; no rule change identified. The line itself dates this from 2025-12-01. Stops applying 2026-10-01, when IN BCB n. 746 de 16/6/2026 (arts. 2 and 3) revokes arts. 16-A and 16-C; the draft successor is pix:rule.limits-contactless-and-initiation-without-redirection-from-2026.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-01",
      "kind": "replaced_by",
      "uid": "pix:rule.limits-the-user-can-drive-the-limit-in-both-directions",
      "rail": "pix",
      "name": "The user can drive the limit in both directions",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-09-29",
      "effective_to": "2026-10-01",
      "successor": {
        "uid": "pix:rule.limits-the-user-can-drive-the-limit-in-both-directions-from-2026",
        "name": "The user can drive the limit in both directions, from 2026-10-01",
        "effective_since": "2026-10-01",
        "status": "corroborated"
      },
      "note": "Split out of pix:limits by the 2026-09 Orca Core migration; no rule change identified. effective_since is the fact's. Stops applying 2026-10-01, when IN BCB n. 746 de 16/6/2026 (arts. 1 to 3) takes the contactless item out of the limit panel (IN 512 art. 10 par. 2 VI revoked); the draft successor is pix:rule.limits-the-user-can-drive-the-limit-in-both-directions-from-2026.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-25",
      "kind": "takes_effect",
      "uid": "pix-reject:DS02",
      "rail": "pix-reject",
      "name": "Order Cancelled",
      "record_url": "data/records/pix-reject/DS02.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/cedsfn/Catalogos/spi.5.13.1.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-10-25",
      "effective_to": null,
      "successor": null,
      "note": "Added in catalog 5.13.1; in force 2026-10-25; pending at snapshot 2026-09-17",
      "updated": "2026-09-21"
    },
    {
      "date": "2026-10-25",
      "kind": "takes_effect",
      "uid": "pix-reject:DU03",
      "rail": "pix-reject",
      "name": "Duplicate Transaction",
      "record_url": "data/records/pix-reject/DU03.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/cedsfn/Catalogos/spi.5.13.1.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-17"
        }
      ],
      "effective_since": "2026-10-25",
      "effective_to": null,
      "successor": null,
      "note": "Added in catalog 5.13.1; in force 2026-10-25; pending at snapshot 2026-09-17",
      "updated": "2026-09-17"
    },
    {
      "date": "2026-10-25",
      "kind": "stops_applying",
      "uid": "pix:codeset.pain012-authorisation-rejection-reasons",
      "rail": "pix",
      "name": "Pix Automatico authorisation rejection reasons (pain.012)",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-06-28",
      "effective_to": "2026-10-25",
      "successor": null,
      "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. Values are the domain table's codes with names written in English in Orca's own words. effective_since is the production date of 5.12.1; on 2026-10-25 the four SPI codes leave the list and this record needs a dated successor. Stops applying 2026-10-25, the SPI production date of catalog 5.13.1; the draft successor is pix:codeset.pain012-authorisation-rejection-reasons-from-2026.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-25",
      "kind": "takes_effect",
      "uid": "pix:codeset.pain012-authorisation-rejection-reasons-from-2026",
      "rail": "pix",
      "name": "Pix Automatico authorisation rejection reasons (pain.012), catalog 5.13.1",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-10-25",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-24 for change calendar decision 3 from the documents named in basis. Published 2026-07-24 (catalog 5.13.1); in SPI production 2026-10-25, the date the BCB comunicacaodados page, read 2026-09-24, gives for version 5.13 on the SPI. Until then pix:codeset.pain012-authorisation-rejection-reasons governs. The Core schema allows supersedes only between Rules, so this CodeSet names the one it replaces through see_also.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-25",
      "kind": "stops_applying",
      "uid": "pix:codeset.pain014-instruction-errors",
      "rail": "pix",
      "name": "Pix Automatico instruction errors (pain.014)",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-06-28",
      "effective_to": "2026-10-25",
      "successor": null,
      "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. Values are the domain table's codes with names written in English in Orca's own words. effective_since is the production date of 5.12.1; on 2026-10-25 the five SPI codes leave the list and this record needs a dated successor. Stops applying 2026-10-25, the SPI production date of catalog 5.13.1; the draft successor is pix:codeset.pain014-instruction-errors-from-2026.",
      "updated": "2026-09-24"
    },
    {
      "date": "2026-10-25",
      "kind": "takes_effect",
      "uid": "pix:codeset.pain014-instruction-errors-from-2026",
      "rail": "pix",
      "name": "Pix Automatico instruction errors (pain.014), catalog 5.13.1",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-10-25",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-24 for change calendar decision 3 from the documents named in basis. Published 2026-07-24 (catalog 5.13.1); in SPI production 2026-10-25, the date the BCB comunicacaodados page, read 2026-09-24, gives for version 5.13 on the SPI. Until then pix:codeset.pain014-instruction-errors governs. The Core schema allows supersedes only between Rules, so this CodeSet names the one it replaces through see_also.",
      "updated": "2026-09-24"
    },
    {
      "date": "2027-01-01",
      "kind": "takes_effect",
      "uid": "us-ach:rule.iat-contact-registry-from-2027",
      "rail": "us-ach",
      "name": "IAT contact required in the ACH Contact Registry from 2027-01-01",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2027-01-01",
      "effective_to": null,
      "successor": null,
      "note": "Rule effective 2027-01-01, not yet in force at snapshot 2026-09-19.",
      "updated": "2026-09-19"
    },
    {
      "date": "2027-01-01",
      "kind": "takes_effect",
      "uid": "us-ach:rule.messages-character-handling-is-not-uniform-between",
      "rail": "us-ach",
      "name": "Character handling is not uniform between operators",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2027-01-01",
      "effective_to": null,
      "successor": null,
      "note": "Split out of us-ach:messages by the 2026-09 Orca Core migration; no rule change identified. The line itself dates this from 2027-01-01.",
      "updated": "2026-09-19"
    },
    {
      "date": "2027-01-01",
      "kind": "takes_effect",
      "uid": "us-ach:rule.messages-the-record-line",
      "rail": "us-ach",
      "name": "The record line",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2027-01-01",
      "effective_to": null,
      "successor": null,
      "note": "Split out of us-ach:messages by the 2026-09 Orca Core migration; no rule change identified. The line itself dates this from 2027-01-01.",
      "updated": "2026-09-19"
    },
    {
      "date": "2027-03-19",
      "kind": "takes_effect",
      "uid": "us-ach:rule.iat-date-of-birth-field-from-2027",
      "rail": "us-ach",
      "name": "Date of birth field in the IAT format from 2027-03-19",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2027-03-19",
      "effective_to": null,
      "successor": null,
      "note": "Rule effective 2027-03-19, not yet in force at snapshot 2026-09-19; known only from a Nacha news post, not a rule page.",
      "updated": "2026-09-19"
    },
    {
      "date": "2027-03-31",
      "kind": "takes_effect",
      "uid": "au-npp:rule.consumer-law-internal-dispute-resolution-and-apportionment-guidelines",
      "rail": "au-npp",
      "name": "A regulated entity must run internal dispute resolution and have regard to any apportionment guidelines",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2027-03-31",
      "effective_to": null,
      "successor": null,
      "note": "Effective since 2027-03-31: for covered banking services this provision is switched off by the Designation's transitional rule until before that date Drafted 2026-09-21 from the Act as made. If a framework rules instrument prescribing apportionment guidelines is registered, this record and the liability fact both change.",
      "updated": "2026-09-21"
    },
    {
      "date": "2027-03-31",
      "kind": "takes_effect",
      "uid": "au-npp:rule.consumer-law-the-rest-of-part-ivf-reaches-banking-on-2027-03-31",
      "rail": "au-npp",
      "name": "The whole of the framework reaches banking from 31 March 2027",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2027-03-31",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-21. This record states a rule that takes effect after the corpus snapshot, which is why it reads as a future dated provision rather than the rule in force today.",
      "updated": "2026-09-21"
    },
    {
      "date": "2027-09-17",
      "kind": "replaced_by",
      "uid": "us-ach:rule.limits-the-same-day-ach-ceiling-today",
      "rail": "us-ach",
      "name": "The Same Day ACH ceiling today",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        },
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2022-03-18",
      "effective_to": "2027-09-17",
      "successor": {
        "uid": "us-ach:rule.limits-the-ceiling-that-is-coming",
        "name": "The ceiling that is coming",
        "effective_since": "2027-09-17",
        "status": "corroborated"
      },
      "note": "Split out of us-ach:limits by the 2026-09 Orca Core migration; no rule change identified. effective_since is the fact's. The line's successor takes effect 2027-09-17.",
      "updated": "2026-09-19"
    },
    {
      "date": "2028-03-17",
      "kind": "takes_effect",
      "uid": "us-ach:R90",
      "rail": "us-ach",
      "name": "Entry returned due to RDFI's sanctions compliance obligations",
      "record_url": "data/records/us-ach/R90.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "url": "https://www.nacha.org/rules/new-return-reason-code-sanctions-compliance-obligations",
          "class": "public_primary",
          "checked_on": "2026-09-17"
        }
      ],
      "effective_since": "2028-03-17",
      "effective_to": null,
      "successor": null,
      "note": "Approved 2025-10-14; in force 2028-03-17; pending at snapshot 2026-09-17",
      "updated": "2026-09-19"
    },
    {
      "date": "2028-03-17",
      "kind": "takes_effect",
      "uid": "us-ach:rule.decision-points-whether-an-entry-breaches-sanctions-obligations",
      "rail": "us-ach",
      "name": "Whether an entry breaches sanctions obligations",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2028-03-17",
      "effective_to": null,
      "successor": null,
      "note": "Split out of us-ach:decision-points by the 2026-09 Orca Core migration; no rule change identified. The line itself dates this from 2028-03-17.",
      "updated": "2026-09-19"
    },
    {
      "date": "2028-03-17",
      "kind": "takes_effect",
      "uid": "us-ach:rule.return-a-new-return-code-with-its-own-window-is-dated",
      "rail": "us-ach",
      "name": "A new return code with its own window is dated",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2028-03-17",
      "effective_to": null,
      "successor": null,
      "note": "Split out of us-ach:return by the 2026-09 Orca Core migration; no rule change identified. The line itself dates this from 2028-03-17.",
      "updated": "2026-09-19"
    },
    {
      "date": "2028-03-17",
      "kind": "takes_effect",
      "uid": "us-ach:rule.return-window-sanctions-determination",
      "rail": "us-ach",
      "name": "Return window for a sanctions compliance return: 2 banking days from the determination",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-17"
        }
      ],
      "effective_since": "2028-03-17",
      "effective_to": null,
      "successor": null,
      "note": "Approved 2025-10-14 with R90; in force 2028-03-17, per us-ach:R90.",
      "updated": "2026-09-22"
    }
  ],
  "mentioned": [
    {
      "date": "2026-09-30",
      "kind": "mentioned",
      "uid": "rtp:participants",
      "rail": "rtp",
      "name": "Who can be on this rail, in what roles, and who cannot?",
      "record_url": "data/records/rtp/participants.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "The roles and restrictions cited are present in the edition effective 2026-06-01. The participant count is as TCH published it for August 2026, read 2026-09-17, and moves continuously. Editions effective 2026-09-30 and 2026-10-04 add indirect domestic send and on line originator arrangements and were not read [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md].",
      "updated": "2026-09-18",
      "read_from": "Editions effective 2026-09-30 and 2026-10-04 add indirect domestic send and on line originator arrangements and were not read [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md]."
    },
    {
      "date": "2026-10-01",
      "kind": "mentioned",
      "uid": "mastercard:limits",
      "rail": "mastercard",
      "name": "What amount and usage limits apply to a Mastercard payment?",
      "record_url": "data/records/mastercard/limits.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/transaction-processing-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2026-06-09",
      "effective_to": null,
      "successor": null,
      "note": "2026-06-09 is the date of the Transaction Processing Rules edition that states these limits, not the date each began; the edition removed past effective dates. The Mastercard Rules edition read is 2026-06-02. Latin America and the Caribbean Stand-In floors extend to eleven more countries on 2026-10-01.",
      "updated": "2026-09-19",
      "read_from": "Latin America and the Caribbean Stand-In floors extend to eleven more countries on 2026-10-01."
    },
    {
      "date": "2026-10-01",
      "kind": "mentioned",
      "uid": "pix:consumer-law",
      "rail": "pix",
      "name": "What protects an end user on Pix, and where does the rulebook stop?",
      "record_url": "data/records/pix/consumer-law.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2024-11-01",
      "effective_to": null,
      "successor": null,
      "note": "The user experience article dates from the original 2020 Regulamento and gained its Pix Automatico journeys through Resolucao BCB n. 402/2024. The limit protections come from IN BCB n. 512/2024, published 2024-09-03, substantially rewritten by IN BCB n. 669 de 29/9/2025 and amended again from 2025-12-01 and 2026-10-01. The complaint driven funds recovery is newer still, from Resolucao BCB n. 493 de 28/8/2025. Confidence is medium rather than high because the two documents that would carry the customer facing detail, the Requisitos Minimos manual and the Manual de Resolucao de Disputas, were not read, and because no Brazilian consumer statute was consulted.",
      "updated": "2026-09-22",
      "read_from": "669 de 29/9/2025 and amended again from 2025-12-01 and 2026-10-01."
    },
    {
      "date": "2026-10-01",
      "kind": "mentioned",
      "uid": "pix:limits",
      "rail": "pix",
      "name": "What limits apply to a Pix, and who sets them?",
      "record_url": "data/records/pix/limits.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Instrução%20Normativa%20BCB&numero=512",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-09-29",
      "effective_to": null,
      "successor": null,
      "note": "The night limit figure of R$1,000.00 has been in IN BCB n. 512/2024 since publication on 2024-09-03, but the article that now carries it was rewritten by IN BCB n. 669 de 29/9/2025, which also revoked the TED peg for day limits and added the risk profile criteria. The contactless articles took effect 2025-12-01; IN BCB n. 746/2026 rewrites art. 10 par. 2 and art. 12 caput and revokes arts. 16-A and 16-C from 2026-10-01, which will supersede the contactless detail line. The R$15,000.00 PSTI cap came in with Resolucao BCB n. 496 de 5/9/2025. Limits move faster than anything else on this rail; treat any figure older than a quarter as suspect.",
      "updated": "2026-09-22",
      "read_from": "16-A and 16-C from 2026-10-01, which will supersede the contactless detail line."
    },
    {
      "date": "2026-10-04",
      "kind": "mentioned",
      "uid": "rtp:participants",
      "rail": "rtp",
      "name": "Who can be on this rail, in what roles, and who cannot?",
      "record_url": "data/records/rtp/participants.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "The roles and restrictions cited are present in the edition effective 2026-06-01. The participant count is as TCH published it for August 2026, read 2026-09-17, and moves continuously. Editions effective 2026-09-30 and 2026-10-04 add indirect domestic send and on line originator arrangements and were not read [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md].",
      "updated": "2026-09-18",
      "read_from": "Editions effective 2026-09-30 and 2026-10-04 add indirect domestic send and on line originator arrangements and were not read [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md]."
    },
    {
      "date": "2026-10-23",
      "kind": "mentioned",
      "uid": "mastercard:finality",
      "rail": "mastercard",
      "name": "When is a Mastercard card payment final, and what can still undo it?",
      "record_url": "data/records/mastercard/finality.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/transaction-processing-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/chargebacks-made-simple-guide.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current editions; start not stated in them",
      "effective_to": null,
      "successor": null,
      "note": "Rules as stated in the Mastercard Rules of 2 June 2026, the Transaction Processing Rules of 9 June 2026, the Security Rules and Procedures Merchant Edition of 4 August 2026, the Quick Reference Booklet of 2 June 2026 and the Chargebacks Made Simple Guide of July 2025, as downloaded from Mastercard's public rules page on 2026-09-19. New editions drop past effective dates, so when a rule began is often not shown. Mastercard reissues its manuals on no fixed calendar and announces changes on Mastercard Connect first [Inference]. From 2026-10-23 an issuer must be ready to use the Transaction Link Identifier in a disputed merchant-initiated transaction to tie it to the earlier transaction when deciding chargeback liability (Transaction Processing Rules rule 2.18).",
      "updated": "2026-09-19",
      "read_from": "From 2026-10-23 an issuer must be ready to use the Transaction Link Identifier in a disputed merchant-initiated transaction to tie it to the earlier transaction when deciding chargeback liability (Transaction Processing Rules rule 2.18)."
    },
    {
      "date": "2026-10-23",
      "kind": "mentioned",
      "uid": "mastercard:messages",
      "rail": "mastercard",
      "name": "Which messages and fields carry a Mastercard payment and its outcome?",
      "record_url": "data/records/mastercard/messages.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/transaction-processing-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/chargebacks-made-simple-guide.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current editions; start not stated in them",
      "effective_to": null,
      "successor": null,
      "note": "Rules as stated in the Mastercard Rules of 2 June 2026, the Transaction Processing Rules of 9 June 2026, the Security Rules and Procedures Merchant Edition of 4 August 2026, the Quick Reference Booklet of 2 June 2026 and the Chargebacks Made Simple Guide of July 2025, as downloaded from Mastercard's public rules page on 2026-09-19. New editions drop past effective dates, so when a rule began is often not shown. Mastercard reissues its manuals on no fixed calendar and announces changes on Mastercard Connect first [Inference]. From 2026-10-23 acquirers must send the original TLID in DE 105 subelement 002 on related merchant-initiated transactions (Transaction Processing Rules rule 2.1).",
      "updated": "2026-09-19",
      "read_from": "From 2026-10-23 acquirers must send the original TLID in DE 105 subelement 002 on related merchant-initiated transactions (Transaction Processing Rules rule 2.1)."
    },
    {
      "date": "2026-10-23",
      "kind": "mentioned",
      "uid": "mastercard:return",
      "rail": "mastercard",
      "name": "Can a Mastercard payment be sent back, and how does a chargeback work?",
      "record_url": "data/records/mastercard/return.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/chargebacks-made-simple-guide.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current editions; start not stated in them",
      "effective_to": null,
      "successor": null,
      "note": "Rules as stated in the Mastercard Rules of 2 June 2026, the Transaction Processing Rules of 9 June 2026, the Security Rules and Procedures Merchant Edition of 4 August 2026, the Quick Reference Booklet of 2 June 2026 and the Chargebacks Made Simple Guide of July 2025, as downloaded from Mastercard's public rules page on 2026-09-19. New editions drop past effective dates, so when a rule began is often not shown. Mastercard reissues its manuals on no fixed calendar and announces changes on Mastercard Connect first [Inference]. The Transaction Link Identifier duty for disputed merchant-initiated transactions takes effect 2026-10-23.",
      "updated": "2026-09-19",
      "read_from": "The Transaction Link Identifier duty for disputed merchant-initiated transactions takes effect 2026-10-23."
    },
    {
      "date": "2026-10-24",
      "kind": "mentioned",
      "uid": "visa-dispute:10.4",
      "rail": "visa-dispute",
      "name": "Other Fraud – Card-Absent Environment",
      "record_url": "data/records/visa-dispute/10.4.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current edition; start not stated in it",
      "effective_to": null,
      "successor": null,
      "note": "Rules as in the 18 April 2026 edition (ID# 0030254 and 0030257 last updated Apr 2026). Known dated changes, by the date a dispute is processed: from 2026-10-24 the history match widens: the earlier transactions may be at one or more merchants on the same card or a credential linked to it, the 120 days count back from when the dispute was submitted, login IDs for an Agentic Payment Provider count, a purchase order number may also stand in for the description on Visa Token Service (TAVV) and Visa Intelligent Data Exchange transactions with ECI 7, device ID and device fingerprint count as one element, and at pre-arbitration an Acquirer may submit only transaction data it accepted and processed; the widened rule does not apply in Chile. Also from 2026-10-24 the AVS result U rule moves from the UK alone to the whole Europe Region and starts for Argentina, Brazil, Mexico, Paraguay, Peru, Puerto Rico and Uruguay. From 2027-04-24 the AVS result U rule starts for Australia, New Zealand and Singapore. Under the dated-id procedure the watch renames this record 10.4@2026-10-24 and drafts a new 10.4 once the first change is in force, and repeats this for 2027-04-24.",
      "updated": "2026-09-19",
      "read_from": "Known dated changes, by the date a dispute is processed: from 2026-10-24 the history match widens: the earlier transactions may be at one or more merchants on the same card or a credential linked to it, the 120 days count back from when the dispute was submitted, login IDs for an Agentic Payment Provider count, a purchase order number may also stand in for the description on Visa Token Service (TAVV) and Visa Intelligent Data Exchange transactions with ECI 7, device ID and device fingerprint count as one element, and at pre-arbitration an Acquirer may submit only transaction data it accepted and processed;"
    },
    {
      "date": "2026-10-24",
      "kind": "mentioned",
      "uid": "visa-dispute:11.1",
      "rail": "visa-dispute",
      "name": "Card Recovery Bulletin",
      "record_url": "data/records/visa-dispute/11.1.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current edition; start not stated in it",
      "effective_to": null,
      "successor": null,
      "note": "Rules as in the 18 April 2026 edition; every 11.1 rule (ID# 0030261 to 0030264, last updated Oct 2025) is limited to disputes processed through 23 October 2026, and the edition names no replacement condition. Under the dated-id procedure the watch retires this record on 2026-10-24 (status superseded, superseded_by null).",
      "updated": "2026-09-19",
      "read_from": "Under the dated-id procedure the watch retires this record on 2026-10-24 (status superseded, superseded_by null)."
    },
    {
      "date": "2026-10-24",
      "kind": "mentioned",
      "uid": "visa:liability",
      "rail": "visa",
      "name": "Who bears the loss for fraud or error on a Visa card payment?",
      "record_url": "data/records/visa/liability.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Not dated in the edition read",
      "effective_to": null,
      "successor": null,
      "note": "Stated as the rules read in the 18 April 2026 edition; the rules cited carry their own last-updated months in their ID# footers. Visa publishes a new edition each April and October, and the next is expected in October 2026 [Inference from the edition pattern]. Known dated change: for disputes processed on or after 2026-10-24 the 10.4 compelling-evidence and AVS rules change (VR 11.7.5.3).",
      "updated": "2026-09-19",
      "read_from": "Known dated change: for disputes processed on or after 2026-10-24 the 10.4 compelling-evidence and AVS rules change (VR 11.7.5.3)."
    },
    {
      "date": "2026-10-24",
      "kind": "mentioned",
      "uid": "visa:return",
      "rail": "visa",
      "name": "How does a Visa card payment come back after settlement?",
      "record_url": "data/records/visa/return.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Not dated in the edition read",
      "effective_to": null,
      "successor": null,
      "note": "Stated as the rules read in the 18 April 2026 edition; the rules cited carry their own last-updated months in their ID# footers. Visa publishes a new edition each April and October, and the next is expected in October 2026 [Inference from the edition pattern]. Known dated changes: for disputes processed on or after 2026-10-24, the 10.4 compelling-evidence rule widens and condition 11.1 is retired (VR 11.7.5.3, ID# 0030254; 11.8.1). On 2027-04-24 a further 10.4 change starts for Australia, New Zealand and Singapore (VR 11.7.5.3).",
      "updated": "2026-09-19",
      "read_from": "Known dated changes: for disputes processed on or after 2026-10-24, the 10.4 compelling-evidence rule widens and condition 11.1 is retired (VR 11.7.5.3, ID# 0030254;"
    },
    {
      "date": "2026-10-25",
      "kind": "mentioned",
      "uid": "pix-reject:RR06",
      "rail": "pix-reject",
      "name": "Tax Information Invalid",
      "record_url": "data/records/pix-reject/RR06.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/cedsfn/Catalogos/spi.5.12.1.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-28",
      "effective_to": null,
      "successor": null,
      "note": "Added in catalog 5.12.1, published 2026-03-27 (release notes); SPI production 2026-06-28 (BCB Comunicação eletrônica de dados page, Comunicado 44.424). Catalog 5.13.1 changes the comment from 2026-10-25 (see caveat); supersession is due on or after that date.",
      "updated": "2026-09-21",
      "read_from": "Catalog 5.13.1 changes the comment from 2026-10-25 (see caveat);"
    },
    {
      "date": "2026-10-25",
      "kind": "mentioned",
      "uid": "pix:messages",
      "rail": "pix",
      "name": "What messages carry a Pix, and what is not a message at all?",
      "record_url": "data/records/pix/messages.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/cedsfn/Catalogos/Catalogo_de_Servicos_do_SFN_Volume_VI_Versao_512.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2026-06-28",
      "effective_to": null,
      "successor": null,
      "note": "Catalog 5.12.1 has been in SPI production since 2026-06-28 and is the version this record describes. Catalog 5.13.1 was published 2026-07-24 and enters production 2026-10-25, adding DS02 and DU03 to the pacs.002 rejection reasons and removing nine Pix Automatico codes; the pacs.004 return reasons are unchanged between the two. On 2026-10-25 this record needs a new version, not an edit.",
      "updated": "2026-09-22",
      "read_from": "Catalog 5.13.1 was published 2026-07-24 and enters production 2026-10-25, adding DS02 and DU03 to the pacs.002 rejection reasons and removing nine Pix Automatico codes;"
    },
    {
      "date": "2026-10-26",
      "kind": "mentioned",
      "uid": "pix-return:BE08",
      "rail": "pix-return",
      "name": "BankError",
      "record_url": "data/records/pix-return/BE08.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/versoes_futuras/X_ManualOperacionaldoDICT-versao8-5.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-17"
        }
      ],
      "effective_since": "2026-09-01",
      "effective_to": null,
      "successor": null,
      "note": "Date DICT manual 8.5, the MED text used here, took effect; its revision history lists no change to section 17.1 against 8.4 [Inference: section 17.1 is unchanged]. The operational failure exclusion in Reg. art. 41-B section 3 dates from Res. BCB 403/2024; the MED itself took effect on 2021-11-16 (Res. BCB 103/2021). The 48 hour indicator was added to the Manual de Tempos in the 2026-02-02 revision of version 7.0. Code list per SPI catalog 5.12.1; 5.13.1 leaves the pacs.004 codes unchanged. A further 8.5 change on 2026-10-26 touches infraction notices only.",
      "updated": "2026-09-17",
      "read_from": "A further 8.5 change on 2026-10-26 touches infraction notices only."
    },
    {
      "date": "2026-10-26",
      "kind": "mentioned",
      "uid": "pix:recall",
      "rail": "pix",
      "name": "Can the payer's side pull a Pix back, and what does asking actually do?",
      "record_url": "data/records/pix/recall.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2026-09-01",
      "effective_to": null,
      "successor": null,
      "note": "The MED itself dates from Resolucao BCB n. 103 de 8/6/2021, in force from 2021-11-01 with effects from 2021-11-16, and was reshaped into the Recuperacao de Valores by Resolucao BCB n. 493 de 28/8/2025 with art. 78-N. The 80 day window for contesting a return took effect 2026-09-01 with Manual Operacional do DICT 8.5; version 8.4, still at the manual's main URL, says 30 days. A further tranche of 8.5 takes effect 2026-10-26, adding the graph depth attribute to the infraction notice. Art. 41-D par. 1 gains a new wording on 2026-07-01 under Resolucao BCB n. 559/2026 and art. 41-G is revoked on the same date.",
      "updated": "2026-09-22",
      "read_from": "A further tranche of 8.5 takes effect 2026-10-26, adding the graph depth attribute to the infraction notice."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip-reject:ED06",
      "rail": "ch-sic-ip-reject",
      "name": "SIC IP cancelled a transfer out of SIC IP",
      "record_url": "data/records/ch-sic-ip-reject/ED06.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/5-3/ig-module-docs-sic-ip-2026-5.3-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "Listed in the edition in force since release 5.2; first listing not established",
      "effective_to": null,
      "successor": null,
      "note": "Listed as a CNC002 reason in IP-pacs.002 v2.3 (2025-02-28), in force since 2025-11-21 with SIC platform release 5.2; which edition first listed it was not established. Withdrawn from 2026-11-13: IP-pacs.002 v2.4 (2026-02-27), valid from that date with release 5.3, removes ED06 (change history, CR2026-SIC-0005; section 4.3). Not superseded yet: the monthly watch retires this record once 2026-11-13 has passed.",
      "updated": "2026-09-18",
      "read_from": "Withdrawn from 2026-11-13: IP-pacs.002 v2.4 (2026-02-27), valid from that date with release 5.3, removes ED06 (change history, CR2026-SIC-0005;"
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:decision-points",
      "rail": "ch-sic-ip",
      "name": "Where in a SIC instant payment does a bank or a person decide the outcome, rather than the system?",
      "record_url": "data/records/ch-sic-ip/decision-points.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 5.2 guidelines cited took effect; the provisions carry over into release 5.3 on 2026-11-13. The facet caps at medium confidence because the reading of provisions as decision points is Orca's.",
      "updated": "2026-09-18",
      "read_from": "the provisions carry over into release 5.3 on 2026-11-13."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:finality",
      "rail": "ch-sic-ip",
      "name": "When does a SIC instant payment become final, and can it be reversed?",
      "record_url": "data/records/ch-sic-ip/finality.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when release 5.2 of the SIC IP guidelines took effect; [Inference: the reserve, feedback and settle cycle has applied since the service started, which the SNB report places in November 2023.] Release 5.3 on 2026-11-13 brings IP Status Report v2.4, which restricts cancellation messages to customer payments and does not change this cycle.",
      "updated": "2026-09-18",
      "read_from": "[Inference: the reserve, feedback and settle cycle has applied since the service started, which the SNB report places in November 2023.] Release 5.3 on 2026-11-13 brings IP Status Report v2.4, which restricts cancellation messages to customer payments and does not change this cycle."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:liability",
      "rail": "ch-sic-ip",
      "name": "Who bears the loss when something goes wrong with a SIC instant payment?",
      "record_url": "data/records/ch-sic-ip/liability.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 5.2 guidelines cited took effect; the ED05 definition was corrected to 'despite a positive IP feedback' in IP Status Report v2.3 for that release. Release 5.3 on 2026-11-13 brings IP Status Report v2.4, which limits cancellation messages to customer payments.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 on 2026-11-13 brings IP Status Report v2.4, which limits cancellation messages to customer payments."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:limits",
      "rail": "ch-sic-ip",
      "name": "What amount limits apply to a SIC instant payment?",
      "record_url": "data/records/ch-sic-ip/limits.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2024/publications0_en/sicsystem_disclosure_2024.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 5.2 guidelines cited took effect. The CHF 20,000 limit has no public start date: it is stated as current in the SNB disclosure report editions published in September 2025 and May 2026. Release 5.3 on 2026-11-13 brings IP Customer Payments v2.3 with the same amount element; the SNB report is the watch input for any change to the limit.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 on 2026-11-13 brings IP Customer Payments v2.3 with the same amount element;"
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:messages",
      "rail": "ch-sic-ip",
      "name": "Which messages does the SIC IP service use, and on which standard?",
      "record_url": "data/records/ch-sic-ip/messages.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when release 5.2 of the SIC IP guidelines took effect. Release 5.3 applies from 2026-11-13 with the same ISO versions and new guideline editions for pacs.002 (v2.4), pacs.004 (v2.4) and pacs.008 (v2.3). The move to 2024/2025 ISO versions is announced for November 2027 without a day.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 applies from 2026-11-13 with the same ISO versions and new guideline editions for pacs.002 (v2.4), pacs.004 (v2.4) and pacs.008 (v2.3)."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic-ip:refund",
      "rail": "ch-sic-ip",
      "name": "Does the SIC IP service give a payer any right to a refund?",
      "record_url": "data/records/ch-sic-ip/refund.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-ip-2025-5.2-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 5.2 guidelines cited took effect; release 5.3 on 2026-11-13 adds no refund process.",
      "updated": "2026-09-18",
      "read_from": "release 5.3 on 2026-11-13 adds no refund process."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:decision-points",
      "rail": "ch-sic",
      "name": "Where in a SIC RTGS payment does a bank or a person decide the outcome, rather than the system?",
      "record_url": "data/records/ch-sic/decision-points.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/dam/jcr:76cdd7c1-828e-47eb-8d5f-d580fdc1881e/sicgiro_access_2023.en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 4.12 guidelines cited took effect. Release 5.3 on 2026-11-13 migrates the RTGS service to SIC5 with minor process changes described only in an extranet document. The facet caps at medium confidence because the reading of provisions as decision points is Orca's.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 on 2026-11-13 migrates the RTGS service to SIC5 with minor process changes described only in an extranet document."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:finality",
      "rail": "ch-sic",
      "name": "When does a payment in the SIC RTGS service become final, and can it be reversed?",
      "record_url": "data/records/ch-sic/finality.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is the date the release 4.12 interbank guidelines cited here took effect; it is not the date SIC finality was first defined, which the public sources do not give. National Bank Ordinance art. 25a has had its current wording since 1 January 2016. Release 5.3 on 2026-11-13 moves the RTGS service to the SIC5 platform; the release notes (v1.3, dated 21 September 2026) describe no change to the finality point, but the process changes are in an extranet document that was not read.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 on 2026-11-13 moves the RTGS service to the SIC5 platform;"
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:hours",
      "rail": "ch-sic",
      "name": "When is the SIC RTGS service open, and how does its clearing day run?",
      "record_url": "data/records/ch-sic/hours.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2024/publications0_en/sicsystem_disclosure_2024.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 4.12 guidelines cited took effect. The SNB dates weekend opening to April 2025 without a day. The clearing stops and clearing day structure are older and their start is not dated in public sources. Release 5.3 on 2026-11-13 moves the RTGS service to the SIC5 platform; the release notes do not announce new operating times.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 on 2026-11-13 moves the RTGS service to the SIC5 platform;"
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:liability",
      "rail": "ch-sic",
      "name": "Who bears the loss when something goes wrong with a SIC RTGS payment?",
      "record_url": "data/records/ch-sic/liability.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when Base Document v2.5 took effect. In Base Document v2.7, in force from 2026-11-13, the same disclaimers sit in sections 2.1, 3.3, 3.4 and 3.5.",
      "updated": "2026-09-18",
      "read_from": "In Base Document v2.7, in force from 2026-11-13, the same disclaimers sit in sections 2.1, 3.3, 3.4 and 3.5."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:messages",
      "rail": "ch-sic",
      "name": "Which messages does the SIC RTGS service use, and on which standard?",
      "record_url": "data/records/ch-sic/messages.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when release 4.12 of the interbank guidelines took effect. Release 5.3 takes effect on 2026-11-13 with the same ISO message versions. A move to the ISO 20022 2024/2025 versions is announced for November 2027; the exact date is not yet published.",
      "updated": "2026-09-18",
      "read_from": "Release 5.3 takes effect on 2026-11-13 with the same ISO message versions."
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:recall",
      "rail": "ch-sic",
      "name": "Can the sending bank stop or recall a SIC RTGS payment?",
      "record_url": "data/records/ch-sic/recall.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-module-docs-sic-rtgs-2025-4.12-en.zip",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 4.12 guidelines cited took effect. From 2026-11-13 (release 5.3) the cancellation guideline is camt.008 v2.2; the return request and rejection guidelines (camt.056 v2.4, camt.029 v2.3) stay the same versions.",
      "updated": "2026-09-18",
      "read_from": "From 2026-11-13 (release 5.3) the cancellation guideline is camt.008 v2.2;"
    },
    {
      "date": "2026-11-13",
      "kind": "mentioned",
      "uid": "ch-sic:settlement",
      "rail": "ch-sic",
      "name": "How and in what money does the SIC RTGS service settle, and what happens when a sender lacks funds?",
      "record_url": "data/records/ch-sic/settlement.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 4.12 guidelines cited took effect, not when these settlement features began, which the public sources do not date. In Base Document v2.7, in force from 2026-11-13 with release 5.3, the split rule moves to section 3.5 with the same content. Release 5.3 also migrates the RTGS service to the SIC5 platform; the release notes say some processes change to a minor extent and put the detail in an extranet document that was not read.",
      "updated": "2026-09-18",
      "read_from": "In Base Document v2.7, in force from 2026-11-13 with release 5.3, the split rule moves to section 3.5 with the same content."
    },
    {
      "date": "2026-11-14",
      "kind": "mentioned",
      "uid": "ch-sic-ip:consumer-law",
      "rail": "ch-sic-ip",
      "name": "What consumer protections apply to a SIC instant payment?",
      "record_url": "data/records/ch-sic-ip/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sps/business-rules-sps-2026-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is the start of the SIC release in force when this was drafted. The duty for retail participants to be able to receive instant payments applies by November 2026 at the latest per the SNB instruction sheet; the SNB report's first chapter of its disclosure part says by the end of 2026. The Business Rules v3.3 cited take effect on 2026-11-14.",
      "updated": "2026-09-18",
      "read_from": "The Business Rules v3.3 cited take effect on 2026-11-14."
    },
    {
      "date": "2026-11-14",
      "kind": "mentioned",
      "uid": "ch-sic:consumer-law",
      "rail": "ch-sic",
      "name": "What consumer protections apply to a payment that settles in the SIC RTGS service?",
      "record_url": "data/records/ch-sic/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.fedlex.admin.ch/eli/cc/27/317_321_377/en",
          "class": "secondary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sps/business-rules-sps-2026-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is the start of the SIC release in force when this was drafted; the legal provisions cited are older. Code of Obligations art. 470 para. 2bis has applied since 1 October 2009. The Business Rules v3.3 cited take effect on 2026-11-14.",
      "updated": "2026-09-18",
      "read_from": "The Business Rules v3.3 cited take effect on 2026-11-14."
    },
    {
      "date": "2026-11-14",
      "kind": "mentioned",
      "uid": "ch-sic:limits",
      "rail": "ch-sic",
      "name": "What amount limits apply to a payment in the SIC RTGS service?",
      "record_url": "data/records/ch-sic/limits.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.six-group.com/dam/download/banking-services/standardization/sic-eurosic/4-12-5-2/ig-base-document-ch-interbank-2025-en.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.snb.ch/public/asset/en/www-snb-ch/publications/sicsystem-disclosure/sicsystem-disclosure-all/sicsystem_disclosure_2025/publications0_en/sic_disclosure_2025.en.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "2025-11-21 is when the release 4.12 guidelines stating the field ceiling and the split rule took effect; neither rule's first introduction is dated in public sources. In Base Document v2.7, in force from 2026-11-13 with release 5.3, the split rule moves to section 3.5 unchanged in substance. The Business Rules v3.3 cited apply from 2026-11-14; the edition in force before then was not read.",
      "updated": "2026-09-18",
      "read_from": "The Business Rules v3.3 cited apply from 2026-11-14;"
    },
    {
      "date": "2026-11-15",
      "kind": "mentioned",
      "uid": "nct-inst:messages",
      "rail": "nct-inst",
      "name": "Which messages carry an NCT Inst payment and its exceptions, and whose rules govern them?",
      "record_url": "data/records/nct-inst/messages.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2025-11-21",
      "effective_to": null,
      "successor": null,
      "note": "Inter-PSP IG 2025 v1.1 issued and effective 2025-11-21 with rulebook 2025 v1.1; the reason code guidance in force is v3.1 of 2026-07-03. The unstructured address format ends on 2026-11-15. The 2027 rulebook and IGs are due for publication in November 2026.",
      "updated": "2026-09-18",
      "read_from": "The unstructured address format ends on 2026-11-15."
    },
    {
      "date": "2026-12-14",
      "kind": "mentioned",
      "uid": "mx-spei:consumer-law",
      "rail": "mx-spei",
      "name": "What must a SPEI participant tell its own customer, and what may it charge?",
      "record_url": "data/records/mx-spei/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.banxico.org.mx/marco-normativo/normativa-emitida-por-el-banco-de-mexico/circular-14-2017/%7BA06FBFEE-06BB-F249-32FC-25B334B2A744%7D.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-21"
        },
        {
          "url": "https://www.banxico.org.mx/marco-normativo/normativa-emitida-por-el-banco-de-mexico/circular-14-2017/%7BFBF220A3-C5B8-268A-C57B-A00CD109BA63%7D.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-17",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-20 in Orca Core form. The date is the day the Diario Oficial de la Federación published Circular 9/2026, the newest source this fact rests on, which made the Guías part of the SPEI rules. Each Rule listed here carries its own date, and compliance with the Guías is due by 2026-12-14.",
      "updated": "2026-09-21",
      "read_from": "Each Rule listed here carries its own date, and compliance with the Guías is due by 2026-12-14."
    },
    {
      "date": "2026-12-14",
      "kind": "mentioned",
      "uid": "mx-spei:rule.datos-a-confirmar-antes-de-autorizar",
      "rail": "mx-spei",
      "name": "A confirmation screen must show five things before the customer authorises",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-17",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-20 in Orca Core form. The date is the day the Diario Oficial de la Federación published Circular 9/2026, which added the Guías to the Reglas and made them binding. Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date. So the obligation exists now and the interface it requires is due by 2026-12-14.",
      "updated": "2026-09-21",
      "read_from": "Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date."
    },
    {
      "date": "2026-12-14",
      "kind": "mentioned",
      "uid": "mx-spei:rule.datos-en-la-notificacion-del-resultado",
      "rail": "mx-spei",
      "name": "The result screen must carry the status, the Clave de Rastreo and a link to the CEP",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-17",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-20 in Orca Core form. The date is the day the Diario Oficial de la Federación published Circular 9/2026, which added the Guías to the Reglas and made them binding. Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date. So the obligation exists now and the interface it requires is due by 2026-12-14.",
      "updated": "2026-09-21",
      "read_from": "Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date."
    },
    {
      "date": "2026-12-14",
      "kind": "mentioned",
      "uid": "mx-spei:rule.guias-de-homologacion-obligatorias",
      "rail": "mx-spei",
      "name": "The Guías are part of the SPEI rules and the mobile interface must follow them",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        },
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-17",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-20 in Orca Core form. The date is the day the Diario Oficial de la Federación published Circular 9/2026, which added the Guías to the Reglas and made them binding. Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date. So the obligation exists now and the interface it requires is due by 2026-12-14.",
      "updated": "2026-09-21",
      "read_from": "Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date."
    },
    {
      "date": "2026-12-14",
      "kind": "mentioned",
      "uid": "mx-spei:rule.nombre-del-participante-receptor-desde-el-identificador",
      "rail": "mx-spei",
      "name": "The screen must show the receiving participant derived from the account identifier",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "checked_on": "2026-09-21"
        }
      ],
      "effective_since": "2026-06-17",
      "effective_to": null,
      "successor": null,
      "note": "Drafted 2026-09-20 in Orca Core form. The date is the day the Diario Oficial de la Federación published Circular 9/2026, which added the Guías to the Reglas and made them binding. Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date. So the obligation exists now and the interface it requires is due by 2026-12-14.",
      "updated": "2026-09-21",
      "read_from": "Participants and the indirect participants they contract with have until 2026-12-14 to comply, under the second transitorio of that circular, and version 1.1 of the Guías itself takes effect on the same date."
    },
    {
      "date": "2027-01-01",
      "kind": "mentioned",
      "uid": "us-ach:messages",
      "rail": "us-ach",
      "name": "What message format does the rail use, and what travels with a payment?",
      "record_url": "data/records/us-ach/messages.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.nacha.org/rules/currently-accepted-characters-ach-network",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.frbservices.org/binaries/content/assets/crsocms/resources/rules-regulations/010526-operating-circular-4.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "The file format is long-standing and no source read here dates it. Two dated changes touch this facet: standard company entry descriptions from 2026-03-20, and the documented character table from 2027-01-01.",
      "updated": "2026-09-19",
      "read_from": "Two dated changes touch this facet: standard company entry descriptions from 2026-03-20, and the documented character table from 2027-01-01."
    },
    {
      "date": "2027-01-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:consumer-law",
      "rail": "sepa-sct-inst",
      "name": "What consumer law applies, and what does it give a consumer that the rules do not?",
      "record_url": "data/records/sepa-sct-inst/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC004-16%202025%20SCT%20Instant%20Rulebook%20v1.1.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-03/EPC218-23%20v1.1%202026%20Verification%20Of%20Payee%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-05/EPC103-24%20v1.1.1%20VOP%20API%20Specifications.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2024-10/EPC288-23%20v1.0%20EPC%20Recommendations%20for%20the%20Matching%20Processes%20under%20the%20VOP%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02012R0260-20240408",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/eli/dir/2015/2366/oj",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-09-20",
      "effective_to": null,
      "successor": null,
      "note": "The payee check lines rest on the 2026 Verification Of Payee rulebook v1.1 and API specification v1.1.1, both effective 2026-09-20 at 03:30 CET, which is why the record as a whole is dated from then; the matching recommendations are v1.0 of 2024-10-10 and can change outside the rulebook cycle. The 2025 SCT Inst rulebook was issued and took effect on 2025-10-05, four days before the 2025-10-09 deadline for euro area banks to offer sending instant credit transfers and to run verification of payee. The charges rule bound euro area banks, and the sanctions screening regime every bank offering instant transfers, from 2025-01-09. Banks outside the euro area follow between 2027-01-09 and 2028-06-09 depending on the obligation. The successor payment services package was not read for this record, so what may change is [Unverified].",
      "updated": "2026-09-24",
      "read_from": "Banks outside the euro area follow between 2027-01-09 and 2028-06-09 depending on the obligation."
    },
    {
      "date": "2027-01-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:refund",
      "rail": "sepa-sct-inst",
      "name": "Does anyone have a right to be refunded, and on what grounds?",
      "record_url": "data/records/sepa-sct-inst/refund.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2025-10-05",
      "effective_to": null,
      "successor": null,
      "note": "The 2025 SCT Inst rulebook was issued and took effect on 2025-10-05 and has never contained a refund process. The verification of payee duties and the charges rule came from Regulation (EU) 2024/886: the charges rule binds euro area PSPs from 2025-01-09 and PSPs elsewhere from 2027-01-09, and verification of payee binds euro area PSPs from 2025-10-09 and PSPs elsewhere from 2027-07-09. The Directive's refund provisions date from the 2015 Directive as transposed nationally; national transposition was not checked for this record.",
      "updated": "2026-09-18",
      "read_from": "The verification of payee duties and the charges rule came from Regulation (EU) 2024/886: the charges rule binds euro area PSPs from 2025-01-09 and PSPs elsewhere from 2027-01-09, and verification of payee binds euro area PSPs from 2025-10-09 and PSPs elsewhere from 2027-07-09."
    },
    {
      "date": "2027-01-13",
      "kind": "mentioned",
      "uid": "mastercard:consumer-law",
      "rail": "mastercard",
      "name": "How do Mastercard's rules relate to consumer protection law?",
      "record_url": "data/records/mastercard/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/transaction-processing-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current editions; start not stated in them",
      "effective_to": null,
      "successor": null,
      "note": "Rules as stated in the Mastercard Rules of 2 June 2026, the Transaction Processing Rules of 9 June 2026, the Security Rules and Procedures Merchant Edition of 4 August 2026, the Quick Reference Booklet of 2 June 2026 and the Chargebacks Made Simple Guide of July 2025, as downloaded from Mastercard's public rules page on 2026-09-19. New editions drop past effective dates, so when a rule began is often not shown. Mastercard reissues its manuals on no fixed calendar and announces changes on Mastercard Connect first [Inference]. The Europe Region rule on unattended POS terminals that applies in SCA countries extends to Albania, Montenegro, North Macedonia and Serbia on 2027-01-13 (Transaction Processing Rules, Europe Region rule 4.10, pp. 186 to 187).",
      "updated": "2026-09-19",
      "read_from": "The Europe Region rule on unattended POS terminals that applies in SCA countries extends to Albania, Montenegro, North Macedonia and Serbia on 2027-01-13 (Transaction Processing Rules, Europe Region rule 4.10, pp."
    },
    {
      "date": "2027-03-01",
      "kind": "mentioned",
      "uid": "mastercard:settlement",
      "rail": "mastercard",
      "name": "How and when do Mastercard customers settle with each other?",
      "record_url": "data/records/mastercard/settlement.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-rules.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        },
        {
          "url": "https://www.mastercard.com/content/dam/mccom/shared/business/support/rules-pdfs/mastercard-quick-reference-booklet-merchant.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current editions; start not stated in them",
      "effective_to": null,
      "successor": null,
      "note": "Rules as stated in the Mastercard Rules of 2 June 2026, the Transaction Processing Rules of 9 June 2026, the Security Rules and Procedures Merchant Edition of 4 August 2026, the Quick Reference Booklet of 2 June 2026 and the Chargebacks Made Simple Guide of July 2025, as downloaded from Mastercard's public rules page on 2026-09-19. New editions drop past effective dates, so when a rule began is often not shown. Mastercard reissues its manuals on no fixed calendar and announces changes on Mastercard Connect first [Inference]. The Australian clearing change takes effect 2027-03-01.",
      "updated": "2026-09-19",
      "read_from": "The Australian clearing change takes effect 2027-03-01."
    },
    {
      "date": "2027-03-01",
      "kind": "mentioned",
      "uid": "rtp-return-request:UAPA",
      "rail": "rtp-return-request",
      "name": "Fraudulently induced payment",
      "record_url": "data/records/rtp-return-request/UAPA.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2026-03-31",
      "effective_to": "2026-09-30",
      "successor": null,
      "note": "UAPA fraud reporting required from 2026-03-31 (section 1.b). This record's statement stops applying 2026-09-30: from that date, under section 1.d.ii of the rules interpretation dated 2026-09-14, a Sending Participant of IDS Payments must also send UAPA for an IDS Payment found to have been fraudulently induced, whether the IDS Originating Institution passes that determination on or the Sending Participant reaches it through its own processes (note 8). UAPA stays in use with that wider scope; once the date has passed the RTP watch drafts the successor under the dated-id procedure in docs/watch.md. Later dates for the successor, not asserted by this record: the two business day reporting deadline (section 1.c) and OBO reporting (section 1.d.i), both 2027-03-01. Found by the RTP watch 2026-09-17; the end date was typed after a later reread of the interpretation (see basis).",
      "updated": "2026-09-26",
      "read_from": "Later dates for the successor, not asserted by this record: the two business day reporting deadline (section 1.c) and OBO reporting (section 1.d.i), both 2027-03-01."
    },
    {
      "date": "2027-03-01",
      "kind": "mentioned",
      "uid": "rtp:recall",
      "rail": "rtp",
      "name": "Can a sent payment be recalled, and who decides?",
      "record_url": "data/records/rtp/recall.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.theclearinghouse.org/-/media/New/TCH/Documents/Payment-Systems/RTP/RTP-Operating-Rules-Effective-June-1-2026pdf.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-17"
        },
        {
          "url": "https://www.theclearinghouse.org/-/media/New/TCH/Documents/Payment-Systems/RTP_Request_for_Returns_v02-19-2021.pdf",
          "class": "public_primary",
          "checked_on": "2026-09-17"
        }
      ],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "The provisions cited are present in the edition effective 2026-06-01. The ten banking day response deadline and the FRAD exemption are recorded in the 2019-11-18 rule change summary, as cited in Orca's rtp-return-request:FRAD entry [Unverified: that summary was not read for this record]. From 2027-03-01 fraud reports are to be sent within 2 business days of the fraud determination, which will change the request timing [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md].",
      "updated": "2026-09-18",
      "read_from": "From 2027-03-01 fraud reports are to be sent within 2 business days of the fraud determination, which will change the request timing [Unverified: from the watch log in Orca's RTP rail brief, docs/rails/rtp.md]."
    },
    {
      "date": "2027-04-24",
      "kind": "mentioned",
      "uid": "visa-decline:R1",
      "rail": "visa-decline",
      "name": "Revocation of authorization order",
      "record_url": "data/records/visa-decline/R1.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Not dated in the edition read",
      "effective_to": null,
      "successor": null,
      "note": "Listed in Table 7-2 of the 18 April 2026 edition; the table rule was last updated in April 2026 and gives no start date for this code. Visa publishes a new edition each April and October; the next is expected in October 2026 [Inference]. Known dated change: on 2027-04-24 an AP Region subscription control change revises codes R1 and R3 (Summary of Changes p. 52; VR 4.1.19.3, ID# 0031078).",
      "updated": "2026-09-19",
      "read_from": "Known dated change: on 2027-04-24 an AP Region subscription control change revises codes R1 and R3 (Summary of Changes p."
    },
    {
      "date": "2027-04-24",
      "kind": "mentioned",
      "uid": "visa-decline:R3",
      "rail": "visa-decline",
      "name": "Revocation of all authorizations order",
      "record_url": "data/records/visa-decline/R3.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Not dated in the edition read",
      "effective_to": null,
      "successor": null,
      "note": "Listed in Table 7-2 of the 18 April 2026 edition; the table rule was last updated in April 2026 and gives no start date for this code. Visa publishes a new edition each April and October; the next is expected in October 2026 [Inference]. Known dated change: on 2027-04-24 an AP Region subscription control change revises codes R1 and R3 (Summary of Changes p. 52; VR 4.1.19.3, ID# 0031078).",
      "updated": "2026-09-19",
      "read_from": "Known dated change: on 2027-04-24 an AP Region subscription control change revises codes R1 and R3 (Summary of Changes p."
    },
    {
      "date": "2027-04-24",
      "kind": "mentioned",
      "uid": "visa-dispute:10.4",
      "rail": "visa-dispute",
      "name": "Other Fraud – Card-Absent Environment",
      "record_url": "data/records/visa-dispute/10.4.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Before the current edition; start not stated in it",
      "effective_to": null,
      "successor": null,
      "note": "Rules as in the 18 April 2026 edition (ID# 0030254 and 0030257 last updated Apr 2026). Known dated changes, by the date a dispute is processed: from 2026-10-24 the history match widens: the earlier transactions may be at one or more merchants on the same card or a credential linked to it, the 120 days count back from when the dispute was submitted, login IDs for an Agentic Payment Provider count, a purchase order number may also stand in for the description on Visa Token Service (TAVV) and Visa Intelligent Data Exchange transactions with ECI 7, device ID and device fingerprint count as one element, and at pre-arbitration an Acquirer may submit only transaction data it accepted and processed; the widened rule does not apply in Chile. Also from 2026-10-24 the AVS result U rule moves from the UK alone to the whole Europe Region and starts for Argentina, Brazil, Mexico, Paraguay, Peru, Puerto Rico and Uruguay. From 2027-04-24 the AVS result U rule starts for Australia, New Zealand and Singapore. Under the dated-id procedure the watch renames this record 10.4@2026-10-24 and drafts a new 10.4 once the first change is in force, and repeats this for 2027-04-24.",
      "updated": "2026-09-19",
      "read_from": "From 2027-04-24 the AVS result U rule starts for Australia, New Zealand and Singapore."
    },
    {
      "date": "2027-04-24",
      "kind": "mentioned",
      "uid": "visa:return",
      "rail": "visa",
      "name": "How does a Visa card payment come back after settlement?",
      "record_url": "data/records/visa/return.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "Not dated in the edition read",
      "effective_to": null,
      "successor": null,
      "note": "Stated as the rules read in the 18 April 2026 edition; the rules cited carry their own last-updated months in their ID# footers. Visa publishes a new edition each April and October, and the next is expected in October 2026 [Inference from the edition pattern]. Known dated changes: for disputes processed on or after 2026-10-24, the 10.4 compelling-evidence rule widens and condition 11.1 is retired (VR 11.7.5.3, ID# 0030254; 11.8.1). On 2027-04-24 a further 10.4 change starts for Australia, New Zealand and Singapore (VR 11.7.5.3).",
      "updated": "2026-09-19",
      "read_from": "On 2027-04-24 a further 10.4 change starts for Australia, New Zealand and Singapore (VR 11.7.5.3)."
    },
    {
      "date": "2027-07-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:participants",
      "rail": "sepa-sct-inst",
      "name": "Who can be on this rail, in what roles, and who cannot?",
      "record_url": "data/records/sepa-sct-inst/participants.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC004-16%202025%20SCT%20Instant%20Rulebook%20v1.1.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC131-17%20v4.0%20Clarification%20Paper%20SCT%20and%20SCT%20Inst%20scheme%20rulebooks.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC122-16%20SCT%20Inst%20Inter-PSP%20IG%202025%20V1.0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-03/EPC218-23%20v1.1%202026%20Verification%20Of%20Payee%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02012R0260-20240408",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/eli/reg/2024/886/oj",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-09-20",
      "effective_to": null,
      "successor": null,
      "note": "The SCT Inst lines rest on the 2025 SCT Inst rulebook, issued and effective 2025-10-05, and on the 2025 inter-PSP guideline effective the same day. The payee check line rests partly on the 2026 Verification Of Payee rulebook v1.1, effective 2026-09-20 at 03:30 CET, which is why the record as a whole is dated from then. Annex IV records that sections 2.6 and 5.3 were rewritten in this edition to follow Article 5a(1) of the amended SEPA Regulation, and that the planned downtime wording follows Article 11(1c). The staged obligations in Article 5a(8) run from 2025-01-09 for euro area receiving through to 2027-07-09 for non-euro area sending, with a derogation for some non-euro area sending until 2028-06-09. The 2027 SCT Inst rulebook is due for publication in November 2026 and would supersede this record when it takes effect.",
      "updated": "2026-09-24",
      "read_from": "The staged obligations in Article 5a(8) run from 2025-01-09 for euro area receiving through to 2027-07-09 for non-euro area sending, with a derogation for some non-euro area sending until 2028-06-09."
    },
    {
      "date": "2027-07-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:refund",
      "rail": "sepa-sct-inst",
      "name": "Does anyone have a right to be refunded, and on what grounds?",
      "record_url": "data/records/sepa-sct-inst/refund.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2025-10-05",
      "effective_to": null,
      "successor": null,
      "note": "The 2025 SCT Inst rulebook was issued and took effect on 2025-10-05 and has never contained a refund process. The verification of payee duties and the charges rule came from Regulation (EU) 2024/886: the charges rule binds euro area PSPs from 2025-01-09 and PSPs elsewhere from 2027-01-09, and verification of payee binds euro area PSPs from 2025-10-09 and PSPs elsewhere from 2027-07-09. The Directive's refund provisions date from the 2015 Directive as transposed nationally; national transposition was not checked for this record.",
      "updated": "2026-09-18",
      "read_from": "The verification of payee duties and the charges rule came from Regulation (EU) 2024/886: the charges rule binds euro area PSPs from 2025-01-09 and PSPs elsewhere from 2027-01-09, and verification of payee binds euro area PSPs from 2025-10-09 and PSPs elsewhere from 2027-07-09."
    },
    {
      "date": "2027-07-09",
      "kind": "mentioned",
      "uid": "sepa-sct:refund",
      "rail": "sepa-sct",
      "name": "Does anyone have a right to be refunded, and on what grounds?",
      "record_url": "data/records/sepa-sct/refund.json",
      "effective_status": "draft",
      "stored_status": "draft",
      "source_class": null,
      "sources": [],
      "effective_since": "2025-10-05",
      "effective_to": null,
      "successor": null,
      "note": "The 2025 SCT rulebook was issued and took effect on 2025-10-05 and has never contained a refund process. The verification of payee refund duty in Article 5c(8) came from Regulation (EU) 2024/886 and binds PSPs in euro area Member States from 2025-10-09 and PSPs elsewhere from 2027-07-09. The Directive's refund provisions date from the 2015 Directive as transposed nationally; national transposition was not checked for this record.",
      "updated": "2026-09-18",
      "read_from": "The verification of payee refund duty in Article 5c(8) came from Regulation (EU) 2024/886 and binds PSPs in euro area Member States from 2025-10-09 and PSPs elsewhere from 2027-07-09."
    },
    {
      "date": "2027-09-17",
      "kind": "mentioned",
      "uid": "us-ach:limits",
      "rail": "us-ach",
      "name": "What amount limits apply, and who sets them?",
      "record_url": "data/records/us-ach/limits.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.nacha.org/rules/increasing-same-day-ach-dollar-limit-10-million-0",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.frbservices.org/binaries/content/assets/crsocms/resources/rules-regulations/010526-operating-circular-4.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2022-03-18",
      "effective_to": null,
      "successor": null,
      "note": "The $1,000,000 per payment limit has applied since 2022-03-18. A change is already dated: on 2027-09-17 the limit becomes $10,000,000, at which point this record should be superseded rather than edited. The values of the ARC, BOC, POP, RCK and XCK limits are not public.",
      "updated": "2026-09-19",
      "read_from": "A change is already dated: on 2027-09-17 the limit becomes $10,000,000, at which point this record should be superseded rather than edited."
    },
    {
      "date": "2028-03-17",
      "kind": "mentioned",
      "uid": "us-ach:decision-points",
      "rail": "us-ach",
      "name": "Where do the rules hand the outcome to a human or a bank?",
      "record_url": "data/records/us-ach/decision-points.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.frbservices.org/binaries/content/assets/crsocms/resources/rules-regulations/010526-operating-circular-4.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.nacha.org/rules/reversals-and-enforcement",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "Most of these provisions are long-standing in the sources read. Dated ones: the improper reversal return from 2021-06-30, fraud monitoring from 2026-03-20 and 2026-06-19, company entry descriptions from 2026-03-20, and the sanctions return decision from 2028-03-17.",
      "updated": "2026-09-20",
      "read_from": "Dated ones: the improper reversal return from 2021-06-30, fraud monitoring from 2026-03-20 and 2026-06-19, company entry descriptions from 2026-03-20, and the sanctions return decision from 2028-03-17."
    },
    {
      "date": "2028-03-17",
      "kind": "mentioned",
      "uid": "us-ach:return",
      "rail": "us-ach",
      "name": "How does an entry come back, and by when?",
      "record_url": "data/records/us-ach/return.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.nacha.org/rules/reversals-and-enforcement",
          "class": "public_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.frbservices.org/binaries/content/assets/crsocms/resources/rules-regulations/010526-operating-circular-4.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.cbsbank.com/wp-content/uploads/2025/03/ACH-Return-Reason-Codes.pdf",
          "class": "secondary",
          "checked_on": "2026-09-23"
        }
      ],
      "effective_since": "Long-standing",
      "effective_to": null,
      "successor": null,
      "note": "The 2 banking day and 60 calendar day windows are long-standing; no source read here dates their introduction, so that is [Unverified]. Two dated changes are ahead: R90 and the sanctions return time frame on 2028-03-17, with R16 narrowing to account frozen on the same date.",
      "updated": "2026-09-23",
      "read_from": "Two dated changes are ahead: R90 and the sanctions return time frame on 2028-03-17, with R16 narrowing to account frozen on the same date."
    },
    {
      "date": "2028-03-17",
      "kind": "mentioned",
      "uid": "us-ach:rule.iat-ofac-hold-before-posting",
      "rail": "us-ach",
      "name": "Holding a suspect IAT, funds availability, and the sanctions return",
      "record_url": "core.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "public_primary",
      "sources": [
        {
          "checked_on": "2026-09-19"
        }
      ],
      "effective_since": "2009-09-18",
      "effective_to": null,
      "successor": null,
      "note": "IAT rules in force since 2009-09-18, per Nacha's 2008 executive summary; no later change to this point identified in the sources read. The R16 to R90 split takes effect 2028-03-17.",
      "updated": "2026-09-19",
      "read_from": "The R16 to R90 split takes effect 2028-03-17."
    },
    {
      "date": "2028-06-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:consumer-law",
      "rail": "sepa-sct-inst",
      "name": "What consumer law applies, and what does it give a consumer that the rules do not?",
      "record_url": "data/records/sepa-sct-inst/consumer-law.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC004-16%202025%20SCT%20Instant%20Rulebook%20v1.1.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-03/EPC218-23%20v1.1%202026%20Verification%20Of%20Payee%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-05/EPC103-24%20v1.1.1%20VOP%20API%20Specifications.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2024-10/EPC288-23%20v1.0%20EPC%20Recommendations%20for%20the%20Matching%20Processes%20under%20the%20VOP%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02012R0260-20240408",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/eli/dir/2015/2366/oj",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-09-20",
      "effective_to": null,
      "successor": null,
      "note": "The payee check lines rest on the 2026 Verification Of Payee rulebook v1.1 and API specification v1.1.1, both effective 2026-09-20 at 03:30 CET, which is why the record as a whole is dated from then; the matching recommendations are v1.0 of 2024-10-10 and can change outside the rulebook cycle. The 2025 SCT Inst rulebook was issued and took effect on 2025-10-05, four days before the 2025-10-09 deadline for euro area banks to offer sending instant credit transfers and to run verification of payee. The charges rule bound euro area banks, and the sanctions screening regime every bank offering instant transfers, from 2025-01-09. Banks outside the euro area follow between 2027-01-09 and 2028-06-09 depending on the obligation. The successor payment services package was not read for this record, so what may change is [Unverified].",
      "updated": "2026-09-24",
      "read_from": "Banks outside the euro area follow between 2027-01-09 and 2028-06-09 depending on the obligation."
    },
    {
      "date": "2028-06-09",
      "kind": "mentioned",
      "uid": "sepa-sct-inst:participants",
      "rail": "sepa-sct-inst",
      "name": "Who can be on this rail, in what roles, and who cannot?",
      "record_url": "data/records/sepa-sct-inst/participants.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC004-16%202025%20SCT%20Instant%20Rulebook%20v1.1.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC131-17%20v4.0%20Clarification%20Paper%20SCT%20and%20SCT%20Inst%20scheme%20rulebooks.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2025-10/EPC122-16%20SCT%20Inst%20Inter-PSP%20IG%202025%20V1.0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-03/EPC218-23%20v1.1%202026%20Verification%20Of%20Payee%20Scheme%20Rulebook_0.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02012R0260-20240408",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        },
        {
          "url": "https://eur-lex.europa.eu/eli/reg/2024/886/oj",
          "class": "authoritative_primary",
          "checked_on": "2026-09-24"
        }
      ],
      "effective_since": "2026-09-20",
      "effective_to": null,
      "successor": null,
      "note": "The SCT Inst lines rest on the 2025 SCT Inst rulebook, issued and effective 2025-10-05, and on the 2025 inter-PSP guideline effective the same day. The payee check line rests partly on the 2026 Verification Of Payee rulebook v1.1, effective 2026-09-20 at 03:30 CET, which is why the record as a whole is dated from then. Annex IV records that sections 2.6 and 5.3 were rewritten in this edition to follow Article 5a(1) of the amended SEPA Regulation, and that the planned downtime wording follows Article 11(1c). The staged obligations in Article 5a(8) run from 2025-01-09 for euro area receiving through to 2027-07-09 for non-euro area sending, with a derogation for some non-euro area sending until 2028-06-09. The 2027 SCT Inst rulebook is due for publication in November 2026 and would supersede this record when it takes effect.",
      "updated": "2026-09-24",
      "read_from": "The staged obligations in Article 5a(8) run from 2025-01-09 for euro area receiving through to 2027-07-09 for non-euro area sending, with a derogation for some non-euro area sending until 2028-06-09."
    },
    {
      "date": "2028-06-30",
      "kind": "mentioned",
      "uid": "my-duitnow:participants",
      "rail": "my-duitnow",
      "name": "Who can be on this rail, in what roles, and who cannot?",
      "record_url": "data/records/my-duitnow/participants.json",
      "effective_status": "corroborated",
      "stored_status": "corroborated",
      "source_class": "authoritative_primary",
      "sources": [
        {
          "url": "https://www.bnm.gov.my/documents/20124/943361/pd_IFTF_June2026.pdf",
          "class": "authoritative_primary",
          "checked_on": "2026-09-18"
        }
      ],
      "effective_since": "2026-06-30",
      "effective_to": null,
      "successor": null,
      "note": "The IFTF took effect 2026-06-30 and superseded the Interoperable Credit Transfer Framework of 2019-12-23 (IFTF 4.1, 7.1). Paragraphs 9.3, 9.4, 9.7(b), 9.8, 9.11 and 9.12(b) run on the Appendix II timelines: proprietary QR networks close by 2028-06-30; cross-border duties start on a Nexus date BNM will announce.",
      "updated": "2026-09-18",
      "read_from": "Paragraphs 9.3, 9.4, 9.7(b), 9.8, 9.11 and 9.12(b) run on the Appendix II timelines: proprietary QR networks close by 2028-06-30;"
    }
  ],
  "passed": [],
  "expected": []
}