Do you hold private keys?

No. Signing stays on your side: we take an already signed transaction and broadcast it. Settla never sees a private key or a seed phrase.

Do we need a separate key per network?

No. One key works across every network and every product — RPC, blockchain API, market data. Limits and usage are counted per key in the dashboard.

Can you watch many addresses at once?

Yes. A subscription takes a list of addresses and the list grows on the fly: the wallet adds a freshly derived address the moment it shows it to the user.

What happens if our handler is down?

Delivery is retried five times over an hour with growing intervals. Undelivered events stay in the dashboard and can be replayed by hand.

What happens on a reorg?

If the block with the transaction is rolled back, you receive tx.reverted carrying the same event id. The higher the confirmation threshold, the rarer this is — at three Bitcoin blocks or twelve Ethereum ones it is an exceptional event.

Shared endpoints or a dedicated node?

Shared endpoints are enough for most wallets. Teams move to a dedicated node when balance and broadcast traffic cannot wait in a shared queue — usually around the first exchange listing.

For wallets

Balances, history and alerts.
Without running an indexer.

A wallet lives on three questions: how much do I have, what happened, did it arrive. Settla answers all three over one key across four networks — no nodes to sync, no indexer to rebuild, nobody on call at four in the morning.

Get a key Read the docs

4: Networks in production
18 ms: Balance response
0.4 s: Block to webhook
99.99%: Uptime · 30 days

Portfolio balances

api.settla.net/v1/portfolio/balances

one key

BTCBitcoin0.482319 ms
ETHEthereum1.28417 ms
SOLSolana214.6215 ms
TRXTron18 42019 ms

All networks · one request 21 ms

Anatomy

Every part of the screen is one call

Take any element of the wallet and the panel shows the route behind it. The payment that arrives on its own works the same way, except nobody asked for it — that is the webhook.

Wallet0x9f2c…4d1a

Calls behind the screen

Pick an element of the wallet — its call lights up

one key

Balance/v1/eth/balance/0x9f2c…18 ms
Token balances/v1/eth/tokens/0x9f2c…24 ms
Transfer history/v1/eth/transfers26 ms
Incoming paymentwebhook: tx.confirmed live
Fee estimate/v1/fees/estimate14 ms
Broadcasteth_sendRawTransaction21 ms

Every call goes over the same key p50 21 ms

Event delivery

The alert arrives once, and it arrives on time

Polling blocks for deposits means a worker, a lag and the same event delivered twice. A webhook means an HTTP handler on your side — everything before it is ours.

Retries with backoff
Five attempts over an hour until your endpoint answers 2xx. Failed deliveries stay visible in the dashboard.
One event, one id
Every delivery carries the same event id, so a repeat is filtered out by your idempotency key.
A reorg is an event too
If the block is rolled back you get tx.reverted — not silence and a balance that stops adding up.
Signed payloads
An HMAC signature in the header: your handler checks the event came from us before it credits anything.

From block to your handler

Median across the four networks

Block arrives0 msThe node in the nearest region sees the block with your transaction.
Transaction parsed+180 msTransfers, token movements and internal calls are unpacked from the block.
Address matched+240 msThe transfer is checked against the addresses you subscribed to.
Webhook delivered+410 msA signed POST lands on your endpoint and the user sees the payment in the app.

The confirmation threshold is yours to set: a webhook can fire on the first block or on the number of confirmations your risk policy asks for.

Networks

One key for four networks, and their differences stay out of your code

Address model, credit threshold and fee mechanics differ in every chain. The shape of the response does not.

BitcoinBTC
Address model
UTXO, outputs
Confirmations to credit
3 · ≈ 30 min
Broadcast
sendrawtransaction
EthereumETH
Address model
Account and nonce
Confirmations to credit
12 · ≈ 2 min
Broadcast
eth_sendRawTransaction
SolanaSOL
Address model
Account and nonce
Confirmations to credit
32 · ≈ 13 s
Broadcast
sendTransaction
TronTRX
Address model
Account and energy
Confirmations to credit
19 · ≈ 57 s
Broadcast
broadcasttransaction

Testnets are shaped the same way — only the network segment of the route changes.

What you skip

The part of a wallet nobody ever sees

The screen takes a day. Everything below it is why a multi-chain wallet ships half a year later than planned.

Your own infrastructure

On Settla

Your own infrastructure
Full nodes in four networks: terabytes of state, client upgrades, forks over the weekend.
On Settla
Four endpoints and one key. Forks and upgrades are our on-call, not yours.
Your own infrastructure
An indexer and a database for balances and history, rebuilt after every reorg.
On Settla
Balances, token balances and transfer history arrive as ready responses.
Your own infrastructure
A worker polling blocks for deposits: it lags behind and delivers the same event twice.
On Settla
A webhook with retries and an event id — deduplication fits in one line of your handler.
Your own infrastructure
Monitoring, alerts and somebody awake when a node stops syncing at night.
On Settla
99.99% uptime, a status page and support with a two-hour response.

Questions

What wallet teams ask

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.

Get a free endpoint Talk to an expert

Balances, history and alerts.Without running an indexer.