How many confirmations does a crypto payment need?
A customer presses "send" and their wallet says the payment is done, yet your checkout still says "confirming". That gap is the confirmation wait. This post explains what a confirmation is, how many easyway waits for on each of its 15 networks, and what your shop should do while it waits.
What a confirmation is
A blockchain groups transactions into blocks. When a payment lands in a block it has one confirmation; every block added after it is one more. On most chains a very recent block can still be replaced, and with it the payment, so a gateway counts a payment as received only after enough blocks sit on top that undoing it is no longer realistic. Some networks work differently and declare a block final on their own; for them, waiting for that signal is the confirmation.
The point of waiting is simple: once an invoice is paid, you ship the order. Marking a payment as received that later disappears from the chain would mean shipping for free.
Confirmations per network
These are the counts the gateway uses today. Every coin and token on a network waits for the same number of confirmations as the network itself.
| Network | Coins and tokens | Confirmations | Counted as final when |
|---|---|---|---|
| ARB | ETH, USDT, USDC | 240 | blocks built on top |
| Polygon | POL, USDT, USDC | 64 | blocks built on top |
| BASE | ETH, USDC | 30 | blocks built on top |
| OP | ETH, USDT, USDC | 30 | blocks built on top |
| TRON | USDT, TRX | 19 | blocks built on top |
| BNB Smart Chain | USDT, BNB, USDC, FDUSD, CAKE, TWT | 15 | blocks built on top |
| Ethereum | USDT, ETH, USDC, DAI, SHIB, PEPE, PYUSD, LINK, UNI, AAVE, ONDO, ENA, CRV, GRT, SKY, USDS, USDe, MNT, ARB, WLD, MANA, SAND, IMX, GALA, FET, JASMY, SPX, XCN, APE, AXS, CHZ, 1INCH, PENDLE, ETHFI, ZRO, BAT, LPT, ZRX, SUSHI, BAL, COMP, RPL, ANKR, CVX, GLM | 12 | blocks built on top |
| Avalanche C-Chain | AVAX, USDT, USDC | 10 | blocks built on top |
| Dogecoin | DOGE | 6 | blocks mined on top (proof of work) |
| Dash | DASH | 4 | blocks mined on top (proof of work) |
| Litecoin | LTC | 4 | blocks mined on top (proof of work) |
| Bitcoin | BTC | 2 | blocks mined on top (proof of work) |
| Solana | SOL, USDT, USDC, BONK, WIF, RENDER, JUP, PYTH, JTO, RAY, W, FARTCOIN, TRUMP, PENGU, POPCAT | 1 | the network marks the block finalized |
| TON | USDT, GRAM, NOT, DOGS, CATI, HMSTR | 1 | the transfer is in the chain |
| XRP Ledger | XRP | 1 | the ledger is validated |
The counts are different because the networks are different, not because one coin is safer to accept. ARB needs the most blocks (240) because its blocks are produced quickly, so many of them still pass in a short time. Bitcoin needs only 2 because each of its blocks takes far more work to replace. Solana, TON and XRP Ledger need a single confirmation because these networks decide finality themselves instead of leaving it to a block count.
What happens while a payment confirms
As soon as the transfer is seen, the invoice moves from pending to confirming and your server receives an invoice.confirming webhook. The hosted payment page shows the customer that the payment was detected, so they don't pay twice. When the last confirmation arrives the invoice becomes paid (or underpaid if less than the amount arrived) and you get invoice.paid.
Treat confirming as "payment on the way": show it on the order page, maybe hold stock, but do not ship and do not unlock a download. Only invoice.paid means the money is final in your wallet. Verify the webhook's signature before you trust it; the webhook signature guide has code for Node.js, PHP and Python.
Confirmations and the invoice timer
An invoice has an expiry time, but a slow confirmation does not lose the payment. Once the customer has picked a coin, the payment stays watched for a while after expires_at (7 days for a fresh address derived from your extended public key, some hours where invoices share one address of yours): a payment that arrives in that window is still recorded and the invoice turns paid or underpaid, flagged late, with the usual webhook. A cancelled invoice is the exception: it stays cancelled, the payment is recorded against it and you are e-mailed, and any refund is yours to send from your own wallet. So keep handling invoice.paid for orders you already marked as expired. The underpaid and late payments guide has a handler for every case.
Which networks feel fastest to customers
If a short wait matters to you — say, a customer standing at a counter, or a digital product they expect at once — offer the networks with a single confirmation (Solana, TON and XRP Ledger) next to the ones your customers already use, and let them choose at checkout. For stablecoins, the USDT networks comparison also compares network fees, and pricing lists the plans. The live list of assets, with the smallest invoice and confirmations as fields, is available from the API at GET /v1/assets (see the API docs).