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.
Your signing key is mathematically split into three independent shards using threshold signature schemes (TSS, GG20, or FROST depending on chain). Two of three shards must cooperate via secure multi-party computation to produce a signature. No machine, no engineer, no region ever holds the full key. Shards are stored in FIPS 140-2 Level 3 hardware security modules.
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.
SOC 2 Type II (renewed annually), ISO 27001 certified, penetration tests by Trail of Bits and Halborn on the MPC signing infrastructure, and $50M of crime insurance coverage through Lloyd's of London syndicates.
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.
Yes. Custom wallets are unlimited, named by you, and inherit the same primitives — MPC custody, multi-sig policy, gasless ops via the paymaster, and full audit trail. Customers use them for escrow pools, regional settlement, payroll batches, fee collectors, reserve funds, and any other taxonomy their product needs.
Per wallet, you can configure: minimum number of signers, geographic separation requirements, time-locks, withdrawal allowlists, per-transaction caps, rolling-window caps (daily/weekly), and cool-down periods for new destination addresses. Policies are enforced at the signing layer, not the API — so they're tamper-proof.
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 bring-your-own-network arrangements. For new stablecoins on supported networks, we add them based on volume signals from existing customers — most additions ship in under 30 days. Contact us with your specific need.
On Base and Solana, typically under three seconds from deposit confirmation to wallet settlement. Tron and BNB Chain land in 3–10 seconds. Ethereum mainnet completes in 12–60 seconds depending on network congestion. Each step emits a webhook for realtime reconciliation.
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 your wallet authorizes the token transfer. Your end users never touch ETH, SOL, or any native asset.
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 your master wallet. You pay spot gas plus 6%; no markup if you bring your own native tokens under Enterprise.
Sandbox is free forever. Scale tier is 8¢ per sweep or payout on mainnet — you pay only for operations that settle. No platform fee, no per-seat fee, no minimum. Enterprise pricing for volume above 1M ops/month, custom SLAs, or dedicated infrastructure.
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.
Yes. Every signature, policy check, screening hit, and admin action is logged with cryptographic integrity. Export the full audit trail with one command — stableops audit export --format=soc2 — including signer attestations and policy snapshots at the time of each operation.
Scale tier: 99.99% uptime SLA, 4-hour priority support response. Enterprise tier: 99.999% uptime with custom SLAs, named technical account manager, and incident page within 60 seconds. A follow-the-sun ops team monitors signing and indexing 24/7 across three regions.
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 workflows — not required for any product surface.
Median time from signup to first sandbox deposit is 11 minutes. Median time from sandbox to mainnet first production transfer is 3 days. Enterprise integrations with custom networks or BYO custody arrangements run 2–6 weeks with our solutions team.
Yes, free forever. Full API access, every wallet type, every supported network in testnet mode, all webhooks. No credit card required to start. The sandbox is the right place to integrate before you ever sign a contract.