Proof-of-funds & KYC/AML infrastructure.
Stage: Spec in progress · Standard: FATF Recommendation 16 (Travel Rule)-aligned
What this vertical does
A bank letter was built to answer one question: does this account hold this much money. It was never designed to answer the question a digital‑asset‑funded application actually raises: where did this money come from, transaction by transaction, over however many years it took to accumulate. ImmiCrypt's Compliance vertical generates that answer automatically — reconstructing a source‑of‑funds narrative from an applicant's on‑chain history, screening against global sanctions and PEP watchlists, and capturing Travel Rule‑compliant originator and beneficiary data — then packages all of it into the specific format each program's Citizenship or Residency Investment Unit requires.
Why the Travel Rule matters here specifically
Since the Financial Action Task Force extended Recommendation 16 to virtual assets in 2019, over fifty jurisdictions — including the EU under its Transfer of Funds Regulation, the UK, Singapore, and the US — now require originator and beneficiary data on transfers above a $1,000 / €1,000 threshold, the same way wire transfers have carried that data for decades. A CBI/RBI application funded by crypto that can't produce this data isn't just weak — in an increasing number of jurisdictions, it's non‑compliant with the same rule that already governs the receiving bank. ImmiCrypt builds this capture in at the point of intake, not bolted on after a government asks for it.
What the CIU-ready file actually contains
- Originator/beneficiary data captured per FATF Recommendation 16, above the $1,000 / €1,000 threshold
- Sanctions & PEP screening results against global watchlists, refreshed at each pipeline stage
- On-chain source-of-funds narrative — a reconstructed transaction history explaining asset origin, not just a balance snapshot
- Program-specific formatting — packaged to the exact documentation standard each CIU already requires, not a generic export
Where it sits in the pipeline
Compliance is the Verify stage of ImmiCrypt's four-stage pipeline (see Verify → Escrow → Convert → Settle) — nothing moves into Custody until this stage clears. It receives its jurisdiction target from Advisory and its output becomes the compliance record that travels with the application through Settlement.
Status today
This vertical is at the spec-in-progress stage — the documentation standard is being built against real CIU requirements, not finalized as a live compliance product yet. See our Terms & Disclaimer for the full picture, and request access if you're a CIU or adviser who wants a say in the spec.