Static Wallets · balance mode
A permanent deposit address for every customer
Static Wallets is Suward’s mode for platforms where users hold a balance: each customer gets their own address, deposits of any amount are screened and credited automatically, and repeat top-ups need nothing from you. No invoices, no expiring addresses, no manual matching.
Who it’s for
For products where “deposit” is a core feature
Betting and casino platforms, brokers and trading apps, game economies, prepaid services — anywhere a user funds an account and spends from it. In these products a deposit isn’t a checkout event; it’s core infrastructure. Static Wallets treats it that way.
Fund → balance → spend · on repeat
Selling in one-off orders instead? You want
PaymentsDeposit lifecycle
From deposit to credited balance — automatically
A user gets their address once.
It stays theirs. They can save it in their wallet and top up whenever they want, with any amount.
Every deposit is screened before crediting.
AML and sanctions checks run on each incoming transaction — not on a sample, and never after the money is already spendable. And only the assets you allow for the wallet are ever credited: a deposit in anything else is recorded for audit, not credited.
How compliance worksThe balance is credited at Accepted.
That means enough confirmations have accumulated to act safely — let the user play, trade, or spend. At Success the funds are irreversible and ready to withdraw. If a chain rewrites its recent history, affected deposits are re-verified automatically while they are still confirming — the checks finish before your user is credited, not after.
How settlement worksA signed webhook fires at every stage.
Your backend credits the user automatically — no operator clicking through a queue of deposits.
Operations & treasury
Thousands of deposits shouldn’t mean thousands of manual steps
Auto-withdrawal.
Set a rule once — funds move to your own wallet automatically. No one on your team has to “sweep addresses” by hand.
Controlled manual payouts.
On-chain withdrawals from the dashboard run under two-factor authentication and role-based access — the person who watches balances doesn’t have to be the person who can move them.
Fees known in advance.
Withdrawal costs are quoted before you confirm, so treasury planning uses real numbers.
Scale
One user or a million — the model doesn’t change
Addresses don’t expire, and deposits don’t queue up for manual review unless screening flags them. Accepted and final balances are updated as one operation, so every balance movement on our side maps to a specific payment at a specific stage — reconciliation on your side has one source of truth. The mode is designed so that scale changes your numbers, not your process.
Talk to us about your volumesOne source of truth · movement ↔ payment ↔ stage
Mode FAQ
Questions platform teams ask
Is there a limit on deposit amounts?
No — a static wallet accepts deposits of any amount, and every deposit is screened before it is credited. What it accepts is under your control too: only the assets you allow for the wallet are credited; a deposit in any other asset is recorded for audit, not credited.
Do deposit addresses expire?
No. Each customer’s address is permanent: they can save it in their wallet and top it up again at any time.
What happens during a chain reorganization?
Affected deposits are re-verified automatically against the new state of the chain — while they are still confirming, before your user’s balance is credited. Nothing is credited on a single block confirmation, and the rare genuinely ambiguous cases are resolved by a person, also before crediting. How settlement works
What do withdrawals cost?
Withdrawal fees are network-dependent and quoted before you confirm — in the dashboard and in the API. Pricing
Tell us how your balances work
Every balance-based product has its own deposit flow, risk profile, and treasury rules. Talk to us — we’ll map Static Wallets onto your architecture, or you can start in the docs and test the flow on real networks with test tokens.