CapchaHere is a $250,000 wire.
A real interbank payment instruction — the kind that moves between banks thousands of times a day, formatted to the ISO 20022 standard the entire industry is migrating to.
Freeze it in time.
One click computes a cryptographic fingerprint of the exact message bytes — right here, in your browser, using the same SHA-256 algorithm banks and auditors already trust.
Now change one penny.
This is the whole point. Edit the amount below — anything, even a single digit — and watch what happens to the seal.
Change anything. A single penny. The record will catch you.
Prove it — without trusting us.
The proof doesn't live only on our servers. It's cryptographically signed and anchored outside our own control, so anyone — including someone who has never spoken to CapchaCloud — can check it independently.
Certificate — chain anchor
GET /api/v1/iso20022/isoev_b5dc…/certificate (public, no key)
- Anchored
- —
- TSA status
- —
- Block height
- —
- Vault hash
- —
- Message SHA-256
- —
Factset — signed statement
GET /api/v1/iso20022/isoev_b5dc…/factset (public, no key)
- Signed
- —
- Signer
- —
- Algorithm
- —
Signed by the operator key — verifiable by anyone, offline, against the published public key.
node examples/chain/verify-capchachain.mjs https://capchacloud.com
Runs on a laptop that has never talked to our servers. If CapchaCloud vanished tomorrow, this still verifies.
What this does not prove: a sealed record proves what was checked, when, and that it hasn't changed since. It does not vouch for the truth of the underlying claim — that the payment was authorized, that funds actually moved, or that either bank's internal ledger agrees. That honesty is the point.