Paste a Corda linearState transaction output or Canton domain event JSON. The verifier decodes state machine transitions, validates settlement finality conditions, attempts WebCrypto signature verification, maps ISO 20022 fields (links to Tool 57), and checks iso20022Hash integrity (keccak256 vs SHA-256 format). Outputs a pass/fail report and AP2 JSON artifact. Settlement Verifier — not a block explorer.
Settlement Verifier vs block explorer: This tool validates settlement finality conditions for a specific transaction — it does not browse the full ledger. The distinction matters for compliance: you are verifying that a specific transaction has reached a final, irrevocable state under the applicable legal and technical framework.
Hash format critical difference: Fabric and Corda store trHash = SHA-256(canonicalXml) where canonicalXml is the W3C Canonical XML 1.1 representation of the pacs.008. Besu stores iso20022Hash = keccak256(canonicalXml). These are different hash functions — cross-platform verification requires recomputing the hash. This tool detects the format from the hash prefix and flags the algorithm mismatch risk.
WebCrypto verification: The tool uses the browser's native window.crypto.subtle.verify() API for signature verification where a public key and signature are present in the transaction JSON. This is a client-side cryptographic operation — no key material is transmitted anywhere.
Corda state machine: Valid terminal states for settlement are: Settled, SETTLED, FinalState. The verifier checks for these in the output state type. For Corda, the BFT Notary signature is the definitive finality signal.
Canton domain events: Canton settlement finality is established by the two-phase commit confirmation from the Global Synchronizer. The verifier checks for confirmationResult: "CONFIRMED" in the domain event payload.