Now running on mainnet across eight networks. See the networks
Keys sealed in AWS Nitro Enclaves

Wallet infrastructure
built for fintech

Give every customer a wallet, credit deposits the moment they confirm, and send withdrawals your team has approved, on Ethereum, BNB Chain, Tron, Solana, Bitcoin and more. The keys never leave hardware enclaves.

Free test workspace on testnets · Go live when you're ready

One API, every network your customers use

USDT, USDC and the native coin of each network, plus any token your team adds. Each network has a testnet twin for your test workspace.

How it works

Wallets · 12,408
NameTypeAddresses
cus_1042User0x8f3c…a91e · TQx4…8vPk · bc1q…7w2d
cus_1043User0x1d07…44b2 · TL9m…2hRa · bc1q…ke0s
TreasuryTreasury0x55a1…0c3f · TGp2…Qx1n · bc1q…3u9x
PayoutsOperational0xb8e2…71dd · TVw8…mN4t · bc1q…h6fz
POST /v1/wallets  { "name": "cus_1044", "type": "user", "externalId": "cus_1044" }

Everything you need to run custody

Wallets, money movement, controls and integrations in one system, with a dashboard for your team and an API for your product.

WalletsCustomer, treasury and operational
DepositsConfirmed, credited, swept
WithdrawalsFees estimated, stuck sends handled
PoliciesWho approves what, and when
Gas stationFees topped up automatically
Address bookAllow-listed payout addresses
API & webhooksSigned requests and events
Analytics & auditFlows, fees and every action

Less infrastructure. More product.

The parts of a crypto wallet that take months to build and never stop needing attention are already running.

Running nodes and indexersSeveral providers per network, automatic failover, reorg handling.
2–3 months
Nonces, fees and stuck transactionsFee estimation, replacement, and clear reasons when a send waits.
1–2 months
Sweeps and gas managementDeposits consolidated to treasury with fees paid from a gas wallet.
1 month
Key management and signingSeeds generated and used only inside attested enclaves.
3–6 months
What you skipBefore writing a line of your own product.
7–12 months

Security

Keys never leave the enclave

Valtu signs inside AWS Nitro Enclaves: isolated machines with no disk, no network and no operator access. Every request is signed, every policy is checked before a key is used, and every action is written to an append-only audit log.

0
Private keys on serversSeeds are created and used only inside attested enclaves.
P-256
Signed requestsEvery write carries a signature from a passkey or an API key you hold.
n of m
ApprovalsYour policies decide who approves what, enforced before signing.
100%
Audited actionsEvery sign-in, approval and change, kept append-only.
  • Each customer workspace is its own enclave organization with its own seeds
  • Passkeys for every person on your team, with roles and custom permissions
  • Allow-listed payout addresses with a cooling-off period
  • Separate test and live workspaces: testnet coins never mix with real funds

Developers

An API your engineers will like

REST endpoints for wallets, transfers and deposits, signed requests and signed webhooks, retry-safe writes, and the same objects you see in the dashboard.

  • Webhooks signed with HMAC and Ed25519, retried with backoff
  • Retry-safe transfers keyed by your own external IDs
  • Test workspace on testnets with the same API
import { ValtuWallet } from "./valtu-wallet.ts";
const valtu = new ValtuWallet({ baseUrl, privateKeyHex });

// Pay out USDC on Ethereum; your policies decide who approves.
const { transfer } = await valtu.createTransfer({
  walletId: payoutsWalletId,
  asset: "USDC-ERC20",
  to: "0x5c1e…9a04",
  amount: "120000000000",   // base units
  externalId: "payout_7781",   // safe to retry
});

Built for teams that move money

Whatever you're building, your customers get a wallet and your team keeps control.

Exchanges & brokersDeposit addresses at scale

Unique addresses per user, credited after confirmations and swept to treasury automatically.

PaymentsStablecoin collections and payouts

Accept USDT and USDC on the networks your payers use and pay out with approvals.

Neobanks & walletsCrypto accounts inside your app

Wallets for every customer behind your own interface, with the controls a regulated business needs.

TreasuryCompany funds under policy

Treasury and operational wallets with multi-person approvals and allow-listed destinations.

Questions

Who holds the keys?

Valtu holds them on your behalf: seeds are generated and used only inside attested hardware enclaves, and each workspace has its own. Nothing is signed unless your workspace's policies allow it.

Does Valtu approve our transfers?

No. Your team approves its own transfers with passkeys, following the policies you set. Valtu runs the infrastructure and never co-signs.

Which networks and coins are supported?

Ethereum, BNB Chain, Polygon, Base, Lisk, Tron, Solana and Bitcoin with their native coins, USDT and USDC, and further tokens added after an on-chain check. Each has a testnet for your test workspace.

Can we try it before going live?

Yes. Start with a test workspace on testnets using the same dashboard and API, then open a live workspace after review.

What happens if a network is retired?

You're told well ahead with a date, by webhook, alert and a notice in the dashboard, so funds can be moved before support ends.

Start with a test workspace today

Same dashboard, same API, free test coins. Go live when your team is ready.