diff --git a/03 - API Reference/Dispute API.md b/03 - API Reference/Dispute API.md index b3c1761..b3d2760 100644 --- a/03 - API Reference/Dispute API.md +++ b/03 - API Reference/Dispute API.md @@ -10,6 +10,9 @@ tags: [api, dispute, reference] Endpoints live under `/api/disputes/*`. `backend/src/routes/disputeRoutes.ts` delegates to `DisputeController` (`backend/src/controllers/disputeController.ts`) for CRUD/triage. `backend/src/services/dispute/disputeRoutes.ts` provides lightweight release-hold endpoints (`raise`, `resolve`, `status`) used by escrow release gating. The routers apply `authenticateToken` globally — every endpoint requires `Bearer JWT`. +> [!warning] Route overlap to verify +> Both route modules define a `POST /:id-or-purchaseRequestId/resolve` shape. Because `app.ts` mounts the full controller router before the lightweight hold router, confirm the intended handler before wiring automation to the lightweight resolve endpoint. + Model: [[Dispute]]. A dispute references a [[PurchaseRequest]] plus optional [[Payment]] context and is the input to the mediation workflow that can lead to refund, replacement, compensation, warning/ban, or no-action. Release/refund execution should go through the ledger-gated [[Payment API]] and [[Payout Flow]]. ## Create diff --git a/PRD - Decentralized Custody and Smart-Contract Escrow Roadmap.md b/PRD - Decentralized Custody and Smart-Contract Escrow Roadmap.md index 822ad24..6436623 100644 --- a/PRD - Decentralized Custody and Smart-Contract Escrow Roadmap.md +++ b/PRD - Decentralized Custody and Smart-Contract Escrow Roadmap.md @@ -192,4 +192,4 @@ This roadmap was created together with a focused documentation alignment pass: - Safe threshold custody model: - OpenZeppelin AccessManager and timelock guidance: -- Request Network payment contracts overview: +- Request Network payment contracts overview: