Choose your signing path
Use WalletSuite MPC, self-hosted OWS, external signers, signed-payload workflows, or customer-controlled HSM/KMS behind one operations layer.
Why WalletSuite
Govern wallet operations across every signing model
Build and govern wallet workflows with policy, approvals, signing, automation controls, and audit evidence across WalletSuite MPC, self-hosted OWS, external signers, and customer-controlled HSM/KMS.
Last updated: May 2026
- 80+
- Chains
- MPC + OWS
- Signing options
- SDK · REST · MCP
- Developer surfaces
- SHA-256
- Hash-chained audit
WalletSuite platform · flexible signing
Five reasons
One wallet operations layer.
Multiple signing paths.
Treasury, payment ops, and compliance teams standardize wallet workflows, approvals, signing, and audit evidence — without rip-and-replace.
Productize controls
Turn internal wallet rules into tenant-scoped policies, approval flows, admin controls, and customer-visible evidence.
Prove every decision
Attach policy version, decision reason, approval trail, signer path, and verifiable audit evidence to every transaction.
Adopt safely
Run WalletSuite in shadow mode alongside existing backend rules before turning on enforcement. No big-bang migration.
Make automation safe
Separate read, prepare, approve, sign, and broadcast so agents and backend jobs operate inside explicit mandates.
Bands
Read, prepare, approve, sign, broadcast.
Never one big call.
Bands are the explicit phases of a wallet operation. Agents and backend jobs only get the bands their mandate allows.
01 · ReadInspect state
Balances, allowances, prior decisions, and policy context. Read-only by default for agents.
02 · PrepareBuild payload
Compose unsigned transactions. Policy evaluates the action before it reaches a signer.
03 · Approve / SignAuthorize
Route approvals to the right humans or systems, then sign through WalletSuite MPC, OWS, or the selected signer path.
04 · BroadcastSettle
Submit to chain, write audit evidence, and reconcile status back to the source system.
Design the right signing architecture
Use WalletSuite as the operations layer across the signing model that fits your workflow — no rip-and-replace.