How long does a Litecoin payment take to confirm, and why CoinsFlow counts one confirmation

Litecoin blocks come about every 2.5 minutes. What a confirmation is, why one is enough to call a payment paid, what a reorganisation can undo, how CoinsFlow holds and reverses safely, and when the money is yours to withdraw.

Short answer: a Litecoin payment is usually seen within seconds and confirmed once within about 2.5 minutes. On CoinsFlow that first confirmation is when an invoice becomes paid and the money can be withdrawn. Below is what those words mean, where the risk is, and how it is handled.

What a confirmation is

When a buyer sends Litecoin, their wallet broadcasts a transaction. Within seconds, nodes all over the network hold it in their mempool: the waiting room. It is not yet in the chain. A miner then puts it in a block. The block that includes the transaction is its first confirmation. Every block mined after that is one more.

Litecoin aims for one block every 2.5 minutes. That target is a constant in Litecoin Core, nPowTargetSpacing = 2.5 * 60 seconds, in chainparams.cpp (read 2026-10-24). It is a target, not a promise: blocks are found by chance, so some come in thirty seconds and some take ten minutes. Over a day the average is close to 2.5 minutes. You can watch blocks arrive on our Litecoin explorer.

So the timeline for a typical payment is:

• Seconds: the transaction is in the mempool. CoinsFlow sends invoice.detected.
• About 2.5 minutes: first confirmation. The invoice becomes paid, and invoice.paid is sent.
• A few more blocks: the payment becomes final. The invoice becomes settled, and invoice.settled is sent.

Why one confirmation is enough to call it paid

A transaction in the mempool can still vanish. The sender can replace it, or spend the same coins elsewhere, and a miner can simply never pick it up. That is why "detected" is a signal to show the buyer, not a reason to ship.

Once a transaction is in a block, undoing it means replacing that block. To do that, somebody has to mine a longer chain that leaves it out, which means out-mining the rest of the network for as long as it takes. For one block that happens by accident now and then, when two miners find a block at almost the same moment. For several blocks in a row it is rare and expensive. The deeper the payment, the safer it is, and the cost of undoing it grows with every block while the value of a $20 payment does not.

CoinsFlow calls a Litecoin invoice paid at the first confirmation because by then the ordinary risks are gone: the payment is in the chain, it cannot be quietly replaced, and the only thing left is a reorganisation. For most orders a seller handles, a role in a Discord server, a game key, a month of a service, that is the right trade between speed and safety. If the order is large or cannot be taken back, wait for settled. The two events exist so you can choose per order.

What a reorganisation can do

A reorganisation (a reorg) is when the network replaces the most recent block or blocks with others. A payment in a replaced block is normally not lost: it goes back to the mempool and is mined again in one of the new blocks, usually minutes later, with the same transaction id. The rare bad case is a replacement block that spends the same coins somewhere else. Then the payment is gone for good.

Here is how CoinsFlow handles both:

1. The watcher follows every block's parent hash, so it notices a reorg at once and rewinds to re-scan the window.
2. A payment whose block was replaced is marked orphaned. The invoice goes back to confirming and stops showing as paid. Nothing is reversed yet.
3. If the same payment is mined again, it carries on from there, and invoice.paid is sent again when it has its confirmation.
4. If the payment stays out of the chain for more than two hours, it is treated as a double-spend. The credit is reversed and the invoice goes back to pending with an invoice.pending event, so the buyer can pay again and your system knows the earlier "paid" no longer stands.

Why early credit is safe for us, and what it means for you

Until a payment is final, the money it brought can leave CoinsFlow only in a transaction that spends the very coins it arrived in. If a reorg takes the incoming payment back, it takes that outgoing transaction back with it, because the coins it spent no longer exist. So a merchant can withdraw at one confirmation without the platform taking on the risk. The one person trusting a single confirmation is the merchant who delivers on paid for a large order. That is a decision we leave to you.

For the money to move freely, to another merchant, as a payout from mixed coins, or on a second withdrawal, it has to be final. CoinsFlow releases it at a depth that depends on the payment's value in dollars at the time:

• Up to $50: 2 confirmations, about 5 minutes.
• Up to $500: 4 confirmations, about 10 minutes.
• Up to $5,000: 6 confirmations, about 15 minutes.
• Larger: 12 confirmations, about 30 minutes.

Two safeguards sit around those tiers. The dollar price used has to be less than an hour old, or the payment waits for the full 12 blocks. And at most $5,000 worth of all merchants' payments in any one block can become final early; whatever a block brings beyond that waits for the full depth too. Somebody who can undo a block undoes everything in it, so the cap is per block, not per payment.

For comparison, Bitcoin on CoinsFlow is also paid at 1 confirmation, with final tiers of 1, 2, 3 and 6 blocks, and its blocks are about ten minutes apart.

When the money is withdrawable

• At paid (1 confirmation): the amount, less our 0.5% fee, is in your balance. You can withdraw it to your own Litecoin address at once, on the coins it arrived in. The smallest withdrawal is 0.0001 LTC and the fee covers the network cost, quoted before you confirm. We call a withdrawal confirmed at 6 Litecoin blocks.
• At settled (2 to 12 confirmations by value): the money is final and free to go anywhere.
• At any time, a buyer who holds Litecoin in a CoinsFlow balance can pay you with Pay with CoinsFlow. That is an internal move, so the invoice is paid and final at once, with no block to wait for.

Practical rules for sellers and bot builders

• Show "payment seen" on invoice.detected. Deliver on invoice.paid. For anything expensive or irreversible, deliver on invoice.settled.
• Expect to hear about the same invoice more than once, and act on the status in the event, not on the order the events arrived in.
• If invoice.pending arrives for an invoice you marked paid, treat that as the last word: the payment did not survive.
• Do not promise a buyer "2.5 minutes". Say "usually a few minutes, sometimes longer".

If you are setting up webhooks, the API docs list every event with its meaning. The whole confirmation table for every network is in the docs too.