Five browser-based verify-only tools plus three ready-made workflows for permissioned-EVM shared-ledger settlement: mapping an ISO 20022 payment message to a contract call, linting a settlement contract against paired-or-revert and compliance-gate invariants, classifying an L2-to-L1 finality window, screening a transfer batch pre-commit, and attesting the off-chain orchestrator that decides commit or halt. Ties into the ISO 20022 messaging profile and the Besu/EVM-compatible settlement-rail concepts already covered on this site.
A permissioned, EVM-compatible settlement layer let banks move bank-issued tokenized deposits and settle interbank payment commitments using ISO 20022 messages, with cross-chain routing handled separately. None of these tools query that layer, submit a transaction to it, or move value. Every tool here operates on bytes you supply: an ISO 20022 message, a contract source or ABI, a finality-state snapshot, a transfer batch, or an orchestrator manifest. Where a field-binding table or contract shape has not been publicly published, the tool says so and marks its output draft-pinned rather than claiming conformance it cannot verify.