Cari Interbank Deposit Transfer
Instant deposit transfer between consortium banks on a shared ledger. Huntington customer → KeyCorp customer in seconds, not hours. ZK proofs verify balances without exposing customer data — the "Glass Vault" model.
Step 1 · Originating Customer Initiates TransferPolicy-Enforced
"A retail customer initiating a Zelle transfer — the bank's online banking surface accepts the instruction and the bank's compliance program runs the screening before any value moves."
The originating customer (a Huntington DDA holder, in the canonical example) initiates a transfer via the Huntington online banking interface. The destination is identified by Cari party-id — analogous to a routing+account number, but on the Prividium party-model rather than ABA/account number.
Identity is inherited from Huntington's CIP file — no new attestation. The originating bank's BSA/AML pipeline runs at this step: structuring detection, velocity heuristics, OFAC re-screen on the originating customer (which the bank does as part of its standard ongoing-monitoring program).
L4 ACCOUNT (customer wallet eligibility) and L5 APPLICATION (bank online banking + BSA/AML pipeline) lit, both policy-enforced bank-side controls. The originating bank holds the regulatory perimeter for its customer; the receiving bank will hold its own customer's perimeter symmetrically.
Step 2 · Originating Bank Authorization + Sanctions Re-ScreenMixed EnforcementINGESTDETECTALERT
"A bank's wire-room sanctions screen plus the receiving-side correspondent-bank's onboarding check — except both legs collapse into a single shared-ledger gate because the participating banks have pre-attested each other's BSA programs at consortium join."
The originating bank's wire-room runs the outbound sanctions screen against OFAC SDN, EU Consolidated, UK HMT, and any bank-specific lists. The receiving bank's identity is implicitly vetted because all consortium members completed the Cari Network onboarding — bank-bank counterparty risk is pre-cleared at consortium-join time, not per-transaction.
The on-chain Cari transfer contract enforces that both originator wallet and destination party-id are on the consortium-allowlist; sanctions screening on the destination party-id happens code-side via Cari's sanctions oracle [typically Chainalysis OFAC Oracle adapted for Prividium party-ids — VERIFY exact vendor and contract address].
L3 EXECUTION (oracle + allowlist contract) and L5 APPLICATION (bank wire-room) lit. Mixed enforcement: bank-side wire-room is policy-enforced, oracle and allowlist gate are code-enforced.
Step 3 · Glass Vault — ZK Balance & Authorization ProofCode-EnforcedINGESTDETECTALERT
"A SWIFT settlement message that proves funds are reserved without exposing the originating customer's account history — the cryptographic equivalent of a confirmed-good-funds advice."
The Cari transfer contract generates a ZK-balance-proof: a cryptographic attestation that the originating wallet holds at least the transfer amount, that the originating bank has authorized the transfer, and that the transfer amount falls within all programmatic ceilings — without revealing the originating customer's identity, full balance, or account history to the receiving bank.
The receiving bank consumes the proof as confirmed-good-funds-advice and is willing to credit its customer's wallet on that basis. The receiving bank sees the destination party-id (its own customer) in clear and the token amount in clear; it does NOT see the originating customer's identity, balance, or transaction memo.
L3 EXECUTION lit, code-enforced. The proof system [PLONK or Groth16 — VERIFY] is the structural primitive that enables bank-grade counterparty privacy at the consortium layer while preserving each bank's internal BSA/AML visibility into its own customer.
Step 4 · Atomic Settlement — On-Ledger TransferCode-Enforced
"A Fedwire transfer that completes in seconds rather than the multi-hour Fedwire window — the value moves atomically with finality on the shared ledger."
The Cari transfer contract executes the atomic settlement: the originating customer's wallet is debited and the receiving customer's wallet is credited in a single Prividium transaction. Both legs commit together or both revert.
Originating bank's GL posts a memo debit against the originating DDA; receiving bank's GL posts a memo credit against the receiving DDA — both legs reconcile end-of-business-day per Cari operational rules. The deposit liability moves between member banks at the GL level; the on-chain token movement is the canonical record of the transfer.
L1 NETWORK · L2 CONSENSUS · L3 EXECUTION · L4 ACCOUNT all lit. Settlement is final on Prividium consensus in under 2 seconds — orders of magnitude faster than ACH (T+1 or T+2) and Fedwire (within Fed business hours only).
Step 5 · Receiving Bank Compliance InheritancePolicy-EnforcedINGESTDETECTALERT
"A correspondent bank's inbound-wire screening — the receiving bank treats the credit as if it had received a SWIFT MT103 with confirmed-good-funds."
Once the on-chain settlement clears, the receiving bank runs its standard inbound-funds compliance against its own customer: structuring detection, velocity heuristics, beneficial-ownership re-attestation if the credit triggers a re-attestation threshold, and Travel Rule data acceptance for credits above $3,000.
Travel Rule data is encoded in the Cari transfer payload as a structured field per FinCEN-compatible IVMS101 packaging [VERIFY exact field schema]. The receiving bank's compliance program ingests this structured data and feeds it into the receiving-side monitoring pipeline.
L5 APPLICATION lit, policy-enforced. The receiving bank holds the BSA/AML perimeter for its customer going forward; any subsequent filing obligations (SAR, CTR) attach to the receiving bank under its own program.
Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.
Coverage notes: 5 disclosed gap(s).
Tokenized Deposit Network Map
Visual map of tokenized-deposit networks — Cari Network, RLN, JPM Onyx — alongside major stablecoin issuers, with participants, chain infrastructure, privacy model, and rollout status.