UK Faster Payments (FPS) — payment-authority governance
UK Faster Payments (FPS) — payment-authority governance — 80% of in-scope requirements covered.
7 requirements · 5 in scope (3 enforced · 2 designed) · 2 out-of-scope (outside KYE™’s authority layer). The 80% is weighted over the in-scope base.
Source: The UK Faster Payment System (operated by Pay.UK) processes near-real-time retail payments that are irrevocable once accepted, settled by deferred multilateral net settlement across prefunded accounts at the Bank of England under net sender caps, with participation as directly connected settling / non-settling participants or indirect access via sponsors and aggregators, and — since October 2024 — a PSR-mandated APP-scam reimbursement requirement operated through the FPS reimbursement rules. KYE Protocol™ governs the PAYMENT-AUTHORITY dimension: whether an instruction (human- or AI-agent-originated) carries a live, purpose-scoped mandate, with the verdict and evidence sealed BEFORE the irrevocable acceptance moment, and a replay-verifiable authorisation evidence trail for APP-scam claim investigations. KYE™ does not process payments, effect settlement, manage liquidity or adjudicate reimbursement claims. · License: The FPS scheme rules are Pay.UK's own publications and the reimbursement requirement is the Payment Systems Regulator's; the KYE™ registry paraphrases each requirement's intent and cites the scheme/regulator for mapping purposes only. No scheme text is reproduced.
By category
| Category | Reqs | Enforced | Designed | Advisory | Deferred | Coverage |
|---|---|---|---|---|---|---|
| Participation, access criteria & authorised-user binding | 1 | 1 | 0 | 0 | 0 | 100% |
| Irrevocability & pre-submission authority checkpoint | 1 | 1 | 0 | 0 | 0 | 100% |
| Messaging integrity & record retention | 1 | 1 | 0 | 0 | 0 | 100% |
| APP-fraud reimbursement & authorisation evidence | 1 | 0 | 1 | 0 | 0 | 50% |
| Operational resilience & incident reporting | 1 | 0 | 1 | 0 | 0 | 50% |
| Scheme processing & settlement execution | 1 | 0 | 0 | 0 | 0 | 0% |
| Liquidity provision & net sender caps | 1 | 0 | 0 | 0 | 0 | 0% |
Every requirement → the KYE™ artefact that enforces it
| ID | Title | Status | KYE™ enforcement |
|---|---|---|---|
uk-fps.participant-access-authority | Payment instructions are submitted only by admitted participants (directly connected settling / non-settling participants, or indirect access via a sponsor or aggregator) through authorised users acting under a recorded, in-force mandate (FPS Rules access & participation criteria) | enforced | audit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1, kye.compliance.attestation.v1engines: internal, internalrule_packs: kye:rule-pack:paymentssector_packs: kye:sector-pack:financial-services, kye:sector-pack:uk-financial-services-sm-crconstitution_refs: constitution/12-PURPOSE-PERMISSION.md |
uk-fps.pre-submission-authority-checkpoint | Because a Faster Payment is processed in near real time and is irrevocable once accepted by the scheme, the authority verdict and its evidence must be complete BEFORE the instruction is submitted — there is no recall window to correct an unauthorised agent action | enforced | audit_events: kye.purpose.admissibility.v1, kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.replay.proof.v1engines: internal, internalrule_packs: kye:rule-pack:paymentsconstitution_refs: constitution/13-RESILIENCE-LOOP.md |
uk-fps.message-integrity-records | Faster Payment messages must be traceable and participants must retain adequate records of submitted payments and their authorisation for audit, dispute and reimbursement-investigation purposes | enforced | audit_events: kye.evidence.pack.v1, kye.evidence.tool_call.v1, kye.audit_retention_policy.v1engines: internalconstitution_refs: constitution/30-AUDIT-WORM-RETENTION.md |
uk-fps.app-fraud-reimbursement-evidence | Under the APP-scam reimbursement rules for Faster Payments (PSR mandatory reimbursement requirement, in force October 2024), sending and receiving PSPs need a defensible evidence trail of who or what authorised the payment, the consent context, and the fraud-assessment steps taken | designed | audit_events: kye.evidence.pack.v1, kye.evidence.decision_map.v1, kye.replay.proof.v1rule_packs: kye:rule-pack:paymentsconstitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/30-AUDIT-WORM-RETENTION.md |
uk-fps.operational-resilience-incident | Participants must meet the scheme's operational-resilience and availability expectations and report incidents affecting their FPS connection to the scheme operator and, where applicable, their regulators | designed | audit_events: kye.compliance.attestation.v1, kye.evidence.pack.v1constitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/34-RECONCILIATION-ENGINE.md |
uk-fps.scheme-processing-settlement | Scheme acceptance and near-real-time processing of payments, deferred multilateral net settlement across accounts at the Bank of England, and the legal conferral of irrevocability on accepted payments | out-of-scope | (no enforcement cited) |
uk-fps.liquidity-net-sender-caps | Prefunding of settlement accounts, management of net sender caps, and intraday liquidity monitoring against the participant's cap | out-of-scope | (no enforcement cited) |
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.