Compliance

IVMS101 Travel Rule.

Tenzro carries the FATF Travel Rule data envelope per the IVMS101 v1.1.0 schema natively. The envelope binds an originator, beneficiary, originating VASP, beneficiary VASP, and transfer data to every above-threshold transfer.

STATUS: Library + canonical-hash RPC live
CRATE: tenzro-identity
STABILITY: Stable
REFERENCE: IVMS101 v1.1.0 / TRP

Envelope

Four nested records carry the canonical IVMS101 shape: originator, beneficiary, originatingVasp, beneficiaryVasp, plus a transfer record holding asset CAIP-19, amount in smallest unit, ISO 8601 timestamp, and the on-chain transaction hash. All field labels match the FATF JSON spec so external compliance tooling ingests the JSON form without Tenzro-specific transforms.

Receipt binding

The on-chain receipt records only the binding hash + originating + beneficiary VASP DIDs + asset/amount summary. The full envelope stays off-chain (carried via TRP). PII never lands on-chain, but auditors get a tamper-evident proof that the receipt was bound to a specific envelope at issuance time.

RPC

POST https://rpc.tenzro.network
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tenzro_ivms101Hash",
  "params": { ...full IVMS101 envelope... }
}

ISO 20022 shim

A minimal Iso20022Message type captures the canonical MX headers needed to bind a TradFi instruction (pacs.008, pacs.009, etc.) to an on-chain settlement — including an optional cre_intent_calldata_hex set when the message arrived via the Chainlink Runtime Environment translator (the canonical SWIFT → on-chain path).

← All docs