OpenChainGraph Suite · CONTRACT A3

PSD3 Readiness, Consent Stress and VoP Match Rate

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.
Reading mode (RUNBOOK): Read these steps in this order. The readiness rubric is the programme-level question, the consent stress simulation is the availability question, and the match-rate analysis is the payee-matching question. Each step is supplied its own inputs; nothing is threaded between them.

PSD3 and PSR readiness rubric > consent-lifecycle stress simulation > batch payee name-match rate analysis. Three independent computations over an open-banking payment-initiation surface. The graph dates PSD3 readiness at 2027-06-01.

OpenChainGraph · 3 Steps compliance mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology: PSD3 and PSR Readiness → Consent Flow Stress → VoP Batch Match Rate
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Market Rationale
Buyer: open-banking product or compliance owner at an ASPSP, PISP or AISP planning the PSD3 and PSR transition
Forcing function: PSD3 and PSR access rights, TPP categorisation and fraud liability provisions, with EU transposition dated 2027-06-01 in the graph; PSD2 RTS availability obligations and EU Instant Payments Regulation verification of payee already in force
Chain Stages · 3 Steps
1 ROOT node
PSD3 / PSR Readiness Checker art-14-psd3-psr-readiness-checker
Six-domain PSD3 and PSR readiness scores with a prioritised gap table. Stage 1 of 3.
↓
2 D2 node
Open Banking Consent Flow Stress Simulator sim-07-open-banking-consent-flow-stress
Consent-lifecycle terminal-state distribution and the ASPSP availability compliance check. Stage 2 of 3.
↓
3 TERMINAL · D3 node
VoP Batch Match-Rate Analyser art-11-vop-batch-match-rate-analyser
Batch match, close-match and no-match counts with the resulting match rate at the declared strictness. Final stage.
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.

Ask your agent

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: What share of open-banking consent flows complete end to end, and does that clear the regulatory success threshold?
Run the AINumbers MCP tool `run_chain` with {"chain":"psd3-readiness-consent-vop"} and read `sim-07-open-banking-consent-flow-stress.success_rate`.
Re-run with `inputs` for `sim-07-open-banking-consent-flow-stress`, reusing the values that result echoed, with `pAuthFail` set to 0.01. 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/psd3-readiness-consent-vop.html