Treasury overview
acme.stableops.finance / treasury / overview
Most fintechs build this themselves over a year. Stableops ships it as building blocks you can compose in an afternoon.
The vault. One consolidated wallet across every supported network, MPC-secured with multi-sig policy. Where reserves sit. Where payouts originate. The discipline of a treasury team, encoded.
The operational wallet for outbound payments — withdrawals, vendor payouts, off-ramp settlements. Capped balance with rolling withdrawal limits, auto-refilled from the master when it runs low.
Fund the paymaster once, in USD. We hold and rebalance the native gas tokens across every network on your behalf, and pay fees for every sweep, payout, and contract call. Your finance team never sees an ETH invoice.
Payroll runs, escrow holds, settlement pools per region, reserves that compound, fee collectors. Spin up unlimited wallet types with your own names and policies. Same primitives, your taxonomy.
When a user sends USDC to a payable address, four things happen automatically. You write zero gas-management code.
You called POST /v1/addresses. We generated a deposit address — a smart wallet on EVM chains, a PDA on Solana — and returned it to your app.
Our indexers tail every supported network. Deposits are confirmed at the configured threshold (1 block on L2s, 12 on Ethereum, 32 slots on Solana) and a deposit.confirmed webhook fires.
We bundle the sweep via ERC-4337 on EVM and Solana fee-payer on SOL. The paymaster wallet pays gas — the payable wallet never needs to hold ETH or SOL.
A second webhook (sweep.settled) fires when the sweep transaction is finalized. Your treasury balance updates atomically. Gas cost is itemized on your paymaster invoice.
Stablecoin custody isn't a feature, it's the product. Every signing key is sharded across MPC, every shard sits in an HSM, every withdrawal flows through a policy engine you control. You never hand us your funds — only the operational signing.
Private keys are sharded and signed via multi-party computation. No single key exists on any single machine — not even ours.
Signer shards are stored in FIPS 140-2 Level 3 hardware security modules. Air-gapped during provisioning, attested at every boot.
Configure per-wallet approval rules: minimum signers, geographic separation, time-locks, allowlists. Enforced at the signing layer, not the API.
Lock the master wallet to a fixed set of destinations. Adding a new address requires multi-party approval and a 24-hour cool-down.
Every counterparty is screened against OFAC, EU, UN, and chain-analysis providers on every transfer. Sanctioned addresses are blocked at the policy layer.
A follow-the-sun ops team monitors signing, indexing, and webhook delivery in three regions. Incidents are paged in under 60 seconds.
Four common shapes, dozens of variations underneath. Each use case below is a real customer pattern in production today.
Pay engineers in 40 countries the same day, in USDC. Maintain regional sub-wallets per pay cycle. Reconcile against the master automatically.
Hold buyer funds in time-locked escrow until delivery confirms. Release to sellers on event, refund without touching the master.
Track per-user balances in custom sub-wallets. Deposits and withdrawals are gasless via the paymaster across every chain.
Cross-region settlement between business entities. Each region gets its own settlement pool with its own approval policy.
More than 200 companies move stablecoins through Stableops. Cross-border payments, payroll, B2B settlement, on-ramps, off-ramps — the primitives carry.
"We replaced our internal MPC custody, our gas relayer, and our reconciliation pipeline in one weekend. The fact that our users never see ETH again is the actual product win."
"Sub-three-second sweeps on Base meant we could finally credit user wallets in realtime. Our checkout conversion went up 11% the week we shipped."
"The paymaster wallet is the cleanest abstraction I've seen for gas. Our finance team understands it. That alone unblocked us."
"MPC custody with policy approvals built in. We didn't have to integrate Fireblocks, write the relayer, or run our own indexers. Three months of work, gone."
"We sent our first USDC payout eleven minutes after signup. Sandbox to production in three days. That's the part that actually surprised me."
The team behind Stableops has spent the last decade building the infrastructure other people now depend on — exchanges, stablecoin rails, P2P on/off-ramps, and distributed engineering organizations. Stableops is what we'd build for ourselves.
Built and operated matching engine and custody systems at the world's largest crypto exchange by volume.
Shipped consumer wallet and stablecoin payment rails across Nigeria, Ghana, Kenya, and South Africa.
Built the P2P on/off-ramp platform Binance uses to move users between fiat and stablecoins.
Trained and led distributed engineering teams across four continents at the largest African tech talent network.
A decade of operating exchange custody, P2P fiat rails, emerging-market stablecoin payments, and the discipline of running engineering at scale. We've seen what breaks under volume, what regulators actually care about, and what a treasury team needs to sleep through the night.
The questions our enterprise customers asked us before integrating. Nothing fluffy — if it's not here, our engineers will answer it on a call.
You do. Every wallet — payable, master, hot, paymaster — is provisioned and signed against keys you control via MPC shards. Stableops operates the signing infrastructure; we never have unilateral access. You can export shard recovery material at any time.
On EVM chains we use ERC-4337 account abstraction with the paymaster wallet as gas sponsor. On Solana we use fee-payer separation, where the paymaster signs as the transaction fee payer while the payable wallet authorizes the token transfer. Your end users never touch ETH, SOL, or any native asset.
Master is the vault — your consolidated, MPC-secured treasury across every network. Hot is the operational wallet that signs outbound payments under a rolling cap, auto-refilled from master. Paymaster holds native gas tokens across every chain and bills you in USD, so your finance team never touches ETH or SOL. Custom wallets are anything else you need — payroll runs, escrow holds, settlement pools, reserves — created with POST /v1/wallets with your own name and policy.
Networks: Ethereum mainnet, Base, Solana, Tron, and BNB Chain — all in production. Assets: USDC and USDT on every supported network. Arbitrum, Optimism, Polygon, and Avalanche are on the roadmap for the next 90 days. Enterprise customers can request additional networks under bring-your-own-network.
On Base and Solana, typically under three seconds from deposit confirmation to master-wallet settlement. On Ethereum mainnet, sweeps complete in 15 to 60 seconds depending on network congestion. Each step emits a webhook, so your reconciliation is realtime.
Your wallets remain on-chain and recoverable. Signing keys are sharded across three independent regions and three independent cloud providers; a region-level outage degrades but does not stop signing. In a worst-case scenario, you can use exported recovery shards to sign transactions independently using our open-source recovery tool.
Every counterparty address is screened against OFAC, EU, UN, and major chain-analysis providers (Chainalysis and Elliptic) on every transfer. Sanctioned addresses are blocked at the policy layer before signing. KYB and travel-rule data flows are included for Scale and Enterprise plans.
You fund the paymaster wallet in USD — never in ETH or SOL. We hold and rebalance native gas tokens across every supported chain on your behalf. Every gas spend is itemized per transaction with the network, gas units used, and converted USD cost. Set auto-top-up rules from your card or from your master wallet. You pay spot gas plus 6%; no markup if you bring your own native tokens under Enterprise.
Yes. We expose a REST API and webhooks; SDKs are available for Node, Python, Go, Ruby, and PHP. Most customers integrate the deposit flow in a day and the payout flow in another. The dashboard is for operations and ops-team workflows — not required for any product surface.