Skip to main content

Disputes & Reputation

When to open a dispute, how it’s resolved, and how scores update.

C
Written by Catalin Fetean
Updated over 3 weeks ago

Audience: Buyers, Sellers, Admins, Procurement
Outcomes: Fair, traceable resolutions; transparent partner selection

Disputes — API & outcomes

# open dispute 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 curl -X POST $API_BASE/api/disputes/dsp_456/evidence -b cookies.txt \ -F '[email protected]' -F '[email protected]' # resolve (admin) curl -X POST $API_BASE/api/disputes/dsp_456/resolve -b cookies.txt \ -H 'Content-Type: application/json' \ -d '{"resolution":"refund_partial","notes":"Late by 2 weeks; refund 30%."}'
  • Resolutions: refund_full, refund_partial, release_to_seller, other.

Reputation & scoring

Signals

  • On-time milestone rate

  • Dispute frequency & outcomes

  • Refund/chargeback rate

  • Counterparty feedback (if enabled)

Usage

  • Thresholds in vendor selection; coaching for underperformers.

Governance

  • Scores update immediately after events; changes are audit-logged.

QA checklist

  • Opening a dispute links it to the correct order and freezes payouts if policy requires.

  • Resolution updates order balance and reputation signals.

  • Evidence files pass AV/MIME checks.


Did this answer your question?