Disputes and buyer protection — v0.1

Status: descriptive. It describes release/0.545.0. The code is in collector/routes/disputes.py (routes) and collector/store/disputes.py (the read-model). The buyer journey is in docs/buyer-protection.md. Gaps are listed under §7 *Open*.

If something is wrong with a marketplace item you have access to, you can report it. The seller can answer, and the platform decides the outcome. Every step is recorded as an event, so the result can be traced:

Body: {kind: memory|session|collection, id, tenant?, reason, detail}. You must be signed in (401 not_logged_in).

detail must be at least 10 characters (400 bad_dispute).

were granted it, or are a member of its tenant. Otherwise the answer is 403 no_access. Takedown reports (copied, unsafe) do not need access.

and whether the report is within the refund window. The window is 14 days by default (REFUND_WINDOW_DAYS) and is counted from the purchase's checkout creation.

is deliberately not applied here).

Anyone, including someone without an account, can also report a listing through the public notice form (POST /support/report, DSA Art. 16, see specs/support). When the listing exists, that report opens a dispute with by: "report:<id>".

The buyer, the seller (matched by the listing owner's handle) and admins may reply. Text is capped at 2000 characters. A seller's first reply moves the status open → answered (store/disputes.py:Disputes.fold).

GET /memory/disputes (list_disputes):

Only a global admin resolves (403 otherwise). A resolved dispute cannot be resolved again (409).

1. What you can do

2. Opening a dispute — POST /memory/disputes (open_dispute)

3. Conversation — POST /memory/disputes/{id}/reply {text} (reply)

4. Resolution — POST /memory/disputes/{id}/resolve {outcome, note?, version?} (resolve)

5. Subscription withdrawals

6. Records and retention

7. Open