How Long Does a USDT Payment Take? Confirmations, “Pending” and “Settled” Explained
Short answer: there is no single answer, because “sent” and “safe to ship” are different moments. A USDT transfer first waits to be included in a block, then collects confirmations as further blocks are added; a business treats the payment as final once it reaches the confirmation threshold it has chosen. The wait therefore depends on the network used, the threshold set, current congestion, and how quickly the payer’s wallet or exchange actually broadcasts the transfer. For a business accepting stablecoin payment, the practical rule is: never promise minutes, explain stages, and ship on “settled”, not on “sent”.
The four stages of a USDT payment
| Stage | What is happening | What your business should do |
|---|---|---|
| 1. Initiated, not yet on-chain | Payer pressed send; the transfer waits in a queue or has not been broadcast yet | Acknowledge it, but do not ship. Low-fee transfers can stall, and exchange withdrawals can be held internally |
| 2. Included, confirming | The transfer is in a block and collecting confirmations | Show the order as “confirming”. Tell the customer you can see the payment |
| 3. Threshold reached (settled) | Confirmations meet the threshold you or your provider set | This is the moment to release goods or service and recognise the receivable |
| 4. Booked and reconcilable | Amount, fee and hash are recorded against the order | Finance matches it to the invoice at period close |
The most common misunderstanding is treating stage 1 as stage 3: the customer’s “sent” screenshot is the first, your “settled” status is the third.
What a confirmation is, and why you wait for some
Public blockchains occasionally replace their most recent blocks (a reorganisation). A transaction sitting in a very recent block is therefore slightly less final than one buried under many later blocks. The confirmation count is simply how many blocks have been added since. More confirmations means it is progressively harder to reverse; fewer means faster but with a small residual risk. Choosing the threshold is a risk-versus-speed decision, not a technical constant, and many businesses set higher thresholds for larger amounts. Ask any provider how their thresholds are set before you rely on them.
Why the wait differs by network
| Factor | Effect on waiting time |
|---|---|
| Block interval of the network used | Sets how long each confirmation takes. It varies widely between networks, so check the public figure for the network you actually use |
| Confirmation threshold | Multiplied by the block interval, it gives the theoretical wait; larger amounts often use higher thresholds |
| Congestion and fee level | An underpriced transfer can sit unconfirmed far longer than the theory suggests |
| Payer’s wallet or exchange | Some withdrawals are reviewed or batched before broadcast; that delay is invisible from your side |
Two of these four are outside your control, which is why quoting an exact arrival time to customers is risky. For guidance on choosing networks, see How to Accept USDT Payments as a Business.
“Confirming” versus “settled”
| Confirming | Settled | |
|---|---|---|
| Ship goods or release service? | Not recommended, unless low value and you accept the risk | Yes |
| Recognise the receivable? | No — the amount can still change | Yes |
| Withdraw or pay out the funds? | No — balance not yet available | Yes |
| What to tell the customer | “We can see your payment and are confirming it” | “Payment confirmed” |
If your system pushes status changes to downstream tools, make sure they act on “settled” only; booking on “confirming” causes duplicates and mismatched amounts later. See USDT Payment Reconciliation: A Finance Team’s Month-End Checklist.
“I already paid”: five checks using one transaction hash
- Ask for the transaction hash. A screenshot cannot be verified independently; a hash can. No hash usually means the transfer was never completed.
- Look the hash up on the correct network’s block explorer. Not found means it was never broadcast; found but pending means it is waiting for inclusion.
- Compare the receiving address with the one issued for this order, character by character.
- Compare the network and token. USDT on one network is a different asset from USDT on another; funds sent on the wrong one will never appear where you are looking.
- Compare the amount. A shortfall is often the payer’s exchange withdrawal fee. Handle it under the tolerance rule you wrote into your payment terms.
After these five checks the problem is always one of: not broadcast, stuck pending, wrong address, wrong network, or wrong amount. Payment terms that fix the network, quote expiry and shortfall rule in advance remove most of the back-and-forth; wording is covered in How to Invoice Overseas Clients in USDT.
Reducing support load
- Show the network and exact amount on the payment page, not just an address.
- Describe stages (“initiated → confirming → confirmed”) instead of promising minutes.
- Write the rules for shortfalls, late payments and duplicates into your terms before the first dispute.
Copay’s stablecoin cashier records each order’s status, amount, fee and hash in one place for businesses with an overseas entity, so support and finance read the same evidence rather than checking explorers by hand. This is operational guidance, not legal or tax advice.
Frequently asked questions
How long does a USDT payment take to arrive?
It depends on the network used, the confirmation threshold the receiver requires, network congestion, and how fast the payer’s wallet or exchange broadcasts the transfer. Rather than promising minutes, explain the stages: initiated, confirming, confirmed.
What is a block confirmation?
It is the number of blocks added to the chain after the block containing your transaction. More confirmations make a reversal progressively less likely, which is why businesses wait for a threshold before treating a payment as final.
Can I ship goods while a USDT payment is still confirming?
It is not recommended except for low-value orders where you accept the small risk. Ship, release service and recognise revenue on the settled status, not on the payer’s “sent” screenshot.
A customer says they paid but I see nothing. What should I do?
Ask for the transaction hash, look it up on the right network’s explorer, then compare receiving address, network and amount against the order. The problem will be one of: not broadcast, pending, wrong address, wrong network or wrong amount.
Why did I receive less USDT than the invoice amount?
Most often the payer’s exchange deducted a withdrawal fee from the amount sent. Decide in your payment terms whether you ask for the difference or accept a tolerance, and record the shortfall explicitly. This is operational guidance, not legal or tax advice.
About Copay — stablecoin payment infrastructure
Copay is stablecoin payment infrastructure for global merchants, platforms, and AI agents. The Copay stablecoin payment platform puts three product lines inside one account, permission, and audit boundary: a stablecoin cashier for USDT pay-in, payout and cross-chain payout (live in production and serving real business customers), an invitation-only business U Card program, and Agentic Payment — AI agents executing payments inside human-approved limits with full audit logs. Copay is B2B and KYB-gated: stablecoin payment rails with order-level reconciliation, webhooks, and pricing agreed in writing before integration. More about Copay.
Form: copay888.com/book-demo · Telegram: @copay8888 · Email: [email protected]