Crypto payments for marketplaces
Buyers and sellers on different continents, and cards failing on either side. Suward gives every order a unique payment address, screens every incoming transaction before it is credited, and keeps reconciliation exact at any volume. One flat 0.4% — the same rate as every other merchant.
0.4% per payment · screening included
Pains, solved
Four problems every marketplace team knows
“Our buyers and sellers are in different countries — cards fail on both sides.”
Payment geography on a marketplace is two-sided, and card acquiring cuts into both. Stablecoins and major cryptocurrencies work wherever your users are: one API, a growing list of assets across multiple networks, and a hosted checkout that needs no frontend work.
Explore Payments“At our volume, tenths of a percent are real money.”
At marketplace volume, tenths of a percent add up fast — the full math is public on /pricing.
Full pricing math“Reconciling thousands of orders by hand doesn’t scale.”
Every order gets a unique payment address, so every transfer matches an order — nothing to reconcile by hand. Balances update atomically with stage changes, and a retried request never creates a duplicate payment.
How settlement works“Incoming payments from payers we’ve never seen — who checks them?”
Every incoming transaction is screened for AML and sanctions exposure before it is credited to your balance. Sanctioned jurisdictions are blocked automatically, and suspicious patterns are monitored continuously — included in the 0.4% rate.
How screening worksOrder lifecycle · m-88122
Buyer confirms the quoted amount. Transfer observed on-chain; screening runs. Nothing is credited yet.
Enough confirmations to act on — a signed webhook releases the order to the seller.
Irreversible, ready to withdraw — under 2FA and role-based access.
The transfer is tied to order m-88122 by its unique address — reconciliation is exact.
Typical scenario
How an order gets paid, at any volume
A buyer checks out and sees the exact amount to pay, with every fee quoted before they confirm. The order gets its own payment address, so the incoming transfer can only belong to that order. Screening runs before anything is credited. At Accepted — enough confirmations to act on — a signed webhook tells your platform to release the order. At Success, the payment is irreversible and ready to withdraw. The same flow holds at ten orders a day or ten thousand.
Orders run onPayments · seller and buyer balances run onStatic Wallets
The modes
Payments for orders. Static Wallets for balances.
Marketplaces usually need both: one-off payments with a unique address per order for the buy side, and permanent deposit addresses where sellers or buyers hold a balance. Both run on one API, with the same screening, the same settlement model, and the same flat 0.4%.
For the committee
Pages to forward to your team
If you’re introducing Suward internally: a flat 0.4% with compliance included, a unique address per order, screening of every incoming transaction before it is credited, and withdrawals under 2FA and role-based access. Every claim is verifiable on the pages below.
For your CTO
The settlement model, unique address per order, and signed webhooks — settlement, payments, developers.
For your CFO
The complete price math — pricing.
For compliance
Screening of every incoming transaction before crediting — compliance.
Walk us through your marketplace
Order flows, seller balances, payout approvals — every marketplace runs differently. Talk to us and we’ll map Suward onto yours.