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.
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