> ## Documentation Index
> Fetch the complete documentation index at: https://docs2.finverse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List Disputes

> List Disputes associated with a Customer App.

**Authorization**: `customer_token`

### Dispute (object)

Current snapshot of each Dispute.



## OpenAPI

````yaml /api-reference/openapi.json get /disputes
openapi: 3.0.0
info:
  description: Documentation of the early finverse services
  title: Finverse Public
  termsOfService: https://example.com
  contact:
    name: Maintainers
    email: info@finverse.com
  license:
    name: unknown license
  version: 0.0.1
servers:
  - url: https://api.prod.finverse.net
security:
  - Oauth2:
      - test
tags:
  - name: public
    description: Publicly accessible endpoints
    x-group: Public
  - name: customer
    description: Customer app and institution endpoints
    x-group: Customer
  - name: link
    description: Finverse Link flows
    x-group: Link
  - name: login_identity
    description: Login identity lifecycle and metadata
    x-group: Login identity
  - name: accounts
    description: Accounts, balances, and account numbers
    x-group: Accounts
  - name: statements
    description: Statements and composite statements
    x-group: Statements
  - name: transactions
    description: Transaction history
    x-group: Transactions
  - name: identity_income
    description: Identity and income insights
    x-group: Identity & income
  - name: payment_links
    description: Payment link creation and checkout
    x-group: Payment links
  - name: mandates
    description: Direct debit mandates
    x-group: Mandates
  - name: payments
    description: Payment initiation and status
    x-group: Payment operations
  - name: payouts
    description: Payouts and scheduled payouts
    x-group: Payouts
  - name: payment_users
    description: Payment user profiles
    x-group: Payment users
  - name: payment_accounts
    description: Payment accounts for users
    x-group: Payment accounts
  - name: payment_methods
    description: Stored payment methods
    x-group: Payment methods
  - name: bills
    description: Bill presentment
    x-group: Bills
  - name: disputes
    description: Payment disputes
    x-group: Disputes
  - name: ledger
    description: Ledger and statements
    x-group: Ledger
paths:
  /disputes:
    get:
      tags:
        - disputes
      summary: List Disputes
      description: |-
        List Disputes associated with a Customer App.

        **Authorization**: `customer_token`

        ### Dispute (object)

        Current snapshot of each Dispute.
      operationId: listDisputes
      parameters:
        - description: Start date for filtering (applied to Dispute `updated_at` field)
          name: date_from
          in: query
          schema:
            type: string
            format: date
        - description: End date for filtering (applied to Dispute `updated_at` field)
          name: date_to
          in: query
          schema:
            type: string
            format: date
        - description: >-
            Comma-separated filter for specific Dispute statuses. Example:
            `statuses=PROCESSING,UNDEFENDED`. Refer to the Dispute statuses
            schema
          name: statuses
          in: query
          style: form
          explode: false
          schema:
            type: array
            items:
              enum:
                - UNKNOWN
                - UNDEFENDED
                - ACTION_REQUIRED
                - PROCESSING
                - ACCEPTED
                - LOST
                - WON
              type: string
        - description: 'Pagination offset (default: 0)'
          name: offset
          in: query
          schema:
            type: integer
            default: 0
        - description: 'Maximum number of records per page (default: 500, max: 1000)'
          name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 1000
            default: 500
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListDisputesResponse'
              examples:
                success:
                  summary: Success
                  value:
                    disputes:
                      - amount: 40
                        arn: Chargeback1755172216672
                        card_details:
                          brand: Visa
                        created_at: '2025-08-14T12:36:10.481Z'
                        currency: HKD
                        defense_period_deadline: '2025-12-12T13:34:56.000Z'
                        dispute_id: 01K2M9992N5GDH4KCKKJWJQ728
                        dispute_status: UNDEFENDED
                        is_auto_defended: false
                        is_defendable: true
                        last_event_name: CHARGEBACK
                        payment_processor: ADYEN
                        payment_processor_dispute_code: '10.4'
                        payment_processor_dispute_reason: Other Fraud-Card Absent Environment
                        payment_processor_dispute_reference: PX7RZWW4KZZBDR75
                        payment_processor_dispute_status: Undefended
                        payment_processor_merchant_reference: ST3293L223228K5MX4JRQDT89
                        payment_processor_payment_reference: QL6DLL2SP66VL3V5
                        payment_reference: '1755172204'
                        updated_at: '2025-08-14T13:27:22.948Z'
                      - amount: 4014
                        arn: Chargeback1755172264736
                        card_details:
                          brand: Visa
                        created_at: '2025-08-14T12:36:10.044Z'
                        currency: HKD
                        defense_period_deadline: '2025-12-12T13:34:56.000Z'
                        dispute_id: 01K2M998NKC20C0E6FCW439QM9
                        dispute_status: UNDEFENDED
                        is_auto_defended: false
                        is_defendable: true
                        last_event_name: CHARGEBACK
                        payment_processor: ADYEN
                        payment_processor_dispute_code: '10.4'
                        payment_processor_dispute_reason: Other Fraud-Card Absent Environment
                        payment_processor_dispute_reference: N58RZWW4KZZBDR75
                        payment_processor_dispute_status: Undefended
                        payment_processor_merchant_reference: ST3293L223228K5MX4JRQDT89
                        payment_processor_payment_reference: DX56JQKNF8VQ3M75
                        payment_reference: '1755172240'
                        updated_at: '2025-08-14T13:27:23.485Z'
                      - amount: 40
                        arn: Chargeback1755172235058
                        card_details:
                          brand: Visa
                        created_at: '2025-08-14T12:32:00.152Z'
                        currency: HKD
                        defense_period_deadline: '2025-12-12T13:31:08.000Z'
                        dispute_id: 01K2M91MMDSKJ3H1VQ0T9BTB85
                        dispute_status: UNDEFENDED
                        is_auto_defended: false
                        is_defendable: true
                        last_event_name: CHARGEBACK
                        payment_processor: ADYEN
                        payment_processor_dispute_code: '10.4'
                        payment_processor_dispute_reason: Other Fraud-Card Absent Environment
                        payment_processor_dispute_reference: C5GBRZTPJXXHQ2W5
                        payment_processor_dispute_status: Undefended
                        payment_processor_merchant_reference: ST3293L223228K5MX4JRQDT89
                        payment_processor_payment_reference: H7SSRLLV66G47NV5
                        payment_reference: '1755172222'
                        updated_at: '2025-08-14T13:32:00.097Z'
                    total_disputes: 3
        '400':
          description: Invalid Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrBodyModelV2'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrBodyModelV2'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrBodyModelV2'
      security:
        - Oauth2:
            - dispute:list
components:
  schemas:
    ListDisputesResponse:
      required:
        - total_disputes
        - disputes
      properties:
        disputes:
          type: array
          items:
            $ref: '#/components/schemas/DisputeResponse'
          description: >-
            List of Disputes objects that satisfy the filters in the request.
            Refer to the Dispute object schema
        total_disputes:
          type: integer
          description: >-
            Total number of Dispute records available for the selected filtering
            criteria (can be used to inform pagination requests)
    ErrBodyModelV2:
      properties:
        error:
          $ref: '#/components/schemas/FvErrorModelV2'
    DisputeResponse:
      type: object
      properties:
        amount:
          description: Amount of the disputed transaction (in minor currency unit)
          type: integer
        arn:
          description: >-
            Disputed transaction's "Acquirer Reference Number" (if provided by
            the payment processor)
          type: string
        card_details:
          type: object
          properties:
            brand:
              type: string
              example: visa
          description: >-
            Details on the card payment method if the disputed transaction was
            paid by card (if provided by the payment processor) Refer to the
            Card `card_details` object data model in `GET
            /users/{payment_user_id}/payment_methods`.
        created_at:
          description: Timestamp when the dispute record was first created
          type: string
          format: date-time
        currency:
          description: Currency of the disputed transaction (e.g. HKD)
          type: string
          example: HKD
        defense_period_deadline:
          description: >-
            Deadline to defend the dispute (if provided by the payment
            processor)
          type: string
          format: date-time
          nullable: true
        dispute_id:
          description: Finverse Dispute ID for this dispute record. Always unique.
          type: string
        dispute_status:
          description: >-
            Current status of the dispute. Note: since disputes can be defended
            & appealed by both parties, dispute statuses should not be
            considered final (e.g. `status` = `WON` or `LOST` are not final and
            may be reversed). Possible values: \- `ACCEPTED` : indicates
            merchant has explicitly accepted the dispute (final status).
            Accepting a dispute is optional. \- `ACTION_REQUIRED`: indicates a
            request for information has not yet received a response \- `LOST` \-
            `PROCESSING`: indicates defense information provided by the merchant
            is being reviewed. \- `UNDEFENDED`: indicates the merchant has not
            yet taken action on the dispute (accepted or defended it). This is
            typically the initial status for any dispute. \- `WON`
          type: string
          enum:
            - UNKNOWN
            - UNDEFENDED
            - ACTION_REQUIRED
            - PROCESSING
            - ACCEPTED
            - LOST
            - WON
        is_auto_defended:
          description: >-
            Flag indicating whether the payment processor will auto-defend the
            dispute (if provided by the payment processor). Disputes may be
            auto-defended when the disputed transaction has already been
            refunded or is protected by 3D Secure, or when the dispute is
            technically invalid
          type: boolean
          nullable: true
        is_defendable:
          description: >-
            Flag indicating whether the dispute can be defended (if provided by
            the payment processor). Typically this flag will be `true` so long
            as the `defense_period_deadline` has not expired.
          type: boolean
          nullable: true
        issuer_comments:
          type: object
          additionalProperties:
            type: string
          description: >-
            Comments/questions raised by the card issuer (if proivded by the
            payment processor). Issuer comments are typically provided when
            `payment_processor_dispute_status` = `ISSUER_COMMENTS`. Object
            contains plaintext fields in key:value format. E.g.
            `orderDetailsNotAsDescribed`: `some_text`
        last_event_name:
          description: The name of the last event for this dispute
          type: string
        payment_id:
          description: >-
            Finverse Payment ID for the disputed transaction (if Finverse is
            able to map the disputed transaction reference to a known Finverse
            Payment ID).
          type: string
        payment_processor:
          description: >-
            Payment processor through which the disputed transaction was
            processed. Possible values: \- `ADYEN`
          type: string
          example: ADYEN
        payment_processor_dispute_code:
          description: >-
            Dispute code ((if provided by the payment processor). For detailed
            guidance on dispute codes/reasons and defense requirements, refer to
            each payment processor: \- `ADYEN`:
            [https://docs.adyen.com/risk-management/understanding-disputes/dispute-reason-codes/](https://docs.adyen.com/risk-management/understanding-disputes/dispute-reason-codes/)
          type: string
        payment_processor_dispute_reason:
          description: >-
            Summary dispute reason associated with the `dispute_code` (if
            provided by the payment processor). See `dispute_code` above.
          type: string
        payment_processor_dispute_reference:
          description: >-
            Payment processor's reference for the dispute (if provided by the
            payment processor)
          type: string
        payment_processor_dispute_status:
          description: >-
            Payment processor's dispute status (if provided by the payment
            processor)
          type: string
        payment_processor_merchant_reference:
          type: string
          description: >-
            Payment processor's merchant / store ID for the merchant account
            which collected the disputed transaction (if provided by the payment
            processor).
        payment_processor_payment_reference:
          description: >-
            Payment processor's reference for the disputed transaction (if
            provided by the payment processor).
          type: string
        payment_reference:
          description: >-
            Merchant's original reference for the disputed transaction (if
            provided by the payment processor).
          type: string
        updated_at:
          description: Timestamp of the last update to the dispute's record
          type: string
          format: date-time
    FvErrorModelV2:
      required:
        - type
        - error_code
        - message
        - details
        - request_id
      properties:
        details:
          type: string
        error_code:
          type: string
          example: CREDENTIALS_INVALID
        message:
          type: string
        request_id:
          description: The request_id provided in the request header
          type: string
        type:
          description: The error type
          type: string
          enum:
            - LINK_ERROR
            - API_ERROR
          example: LINKING_ERROR
  securitySchemes:
    Oauth2:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://finverse-dev.us.auth0.com/oauth/token
          scopes:
            account: Account
            balance: Balance
            credit: Credit
            institution: Institution
            investment: Investment
            link: Link
            test: Test
            transaction: Transaction

````