Knowledge Base
  1. Home
  2. Knowledge Base
  3. Crypto basics
Crypto basics

Confirmations: when is a crypto payment final?

What a blockchain confirmation is, how long Bitcoin, Ethereum, TRON, Solana, XRP and Monero take, and how PayGate.to tells your shop that a payment is confirmed.

3 min readUpdated Beginner
On this page
  1. Typical confirmation times
  2. How PayGate.to handles confirmations
  3. What customers see
  4. Frequently asked questions

When a customer sends crypto, the transaction first sits in a waiting area (the mempool). It becomes confirmed once it's included in a block, and each block added afterwards is one more confirmation. The more confirmations, the harder it would be to reverse, until it's practically impossible.

Typical confirmation times

NetworkBlock timeWhen it's usually treated as final
Bitcoinabout 10 minutes1 to 3 confirmations for ordinary purchases; more for large amounts
Litecoinabout 2.5 minutesa few confirmations
Dogecoinabout 1 minutea few confirmations
Ethereum12 secondsfinalised after about 13 minutes
Polygon, BNB Smart Chain, layer 2 networksa few secondsseconds to minutes
TRON3 secondsabout a minute
Solanaunder a secondfinalised in seconds
XRP Ledger3 to 5 secondsfinal when the ledger closes
Moneroabout 2 minutesreceived funds are spendable after 10 blocks (about 20 minutes)

Times vary with network load. A Bitcoin transaction with a low fee can wait in the mempool for a long time before its first confirmation.

How PayGate.to handles confirmations

  1. The customer pays a one-time payment address created for the order.
  2. When the network confirms the payment, PayGate.to forwards it to your wallet and sends your shop a signed callback with the amount received (value_coin), the coin and the transaction IDs.
  3. Your plugin marks the order as paid. With the API, your code does this; see Verify PayGate.to callback signatures.

Two optional parameters on the wallet request let you tune this:

  • pending=1 sends an extra callback as soon as a payment is seen but not yet confirmed, so you can show "payment received, waiting for confirmation". Never ship goods on a pending callback.
  • confirmations=N sets how many confirmations are needed before the confirmed callback.

Both are described in the crypto payment API reference.

What customers see

On the hosted checkout, the customer sees Waiting for payment... until the payment is detected, then a confirmation. They don't need to stay on the page: the order updates through the callback either way.

PayGate.to hosted checkout showing the amount, the payment address and Waiting for payment
The checkout waits for the payment. The order updates by callback, even if the customer closes the page.

Frequently asked questions

Can a confirmed crypto payment be reversed?

Not by the customer. There are no chargebacks in crypto. In theory very recent blocks can be reorganised, which is why large amounts wait for more confirmations.

Why is my customer's payment still unconfirmed after an hour?

On Bitcoin, the customer probably paid a low fee and the network is busy. It will usually confirm later. Don't ask them to pay again while it's pending: if the network ever drops the transaction, the coins stay in the customer's wallet and they can send them again.

Do I have to wait for confirmations to see the money in my wallet?

Your wallet may show an incoming transaction before it's confirmed. Treat it as final only once it's confirmed, and once your shop has received PayGate.to's confirmed callback.

This guide is also available as Markdown for AI assistants and offline reading.