Accept a Dispute

If you don’t intend to contest a chargeback, you can accept it — conceding the loss without submitting evidence. This is terminal: the dispute moves to accepted, the customer keeps the funds, and no evidence can be submitted afterward.

POST /api/v1/disputes/{dispute_id}/accept

$ curl -s -X POST "https://dev-api.truemed.com/api/v1/disputes/$DISPUTE_ID/accept" \
>   -H "Authorization: Bearer $TRUEMED_API_KEY"

The response is the updated dispute, now in state accepted with outcome: "accepted".

When accept is allowed

Accept is only valid for a dispute that is currently contestable (needs_response). Everything else is rejected:

Current state	Result
`needs_response`	Accepted — dispute moves to `accepted`.
`accepted`	No-op — accepting an already-accepted dispute is idempotent and returns the dispute unchanged.
`inquiry`	Rejected — inquiries aren’t chargebacks and can’t be accepted.
`under_review`, `won`, `lost`, `expired`, `closed`	Rejected — `400 Bad Request`, the dispute can’t be accepted from this state.

Accept is idempotent — a retried or duplicated accept maps to the same action rather than double-submitting, so you can safely retry a request that timed out.

After accepting

As with evidence submission, the authoritative resolved state is confirmed by the processor and surfaced via a dispute.closed webhook. Re-fetch the dispute to read its final outcome and resolved_at.