Suward documentation
Suward is a payment gateway for accepting stablecoins and major cryptocurrencies over one REST API. Everything here is public — no account is required to read any of it.
Two things you can build on
A one-time request to collect a fixed amount of a single asset at a unique, single-use deposit address. Built for checkouts and invoices.
A reusable deposit address scoped to one of your customers, accepting repeat deposits of any amount in the assets you allow. Built for account funding, top-ups, and user balances.
Both settle into the same project balance, report through the same signed webhooks, and follow the same lifecycle: funds are credited at Accepted (enough confirmations to act on) and become withdrawable at Success (irreversible). → Settlement & finality
Created, waiting for funds — or confirming the transfer that arrived.
Enough confirmations to act on. Balance credited. Ship, credit, deliver.
Irreversible. Funds are withdrawable.
Expired, cancelled, or invalidated without a valid payment. Terminal.
Where to start
The Quickstart runs one payment end to end on free test tokens, in about 10 minutes.
Statuses, finality, fees, and screening, each on its own page.
Every endpoint, webhook, error code, and limit.
Live data, not lists
The accepted assets, supported networks, and confirmation requirements are served by the API itself — GET /v1/assets, GET /v1/blockchains — with no authentication. What you read there is what production uses. → Assets & networks
curl https://api.suward.com/v1/assetsThe rest of the map
Create a payment, redirect to its page. No frontend to build.
Signed events at every stage transition, with Ed25519 verification in three languages.
Free test tokens on real networks, or drive statuses with no chain at all.
Test to production is a checklist, not a project.
Official TypeScript and Go clients for the Suward merchant API, plus REST integration for Python and any other language.
Error shape, HTTP codes, rate limits, and the per-payment cap.
Something unclear? payments@suward.com — we treat every integration question as a documentation defect.