When to open a dispute
Missed deadlines, poor quality, non‑delivery, or payment issues.
Lifecycle
stateDiagram-v2 [*] --> Open Open --> UnderReview UnderReview --> Resolved_Refund UnderReview --> Resolved_Release UnderReview --> Resolved_Other Resolved_Refund --> [*] Resolved_Release --> [*] Resolved_Other --> [*]
APIs
# open curl -X POST $API_BASE/api/disputes -b cookies.txt \ -H 'Content-Type: application/json' \ -d '{"orderId":"ord_123","reason":"non_delivery","details":"No deliverables by due date."}' # add evidence (files) curl -X POST $API_BASE/api/disputes/dsp_123/evidence -b cookies.txt \ -F '[email protected]' -F '[email protected]' # resolve (admin) curl -X POST $API_BASE/api/disputes/dsp_123/resolve -b cookies.txt \ -H 'Content-Type: application/json' \ -d '{"resolution":"refund_partial","notes":"Late by 2 weeks; refund 30%."}'Effects
Reputation updated for the involved organizations.
All participants notified (in‑app + email, if enabled).