OpenChainGraph Suite · ART-376 · VoP / CoP liability evidence
Payee Name-Match Score (VoP/CoP)
Scores one declared payee name pair — the name held on the receiving account against the name the payer declares — using a versioned, deterministic algorithm: normalization (diacritic stripping, legal-entity suffix removal), then integer Levenshtein edit distance on both a plain and a token-sorted form, scaled to an integer 0–100 score. The point is declared determinism: “score 87, algorithm v1.0.0” is reproducible evidence, unlike a black-box vendor match score. algorithm_version is carried in both the manifest and the receipt below.
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope & fences
This tool attests the COMPUTATION on the two names it is given — not ground-truth identity, and not what a PSP's own UI actually displayed to a consumer (that assertion is bound separately, in the VE-2 session receipt). Transliteration across scripts (e.g. Cyrillic → Latin) is explicitly out of scope — non-Latin characters are stripped by normalization, not converted, so a cross-script pair correctly scores NO_MATCH rather than silently guessing. Distinct from the batch aggregate tool art-11 VoP Batch Match-Rate Analyser, which reports match-rate statistics over a payee list; this node scores one declared pair with a declared algorithm_version for evidentiary binding.