Preview site — orders are not processed, do not send funds.

One place for order history, saved payout details and a fixed rate on repeat directions. The same button signs you in and creates an account.

Continue with email

An account is the second step of every exchange. Signing in means you accept the user agreement and the privacy policy.

MoneyBeginner · 6 min

How long an exchange takes and what delays it

Euro banknotes and coins

Key takeaways

  • Confirmation time is set by the chain: about one minute on Tron, three on Ethereum, 20 to 40 on Bitcoin.
  • Bank rails have hours: a wire created after the bank's cutoff waits until the next working morning regardless of us.

The half that takes longer is the more interesting one. Four separate clocks run inside one exchange, and any one of them can stall. Here is where the minutes go and which stalls you can prevent.

Four clocks inside one order

Clock one is yours: from opening the order to pressing send in the wallet. Clock two is the chain: from broadcast to enough confirmations for us to credit the deposit. Clock three is the desk: an operator matches the deposit to the order and releases the payout. Clock four is the payout rail: a card processor or a bank.

Confirmations, in minutes per network

We credit a TRC20 deposit once the Tron network confirms it, usually within about a minute. An ERC20 or ETH deposit after 12 Ethereum blocks, about three minutes, sometimes five when the network is busy. BEP20 on BNB Chain lands in under a minute. Solana in seconds. Bitcoin is the slow one: we wait for two confirmations, and a block arrives every ten minutes on average, so 20 to 40 minutes is normal and an hour is not a fault. If speed matters and the choice is yours, Tron or BNB Chain.

The order matters more than it looks. Doing these two things in the wrong sequence is the difference between a locked rate and whatever the market gives you twenty minutes later.

What the operator does meanwhile

Once the chain confirms, a person matches the incoming amount to an open order by address and sum, checks that the amount is within tolerance of what the order expected, runs the address through a chain analytics check, and triggers the payout.

RouteCostSettlementWho you trust
Bank cardshown in the orderdepends on the issuing bankExchanger and issuing bank
Bank transfershown in the orderfollows banking daysTwo banks and a compliance officer
P2P on an exchangeset by the sellerminutes to hoursA stranger and an escrow

Five things that stop the clock

The usual causes are these. A different amount sent than the order stated, usually because the wallet deducted its fee on top. No hash in the chat when the deposit came from an exchange with a shared address. A card that the processor rejected, for example a corporate card or one issued in a country the processor does not serve. And a bank wire created at 17:40 when the bank's cutoff was 17:00.

The 15-minute rate hold and being late

The rate on the order is fixed for 15 minutes from creation. If the transaction is broadcast inside that window, the rate stands for the whole order, however long confirmations and the payout rail take afterwards. If the coins are broadcast late, the order is re-quoted at the rate current when the deposit confirms, up or down, and the chat shows the new figure before the payout goes out. That is why we advise creating a Bitcoin order only after the wallet is open and the fee set.

Try it on your amount
Rate 1 USDT = 1.00 USDFee 0.9%
Exchange USDT → USD

Questions

It has been 40 minutes and the order still says waiting. What now?
Open the hash in a block explorer. If it shows fewer confirmations than we need, the chain is the delay and nothing is wrong. If it shows enough confirmations, paste the hash and the order number in the chat: the deposit is likely sitting unmatched because the amount or address differs slightly from the order.
Do you pay out at night and at weekends?
Bank wires follow bank hours: anything created after the cutoff or on a weekend is sent on the next working morning.
Can I pay extra to be processed first?
No, and it would not help: the queue is not the bottleneck, the confirmations and the rail are.