Usually feels like
Minutes
You stay at the keyboard and it finishes there.
This is a write that takes locks rather than a page that can be served from a cache, so it queues under load while still finishing at the keyboard.
The wait, in plain words
The cart was ready, the button said something final, and now the page is not coming back. No order number, no confirmation, just a browser still asking for something.
What sits in this gap is the difference between having pressed and having an order. Nearly everything you have waited for until now was a read. This one is a write, and a write with several parts that have to agree with each other.
It normally resolves at the keyboard, which is what puts it in this band. What it must not do is resolve twice, and that is the part worth carrying away from this card.
Underneath, while nothing moves
Placing an order moves money inside the market. Your spendable balance goes down, an escrow record opens holding that amount, an order row is created with an identifier attached, and something lands in the vendor queue. Often an encrypted block of text you supplied is stored against the order, and often a stock count somewhere is reduced.
Those parts have to agree. A market that reduced your balance and failed to create the order would have a mess to unwind by hand, so any sane implementation wraps the whole set so that either all of it happens or none of it does. Wrapping means locks, and locks mean waiting when the market is busy, because your write has to queue behind other writes touching the same rows.
A page view can be answered from a cache and can be answered by any of several machines. This cannot. It has to reach the place where the truth is kept, and it has to take its turn there.
That is the whole reason a duplicate press is dangerous here rather than merely rude. A repeated read costs a page. A repeated write can cost a second order, a second escrow holding, and a second spend of the same balance. Some markets defend against that with a token that turns the second press into nothing. You cannot see from outside whether this one does, so the safe assumption is that it does not.
There is a second reason to be patient with this particular gap. The response you are waiting for is not the work. The work happens on the far side, and it carries on whether or not the answer ever reaches your browser. A path that dies after your press has been received still leaves an order behind it, complete and paid for, sitting in a list you have not looked at yet. Treating silence as failure is how a single order becomes two.
Behaving, and not behaving
After a press that never returned, the question is not whether the market is slow. The question is whether the order exists.
A write that landed
The order list has a new entry in it, whether or not the page that created it ever came back to you.
The spendable balance has gone down by the right amount and the difference is sitting in escrow against that order.
A press that was lost
No new order anywhere in the list, and the balance is exactly where it was before you pressed.
Or there are two orders where there should have been one, which is what a second press buys and what it costs to undo.
The balance line is the fastest tell. Money that has moved means a write landed, no matter what your browser showed you. From there the order is either visible in the list or it is a support conversation, and support runs in a far slower band than this one.
Once the order exists the clock changes completely. Escrow begins counting toward a release nobody asked you about, and that is a wait measured in days rather than one that ends at the keyboard. Two orders means two of those clocks, both running, both holding money that is no longer yours to move.
Safe to do meanwhile
Everything useful here is about finding out what happened rather than making it happen again.
- Open the order list in a second tabA separate request answers the only question that actually matters.
- Look at the balance before deciding anythingA balance that moved is a write that landed.
- Keep whatever you typed into the orderIf it has to be entered again you do not want to be rebuilding it from memory.
- Read what escrow does nextThe order existing starts a wait that cannot be paused once it is running.
What makes it longer
Order writes get slow for reasons that have little to do with you, and get duplicated for reasons that have everything to do with you.
- Pressing the button a second time. This is the most expensive habit in the band and it is the easiest one to acquire.
- A busy market, where writes queue behind other writes touching the same rows.
- A slow path, which can lose you the response while the write goes through regardless. See a page that half arrived.
- A front layer that decides to challenge you in the middle of a checkout.
- A vendor with limited stock, where the market has to check and reserve before it can accept anything.
What this card is not. This card is not about what to order or what to write into one, only about the gap between a press and a record.