Solutions

Built for teams that move money.

The same wallets, policies and API, set up for how your business works. Each solution has a full guide in the docs, down to the rules to set before going live.

Payment acceptance

Take stablecoin payments and settle them to treasury.

A deposit address per customer or per order, orders marked paid only on deposit.confirmed, sweeps to a settlement wallet, and refunds that go through approval when they're unusual.

  • Under-, over- and unmatched payments go to a review queue
  • Sweep minimums so fees never exceed what's collected
  • Small refunds automatic, unusual refund volume needs a person

Exchanges and brokers

Deposit addresses at scale, withdrawals under limits.

An address per user, credited on confirmation and keyed on the deposit ID. Withdrawals leave a hot wallet with velocity rules, and treasury sends only to saved addresses.

  • Separate, scoped API keys for deposits and withdrawals
  • A leaked key can't touch wallets outside its scope
  • Alerts on hot-wallet balance, low gas and failed transfers

Payouts and remittance

Batches on the right network, every one retry-safe.

Send up to 100 payouts in one request, each with your own externalId so a retry never pays twice. Tron payouts can rent energy, and every transfer shows what the network charged.

  • Preview fees and policy outcomes before sending
  • Approvals for large or unusual batches
  • Clear reasons when a payout can't be sent

Treasury operations

Company funds under multi-person policy.

Treasury and operational wallets with approval groups, allow-listed destinations, alerts on every treasury transfer, and an audit log your auditors can export.

  • Every member signs in with a passkey; custom roles
  • API keys scoped to wallets, IP-restricted and set to expire
  • Analytics on inflow, outflow and fees by asset and day

Not sure which fits?

Tell us what you're building and we'll suggest a setup: wallets, policies and the networks to start with.

Talk to sales