SwapSS learn
Crypto payment statuses
A useful crypto checkout does not collapse every payment into paid or failed. The merchant needs to know whether the customer has not paid, the chain is still confirming, the amount is wrong, the invoice expired, or support needs to review the payment.
Do not fulfill too early
A payment broadcast is not the same as a settled merchant order. Fulfillment should wait for the status that the gateway documents as safe for the selected asset, network, and business rule.
Expose mismatch states clearly
Underpaid, overpaid, wrong-asset, wrong-network, late, and duplicate-payment states reduce support confusion. Each state should have a visible next step for the merchant and customer.
Keep review state honest
Some payments need manual review because amount, timing, network, compliance, or recovery evidence is unclear. Public copy should say review required instead of hiding the condition behind a vague failure.
What SwapSS Pay should expose
Docs and dashboard surfaces should align on status names, webhook event names, customer-facing checkout text, merchant balance movement, and refund or support evidence.