Static Wallets

Reusable deposit addresses for continuous per-customer balance tracking.

A static wallet is a reusable deposit address — one EVM address, valid across every supported EVM chain — that a customer or account can fund any number of times. Use it for continuous, per-customer balance tracking, unlike a payment (one address, one asset, one amount, single-use).

Each incoming transfer is recorded as an individual deposit and moves through Detected → Accepted → Confirmed as on-chain finality accrues; a reorg rolls it back to Invalidated.

Accepted-asset allow-list. A wallet accepts only the assets in allowedAssets; a deposit of any other asset is recorded for audit as Ignored — not credited and not delivered as a webhook.

Crediting. The gross amount is credited to your balance; fee and networkFee are informational and are not deducted. Balance updates are atomic and reorg-safe.

Settings. Idempotent creation by externalId, a per-wallet webhookUrl override, and arbitrary metadata. Drive a synthetic deposit through its lifecycle with POST /v1/static-wallets/{staticWalletId}/simulate (test assets only).

Conventions shared by every endpoint — auth, amounts, timestamps, pagination — are on the reference overview. The full walkthrough lives in the Static wallets guide.

Endpoints

Objects

Each endpoint page lists its own request and response fields. The wallet and deposit objects in full, plus every shared enumeration: Objects & enums

Something unclear? payments@suward.com — we treat every integration question as a documentation defect.