🔄 VASPS · EXCHANGES · PAYMENT PROVIDERS

Prove every qualifying transfer carried complete originator and beneficiary data.

The FATF Travel Rule requires that qualifying virtual asset transfers carry originator and beneficiary information end to end. Demonstrating that to a supervisor normally means handing over transaction records — the exact data the rule exists to protect. VeraZK proves completeness across the entire transfer set: that every qualifying transfer carried the required fields, with no transfer skipped and no record exposed.

Book a Free Pilot → See a Live Proof

FATFVARAMASFINMA

The Problem

Why the current approach forces a trade-off.

The obligation and the disclosure it demands are two separate things. Today they are bundled together — and that bundling is a choice, not a requirement.

Sampling cannot prove completeness

A supervisor reviewing a sample learns something about the sample. The obligation is about every qualifying transfer, and the gap between those two statements is where enforcement action lives.

Demonstrating compliance means disclosing customers

Producing transfer records to prove they were complete exposes originator and beneficiary identities to a party that has no need for them — an obligation in tension with data-protection duties.

Thresholds and scope differ by jurisdiction

The qualifying threshold, the required fields, and the treatment of unhosted wallets vary across FATF, GCC, EU, Swiss, and Asia-Pacific implementations.

Evaluation exposure is concentrated

MENAFATF and equivalent mutual evaluations examine implementation depth. A demonstrable completeness proof is a materially stronger position than a sampled review.

How It Works

From your data to an independently verified proof.

The same four-step process used across every VeraZK service, configured for this proof type.

Configure Your Service

Select the proof service you need, map your data sources, and define the rules your data must satisfy. Configuration is declarative — a manifest file, not custom code.

Your Data Stays Inside Your Infrastructure

The VeraZK engine runs entirely within your own systems. Customer identifiers are irreversibly anonymised inside your hardware before any computation begins. Raw data never leaves your trust boundary.

The Proof is Generated

A post-quantum proof is computed over your data — proving the required properties without embedding any raw data in the output. The bundle is compact, tamper-evident, and carries a complete signed audit trail.

Anyone Can Verify — Independently

The regulator, your auditor, your counterparty, or any member of the public runs the verifier against the proof bundle. Verification requires no account and no call to our systems.

What This Service Does

Travel Rule Compliance in practice.

Completeness proof for FATF Travel Rule records

Covers originator, beneficiary, and intermediary data

Per-transaction or batch compliance attestation

GCC, EU, Swiss, and Asia-Pacific travel rule requirements

What We Guarantee

Properties of the proof system, not promises about us.

🔒 The proof cannot be forged

Producing a false proof that passes verification is computationally impossible — even for the institution that generated it. A mathematical property, not a policy.

👁️ Zero data exposure

No customer record, transaction amount, balance, or proprietary data point appears in any proof bundle. Exposure is zero by construction.

🌐 Anyone can verify

The verifier requires no account, no licence, and no contact with us. Any regulator or auditor reaches the same result independently.

🛡️ Post-quantum secure

Resistant to both classical and quantum attack. No trusted setup ceremony, no shared secrets, no single point of trust.

🔗 Tamper-evident audit trail

Every stage of the pipeline produces a signed, chained record. Tampering between stages is cryptographically detectable.

⚡ Verification in seconds

Any proof can be verified in seconds on a standard laptop. No cloud infrastructure, no specialised hardware, no GPU.

Regulatory Fit

Configured to how each regime defines the obligation.

International — FATFRecommendation 16 sets the originator and beneficiary information requirements that national regimes implement.

UAE — VARATravel-rule obligations apply to licensed VASPs, with supervisory attention on implementation completeness rather than policy existence.

Singapore — MASPSN02 travel-rule requirements apply to digital payment token services.

Switzerland — FINMAThe revised AMLA framework carries travel-rule expectations for Swiss VASPs, with MROS as the reporting channel.

FAQ

Questions specific to this service.

What does a completeness proof actually assert?+

That every record in the submitted set satisfied the required-field predicate — not that a sample did. The proof binds to the whole partition, so a transfer cannot be silently excluded from the set being proven over.

Can this run per transaction, or only in batches?+

Both. Per-transaction attestation and periodic batch proofs use the same circuit; the choice is a cadence decision driven by your supervisor's expectations, not a technical constraint.

Does the regulator learn who the customers are?+

No. The proof carries the assertion about field completeness. Originator and beneficiary identities remain with the parties who are required to hold them.

How are differing national thresholds handled?+

The qualifying threshold is a configured parameter rather than a hard-coded value, so the same circuit answers whichever national implementation applies to you.

Get Started

See a real proof, on your own infrastructure.

One day. No charge. No commitment. Your team runs the verifier before the session ends.

Book a Free Pilot Workshop →