Home / Database / Orders and disputes
The dispute was raised and there has been no visible movement.
Disputes are read by people working through a queue. Movement is often slower than it feels, and the strongest thing you can do is make your case easy to read.
Whoever is deciding has two accounts of the same order, whatever the market recorded, and both parties histories. They are looking for which version fits the record. Dates, order references and consistency do that work. Volume and tone do not.
Add a short factual follow up rather than a longer version of the same case. Escrow is holding the funds in the meantime, so the delay costs time rather than money.
Escrow needs two of three keys. In a normal order those are yours and the vendor. In a dispute the market key becomes the tiebreaker, which is the only point at which the market has any say over the money. It is a narrow power and it is the reason arbitration exists at all rather than the market simply refunding whoever complains loudest.
Because it is a judgement between two accounts of the same order, the material that helps is the material that can be checked. Dates that line up, an order reference, listing terms quoted accurately. The material that does not help is a description of how unfair the situation feels, however true that is.
| Severity | Problem | Area | Likely cause |
|---|---|---|---|
| Common | Order funded but stuck in pending Escrow is funded and the order has not moved for days. | Orders and disputes | The vendor has not marked dispatch, which is often just their schedule. |
| Serious | The vendor has stopped responding Messages go unanswered after an order was funded. | Orders and disputes | Vendor inactive, overloaded, or no longer operating. |
| Common | BlackOps will not load at all The address times out or the page never finishes loading. | Access and loading | A degraded Tor circuit on your side, or a flood against that specific address. |