Treasury
Multisig treasury explained: M-of-N control for company funds
What multisig treasury means, how M-of-N approvals work on Safe and Squads, and why teams use it instead of a single shared bank login. Covers mid-market FX, DCC, local rails vs SWIFT, true-cost comparison, and Glide’s stablecoin + multisig operating model.
Multisig (multi-signature) treasury means spending requires M approvals out of N authorized signers. Instead of one person with unilateral control of a hot wallet or a shared password to a bank portal, policy lives in the signing threshold.
Why teams adopt it
- No single-key rug or compromised laptop drains the treasury
- Clear approval paths for finance + founder dual control
- On-chain auditability of configuration changes
- Alignment with how serious crypto organizations already operate
Safe (EVM) and Squads (Solana)
On EVM chains, Safe-style smart accounts are the common standard. On Solana, Squads-style multisigs play a similar role. Glide provisions and operates across these patterns so teams are not trapped on one chain’s tooling.
Always price FX against mid-market
The mid-market rate is the only honest benchmark. Bank boards, airport desks, and “zero commission” bureaux price away from it. Compare total funded amount to deliver a fixed foreign outcome — not headline fees. A fair question is always: “What do I pay today so they receive exactly X by Friday?”
| Path | What usually inflates cost | When it still wins |
|---|---|---|
| Bank SWIFT + desk FX | Flat wire + 1.5–4% FX vs mid-market + intermediary fees | Beneficiary only accepts classic wire instructions |
| Fintech local-rail payout | Transparent fee + small FX spread | Recipient has local account or wallet rails |
| Card spend in local currency | Issuer FX; DCC if accepted | Tourist day-to-day at card-friendly merchants |
| Stablecoin leg + offramp | Network fee + conversion spread | Both ends can hold/offramp crypto-capable balances |
Fee stack anatomy (generic)
Cross-border cost is a four-layer stack: FX distance from mid-market, explicit send fees, intermediary or network fees, and time risk around cut-offs. Marketing that only advertises one layer is incomplete. Force every provider to answer with a single funded amount for a fixed receive outcome.
| Layer | Example failure mode | How to pressure-test |
|---|---|---|
| FX | Airport board 3–6% off mid-market | Screenshot mid-market vs offered rate |
| Send fee | “Free” transfer with worse FX | Ask all-in funded amount |
| Intermediary | SWIFT lifting fee surprises | Ask if OUR/SHA/BEN or local rail |
| Time risk | Missed rent/payroll cut-off | Add 1–2 buffer business days |
Decision checklist
- Write the delivered amount and deadline first
- Quote two paths with the same outcome sentence
- Refuse DCC on every terminal
- Confirm local-rail eligibility before paying SWIFT prices
- Document fees for expense reports and disputes
- For teams: dual-control approvals on treasury-scale payouts
Week-one money calendar
- Before travel or a large send: enable issuer controls and save backup funding path
- Day 0: fix the receive amount and deadline in writing
- Day 1: run a small test payment or card auth before full amount
- Day 2–3: confirm credit, save receipts, adjust playbook
- Ongoing: refuse DCC, prefer local rails, re-check mid-market before big converts
Glide operating angle
Hold multi-currency or USDC as the long-haul operating balance, convert when mid-market works for you, and pay out on modern local rails. Solo users get portable balances and emergency top-ups; teams get M-of-N multisig so no single laptop can drain treasury. That is the product gap versus consumer multi-currency apps that stop at cards and IBAN-like details.
| Job | Consumer multi-currency strength | Glide-oriented strength |
|---|---|---|
| Tourist card spend | Strong FX + ATM tooling | Same jobs + stablecoin float for longer trips |
| Freelance collect | Local account details in some markets | USDC collect + controlled offramp |
| Team treasury | Usually single-user apps | Multisig + policy-shaped approvals |
| True-cost compares | In-app quotes | Mid-market framing across rails including crypto legs |
Scenario walkthroughs
Scenario A — tourist week: primary travel card for hotels and restaurants, backup card on a second network, modest local cash for markets, zero airport full-budget converts, DCC refused everywhere. Scenario B — remote worker paid in USD spending in a second currency: collect into a portable multi-currency or USDC balance, convert in tranches near mid-market, pay rent on local rails once banked. Scenario C — team treasury: M-of-N approvals on payouts, policy limits by counterparty and amount, stablecoin leg for speed with local offramp for vendors who cannot receive crypto.
Scenario D — family remittance: fix the receive amount in local currency first, quote SWIFT vs local-rail fintech with the same deadline, never trust “$0 fee” without the funded total. Scenario E — student term: tuition deadlines are time-risk; send early, keep a buffer month of living costs, and avoid cash-heavy airport logistics on arrival day.
Common failure modes
- Accepting DCC “for convenience” on large hotel deposits
- Using SWIFT for euro-to-euro or other domestic-rail-eligible payments
- Converting a full trip budget at the first airport desk
- Single-card dependence with no freeze/backup plan
- Team balances on a single laptop-controlled wallet
- Comparing providers on headline fees instead of funded totals
What good looks like
- You can explain mid-market vs the board in one sentence
- You refuse DCC by default
- You know when local rails beat SWIFT for your beneficiary
- You have a two-card + cash float emergency stack
- Treasury-scale balances require more than one person to move
Next step
Vault controls without spreadsheet chaos
Glide’s vault workflows combine multisig approvals with productized policies, recovery paths, and spend visibility.
Explore Glide treasuryFrequently asked questions
What is the mid-market rate?+
The midpoint between buy and sell on wholesale FX markets — the fair benchmark for comparing any consumer FX offer. Airport boards and hotel cashiers routinely diverge from it.
What is DCC?+
Dynamic currency conversion: the terminal offers to charge your home currency at the merchant’s rate. Decline and pay local so your issuer converts under its published rules.
When is SWIFT still necessary?+
When the beneficiary cannot receive on local or real-time domestic rails. Otherwise local rails usually win on cost and speed — especially inside SEPA, Faster Payments, UPI, PIX, SPEI, and similar systems.
How does Glide differ from multi-currency apps?+
Glide adds stablecoin-native balances and optional multisig treasury controls alongside transparent conversion and modern payouts — useful for freelancers and teams who outgrow consumer multi-currency alone.
Is this financial advice?+
No — educational planning guidance. Verify fees, eligibility, and regulations for your passport and corridor before moving large amounts.
What is a true-cost comparison?+
Fix the receive amount and deadline, then ask each provider what you must fund today. That single number includes FX, fees, and intermediary costs — unlike “$0 fee” headlines.
Glide · Borderless banking
Moving money across borders?
Hold multi-currency or USDC balances, convert near mid-market, decline DCC habits, and pay out on local rails - solo or with multisig for teams.
Keep reading
Stablecoins for cross-border payments: how USDC changes the path
How stablecoins like USDC are used for cross-border payments, treasury, freelancing, and offramps — benefits, risks, and operational reality.
Self-custody vs bank custody: who actually holds your money?
Self-custody, custodial fintech balances, and bank deposits compared — control, failure modes, recovery, and which model fits travel vs treasury.