You always know when the money is truly yours
Accepting a crypto payment is easy. Knowing when it’s safe to ship against, safe to credit, and safe to withdraw is the hard part. Suward answers that question with an explicit settlement model — two stages, verifiable mechanics, all of it documented publicly.
Two-phase finality
Two stages of certainty: Accepted, then Success
Every payment moves through two explicit stages. Accepted means the payment has accumulated enough confirmations to act on — ship the goods, credit the user, deliver the service. Success means the payment is irreversible — this is when funds become available to withdraw. The two stages are separate on purpose: you can serve your customer fast without ever moving money that could still be undone. All verification happens on the way to a stage, not after it — when Suward tells you to act, the checks behind that stage are already done.
Payment timeline
Chain fork · automatic re-verification
Reorg safety
Chain reorganizations are handled before they reach you
Blockchains occasionally rewrite their recent history — a reorganization. A gateway that credits payments on a single block confirmation passes that risk straight to you. Suward doesn’t: no payment is credited on one block, and reorganizations are handled while a payment is still confirming. If the chain rewrites, affected payments are re-verified automatically against the new state of the chain, and the rare cases the chain leaves genuinely ambiguous go to operator review — all of it before you are told to act, not after. Accepted is the end of that process, not the middle of it.
Atomic balances
Balances that structurally cannot go negative
Your accepted and final balances are updated atomically — a payment’s stage change and the corresponding balance change happen as one operation or not at all. There is no window where a webhook says one thing and your balance says another, and no sequence of events that can drive a balance below zero. Reconciliation stops being detective work.
Every balance movement is attributable to a specific payment at a specific stage.
Ledger · one operation
atomicPayouts under control
Moving money out is a controlled operation
Manual withdrawals run from the dashboard under two-factor authentication and role-based access: viewing balances, initiating payouts, and approving them can be different people.
Auto-withdrawal moves funds to your own wallet by a rule you define — no standing balance at the gateway beyond what you choose, no manual steps to forget.
Every withdrawal fee is quoted before you confirm — treasury works with real numbers, not estimates.
In practice
What this means in practice
You can automate order delivery and user crediting without holding your breath. Your support queue isn’t full of “where is my deposit” tickets, because every payment has an explicit, webhook-reported stage. Your finance team reconciles balances that always add up. And when something on-chain is genuinely ambiguous, a person resolves it before you’re told to act — you don’t find out from an angry customer.