Hosted checkout

Take crypto payments without building a checkout.

Launch a compliant checkout today — no UI to build. Send the customer one link; Suward shows the hosted page, mints a unique address, watches the chain, and hands the status back the moment it settles.

Every payer screened for AML.
Integration

One redirect. That's the integration.

You create a payment, Suward returns a checkout URL, you send the customer there. When the money clears, we tell you. Suward handles the checkout UI, wallet logic and address handling for you. If your store can redirect to a payment link, it can take crypto through Suward. Marketers and ops people ship this; a backend developer is nice to have, not required.

01

Create the payment

Set the amount, asset and network. The request is idempotent, so a retry never doubles the order. Handles payments up to 60,000 per charge.

create-payment.sh
curl -X POST https://api.suward.com/v1/payments \
-H "X-Api-Key: sk_live_••••••••" \
-H "Content-Type: application/json" \
-d '{
"amount": "120000000",
"asset": "USDC_BASE",
"externalId": "order-7842",
"webhookUrl": "https://your-store.com/hooks/suward"
}'
# amount: smallest unit — USDC has 6 decimals, so 120000000 = 120 USDC
02

Redirect the customer

Suward returns a checkout URL. Open it in the customer's browser, or drop it into an email or invoice.

03

Get the result

The page shows live status; you receive signed webhooks on every transition. Pending → Accepted → Success.

Payment activity
120.00USDC
Base·0xa1b2…c3d4
final
50.00USDT
Optimism·0xe5f6…g7h8
accepted
Never negative
Payer experience

The checkout page, from the payer's side.

The payer lands on a clean Suward page with a single job: pay this amount, to this address, on this network, before the timer runs out. A QR scans straight into any wallet. The address is unique to this one payment and never reused, so two orders never collide. While the customer pays, the page sits in "watching the network" and updates itself as confirmations come in.

  • QR plus a copyable address
  • Live countdown before the payment expires
  • Self-updating status, no page refresh
  • Underpayments are tracked and shown as PartiallyPaid
Compare

Hosted checkout or Payments API?

Same engine underneath, two ways to drive it. Hosted checkout gives you the whole payment screen and you write no UI. The Payments API gives you the raw payment object so you can build your own checkout, your own branding, your own flow. Most teams start hosted to go live this week, then move to the API when they want the screen to live inside their own product.

Hosted checkoutPayments API
Front-end workNone, Suward hosts the pageYou build the checkout UI
Time to first paymentSame dayAn evening with the quickstart
Branding controlSuward pageFully yours
Status deliveryWebhooks + page statusWebhooks or poll
Good to know

The rest is shared platform.

Networks & assets

7 networks, 21 assets — USDT, USDC and each chain's native coin. You choose the asset and network when you create the payment, and what the payer sends is exactly what lands in your balance — clean to reconcile.

Finality

Pending → Accepted → Success. Accepted the moment it's safe to release the order, Success once it's final and ready to withdraw. Signed webhooks fire on every transition.

Pricing

0.4% per payment, minimum $1, plus a small fixed network fee per chain. The floor is 1% on a $100 payment and trends toward 0.4% on larger ones.

Accept your first crypto payment today.

From signup to your first confirmed payment in one session. Point the same redirect at production when you're ready — or talk to us first.