Revolut Disputes API

Endpoints that allow merchants to view customer payment disputes. It provides a robust framework with high-level states (e.g., `won`, `lost`, `needs_response`, `under_review`) and detailed substates (e.g., `lost_expired`, `pre_arbitration`, `won_pre_arbitration`, etc.) to accurately track the dispute lifecycle. Additionally, the API integrates standard dispute reason codes and human-readable descriptions, offering a customisable approach to dispute resolution that facilitates effective dispute management.

Operations 5

GET /api/disputes Retrieve a dispute list #
GET /api/disputes/{dispute_id} Retrieve a dispute #
POST /api/disputes/{dispute_id}/accept Accept a dispute #
POST /api/disputes/{dispute_id}/evidences Upload evidence for a dispute #
POST /api/disputes/{dispute_id}/challenge Challenge a dispute #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/revolut-disputes-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

revolut-disputes-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Merchant Disputes API
  version: '2026-04-20'
  description: 'Welcome to the Revolut Merchant API - your solution to managing the core aspects of e-commerce and accepting online payments. Whether you''re a startup, a growing business, or an established enterprise in the e-commerce industry, our API helps you streamline your operations.


    As a Revolut Business customer with a Merchant Account, you can use the

    Merchant API to leverage the following features:


    - [Order management](https://developer.revolut.com/docs/api/merchant#tag-orders)

    - [Customer management](https://developer.revolut.com/docs/api/merchant#tag-customers)

    - [Payment management](https://developer.revolut.com/docs/api/merchant#tag-payments)

    - [Subscription management](https://developer.revolut.com/docs/api/merchant#tag-subscriptions)

    - [Payout management](https://developer.revolut.com/docs/api/merchant#tag-payouts)

    - [Dispute management](https://developer.revolut.com/docs/api/merchant#tag-disputes)

    - [Reporting analytics](https://developer.revolut.com/docs/api/merchant#tag-report-runs)

    - [Webhook management](https://developer.revolut.com/docs/api/merchant#tag-webhooks)

    - [Location management](https://developer.revolut.com/docs/api/merchant#tag-locations)


    ... and more.


    ### API versions


    :::warning

    We highly recommend using versioning in your API calls. If you don''t provide a version header on the operations where it''s required, you will receive an error response.

    :::


    The Merchant API uses request header versioning. Where it is required you need to use the `Revolut-Api-Version` header parameter to specify an API version. Each request, where it is indicated in the API specification, must contain a version header in the following format:


    ```

    ''Revolut-Api-Version: 2026-04-20''

    ```


    :::info

    For more information, see: [API versions](https://developer.revolut.com/docs/guides/merchant/reference/versioning/api-versions)

    :::


    ### Test the Merchant API


    You can test the Merchant API in Postman by forking this collection:


    [![View in Postman](https://run.pstmn.io/button.svg)](https://www.postman.com/revolut-api/workspace/revolut-developers/overview)'
  contact: {}
servers:
- description: Production server (uses live data)
  url: https://merchant.revolut.com
- description: Sandbox server (uses test data)
  url: https://sandbox-merchant.revolut.com
security:
- Api-Key: []
tags:
- name: Disputes
  description: "Endpoints that allow merchants to view customer payment disputes.\n\n It provides a robust framework with high-level states (e.g., `won`, `lost`, `needs_response`, `under_review`) and detailed substates (e.g., `lost_expired`, `pre_arbitration`, `won_pre_arbitration`, etc.) to accurately track the dispute lifecycle.\n\n Additionally, the API integrates standard dispute reason codes and human-readable descriptions, offering a customisable approach to dispute resolution that facilitates effective dispute management."
paths:
  /api/disputes:
    parameters:
    - $ref: '#/components/parameters/Authorization'
    - $ref: '#/components/parameters/Revolut-Api-Version'
    get:
      summary: Retrieve a dispute list
      operationId: retrieveDisputeList
      servers:
      - description: Production server (uses live data)
        url: https://merchant.revolut.com
      description: "Retrieve a list of disputes associated with your merchant account. \n\n:::note\nThis endpoint is only available in **Production** environment.\n:::\n\nYou can also use the query parameters for:\n  \n  | Filtering | Pagination |\n  | --------- | ---------- |\n  | Filter the diputes that you want to retrieve, for example, only retrieve the disputes that have a specific state. <br/><br/>Parameters used for filtering:<br/><ul><li>`from_created_date`</li><li>`to_created_date`</li><li>`payment_id`</li><li>`state`</li></ul> | View the disputes without loading all of them at once, for example, return a specified number of disputes per page. <br/><br/>Parameters used for pagination: <br/><ul><li>`limit`</li><li>`from_created_date` or `to_created_date`</li></ul> |"
      parameters:
      - $ref: '#/components/parameters/Limit'
      - $ref: '#/components/parameters/From-Created-Date'
      - $ref: '#/components/parameters/To-Created-Date'
      - $ref: '#/components/parameters/Dispute-State-Query'
      - $ref: '#/components/parameters/Payment-Id-Query'
      responses:
        '200':
          description: List of disputes retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Disputes'
              examples:
                dispute_list:
                  $ref: '#/components/examples/Res-Dispute-List'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: validation
                message: limit must be between 1 and 500
                timestamp: 1601296792533
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: unauthenticated
                message: Authentication failed
                timestamp: 1721049596461
      security:
      - Api-Key: []
      tags:
      - Disputes
  /api/disputes/{dispute_id}:
    parameters:
    - $ref: '#/components/parameters/Authorization'
    - $ref: '#/components/parameters/Revolut-Api-Version'
    - $ref: '#/components/parameters/Dispute-Id'
    get:
      summary: Retrieve a dispute
      operationId: retrieveDispute
      servers:
      - description: Production server (uses live data)
        url: https://merchant.revolut.com
      description: 'Retrieve the details of a specific dispute by its ID.


        :::note

        This endpoint is only available in **Production** environment.

        :::'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Dispute'
              examples:
                card_dispute:
                  $ref: '#/components/examples/Res-Dispute-Card'
                sepa_direct_debit_dispute:
                  $ref: '#/components/examples/Res-Dispute-Sepa-Direct-Debit'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: bad_request
                message: Missing Revolut-Api-Version header
                timestamp: 1601296792533
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: unauthenticated
                message: Authentication failed
                timestamp: 1721049596461
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested resource is not found
                timestamp: 1721050063886
      security:
      - Api-Key: []
      tags:
      - Disputes
  /api/disputes/{dispute_id}/accept:
    parameters:
    - $ref: '#/components/parameters/Authorization'
    - $ref: '#/components/parameters/Revolut-Api-Version'
    - $ref: '#/components/parameters/Dispute-Id'
    post:
      summary: Accept a dispute
      operationId: acceptDispute
      servers:
      - description: Production server (uses live data)
        url: https://merchant.revolut.com
      description: 'Marks a specific dispute as accepted.


        After accepting a dispute, you cannot challenge it.


        :::note

        This endpoint is only available in **Production** environment.

        :::'
      responses:
        '204':
          description: Dispute accepted successfully
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: bad_request
                message: Missing Revolut-Api-Version header
                timestamp: 1601296792533
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: unauthenticated
                message: Authentication failed
                timestamp: 1721049596461
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested operation is forbidden
                timestamp: 1721050063886
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested resource is not found
                timestamp: 1721050063886
        '422':
          description: Unprocessable entity
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
      security:
      - Api-Key: []
      tags:
      - Disputes
  /api/disputes/{dispute_id}/evidences:
    parameters:
    - $ref: '#/components/parameters/Authorization'
    - $ref: '#/components/parameters/Revolut-Api-Version'
    - $ref: '#/components/parameters/Content-Type'
    - $ref: '#/components/parameters/Dispute-Id'
    post:
      summary: Upload evidence for a dispute
      operationId: uploadDisputeEvidence
      servers:
      - description: Production server (uses live data)
        url: https://merchant.revolut.com
      description: "Allows uploading a single evidence file for a specific dispute. \n\nUse these evidences to provide proof for claims when challenging a dispute.\n\n:::warning\n**Limitations:**\n  - Maximum `100` uploaded files are allowed per dispute.\n  - Maximum file size: `10MB`.\n  - Allowed file types: `PDF`, `PNG`, `JPEG`.\n:::\n\n:::note\nThis endpoint is only available in **Production** environment.\n:::"
      requestBody:
        required: true
        content:
          multipart/form-data:
            encoding:
              file:
                contentType: application/pdf, image/png, image/jpeg
            schema:
              $ref: '#/components/schemas/Dispute-Evidence-Creation'
      responses:
        '201':
          description: Evidence uploaded successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Dispute-Evidence'
              examples:
                evidence_uploaded:
                  $ref: '#/components/examples/Res-Dispute-Evidence'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: bad_request
                message: Missing Revolut-Api-Version header
                timestamp: 1601296792533
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: unauthenticated
                message: Authentication failed
                timestamp: 1721049596461
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested operation is forbidden
                timestamp: 1721050063886
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested resource is not found
                timestamp: 1721050063886
        '422':
          description: Unprocessable entity
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
      security:
      - Api-Key: []
      tags:
      - Disputes
  /api/disputes/{dispute_id}/challenge:
    parameters:
    - $ref: '#/components/parameters/Authorization'
    - $ref: '#/components/parameters/Revolut-Api-Version'
    - $ref: '#/components/parameters/Dispute-Id'
    post:
      summary: Challenge a dispute
      operationId: challengeDispute
      servers:
      - description: Production server (uses live data)
        url: https://merchant.revolut.com
      description: 'Allows challenging a dispute with a reason, comment and associated evidences.


        Use the uploaded evidences to provide proof for the challenge.


        A dispute previously accepted, cannot be challenged.


        :::note

        This endpoint is only available in **Production** environment.

        :::'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Dispute-Challenge'
            examples:
              challenge_min:
                $ref: '#/components/examples/Req-Dispute-Challenge-Min'
              challenge_with_evidence:
                $ref: '#/components/examples/Req-Dispute-Challenge-With-Evidence'
      responses:
        '204':
          description: Dispute challenged successfully
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: bad_request
                message: Missing Revolut-Api-Version header
                timestamp: 1601296792533
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: unauthenticated
                message: Authentication failed
                timestamp: 1721049596461
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested operation is forbidden
                timestamp: 1721050063886
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
              example:
                code: not_found
                message: The requested resource is not found
                timestamp: 1721050063886
        '422':
          description: Unprocessable entity
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error-v2'
      security:
      - Api-Key: []
      tags:
      - Disputes
components:
  parameters:
    Limit:
      name: limit
      in: query
      schema:
        type: integer
        minimum: 1
        maximum: 500
        default: 100
      description: Maximum number of records to return. Used for **pagination**.
      required: false
    Authorization:
      name: Authorization
      in: header
      schema:
        type: string
        format: Bearer <yourSecretApiKey>
        example: Bearer sk_1234567890ABCdefGHIjklMNOpqrSTUvwxYZ_1234567890-Ab_cdeFGHijkLMNopq
      required: true
      description: "This parameter accepts the [Merchant API Secret key](https://business.revolut.com/settings/apis?tab=merchant-api) to authorise requests coming from the merchant's backend. \n\nIt ensures that ensures that each request is authenticated and authorised by verifying the secret key. The secret key should be included in all request headers as a `Bearer` token.\n\n:::info\nFor more information, see: [Authentication](https://developer.revolut.com/docs/api/merchant#authentication)\n:::"
    From-Created-Date:
      name: from_created_date
      in: query
      required: false
      schema:
        type: string
        format: date-time
      description: 'Retrieve records with a `created_at` value ≥ `from_created_date`.


        Use the [ISO 8601 date-time format](https://en.wikipedia.org/wiki/ISO_8601): `yyyy-MM-ddTHH:mm:ss[.SSSSSS]Z`.'
    Dispute-Id:
      name: dispute_id
      in: path
      schema:
        type: string
        format: uuid
        description: A UUID string, typically used to identify resources.
      required: true
      description: The ID of the `Dispute` object.
    To-Created-Date:
      name: to_created_date
      in: query
      required: false
      schema:
        type: string
        format: date-time
      description: 'Retrieve records with a `created_at` value ≤ `to_created_date`.


        Use the [ISO 8601 date-time format](https://en.wikipedia.org/wiki/ISO_8601): `yyyy-MM-ddTHH:mm:ss[.SSSSSS]Z`.'
    Dispute-State-Query:
      name: state
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
          enum:
          - needs_response
          - under_review
          - won
          - lost
      style: form
      explode: true
      description: 'Filter disputes by state. Repeat the parameter to filter by multiple states.


        | Value | Description |

        |-------|-------------|

        | `needs_response` | Dispute requires your response |

        | `under_review` | Dispute is being reviewed |

        | `won` | Dispute resolved in your favour |

        | `lost` | Dispute resolved against you |


        The parameter is case sensitive.'
    Content-Type:
      name: Content-Type
      in: header
      required: true
      schema:
        type: string
      description: The content type sent in the request.
      example: multipart/form-data
    Revolut-Api-Version:
      name: Revolut-Api-Version
      in: header
      schema:
        type: string
        format: date
        example: '2026-04-20'
        enum:
        - '2023-09-01'
        - '2024-05-01'
        - '2024-09-01'
        - '2025-10-16'
        - '2025-12-04'
        - '2026-03-12'
        - '2026-04-20'
      required: true
      description: 'The version of the Merchant API, specified in `YYYY-MM-DD` format.


        If not specified, you will receive an error.



        :::info

        For more information about API versioning, see: [API versions](https://developer.revolut.com/docs/guides/merchant/reference/versioning/api-versions).

        :::'
      x-config-always-visible-in-example: true
    Payment-Id-Query:
      name: payment_id
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
          format: uuid
      style: form
      explode: true
      description: 'Filter disputes by the ID of the associated payment. Repeat the parameter to filter by multiple payment IDs.


        ```

        https://merchant.revolut.com/api/disputes?payment_id=123&payment_id=456

        ```'
  examples:
    Res-Dispute-Evidence:
      summary: Uploaded evidence
      value:
        id: 121ac27c-b00a-44d0-9120-efeeec7c912d
    Res-Dispute-Sepa-Direct-Debit:
      summary: Dispute for a SEPA Direct Debit payment
      value:
        id: 7a2d8f4b-1c3e-4a56-b789-0d1e2f3a4b5c
        state: needs_response
        substate: new
        created_at: '2026-05-22T09:00:00Z'
        updated_at: '2026-05-22T09:00:00Z'
        response_due_date: '2026-06-05T09:00:00Z'
        reason_code: OTHER
        reason_description: merchant_dispute
        amount: 10000
        currency: EUR
        payment:
          id: 6a0f2bc4-2137-a1ad-9eb6-b34cf4ca6597
          order_id: 2bcaf93a-aa87-4d3d-b5c6-62e06051cff2
          created_at: '2026-05-21T15:59:00.451602Z'
          amount: 10000
          currency: EUR
          payment_method:
            type: sepa_direct_debit
            debtor_iban_last_four: '3273'
            debtor_name: John Doe
            mandate_reference: 69F1CB61BD99A32C8E20D7FB9E21E146
    Res-Dispute-List:
      summary: List of disputes
      value:
      - id: ab934829-e4ba-4e7f-8a21-365cad85c763
        state: under_review
        substate: arbitration
        created_at: '2024-06-13T12:06:18.732706Z'
        updated_at: '2024-09-12T22:27:10.005680Z'
        response_due_date: '2024-10-12T22:27:10.005625Z'
        reason_code: '50'
        reason_description: Fraud
        amount: 50
        currency: EUR
        payment:
          id: 6666f6c7-3898-a094-9c83-dc0152e0185c
          order_id: 6666f685-46a7-a7b9-9860-a28a4f3495a4
          created_at: '2024-06-10T12:51:19.960490Z'
          amount: 50
          currency: EUR
          payment_method:
            type: revolut_pay_account
      - id: 340b85dc-da99-4c5f-9d47-37a45d52a455
        state: lost
        substate: lost_expired
        created_at: '2024-09-11T21:20:05.659978Z'
        updated_at: '2024-09-12T22:35:31.721921Z'
        response_due_date: '2024-09-22T22:35:31.721860Z'
        reason_code: '12.4'
        reason_description: Incorrect Account Number
        amount: 40
        currency: EUR
        payment:
          id: 66e1fc66-7606-a7fb-b2e8-b48fb637783a
          order_id: 66e1fc4d-5cbe-a692-80aa-1cb912291d55
          created_at: '2024-09-11T20:24:06.271746Z'
          amount: 40
          currency: EUR
          payment_method:
            type: card
            card_brand: visa
            card_last_four: '1234'
      - id: e9b5472b-7308-4aea-86a0-d4427bc04c24
        state: lost
        substate: lost_pre_arbitration
        created_at: '2026-05-22T09:00:00Z'
        updated_at: '2026-05-22T10:15:00Z'
        response_due_date: '2030-12-15T00:00:00Z'
        reason_code: OTHER
        reason_description: merchant_dispute
        amount: 91700
        currency: GBP
        payment:
          id: 6a0f2bc4-2137-a1ad-9eb6-b34cf4ca6597
          order_id: 2bcaf93a-aa87-4d3d-b5c6-62e06051cff2
          created_at: '2026-05-21T15:59:00.451602Z'
          amount: 1000
          currency: GBP
          payment_method:
            type: sepa_direct_debit
            debtor_iban_last_four: '3273'
            debtor_name: John Doe
            mandate_reference: 69F1CB61BD99A32C8E20D7FB9E21E146
    Req-Dispute-Challenge-Min:
      summary: Minimal dispute challenge with reason and evidence
      value:
        reason: refund_already_issued
        evidences:
        - 121ac27c-b00a-44d0-9120-efeeec7c912d
    Req-Dispute-Challenge-With-Evidence:
      summary: Dispute challenge with reason, multiple evidences, and comment
      value:
        reason: product_already_delivered
        comment: The customer received the product on 2026-05-10 as confirmed by our delivery records.
        evidences:
        - 121ac27c-b00a-44d0-9120-efeeec7c912d
        - 0010e98d-0653-4dbe-8a4f-70cd5e9491f2
    Res-Dispute-Card:
      summary: Dispute for a card payment
      value:
        id: fccc53e9-00e0-4847-9d54-6938e9cdd3ef
        state: lost
        substate: lost_accepted
        created_at: '2025-03-12T07:00:00.000000Z'
        updated_at: '2025-03-13T10:00:00.000000Z'
        response_due_date: '2025-03-15T12:00:00.000000Z'
        reason_code: '50'
        reason_description: Fraud
        amount: 1500
        currency: EUR
        payment:
          id: 67810850-4c48-a25d-8765-d03d36ca6719
          order_id: 38bd1186-a276-4b14-91b4-5da886481f85
          created_at: '2025-01-02T10:00:00Z'
          arn: P58PC241502Q7800000000A
          amount: 3000
          currency: EUR
          payment_method:
            type: card
            card_brand: visa
            card_last_four: '1234'
  schemas:
    Dispute-Payment:
      type: object
      description: Object containing the details of the original payment associated with the dispute.
      properties:
        id:
          $ref: '#/components/schemas/Dispute-Payment-Id'
        order_id:
          $ref: '#/components/schemas/Dispute-Payment-Order-Id'
        created_at:
          $ref: '#/components/schemas/Dispute-Payment-Created-At'
        arn:
          $ref: '#/components/schemas/Dispute-Payment-Arn'
        amount:
          $ref: '#/components/schemas/Dispute-Payment-Amount'
        currency:
          $ref: '#/components/schemas/Currency'
        payment_method:
          $ref: '#/components/schemas/Dispute-Payment-Method'
    Sepa-Direct-Debit-Mandate-Reference:
      type: string
      description: The unique mandate reference generated by Revolut. Include this in pre-debit notifications sent to your customers.
    Card-Brand-v2:
      type: string
      description: The brand of the payment card.
      enum:
      - visa
      - mastercard
      - american_express
    Dispute-Payment-Order-Id:
      type: string
      format: uuid
      description: The ID of the order linked to the original disputed payment.
    Sepa-Direct-Debit-Debtor-Iban-Last-Four:
      type: string
      description: The last four digits of the debtor's IBAN.
      minLength: 4
      maxLength: 4
    Dispute-Payment-Method-Sepa-Direct-Debit:
      type: object
      description: Object containing details of a SEPA Direct Debit payment.
      properties:
        type:
          $ref: '#/components/schemas/Dispute-Payment-Method-Type'
        debtor_iban_last_four:
          $ref: '#/components/schemas/Sepa-Direct-Debit-Debtor-Iban-Last-Four'
        debtor_name:
          $ref: '#/components/schemas/Sepa-Direct-Debit-Debtor-Name'
        mandate_reference:
          $ref: '#/components/schemas/Sepa-Direct-Debit-Mandate-Reference'
      required:
      - type
    Currency:
      type: string
      format: ISO 4217
      minLength: 3
      maxLength: 3
      description: '[ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code in upper case.


        :::info

        For more information about the supported currencies, see: [Help Center](https://help.revolut.com/business/help/merchant-accounts/payments/in-which-currencies-can-i-accept-payments/).

        :::'
    Dispute-Payment-Id:
      type: string
      format: uuid
      description: The ID of the original payment that was disputed.
    Dispute-Challenge-Evidences:
      type: array
      description: 'A list of IDs of previously uploaded evidence files to associate with this challenge.


        :::warning

        Each evidence ID can only be used for **a single challenge**. This means, that evidences already assigned to a challenge **cannot be reused** for other challenges.

        :::'
      items:
        type: string
        format: uuid
        description: ID of a previously uploaded evidence file.
      minItems: 1
      maxItems: 10
      uniqueItems: true
      example:
      - 121ac27c-b00a-44d0-9120-efeeec7c912d
      - 0010e98d-0653-4dbe-8a4f-70cd5e9491f2
    Dispute-Challenge-Comment:
      type: string
      description: Additional explanation or comment for the challenge, if needed.
      example: Refund PDF attached as evidence.
      maxLength: 250
    Sepa-Direct-Debit-Debtor-Name:
      type: string
      description: The full name of the debtor as provided in the mandate.
    Dispute:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Unique identifier of the dispute.
        state:
          type: string
          enum:
          - needs_response
          - under_review
          - won
          - lost
          description: 'Represents the state of the dispute.


            It indicates either the final outcome of the dispute or if further action is required.


            | Parameter value | Description |

            | --------------- | ----------- |

            | `needs_response` | Indicates that the dispute requires a response or action from the merchant. |

            | `under_review` | Indicates that the dispute is currently under review, and the outcome is pending. |

            | `won` | Indicates that the dispute has been resolved in favor of the merchant. |

            | `lost` | Indicates that the dispute has been resolved against the merchant. |'
        substate:
          type: string
          enum:
          - arbitration
          - lost_accepted
          - lost_arbitration
          - lost_expired
          - lost_pre_arbitration
          - lost_representment
          - new
          - pre_arbitration
          - representment
          - won_arbitration
          - won_pre_arbitration
          - won_representment
          - won_reversal
          description: 'Provides additional granularity about the dispute state.


            It details the progression of the dispute process, showing the current stage or phase.


            | Parameter value | Description |

            | --------------- | ----------- |

            | `new` | The dispute has been recently created and is in the initial phase, awaiting further processing. |

            | `lost_expired` | The dispute has been lost due to expiration, likely because the merchant did not respond within the required timeframe. |

            | `pre_arbitration` | The dispute is in the pre-arbitration phase, where preliminary evidence is being gathered before a formal arbitration process. |

            | `won_pre_arbitration`| The merchant secured a win during the pre-arbitration phase based on the evidence provided. |

            | `lost_pre_arbitration` | The dispute was lost during the pre-arbitration phase, indicating that the preliminary review did not favor the merchant. |

            | `lost_accepted` | The loss has been accepted as final, implying that no further contestation is likely or needed. |

            | `arbitration` | The dispute has escalated to the arbitration stage, where a neutral third party is reviewing the evidence. |

            | `won_arbitration` | The merchant won the dispute during the arbitration process. |

            | `lost_arbitration` | The merchant lost the dispute during the arbitration process. |'
        created_at:
          type: string
          format: date-time
          description: '[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time when the dispute was created.'
        updated_at:
          type: string
          format: date-time
          description: '[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time when the dispute was last updated.'
        response_due_date:
          type: string
          format: date-time
          description: "[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time until when the merchant needs to respond to the dispute.\n\nThe response time by default is 15 days after the dispute is created. If no response is provided by this date, the dispute transitions to:\n  - `state: lost`\n  - `substate: lost_expired` "
        reason_code:
          type: string
          description: "Dispute reason code from the payment scheme, following standard formats defined by individual providers.\n\n:::info\nFor complete, official lists of dispute codes, see:  \n- **Visa**: [Visa Core Rules and Visa Product and Service Rules](https://corporate.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf) \n- **Mastercard**: [Chargeback Guide - Merchant Edition](https://www.mastercard.com/content/dam/public/mastercardcom/na/global-site/documents/chargeback-guide.pdf)\n- **American Express**: [Chargeback Codes](https://www.americanexpress.com/content/dam/amex/au/en/merchant/static/chargebackcodeguide.pdf)\n:::"
        reason_description:
          type: string
          description: Provides a human-readable explanation for the dispute reason codes.
        amount:
          type: integer
          description: 'Disputed amount expressed in minor currency units, according to the [ISO 4217 standard](https://en.wikipedia.org/wiki/IS

# --- truncated at 32 KB (40 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/revolut/refs/heads/main/openapi/revolut-disputes-api-openapi.yml