> ## 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. # Get Chargeback > Retrieve one chargeback, with your latest answer to it. ## OpenAPI ````yaml openapi/openapi.json GET /pg/chargebacks/{chargeback_id}/ 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/{chargeback_id}/: get: tags: - Chargebacks summary: Get Chargeback description: One chargeback, with your latest answer to it. operationId: v2_get_chargeback parameters: - name: chargeback_id in: path required: true description: EximPe chargeback ID, e.g. `CB6358819770`. schema: type: string responses: '200': description: OK content: application/json: schema: type: object properties: success: type: boolean message: type: string data: $ref: '#/components/schemas/v2_ChargebackDetail' example: success: true message: Chargeback details retrieved successfully data: 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' response: action: contest condition: product_delivered submitted_at: '2026-10-26T03:48:13Z' '404': description: >- No chargeback with this ID on your payments (or your sub-merchants' payments). content: application/json: schema: $ref: '#/components/schemas/v2_ErrorResponse' example: success: false error: code: 40669 message: Chargeback not found details: chargeback_id: Chargeback not found security: - clientAuth: [] clientSecretAuth: [] apiVersionHeader: [] components: schemas: v2_ChargebackDetail: allOf: - $ref: '#/components/schemas/v2_Chargeback' - type: object properties: response: $ref: '#/components/schemas/v2_ChargebackAnswer' v2_ErrorResponse: type: object required: - success - error properties: success: type: boolean enum: - false description: >- Indicates if the request was successful. Always false for error responses. error: $ref: '#/components/schemas/v2_ErrorDetails' 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_ChargebackAnswer: type: object nullable: true description: Your latest answer, or `null` if there is none. properties: action: $ref: '#/components/schemas/v2_ChargebackActionType' condition: type: string nullable: true description: >- The condition you answered with. `null` for an answer given from the merchant dashboard. example: product_delivered submitted_at: type: string format: date-time v2_ErrorDetails: type: object required: - code - message properties: code: type: string description: Error code (e.g., ERR_ORDER_002) message: type: string description: Error message details: type: object description: Detailed validation error information with field-specific errors additionalProperties: type: string description: Error message for the specific field 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.