> ## Documentation Index > Fetch the complete documentation index at: https://docs.dimepayments.com/llms.txt > Use this file to discover all available pages before exploring further. # List Chargebacks > Get the chargebacks raised against a merchant. Chargeback data reaches us through a once-daily file from the processor, so this reflects the most recent daily import rather than live dispute activity. Pair it with the `chargeback_opened` / `chargeback_updated` / `chargeback_resolved` webhooks: the webhooks tell you when something changed, this endpoint is how you reconcile or backfill after an outage, since webhook deliveries are not replayable. ## OpenAPI ````yaml https://app.dimepayments.com/openapi.yaml get /api/chargeback/list openapi: 3.0.3 info: title: Dime Payments API Documentation description: >- A simple, basic API for managing Merchants through Dime Payments. JSON based REST API version: 1.0.0 servers: - url: https://app.dimepayments.com security: - default: [] tags: - name: Merchant management description: '' - name: Transaction management description: >- APIs for managing transactions. Depending on API KEY permissions, one should be able to charge credit cards, ACH, Google/Apple Pay wallets along with other functions. - name: Chargeback management description: '' - name: Document management description: '' - name: Addresses description: |- APIs for managing customer addresses - name: Customer management description: >- APIs for managing customers. Depending on API KEY permissions, one should be able to list, create, update, and delete customers along with several other customer specific requests. - name: Deposit management description: '' - name: Held funds description: '' - name: Invoice management description: >- APIs for managing invoices. Depending on API KEY permissions, one should be able to list, create, update, delete, and send invoices, manage their line items, and manage recurring-invoice schedules. Every request is scoped to a single Merchant via the required `data.sid`. - name: Payment Method management description: >- APIs for managing payment methods associated with customers. Depending on API KEY permissions, one should be able to list, show, create, update, and delete payment methods. - name: Recurring Payments management description: >- APIs for managing recurring payments. Depending on API KEY permissions, one should be able to create, edit, pause, cancel along with other functions. - name: Subscription Plans management description: >- Merchant-facing API for subscription plans (recurring offerings customers subscribe to). The merchant is identified by `data.sid`; the token must carry the matching `subscription-plan:*` ability. Mirrors the recurring-payment and invoice API controllers. - name: Subscriptions management description: >- Merchant-facing API for individual customer subscriptions (enrollments in a plan). The merchant is identified by `data.sid`; the token must carry the matching `subscription:*` ability. Lifecycle transitions delegate to the {@see \App\Actions\Subscription} action classes so the matching `SUBSCRIPTION_*` webhook always fires. Mirrors the recurring-payment and subscription-plan API controllers. - name: Zapier description: >- APIs for use through Zapier. Depending on API KEY permissions, one should be able to see customers and transactions data. paths: /api/chargeback/list: get: tags: - Chargeback management summary: List Chargebacks description: |- Get the chargebacks raised against a merchant. Chargeback data reaches us through a once-daily file from the processor, so this reflects the most recent daily import rather than live dispute activity. Pair it with the `chargeback_opened` / `chargeback_updated` / `chargeback_resolved` webhooks: the webhooks tell you when something changed, this endpoint is how you reconcile or backfill after an outage, since webhook deliveries are not replayable. operationId: listChargebacks parameters: [] requestBody: required: false content: application/json: schema: type: object properties: data: type: object description: '' example: [] properties: sid: type: string description: The ID of the merchant. example: '91828382' required: - sid filters: type: object description: '' example: [] properties: start_date: type: string description: >- Chargeback start date, in UTC, with format: "YYYY-mm-dd 00:00:00" example: '"2026-04-01 00:00:00"' end_date: type: string description: >- Chargeback end date, in UTC, with format: "YYYY-mm-dd 00:00:00" example: '"2026-04-30 23:59:59"' representment_status: type: string description: >- Only chargebacks in this dispute state. Free text from the processor, e.g. "New" or "Resolved". example: '"New"' responses: '200': description: '' content: application/json: schema: type: object example: data: - transaction_info_id: '1134722723' parent_transaction_info_id: '1132652128' gateway_transaction_id: null transaction_number: '1566' invoice_number: null chargeback_date: '2025-05-04T17:45:05-04:00' merchant_chargeback_date: '2025-05-04T19:45:05-04:00' transaction_amount: 391.48 chargeback_amount: 391.48 card_brand: V cc_last_four: '2510' payee_name: null days_to_represent: 0 representment_date: '2025-05-12T06:26:00-04:00' merchant_representment_date: '2025-05-05T07:32:01-04:00' representment_status: accepting chargeback result: Accepting chargeback_code: '4' chargeback_response_code: Other fraud - Card Absent Environment resolved: false - transaction_info_id: '1134722723' parent_transaction_info_id: '1132652128' gateway_transaction_id: null transaction_number: '1566' invoice_number: null chargeback_date: '2025-05-04T17:45:05-04:00' merchant_chargeback_date: '2025-05-04T19:45:05-04:00' transaction_amount: 391.48 chargeback_amount: 391.48 card_brand: V cc_last_four: '2510' payee_name: null days_to_represent: 0 representment_date: '2025-05-12T06:26:00-04:00' merchant_representment_date: '2025-05-05T07:32:01-04:00' representment_status: accepting chargeback result: Accepting chargeback_code: '4' chargeback_response_code: Other fraud - Card Absent Environment resolved: false links: prev: null next: null meta: path: / per_page: 500 next_cursor: null prev_cursor: null properties: data: type: array example: - transaction_info_id: '1134722723' parent_transaction_info_id: '1132652128' gateway_transaction_id: null transaction_number: '1566' invoice_number: null chargeback_date: '2025-05-04T17:45:05-04:00' merchant_chargeback_date: '2025-05-04T19:45:05-04:00' transaction_amount: 391.48 chargeback_amount: 391.48 card_brand: V cc_last_four: '2510' payee_name: null days_to_represent: 0 representment_date: '2025-05-12T06:26:00-04:00' merchant_representment_date: '2025-05-05T07:32:01-04:00' representment_status: accepting chargeback result: Accepting chargeback_code: '4' chargeback_response_code: Other fraud - Card Absent Environment resolved: false - transaction_info_id: '1134722723' parent_transaction_info_id: '1132652128' gateway_transaction_id: null transaction_number: '1566' invoice_number: null chargeback_date: '2025-05-04T17:45:05-04:00' merchant_chargeback_date: '2025-05-04T19:45:05-04:00' transaction_amount: 391.48 chargeback_amount: 391.48 card_brand: V cc_last_four: '2510' payee_name: null days_to_represent: 0 representment_date: '2025-05-12T06:26:00-04:00' merchant_representment_date: '2025-05-05T07:32:01-04:00' representment_status: accepting chargeback result: Accepting chargeback_code: '4' chargeback_response_code: Other fraud - Card Absent Environment resolved: false items: type: object properties: transaction_info_id: type: string example: '1134722723' description: >- The processor's unique identifier for this chargeback. Stable, and what you pass to the show endpoint. parent_transaction_info_id: type: string example: '1132652128' description: >- The identifier of the original transaction being disputed. gateway_transaction_id: type: string example: null nullable: true transaction_number: type: string example: '1566' invoice_number: type: string example: null nullable: true chargeback_date: type: string example: '2025-05-04T17:45:05-04:00' description: When the chargeback was raised. merchant_chargeback_date: type: string example: '2025-05-04T19:45:05-04:00' transaction_amount: type: number example: 391.48 description: The amount of the original transaction. chargeback_amount: type: number example: 391.48 description: >- The amount being disputed, which may be less than the original transaction. card_brand: type: string example: V cc_last_four: type: string example: '2510' payee_name: type: string example: null nullable: true days_to_represent: type: integer example: 0 description: >- Days remaining to submit evidence contesting the chargeback. representment_date: type: string example: '2025-05-12T06:26:00-04:00' description: The deadline for submitting evidence. merchant_representment_date: type: string example: '2025-05-05T07:32:01-04:00' representment_status: type: string example: accepting chargeback description: >- The dispute's state, as free text from the processor, e.g. "New", "accepting chargeback", "Resolved". result: type: string example: Accepting description: >- The outcome once decided, e.g. "Resolved in favor of Merchant". Null while the case is open. chargeback_code: type: string example: '4' description: The card network's numeric reason code. chargeback_response_code: type: string example: Other fraud - Card Absent Environment description: The reason in words, e.g. "Duplicate Processing". resolved: type: boolean example: false description: >- Whether the dispute has reached a terminal state. Derived from representment_status and result. links: type: object properties: prev: type: string example: null nullable: true next: type: string example: null nullable: true meta: type: object properties: path: type: string example: / per_page: type: integer example: 500 next_cursor: type: string example: null description: >- The handle for the next page, or null on the last one. Re-send the same request with `?cursor=` appended to the URL and the body unchanged. Do not follow `links.next` on its own: this endpoint reads `data.sid` and `filters` from the request body, so fetching that URL without the body fails. prev_cursor: type: string example: null nullable: true '400': description: Malformed Request content: application/json: schema: type: object example: errors: filters.start_date: - >- The filters.start_date field must match the format Y-m-d H:i:s. properties: errors: type: object properties: filters.start_date: type: array example: - >- The filters.start_date field must match the format Y-m-d H:i:s. items: type: string '401': description: '' content: application/json: schema: oneOf: - description: Incorrect API Key Permission type: object example: data: message: Permission Denied. properties: data: type: object properties: message: type: string example: Permission Denied. - description: Not associated with Affiliate type: object example: data: message: Not associated with Affiliate properties: data: type: object properties: message: type: string example: Not associated with Affiliate '404': description: '' content: application/json: schema: oneOf: - description: Unknown merchant type: object example: data: message: No such Merchant properties: data: type: object properties: message: type: string example: No such Merchant - description: No chargebacks found type: object example: data: message: No chargebacks found properties: data: type: object properties: message: type: string example: No chargebacks found components: securitySchemes: default: type: http scheme: bearer description: >- You can retrieve your token by visiting your dashboard and clicking Generate API token under your profile in top right. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.