Cryptographic receipt authority for ISO 20022 financial messages

Name: Cryptographic receipt authority for ISO 20022 financial messages
Availability: InStock
Author: NextGenRails

by NextGenRails·May 3, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidNiche GemBig Brain

Zero-retention Merkle receipts for ISO 20022 messages solve a specific audit nightmare.

Strengths

•Zero-retention architecture ensures sensitive financial data is never stored on servers.
•Per-field SHA-384 hashing creates granular, tamper-evident audit trails.
•Standard JWS output allows verification with existing tools like jwt.io.

Weaknesses

•Extremely narrow audience limited to institutions migrating to ISO 20022 standards.
•Relies on external trust in the validator's public key for long-term verification.

Post Description

ISO 20022 is replacing SWIFT MT messages globally. FedNow, TARGET2, and SEPA are all mid-migration. Financial institutions are processing these messages and logging them internally — but a log entry is a claim, not proof. 20022Validator issues SHA-384 hashed, Merkle-committed, RS256 signed JWS receipts for ISO 20022 JSON messages. Zero retention — the message is never stored. The receipt is independently verifiable against a published public key at any time using jwt.io or token.dev. Supported message types: pain.001, pain.002, pain.008, camt.052, camt.053, camt.054, pacs.002, pacs.003, pacs.008, pacs.009 and more. The core argument: an ISO 20022 message without independent validation is just a file. A cryptographically signed receipt is evidence. White paper: https://drive.google.com/file/d/1ge9cukaYM2sQzJYmDQHNL3Zp0sa...