01
Real, domiciled bank accounts held in your legal name across the markets that matter to your business. Pockyt operates the underlying infrastructure; you operate the policy.
02
Decide what you want to hold locally (operating reserves, FX exposure you're comfortable carrying) and what you want to sweep home (excess, working capital). Express it as rules, not as workflows.
03
Configure when and how cross-currency movements happen: mid-market on demand, scheduled rebalancing, threshold-based triggers, hedge against rate conditions. The treasury team owns the policy; Pockyt owns the execution.
04
Balances, FX trades, sweeps, deposits, withdrawals — all roll up to a single Pockyt ledger. One export to your ERP or accounting system. One source of truth.
The consolidation savings — banking relationships, FX margin, reconciliation overhead — start to compound around the third active currency. Below that threshold, a single operational bank account is usually enough.
If you're collecting in one currency and spending entirely in another, the case is clear. If you're holding operating reserves in multiple currencies and want them programmable and visible in one place, the case is even clearer.
Companies that operate primarily in USDC but need to settle fiat obligations — vendors, payroll-adjacent flows, regulatory commitments — benefit from holding USDC as primary treasury and converting to fiat on demand through Pockyt.
If your treasury team is spending more time managing the plumbing than analyzing the position, the operating-layer model frees them to do the analytical work instead.
Talk to our team about how Multi-currency Treasury fits into your current finance operation — or replaces it.