Wallet-as-a-Service (WaaS)

Embed crypto wallets in your product. One vault, unlimited addresses.

Generate unique deposit addresses programmatically from a single MPC vault seed. Attribute deposits per customer, keep full recoverability, ship wallet features in weeks — and never create a vault per user again.

Scale without vault sprawl

Unique addresses derive from one seed, so onboarding ten thousand customers does not mean ten thousand key ceremonies or ten thousand fees.

Built for high frequency

No vault-creation delay in the deposit path. Addresses are issued on demand at API latency, so checkout never waits on cryptography.

API-first, developer-friendly

Create, query and manage addresses and balances through the wallet engine APIs, with role-based access scoped per key.

What you can build

Deposit and payout infrastructure, fully under your control

  • Create single or bulk deposit addresses via API
  • Customise derivation paths per product line
  • Query native and token balances per address
  • Export master public keys per vault for reconciliation
  • Show or hide asset visibility per address
  • Inbound transaction screening on arrival
  • Role-based API access scoped for every key
POST /v1/vaults/:id/addresses
curl -X POST \
  https://api.nodus-360.com/v1/vaults/vlt_8f21/addresses \
  -H 'Authorization: Bearer $NODUS_KEY' \
  -d '{ "chain": "ethereum", "count": 250,
        "label": "customer_batch_apr" }'
  • 201 — 250 addresses derived (84 ms)
  • every address recoverable from the vault seed
  • inbound KYT screening applied on arrival

Key ownership models

You decide who holds the key shares

Three models, all with BIP39 disaster recovery. In none of them does Nodus360 or io.finnet hold key material — which is usually the difference between launching a wallet and becoming a custodian.

Model A

You own the keys

Omnibus model. Your team holds every share; end users never touch cryptography.

Model B

Your users own the keys

Non-custodial product model. Shares live on user devices; you provide the interface, not the liability.

Model C

Shared control

Threshold split between you and your user, so neither side can move funds alone.

Send us your deposit flow. We will show you the integration on the first call.

Request access