Usually feels like
Days
Tomorrow is the right time to look, not tonight.
It sits in days because it needs two schedules to overlap, sometimes three, and none of them is yours.
The wait, in plain words
An agreement is not a transfer. Two people typing that they agree produces a shared understanding and nothing else. Somewhere after that, one of them has to open an interface and enter what was agreed, and until that happens the agreement exists only as text in a thread.
This is a negotiation rather than a process, which is why it does not behave like the other waits here. Processes have stages you can watch. Negotiations have two schedules, three when staff are involved, and they only advance where the schedules overlap.
Most of the frustration on this card comes from that mismatch. Agreement was reached in an evening and then took days to become real, and nothing in between was broken.
Underneath, while nothing moves
A partial settlement in particular has to be typed by somebody, because a partial is not a state the mechanism reaches on its own. Full release and full refund are usually a button each. Anything between them is a figure a person enters, which means a person has to be at a keyboard, awake, and willing.
- Agreed. Both sides have said the same figure in a thread. Nothing has moved and nothing is committed.
- Entered. Somebody has opened the order and performed the action. This is the step that needs a person, and the step that slips.
- Credited. The amount appears against your account at the market, which is a bookkeeping change rather than a movement of coins.
- Withdrawn. You take it out, which begins a wait of its own: a withdrawal being sent, with the network wait behind it.
The wait before agreement and the wait after it are different animals. Before, you are waiting on a decision, and messages have a purpose because they carry the argument. After, you are waiting on an action, and messages carry nothing but a reminder. Confusing the two is why people settle a refund and then carry on negotiating it.
If staff are involved, add a queue. A refund arranged inside a dispute gets entered by a reader working through a list, so it inherits everything on a dispute being looked at, including the fact that the case has to be read before anything can be typed.
The deadline underneath is the settlement window on the original order. Negotiating does not pause it in most order flows, and an agreement reached after it closes is a favour rather than a mechanism. That is the trap here: talking politely while the only leverage in the room quietly expires. See escrow running down to auto release.
Behaving, and not behaving
A refund that is moving is one where both sides know which stage they are in. The same wait becomes a problem as soon as the stages blur.
A settlement that is moving
One figure was agreed, once, in plain terms, and both sides described it the same way afterwards.
You know who has to enter it, and you have allowed that person a stretch of their own day in which to do it.
A settlement that has stalled
The figure has been revised twice since it was agreed, so there is no longer an agreement to enter.
You are waiting on money nobody has been asked to send, because the conversation ended before anyone said who would act.
The commonest failure is not bad faith. It is that each side believed the other was going to perform the action and neither said so out loud. One sentence naming who enters it, and when, removes most of this wait.
The second commonest is reopening. A settlement reopened after agreement resets the negotiation, and the person who thought the matter was closed now has to think about it again, from the bottom of their list.
Safe to do meanwhile
This wait is short on useful things to do and long on things not to do, which makes the few useful ones worth doing properly.
- Write the agreement in one lineWhat amount, to whom, entered by whom. Ambiguity here turns into days later.
- Name who performs the actionRefunds stall on this more often than on anything else.
- Watch the balance, not the threadA credit lands against the account. It does not announce itself in the conversation.
- Keep the window in viewA negotiation running past the settlement point is a negotiation with nothing behind it.
What makes it longer
Refunds stall in a small number of recognisable places, and most of them are about who was expected to act.
| Where it stops | Why it sits there |
|---|---|
| After agreement, before entry | The action needs a person at a keyboard, and that person has a day of their own. |
| During entry, on the figure | A partial has to be typed. A figure agreed loosely is a figure that gets queried. |
| At the credit | The amount arrives as a line against the account rather than as a message, so nobody announces it. |
| At the withdrawal | That is a separate wait with a separate mechanism, and it starts only when you start it. |
- Reopening a figure that had already been agreed.
- Agreeing in one place and asking about it in another, so two threads hold half the story each.
- Assuming a credit will be announced, when it is a line in an account and nothing more.
- Letting the original settlement window run out while the conversation stays friendly.
What this card is not. This card is not a way of getting money back, and it takes no view on who ought to have it.