Cari Intraday Liquidity Sweep
Automated 24/7/365 treasury balance optimization across consortium banks. Programmatic sweeps move tokenized deposits to where liquidity is needed — bypassing Fedwire windows entirely.
Step 1 · Sweep Policy Setup (Corporate Authorization)Policy-Enforced
"A corporate treasury team configuring zero-balance-account sweep rules with their bank — except the rules now span multiple consortium banks and execute around the clock."
The corporate treasurer defines the sweep policy in the originating bank's commercial portal: target balance per participating account, source/destination prioritization, time-of-day constraints (or 24/7 enablement), regulatory-window exclusions, and per-cycle programmatic ceilings.
Regulatory-window exclusions are operationally important — for example, public-company treasurers may pause sweeps in the final hour before a 10b-5 disclosure event so that automated treasury movements do not coincide with material non-public information windows.
L4 ACCOUNT (corporate wallet authorization) and L5 APPLICATION (corporate treasury policy + bank commercial portal) lit. The policy is encoded as a Cari sweep-policy contract on Prividium; the corporate's signature gates the policy's activation. C16 (programmable compliance) attaches because the policy is the canonical artifact of machine-enforced treasury-policy in the Cari architecture.
Step 2 · Continuous Balance MonitoringCode-EnforcedINGESTDETECTALERT
"An automated cash-management system continuously polling account balances against target thresholds — except across multiple banks on a shared ledger rather than via per-bank API integrations."
The Cari sweep-monitor contract continuously evaluates participating-account balances against the policy thresholds. Evaluation cadence is sub-minute [VERIFY current Cari operational-rule polling interval].
When a participating account's balance crosses a threshold (above ceiling or below floor), the monitor contract emits a `SweepNeeded` event that triggers step 3. The continuous-evaluation architecture is what enables 24/7/365 treasury optimization.
L3 EXECUTION (monitor contract evaluation) and L4 ACCOUNT (balance state across participating accounts) lit, code-enforced. C9 (prudential) attaches at the participating-bank level because every sweep changes the bank's intraday liquidity exposure profile.
Step 3 · Sweep Execution (Atomic Transfer)Code-Enforced
"A zero-balance account sweep firing automatically at end-of-day at a single bank — except this fires every time the threshold trips, around the clock, across multiple banks."
On a `SweepNeeded` event, the Cari sweep-execution contract calculates the optimal transfer (source account, destination account, amount, prioritization) per the active policy and fires an atomic transfer.
Both source and destination banks' GLs post memo entries; the on-chain settlement is final on Prividium consensus in under 2 seconds. Sanctions screening is bypassed for intra-corporate sweeps because a corporate sweeping its own balances among its own consortium-bank accounts is not a counterparty payment — confirm at policy-setup time which sweep flows are corporate-internal versus inter-corporate.
L1 NETWORK · L2 CONSENSUS · L3 EXECUTION · L4 ACCOUNT all lit, code-enforced. C11 (recordkeeping) attaches per sweep — the on-chain transaction hash + GL memo entries together constitute the audit trail.
Step 4 · Bank Liquidity Posture (LCR / NSFR Integration)Policy-EnforcedINGESTDETECTALERT
"A bank's intraday liquidity-management desk recalculating LCR / NSFR positions in real-time — except the underlying deposit movements happen continuously, so the recalculation is continuous too."
Each participating bank's intraday liquidity-management desk integrates Cari sweep activity into its LCR (Liquidity Coverage Ratio, 12 C.F.R. § 249.20) and NSFR (Net Stable Funding Ratio, 12 C.F.R. § 249.100) positions.
Continuous sweep activity changes the bank's deposit-stability profile — a deposit that sweeps out at 2am on a Sunday is operationally different from a deposit that sits stable. The bank's liquidity posture must reconcile to its regulatory ratios continuously rather than at end-of-day.
L5 APPLICATION lit, policy-enforced. The integration with bank treasury-risk systems (Quantifi · Numerix · proprietary risk engines — VERIFY bank-by-bank) carries the regulatory weight at this step.
Step 5 · Sweep Reporting & RecordkeepingPolicy-EnforcedINGESTDETECTALERT
"The corporate's monthly cash-management statement plus the bank's sweep-activity report to internal audit — both rolled up from the underlying continuous activity."
Sweep activity rolls up into corporate-treasury reporting (per-account-per-day sweep counts, total volume, idle-balance reduction metrics) and bank internal-audit reporting (per-corporate-customer sweep activity, LCR / NSFR impact, BSA/AML flags for unusual sweep patterns).
Cari Network provides the consolidated reporting surface drawing on the on-chain ledger; corporate treasury and bank internal audit both ingest the same canonical record. The single-source-of-truth property is operationally important — sweep reconciliation that traditionally requires per-bank API pulls collapses to one ledger query.
L5 APPLICATION lit, policy-enforced. C11 (recordkeeping) and C12 (independent audit trail) satisfied at the on-chain ledger level — the cryptographic transaction hash is the canonical record for every sweep event.
Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.
Coverage notes: 5 disclosed gap(s).