TIP-20's TransferWithMemo carries a 32-byte memo that the docs prescribe using as a hash-or-locator commitment for larger or PII-bearing off-chain payloads. This validator checks the memo's length/hex form and, when you supply the off-chain payload or an invoice ID, recomputes the SHA-256 commitment and reports whether it matches. Integrity-only — distinct from the AML/Travel Rule batch screener.
32-Byte Memo Form CheckSHA-256 Commitment RecomputeInvoice-Locator Template Match
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
⚠ Integrity check only, NOT an AML/sanctions screener (see art-38 for that). Verifies whether a claimed memo commitment matches its supplied preimage — nothing more.
Memo & commitment inputs
Memo (64 hex chars / 32 bytes)
Off-chain payload (optional — recompute commitment over this text)
Invoice ID (optional — checked against the locator template below)