A permanent deposit address for every customer
Create one wallet per customer — USDT, USDC, or the native coin of any supported network. Every deposit they send — at any amount, any time — is detected on-chain and credited to your balance. The address never expires.
Permanent addresses, not one-off charges
Payments and static wallets are two different deposit models. Choose the one that matches how your customers pay.
Payments
A one-time charge for a fixed amount and asset. Create it, share the address, and Suward settles the exact amount into your balance. Best for checkouts and invoices where a customer pays once.
Static Wallets
A permanent per-customer address. Any deposit at any amount is detected and credited automatically. Best for exchanges, account funding, and anywhere a customer returns to top up.
Built for repeat deposits
If your customers deposit more than once, static wallets remove the overhead of creating a new payment for each transfer.
Exchanges and wallets
Give each user a persistent funding address. They deposit when they want, at any amount, and the balance updates automatically.
Recurring top-ups
Let customers fund their account balance on their schedule. No expiring payment links, no re-creation on each cycle.
Account funding
Assign a wallet on sign-up. The customer sends from any supporting wallet; every transfer is credited without a matching payment create call.
Every deposit tracked to finality
Each inbound transfer to the static wallet address is detected on-chain and recorded as a deposit object. Deposits move through the same lifecycle as payments — pending, accepted, success — and your webhook fires on each status transition.
Add a permanent deposit address to your integration
Create an account, generate a static wallet in test mode, and watch the deposit lifecycle run end to end — before you touch production.