Use this endpoint to open a new dispute for an exception. Disputes are used to formally challenge or investigate discrepancies with external parties.
Bearer token authentication (format: "Bearer {token}")
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Also accepts Idempotency-Key as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with X-Idempotency-Replayed: true.
See Retries and idempotency for details.
Exception ID
Open dispute payload
Indicates that the resource was successfully created.
The response includes the X-Idempotency-Replayed header.
If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.
Dispute details
Category of the dispute
BANK_FEE_ERROR, UNRECOGNIZED_CHARGE, DUPLICATE_TRANSACTION, OTHER "BANK_FEE_ERROR"
Creation timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"
Description of the dispute
"Transaction amount differs from expected"
Evidence submitted for this dispute
Exception ID this dispute is for
"019c96a0-10d2-7134-ba5f-664142ee7052"
Unique identifier for the dispute
"019c96a0-10d2-7193-8841-0d7347efd09a"
User who opened the dispute
"user@example.com"
Reason for reopening if reopened
"New evidence discovered"
Resolution description when closed
"Counterparty confirmed error"
Current state
DRAFT, OPEN, PENDING_EVIDENCE, WON, LOST "OPEN"
Last update timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"