SwapSS learn

Block confirmations and payment finality

A blockchain transaction can appear quickly and still need confirmations before a merchant treats it as settled. Finality policy is part of payment safety, not a cosmetic delay.

Mempool is not settlement

A pending transaction can be replaced, fail, or never confirm. Checkout and exchange flows should show an intermediate confirming state instead of treating first sighting as final.

Different chains need different policies

Confirmation requirements depend on chain design, asset type, amount, and business risk. The merchant should rely on the gateway status rather than hard-coding one rule for every network.

Fulfillment should follow documented status

Digital goods, subscriptions, marketplace credits, and exchange payouts all need a clear fulfillment boundary. The docs should say which status is safe to use for fulfillment.

What customers should see

The status page should show that the payment was detected, that confirmations are in progress, and that no extra action is needed unless the payment becomes late, partial, or mismatched.