Disputes
Operations related to disputes
All endpoints require a JWT Bearer token in the Authorization header; most also require an API key in the X-API-KEY header.
GET /v1/disputes
Get a list of disputes with pagination
Parameters
Name | In | Type | Required | Description |
|---|---|---|---|---|
| query |
| Yes | Maximum number of records to return. Starts from 1 to 1000. |
| query |
| Yes | Page number to retrieve, starting from 0. |
| query |
| No | Choose specific fields to include in the response (comma-separated). |
| query |
| No | A JSON object representing the filter criteria in MongoDB Query Language (MQL) format. |
| query |
| No | A JSON object representing the sort criteria in MongoDB Query Language (MQL) format. |
| query |
| No | Include related data in query results using a JSON object. |
Responses
Status | Description |
|---|---|
| Successfully retrieved a paginated list of disputes. |
GET /v1/disputes/{id}
Get a specific dispute by ID
Parameters
Name | In | Type | Required | Description |
|---|---|---|---|---|
| path |
| Yes | The disputeId field |
| query |
| No | Include transaction data in the response. When true, enriches the dispute with transaction data where dispute.paymentPspReference === transaction.transactionId. |
| query |
| No | Choose specific fields to include in the response (comma-separated). |
| query |
| No | Include related data in query results using a JSON object. |
Responses
Status | Description |
|---|---|
| Dispute details retrieved successfully |
The following endpoints are served from https://payments.valpay.com.
GET /v1/disputes/get-defense-reasons/{id}
Get disputes defense reasons
Parameters
Name | In | Type | Required | Description |
|---|---|---|---|---|
| path |
| Yes | Dispute Transaction PSP reference (id) |
Responses
Status | Description |
|---|---|
| Disputes defense reasons retrieved successfully |
Response schema (2xx)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | |
|
| Yes | Success message |
POST /v1/disputes/accept-dispute
Accept a dispute
Request body (required)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Transaction ID |
Responses
Status | Description |
|---|---|
| Dispute accepted successfully |
Response schema (2xx)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Whether the operation was successful |
|
| Yes | Response data |
|
| Yes | Success message |
POST /v1/disputes/defend-dispute
Defend a dispute
Request body (required)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Transaction ID |
|
| Yes | Code identifying the defense reason |
Responses
Status | Description |
|---|---|
| Dispute defense initiated successfully |
Response schema (2xx)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Whether the operation was successful |
|
| Yes | Response data |
|
| Yes | Success message |
POST /v1/disputes/supply-defense-document
Supply a defense document for a dispute
Request body (required)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Transaction ID |
|
| Yes | Array of defense documents |
Responses
Status | Description |
|---|---|
| Defense document supplied successfully |
Response schema (2xx)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Whether the operation was successful |
|
| Yes | |
|
| Yes | Success message |
POST /v1/disputes/delete-defense-document
Delete a defense document from a dispute
Request body (required)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Transaction ID (PSP reference of the dispute) |
|
| Yes | The document type code of the defense document to delete |
Responses
Status | Description |
|---|---|
| Defense document deleted successfully |
Response schema (2xx)
Field | Type | Required | Description |
|---|---|---|---|
|
| Yes | Whether the operation was successful |
|
| Yes | |
|
| Yes | Success message |
Examples
GET /v1/disputes
First page of open (Notified) disputes, newest first:
Response 200 (illustrative):
GET /v1/disputes/{id}
Fetch a dispute enriched with its transaction:
POST /v1/disputes/defend-dispute
Response 200: