Scope: self-assessment, not certification. This tool scores answers you declare about your own PSP. It is not an audit, not a Pay.UK or EPC scheme certification, and not a determination of scheme compliance: only Pay.UK and the EPC certify scheme participants. Every finding below is asserted from your own input, not independently verified. Rule citations are verified against the source publications as of 2026-07-18 and are re-stated with their document reference and date below: re-verify against the live Pay.UK and EPC publications before relying on this for a real readiness decision.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

1 · Scope

Your PSP's role

Scheme scope

2 · EPC Verification of Payee Rulebook EPC218-23 v1.1 · published 2026-03-16 · v1.1 effective 2026-09-20

Responding-PSP or requesting-PSP role formally scoped§ Scheme roles and obligations, EPC218-23 All four outcome codes implementedMatch / Close Match (returns payee name) / No Match / Verification Not Possible, EPC218-23 5-second maximum response time met, 1-second target pursuedEPC218-23 response-time requirement Reachable via an EPC-listed routing & verification mechanismEPC218-23 scheme infrastructure Own matching-algorithm governance documentedRulebook does not prescribe an algorithm; each responding PSP owns and governs its own v1.1 urgent-change amendments reviewed and appliedEPC218-23 v1.1, published 2026-03-16, effective 2026-09-20: re-check for further published change requests

3 · Pay.UK Confirmation of Payee: baseline obligations Live since April/July 2019 · PSR Feb 2022 Direction expanded scope

CoP requests answered (Group 1/2 responding-PSP obligation)PSR direction: Group 1 by 31 Oct 2023, Group 2 by 31 Oct 2024 CoP requests sent before payment initiation (requesting-PSP obligation)Original Pay.UK CoP standard, live since Jul 2019 All three baseline response types surfaced"Yes" / "No, please check" (close) / "No, the name is wrong": original Pay.UK CoP Customer-facing warning UX designed for non-match responsesPayer retains discretion to proceed after a non-match; friction must be genuine, not decorative CoP outcome retained per transaction for APP-fraud evidenceCoP status is evidence in Contingent Reimbursement Model / PSR reimbursement-claim assessments

4 · CoP enhancement track (pilot-stage, NOT yet a published mandatory Pay.UK standard) Industry-reported pilots, 2026 · verify against Pay.UK's own publication before use as compliance evidence

Multi-name / legal-entity-alias account matching supportedReported CoP-enhancement capability, PSP pilots 2026: not yet formally published by Pay.UK as of 2026-07-18 Richer mismatch metadata returned to the originator's screenReported CoP-enhancement capability, PSP pilots 2026: same publication caveat PSR 2026 reimbursement-regime review tracked internallyPSR review opened February 2026, reporting October 2026: may change CoP design requirements

CoP & VoP Scheme Readiness Self-Assessment