Blockchain Confirmations Explained for Merchants
A blockchain confirmation is the process by which a transaction gets permanently recorded on the network. The number of confirmations determines how secure and irreversible a payment is.
When a customer sends you a crypto payment, the transaction does not become final the instant they click “send.” First, it enters the mempool, a waiting area of unconfirmed transactions. Then, a validator includes it in the next block. That first block is the first confirmation. Each subsequent block added to the chain after that counts as an additional confirmation. The more confirmations a transaction has, the harder it becomes to reverse.
For merchants, confirmations are the mechanism that guarantees you actually received the money. Releasing a product or service before sufficient confirmations is like handing over goods before the check clears.
What Happens During Confirmation
The confirmation process involves several steps that happen automatically on the blockchain. First, the customer's wallet broadcasts the transaction to the network. Validator nodes verify that the sender has sufficient balance, that the digital signature is valid, and that the transaction follows the protocol rules.
Once validated, the transaction is included in a new block. On proof-of-work chains like Bitcoin, miners compete to solve a cryptographic puzzle to create the block. On proof-of-stake chains like Ethereum, Polygon, and Solana, validators are selected based on their staked collateral. The block is proposed, attested to by other validators, and appended to the chain.
After the first confirmation, each new block added on top further cements the transaction. Reversing a transaction with one confirmation requires reorganizing one block. Reversing a transaction with 64 confirmations would require reorganizing 64 blocks, which is computationally and economically infeasible on any major network.
How Many Confirmations Do Different Chains Need?
Each blockchain has different security properties, block times, and finality mechanisms. Here is how many confirmations are typically required for a payment to be considered safe.
| Blockchain | Confirmations | Approx. Time | Finality Type |
|---|---|---|---|
| Ethereum | 64 blocks | ~13 min | Economic finality |
| Polygon PoS | 64 blocks | ~2.5 min | Checkpoint finality |
| Solana | 1 slot | < 1 sec | Optimistic confirmation |
| Arbitrum | 1 block | ~15 sec | Sequencer confirmation |
| Base | 1 block | ~2 sec | Sequencer confirmation |
| Optimism | 1 block | ~2 sec | Sequencer confirmation |
Solana stands out because its optimistic confirmation mechanism provides near-instant finality. A transaction is confirmed in roughly 400 milliseconds and becomes extremely difficult to reverse after a single slot. Layer 2 rollups like Arbitrum, Base, and Optimism achieve fast “soft” confirmations through their sequencer, with full Ethereum-level security arriving once the rollup data is posted to L1.
Why Confirmations Matter for Payment Security
The risk of accepting a transaction with zero confirmations is a double-spend attack. In this scenario, an attacker sends a payment to a merchant and simultaneously sends the same funds to their own wallet with a higher fee. If the attacker's second transaction gets confirmed first, the merchant's payment vanishes. Waiting for confirmations eliminates this risk.
The required number of confirmations depends on the transaction value and the chain's security model. For a $10 purchase on Polygon, one confirmation is generally sufficient because the cost of attacking the network vastly exceeds the potential gain. For a $10,000 payment on Ethereum, waiting for the full 64-block finality epoch is prudent.
How Zateway Handles Confirmations Automatically
Merchants should not have to think about confirmation counts, block times, or finality mechanisms. Zateway handles all of this behind the scenes. When a customer completes a payment, Zateway monitors the blockchain and waits for the appropriate number of confirmations based on the chain and transaction amount before marking the payment as confirmed.
The checkout page shows real-time status updates to the customer: “Transaction detected,” “Confirming,” and “Confirmed.” Once confirmed, Zateway fires a webhook to your server so you can fulfill the order. The entire process takes under a second on Solana and typically under three minutes on Polygon.
For merchants, this means you get the security of proper confirmation handling without building any blockchain monitoring infrastructure. You integrate once, and Zateway manages the chain-specific logic for every supported network.
Automatic confirmation handling
Zateway monitors confirmations on every chain so you do not have to. Just listen for the webhook.
Get started free