Two-node payments workflow producing the evidence a PSP presents in an APP-fraud reimbursement liability review. Stage 1 scores a declared payee-name match under a versioned algorithm. Stage 2 binds that match result, the warning text and severity shown, and the consumer's declared action into a signed, hash-chained session receipt: what the check found and what happened next, not who is at fault.
score_payee_name_match{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "score_payee_name_match",
"arguments": {
"account_name": "J Smith Consulting Ltd",
"reference_name": "James Smith Consulting Limited",
"match_threshold": 2,
"close_match_threshold": 5
}
},
"id": 1
}
build_vop_session_receipt{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "build_vop_session_receipt",
"arguments": {
"session_id": "SESS-2026-0718-0042",
"attempts": [
{
"attempt_id": "ATT-1",
"match_result": {
"source": "score_payee_name_match",
"algorithm_version": "vop-namematch-1.0.0",
"score": 4,
"match_band": "CLOSE_MATCH"
},
"warning_shown": {
"text": "The name on this account is a close, not exact, match to the name you entered.",
"severity": "warning"
},
"consumer_action": "proceeded",
"asserted_at": "2026-07-18T14:22:03Z"
}
]
}
},
"id": 2
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: A disputed instant payment is in front of us. Which name-match band did the payee verification actually record for the claim?
Run the AINumbers MCP tool `run_chain` with {"chain":"vop-liability-evidence"} and read `art-376-score-payee-name-match.match_band`.
Re-run with `inputs` for `art-376-score-payee-name-match`, reusing the values that result echoed, with `account_name` set to "Northwind Freight Solutions BV". Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/vop-liability-evidence.html