Ouvrir un litige sur HstockPlus : le délai, la capture d'écran et la voie la plus rapide

Two facts decide whether disputing is the right move, and both are easier to act on before you start than halfway through the form.

The first is that you are on a clock that started at delivery. The second is that most problems on this site are not solved by disputing at all. Of the orders that have ever reached a dispute outcome, slightly more than half ended with the funds going to the seller. Support tickets over the same catalogue outnumber disputes three to one, and roughly three quarters of the ones that reach a resolution end in a replacement.

So the sequence that works is usually: open a ticket, and keep the dispute in reserve.

The clock, which is measured in hours and starts at delivery

Every order carries a warranty window inherited from the listing. It is written and displayed in hours rather than days, the site floor is four hours, and twelve is the common figure. Once it closes the dispute route refuses you outright with an expired-warranty error, and there is no appeal built into that path.

The important detail is the anchor. The window runs from when the order was delivered, not from when you paid. On instant delivery those are minutes apart and it makes no difference. Where an order sat processing for a day first, the difference is the whole window.

The order also has to be in completed state. An order still processing cannot be disputed, because as far as the system is concerned nothing has been delivered to complain about yet.

At least one screenshot, or the form will not submit

This is the single most common reason a dispute fails to go through, and it is not obvious from the interface. Attachments are not optional and not merely recommended. The submit is refused unless there is at least one uploaded image on it.

Capture the error before you do anything else, because some evidence stops existing once you have retried a login or a seller has touched the inventory. A screenshot of the actual failure message is worth more than a description of it, and the description is what you will be left with if you did not take one.

The reason list is a tree, and one click is not enough

The form does not present four reasons. It presents a two level list: five headings, each opening into two to four specific statements, plus a single Other at the top level for anything that does not fit. The submit requires at least two selections, so you must go into a heading and pick the statement underneath it.

• The account cannot be used. Wrong password or locked or a wrong two-factor code; a verification you cannot complete; banned or invalid; credentials arrived but still do not work.
• Delivery or product content. Nothing delivered; wrong quantity or wrong item; credentials never arrived.
• Order status. Where is my order; the delivery window has passed and there is still nothing.
• How to use. How to log in with what arrived; how to use a cookie, token or two-factor secret.
• Refund or cancel. A direct request.
• Other, which always requires you to write the problem out.

Several of the specific statements also require a written description before the form will accept them. Where you are not required to write anything, the selections you made become the reason text automatically.

One thing to avoid in whatever you do write: do not ask to be contacted outside the site. The reason field is scanned for that, and it will block your submission and put a cooldown on your account rather than simply stripping the line.

What a dispute can end as, and what it cannot

There are exactly three recorded outcomes, and one commonly listed outcome is not among them.

• Released to the seller. The held funds go to the supplier and the order stands.
• Refunded to you. The money is credited to your site balance as a refund transaction. That is the automatic path, and it is the only one that happens on its own. If you want it back on the card or the crypto address you paid from, ask support and it is arranged by hand, because several of the payment routes here cannot be reversed automatically.
• Cancelled. Available in the model and never yet used on this site.

Replacement is not a dispute outcome. A replacement is something a seller performs on a single delivered item: the system pulls the oldest unsold row for the same product, hands it to you, and disables the original. It is recorded against the ticket, not against the dispute, and it fails if the seller has no stock left on that product. That is exactly why the ticket route matters, and why a dispute cannot deliver the thing most buyers actually want.

Measured across everything that has resolved, the split between released and refunded is close to even, with released slightly ahead. Treat a dispute as a coin flip that costs you the option of a replacement, not as an escalation that improves your odds.

The three day clock that runs in the seller's favour

This is undocumented elsewhere and worth knowing before you close anything. Once every ticket attached to a disputed order is closed, a background job waits three days and then resolves the dispute to the supplier automatically. No human decides it and nothing notifies you that the countdown has begun.

An order with any still-active ticket is skipped, so an open conversation is what holds the position. The practical rule is simple: while a dispute is live, do not close or let close the tickets that support it until you have the outcome you want.

What people actually report, which is not what you would guess

Across nearly twelve thousand tickets, the largest identifiable complaint is that the account does not work: it will not log in, it demands a verification the buyer cannot pass, or it is banned. That group is around twenty seven per cent of all tickets.

Receiving the wrong item, which is the reason most guides lead with, is around two per cent. So if you are writing your case, weight it toward proving that access failed rather than toward proving that something was mislabelled. Access failure is the thing sellers here are used to answering and the thing they are equipped to answer with a replacement.

The order that works

1. Screenshot the failure the moment it happens.
2. Check how long your window is and when delivery landed, so you know how much of it is left.
3. Open a ticket. Three quarters of resolved tickets end in a replacement, and a replacement is not something a dispute can produce.
4. If the ticket stalls, dispute before the warranty closes, with the screenshot attached and both levels of the problem list selected.
5. Keep the ticket open until the dispute is decided, because closing it starts a three day timer that ends in the seller's favour.