> ## Documentation Index > Fetch the complete documentation index at: https://docs.eximpe.com/llms.txt > Use this file to discover all available pages before exploring further. # List Chargebacks > List chargebacks raised on your payments, filtered by status, payment, order or date. Use `status=NEW` (and `PENDING_RESPONSE`, `INSUFFICIENT_DOCUMENT`) to find chargebacks still waiting on you, or rely on the [`DISPUTE_UPDATED`](https://docs.eximpe.com/api-reference/v2/webhooks/dispute-updated) webhook to hear about each one as it is raised. ## OpenAPI ````yaml openapi/openapi.json GET /pg/chargebacks/ openapi: 3.0.0 info: title: Eximpe Payment Gateway API description: >- API for payment processing and order management through Eximpe payment gateway. This specification includes v1, v2, and v3 API versions. license: name: Proprietary version: 2.0.0 servers: - url: https://api-pacb-uat.eximpe.com description: Payment Gateway Sandbox URL security: - clientAuth: [] clientSecretAuth: [] apiVersionHeader: [] tags: - name: Card Tokens - name: Merchants - name: Orders - name: Payment Links - name: Payments - name: Refunds - name: Chargebacks description: >- Chargebacks on your payments, and your answer to them. The same request and response shape works whichever gateway the payment was made on. - name: Settlements - name: Subscriptions paths: /pg/chargebacks/: get: tags: - Chargebacks summary: List Chargebacks description: >- Chargebacks raised on your payments and, for a PSP, on your sub-merchants' payments, newest first. operationId: v2_list_chargebacks parameters: - name: status in: query description: Only chargebacks in this status, e.g. `NEW` or `PENDING_DOC_REVIEW`. schema: type: string - name: payment_id in: query description: Only chargebacks on this payment. schema: type: string - name: order_id in: query description: Only chargebacks on this EximPe order. schema: type: string - name: order_reference_id in: query description: Only chargebacks on the order with this reference of yours. schema: type: string - name: from_date in: query description: 'Created on or after this date. Format: YYYY-MM-DD.' schema: type: string format: date - name: to_date in: query description: 'Created up to and including this date. Format: YYYY-MM-DD.' schema: type: string format: date - name: page in: query description: Page number, from 1. schema: type: integer default: 1 - name: page_size in: query description: Results per page. schema: type: integer default: 250 - name: X-Merchant-ID in: header required: false description: >- PSPs only: list just this sub-merchant's chargebacks. Without it, a PSP sees its own and all its sub-merchants' chargebacks. schema: type: string responses: '200': description: OK content: application/json: schema: type: object properties: success: type: boolean message: type: string data: type: object properties: count: type: integer page: type: integer page_size: type: integer next: type: string nullable: true previous: type: string nullable: true results: type: array items: $ref: '#/components/schemas/v2_Chargeback' example: success: true message: Chargebacks retrieved successfully data: count: 2 page: 1 page_size: 250 next: null previous: null results: - chargeback_id: CB6358819770 payment_id: PR1400935863 order_id: OD8950153797 order_reference_id: ORDER-10422 amount: '2500.00' status: PENDING_DOC_REVIEW action: contest chargeback_type: Chargeback reason_description: Goods or Services Not Provided / Not Received raised_on: '2026-10-26T03:47:59Z' respond_by: '2026-11-02T03:47:59Z' can_respond: false created_at: '2026-10-26T03:47:59Z' - chargeback_id: CB4073011797 payment_id: PR5447061737 order_id: OD8949028750 order_reference_id: ORDER-10419 amount: '999.00' status: NEW action: null chargeback_type: Chargeback reason_description: Goods or Services Not Provided / Not Received raised_on: '2026-10-26T03:47:59Z' respond_by: '2026-11-02T03:47:59Z' can_respond: true created_at: '2026-10-26T03:47:59Z' security: - clientAuth: [] clientSecretAuth: [] apiVersionHeader: [] components: schemas: v2_Chargeback: type: object properties: chargeback_id: type: string description: EximPe chargeback ID. example: CB6358819770 payment_id: type: string description: The disputed payment. example: PR1400935863 order_id: type: string description: EximPe order ID of the disputed payment. example: OD8950153797 order_reference_id: type: string nullable: true description: Your own reference for the order. example: ORDER-10422 amount: type: string description: Disputed amount, two decimals, in the payment's currency. example: '2500.00' status: $ref: '#/components/schemas/v2_ChargebackStatus' action: allOf: - $ref: '#/components/schemas/v2_ChargebackActionType' nullable: true description: How the chargeback was answered; `null` until it is. chargeback_type: type: string description: Kind of dispute raised by the customer's bank. example: Chargeback reason_description: type: string description: Why the customer disputed the payment. example: Goods or Services Not Provided / Not Received raised_on: type: string format: date-time description: When the dispute was raised. respond_by: type: string format: date-time nullable: true description: >- Answer before this time. With no answer by then, the dispute is closed in the customer's favour. can_respond: type: boolean description: Whether the chargeback can be answered now. created_at: type: string format: date-time v2_ChargebackStatus: type: string enum: - NEW - PENDING_RESPONSE - PENDING_DOC_REVIEW - SUBMITTED_TO_BANK - INSUFFICIENT_DOCUMENT - CLOSED_CUSTOMER_FAVOUR - CLOSED_IN_MERCHANT_FAVOUR - CLOSED_UNDER_FRAUD_LIABILITY description: >- Where the chargeback is in its lifecycle. It can be answered only while `NEW`, `PENDING_RESPONSE` or `INSUFFICIENT_DOCUMENT` (see `can_respond`). `PENDING_DOC_REVIEW`: your answer is in. `SUBMITTED_TO_BANK`: your answer has gone to the bank. `CLOSED_*`: decided. v2_ChargebackActionType: type: string enum: - accept - contest - partial_accept description: >- `accept`: accept the chargeback in full. `contest`: dispute it with evidence. `partial_accept`: accept part of the disputed amount. securitySchemes: clientAuth: type: apiKey name: X-Client-ID in: header description: >- **Client Application ID** - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard. x-displayName: Client ID x-example: your-client-id clientSecretAuth: type: apiKey name: X-Client-Secret in: header description: >- **Client Secret Key** - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard. x-displayName: Client Secret x-example: your-client-secret apiVersionHeader: type: apiKey name: X-API-Version in: header description: >- **API Version** - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings. x-displayName: API Version x-example: 3.0.0 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.