Developers
The docs are public.
Start there.
The Suward crypto payments API: REST endpoints, SDKs for TypeScript and Go, a hosted checkout, and signed webhooks. Everything below is described in full at suward.com/docs — no account required to read any of it.
Quickstart
Your integration, end to end
Create a payment with one API call — or skip the API and drop in the hosted checkout page.
Get notified by signed webhooks as the payment moves through its stages. Every notification is cryptographically signed: your server can reject anything that isn’t from Suward.
Act on Accepted, withdraw on Success. The two-stage settlement model is explicit in the API, so “can I ship?” and “can I withdraw?” are separate, answerable questions.
Reliability
Designed for the 3 a.m. failure cases
Retries are safe.
A retried request never creates a second payment — timeouts and crashes don’t turn into double charges.
Notifications can’t be forged.
Webhooks are signed; a spoofed “payment received” can’t trick your fulfillment.
Keys are containable.
API keys carry limits, support rotation, and can be revoked instantly — a leaked key is an event, not a catastrophe.
Upgrades don’t break you.
API changes are backward compatible — the integration you ship today keeps working as the product grows.
Test on real networks.
Suward test tokens are deployed on real networks: your integration is verified against production infrastructure, not a lookalike sandbox.
Testing
Test the whole flow before you take real payments
Anyone can mint Suward test tokens — no registration needed. The tokens are free and valueless; a mint is one on-chain transaction, so your wallet needs a small amount of the network’s native token for gas. Point your integration at real networks, pay with test tokens, and watch the full lifecycle, including test withdrawals on low-fee networks. Prefer to see it working before you build? Our demo store runs the same hosted checkout on test tokens — and its source code is public, so you can read a working integration end to end. To run the complete scenario (creating payments, receiving webhooks, using the dashboard), create a free account: it’s free unconditionally, and you can start accepting real payments right after sign-up — screening runs on every incoming payment, not as an onboarding gate. There is no separate sandbox that behaves differently from production: the same networks, the same API, the same webhooks and dashboard — the only difference is that the tokens are test assets.
Everything else is in the docs
API reference, webhook signatures, settlement stages, asset and network coverage, error handling — documented in full, publicly, at suward.com/docs. And the API is stable by policy: changes are backward compatible and don’t break existing integrations.