How crypto payment confirmations work

Why gateways wait at all

A transaction that appears in the latest block is not yet history, it is a proposal that history will probably keep. Blockchains occasionally reorganize: a competing block wins, and transactions in the loser get reshuffled or, in the worst case, replaced by a conflicting spend of the same coins. The deeper a transaction sits under later blocks, the more expensive that replacement becomes, until it is economically absurd. Waiting for confirmations is how a gateway converts "probably" into "safe to ship the order". Waiting too little exposes merchants to double-spends. Waiting too long costs sales to impatience. The right number is a per-chain judgment, not a constant.

The four finality models

Probabilistic proof-of-work is Bitcoin's model, shared by Litecoin, Bitcoin Cash, Dogecoin, and Monero: no block is ever formally final, reversal just gets exponentially harder with depth, so the rule is a confirmation count sized to each chain's hashrate and history. Ethereum and its layer-2 family run checkpoint finality: proof-of-stake validators finalize whole spans of blocks, so the rule is waiting for the network's own finalized marker rather than counting to a magic number. TRON uses delegated-proof-of-stake solidification, where a supermajority of block producers confirming makes a block solid, and the practical rule is a small count past solidification. And the BFT single-slot family, XRP, Stellar, Solana in effect, and TON, reaches consensus per ledger or slot: once validated, a transaction is final with no reorg window at all, which is why those chains confirm in seconds.

Live rules, per chain

These are the rules this platform is applying right now, rendered from live configuration rather than typed into the article. When an operator retunes a chain's confirmation depth, this table changes with it.

What happens between detection and confirmation

A good gateway tells the merchant twice. Detection fires the moment the payment appears on the network, which is when a checkout can show the customer that their transfer arrived and is being counted. Confirmation fires when the chain's rule is met, which is when the order should actually ship. Between the two, edge cases live: a payment short of the invoice by more than the tolerance becomes an underpayment the merchant can accept or refund, a payment after the invoice expired can revive it within a grace window, and a reorganized block can send a once-confirmed payment back to counting. Merchants never need to handle those cases by hand, but knowing they exist explains why serious gateways publish state machines instead of a single paid flag.

Common questions

Why does Bitcoin take so much longer to confirm than XRP or Solana?

Different consensus designs. Bitcoin's proof-of-work never formally finalizes anything, so safety comes from depth, several ten-minute blocks stacked on top of the payment. XRP, Stellar, Solana, and TON reach explicit consensus per ledger or slot, so a validated transaction is final in seconds with no reorg window to wait out.

Can a confirmed crypto payment be reversed?

On BFT-style chains, no: validation is final. On proof-of-work chains, a deep reorganization could in principle unwind a confirmed payment, which is why confirmation counts are sized so that doing so would cost an attacker far more than the payment is worth. Gateways also track reorgs and adjust payment status if one touches a contributing transaction.

Who decides how many confirmations a payment needs?

The gateway sets a per-chain rule, ideally informed by each network's hashrate, history of reorganizations, and finality design. On this platform the rules are live configuration rather than code constants, so they can be tightened after an incident on a chain without redeploying anything, and the table above always shows the current values.

Does the customer have to wait for full confirmation at checkout?

They wait to see it confirmed, but they do not have to sit there. A well-built checkout shows detection immediately, so the customer knows the payment registered, and the merchant ships when confirmation lands. For low-value goods some merchants fulfil on detection for fast chains, accepting the small residual risk for the better experience.