One platform to operate digital assets
Wallets, transaction controls, payments and treasury across ten networks, through one REST API. Build the product. Tetlith runs the infrastructure underneath it.
A wallet for every customer, opened in one call
Open wallets for customers, accounts or teams on demand, on any supported network. They run inside your product under your brand, and your users never handle a seed phrase.
- A wallet per customer, created through the API
- A deposit address per customer on each network
- One balance per currency across every network
- Every balance and movement visible to your team
Decide what can move, and who can move it
Set limits, approved destinations and approval thresholds for each asset. Every payout is checked against them before it moves, and transfers started in the dashboard above your threshold wait for the right people to approve.
- Per-transaction and daily limits
- Transfers only to approved destinations, if you choose
- Multi-person approval in the dashboard above your threshold
- Fees estimated per transaction and failed sends retried
Accept payments and send payouts on the same rails
Know when a payment arrives and which customer it belongs to, then pay out to any address under the same controls as every other transfer.
- Deposits detected and attributed to a customer
- Confirmations tracked, and reversed deposits handled
- Signed webhooks when payments arrive and payouts complete
- Transfers between your customers' accounts
Company funds kept apart, under their own controls
Hold company funds in dedicated treasury wallets, separate from customer wallets. Treasury spending follows its own limits, approvals and approved destinations, set independently of customer withdrawals.
- Treasury wallets kept apart from customer wallets
- Separate limits and approved destinations for treasury
- Several assets in one treasury account
- Every movement recorded against its account
Ten networks, one integration
Write your integration once and it covers all of them. Giving a customer an address on another network is one API call, not a new integration.
Controls your security team can verify
Every transfer is checked against your rules before it moves, and every action is recorded.
MPC key management
New keys are managed with multi-party computation by default.
Approvals in the dashboard
Transfers started in the dashboard above your threshold need sign-off from another authorised member. No one approves their own request.
Separate API access
Read-only keys are issued apart from keys that move money, and a read key cannot be turned into a spend key.
Signed webhooks
Every event is signed so you can confirm it came from Tetlith, and deliveries retry until you acknowledge them.
Audit trail
A record of who requested each action and who approved it.
Try the whole platform in the sandbox.
Sandbox keys are issued before company verification, on test networks, with the same API you will use in production.