Interactive prototype. Sample wire data. The selective-disclosure proof (SHA3-256 field commitments, Merkle root, inclusion proofs) is computed live in your browser; the compliance verdicts are illustrative. It produces the portable H33-74 evidence (see the offline verifier demo).

New Wire Transfer MT103 / ISO 20022

Originator Name

Originator BIC

Originator Account

Originator Country

Beneficiary Name

Beneficiary BIC

Beneficiary Account

Beneficiary Country

Amount

Currency

Payment Reference

Enable Protected Validation

Validate compliance without exposing underlying data to intermediaries

■

Sanctions

Clear

■

Beneficiary

Verified

■

Jurisdiction

Permitted

■

Travel Rule

Complete

■

Risk Score

Low (0.12)

Zero plaintext transmitted. All fields validated in protected form. No raw data left the originating environment.

—

Validation Time (measured in your browser)

5/5

Signals Passed

—

Proof Size (this run)

3

Signatures

89%

Data Reduction

● Disclosed to Receiving Bank (5 fields)

Originator NameMeridian Capital Partners LLC

Originator BICMRDNUS33XXX

Beneficiary NameNextera Industrial GmbH

Amount$2,450,000.00

Payment RefINV-2026-04881

■ Withheld — Proven, Not Shared (5 fields)

Originator AccountProven valid

Originator AddressProven compliant

Beneficiary AccountProven valid

Risk AssessmentProven low-risk

Source of FundsProven legitimate

▾ Why withheld?

These fields are not required by the receiving bank for settlement under current EU Transfer of Funds Regulation (TFR) or FATF Travel Rule guidelines. Wire Proof validates each field locally and transmits only a cryptographic proof that the field meets compliance requirements — the actual data never leaves the originator's environment. The receiving bank is designed to check each proof without accessing the underlying value (not yet available in production).

Traditional Wire (SWIFT MT103)

✕ 47 data fields transmitted in plaintext

✕ Full account numbers exposed to intermediaries

✕ Beneficiary details visible at every hop

✕ Manual compliance review (4-8 hours)

✕ No cryptographic proof of validation

✕ Compliance evidence = screenshots + emails

Wire Proof (H33)

✓ 5 fields disclosed, remainder proven

✓ Accounts validated without exposure

✓ Beneficiary proven, not transmitted

✓ Automated validation, timed on the run you perform

✓ Cryptographic receipt designed for triple signing (full three-family production verification pending)

✓ Machine-verifiable compliance proof

47 → 5 fields

89% data reduction. Same compliance outcome.

Cryptographic Receipt ▾

Fields committed

—

Disclosed to the validating institution

—

Withheld — committed, never sent

—

Wire commitment (Merkle root, SHA3-256)

—

Inclusion proofs verified against the root

—

Proof size on the wire

—

Elapsed, measured in your browser

—

Per-field verification

—

Try to break it

Alter one disclosed value after the proof was built. Its commitment no longer reproduces, so its path stops reaching the root — which is the whole point of sending a proof instead of the payload.

Salts are fresh on every run, so the root changes each time even for an identical wire. Without them, an observer could confirm a guessed account number by hashing it. No post-quantum signature is produced here: this page demonstrates selective disclosure, and signing needs a key it has no business holding.

Transactions

841

Verified

4

Action Required

2

Blocked

847

Total

Reference	Counterparty	Amount	Status	Signals	Time

Showing 20 of 847 transactions

Verify Receipt Illustrative UX — this panel demonstrates the receiving-party flow.

Illustrative demonstration. This prototype shows the Wire Proof compliance UX with sample data; the verdict below illustrates the flow and does not run a real cryptographic check. To try sample receipts in your browser (public demo key; no issuer verification), use the offline verifier or the public verifier. Wire Proof produces the same portable H33-74 evidence those tools check.

✓

VALID illustrative

In production this is where receipt integrity, all three signatures, and the policy hash are confirmed. This panel illustrates that result; try sample receipts in the offline verifier.

Verification Details (illustrative)

Dilithium signature: Valid
FALCON signature: Valid
SLH-DSA signature: Valid
Policy hash: Matches
Timestamp: 2026-04-24T14:32:17.841Z

✕

INVALID

Receipt could not be verified. Signature mismatch or receipt not found in registry.

Active Policies

Sanctions Screening

All originator and beneficiary entities are screened against OFAC SDN, EU Consolidated, UN Security Council, and HMT sanctions lists. Screening is performed on protected data — names and identifiers are validated without being transmitted in plaintext.

Show policy hash

—

Beneficiary Verification

Beneficiary identity is validated against the receiving institution's records. For EU transfers, LEI or national identifier is required per Article 14 of Regulation (EU) 2023/1113. Verification result is proven without disclosing the identifier.

Show policy hash

—

Jurisdiction Controls

Originator and beneficiary jurisdictions are validated against the institution's permitted corridor list. Sanctioned jurisdictions (DPRK, Iran, Syria, Crimea) are blocked. High-risk jurisdictions trigger enhanced conditions.

Show policy hash

—

Travel Rule Compliance

Validates that originator and beneficiary information is present as described in FATF Recommendation 16. For transfers over $3,000 / EUR 1,000, full originator details must be available. Wire Proof confirms completeness without transmitting all fields.

Show policy hash

—

Risk Scoring

Composite risk score calculated from transaction amount, corridor risk, counterparty history, and pattern analysis. Score range 0.00 (lowest) to 1.00 (highest). Threshold: ≤0.30 auto-clear, 0.31-0.70 conditions, >0.70 blocked for review.

Show policy hash

—

Audit Timeline WP-2026-04-24-0882-MRDNUS33-NXTRDEFF

✓

Wire Initiated

2026-04-24T14:32:14.102Z

▸ Originating bank submitted MT103 payload with 47 fields

Meridian Capital Partners LLC initiated a USD 2,450,000.00 wire to Nextera Industrial GmbH (Germany). Standard MT103 format with full field set. Payment reference: INV-2026-04881.

✓

Protected Validation Started

2026-04-24T14:32:14.108Z

▸ 47 fields encoded for protected validation

All 47 MT103 fields were encoded in protected form within the originator's environment. No plaintext data left the originator boundary. Protected encoding completed in 0.4ms.

✓

Compliance Signals Evaluated

2026-04-24T14:32:17.312Z

▸ 5/5 signals passed: sanctions, beneficiary, jurisdiction, travel rule, risk

Sanctions screening: Clear (OFAC, EU, UN, HMT). Beneficiary verification: Confirmed against NXTRDEFFXXX records. Jurisdiction: US-DE corridor permitted. Travel Rule: All required originator/beneficiary fields present. Risk score: 0.12 (low).

✓

Disclosure Policy Applied

2026-04-24T14:32:17.318Z

▸ 5 fields disclosed, 42 fields proven without disclosure

Active policy (sha3-256:e4b2c9...) applied. Disclosed: originator name, originator BIC, beneficiary name, amount, payment reference. Withheld with proof: account numbers, addresses, risk assessments, source of funds, and 37 additional MT103 fields.

✓

Commitment Produced

2026-04-24T14:32:17.841Z

▸ Merkle root over 47 salted field commitments (not signed on this page)

A wire commitment is produced: a Merkle root over 47 salted SHA3-256 field commitments. The five policy-required fields travel with inclusion paths; the other 42 stay behind. No signature is produced on this page — it demonstrates selective disclosure, and signing would need a key it has no business holding. The elapsed time shown is the run you performed.

→

Send Simulated — Not Transmitted

2026-04-24T14:32:17.845Z

▸ No payment network is connected; nothing was queued or settled

This demo stops at the proof. No wire is submitted to SWIFT or any other network, and there is no settlement. In a live deployment the receiving bank (NXTRDEFFXXX) would receive the 5 disclosed fields with their inclusion paths and the commitment root (independent verification not yet available in production).

H33 Wire Proof — Compliance Compression for Cross-Border Payments

● Disclosed to Receiving Bank (5 fields)

■ Withheld — Proven, Not Shared (5 fields)

Traditional Wire (SWIFT MT103)

Wire Proof (H33)