OpenChainGraph Suite · CONTRACT A3 · arch #5

Open Banking API Lifecycle

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 (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. The API explorer, the VRP/SEPA validation, and the consent audit each check a separate fact and are combined into one composite mandate.

Open Banking API explorer > VRP mandate/SEPA validation > consent compliance audit — composite open banking API lifecycle mandate.

OpenChainGraph · 3 Steps compliance mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Open Banking Api Explorer → Vrp Mandate Sepa Validator → Consent Compliance Auditor
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Market Rationale
Buyer: Open Banking API Product Manager / TPP Developer
Forcing function: PSD2 SCA-RTS mandate ongoing; FIDA preparation 2026; UK OBL OBIE transition to JROC
Live Execution

This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:

▶ Run this chain in your browser
Chain Stages · 3 Steps
1 ROOT · D0 catalog
Open Banking Api Explorer 10-open-banking-api-explorer
api_capabilities and endpoint_coverage feed Stage 2 VRP/SEPA mandate validation
↓
2 D2 catalog
Vrp Mandate Sepa Validator 11-vrp-mandate-sepa-validator
vrp_mandate_terms and sepa_compliance feed Stage 3 consent compliance audit
↓
3 TERMINAL · D3 catalog
Consent Compliance Auditor 03-consent-compliance-auditor
consent_obligations and compliance_gaps — final open banking API mandate
▶ Run this chain (live) browser · real execution · composite §4 hash
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.