> ## Documentation Index
> Fetch the complete documentation index at: https://yn-c9bb3266.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Dispute

> Updates an existing dispute with additional evidence or status changes.



## OpenAPI

````yaml PATCH /v1/payments/{payment_id}/disputes/{dispute_id}
openapi: 3.1.0
info:
  title: Yuno Payments API
  description: >-
    Yuno payment orchestration platform — unified REST API for payments,
    checkout sessions, customers, payment methods, subscriptions, payouts,
    marketplace transfers, and banking connectivity across Latin America.
  version: 1.0.0
  contact:
    name: Yuno Support
    email: support@y.uno
    url: https://docs.y.uno
  license:
    name: Proprietary
    url: https://y.uno
servers:
  - url: https://api-sandbox.y.uno
    description: Sandbox
  - url: https://api.y.uno
    description: Production
security:
  - publicApiKey: []
    privateSecretKey: []
paths:
  /v1/payments/{payment_id}/disputes/{dispute_id}:
    patch:
      tags:
        - Payments
      summary: Update dispute
      description: Updates an existing dispute with additional evidence or status changes.
      operationId: updateDispute
      parameters:
        - name: payment_id
          in: path
          required: true
          description: The unique identifier of the payment
          schema:
            type: string
            format: uuid
        - name: dispute_id
          in: path
          required: true
          description: The unique identifier of the dispute
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DisputeUpdate'
            example:
              evidence:
                description: Order was delivered on 2026-02-28
                documents:
                  - https://example.com/proof-of-delivery.pdf
              status: EVIDENCE_SUBMITTED
      responses:
        '200':
          description: Dispute updated successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Dispute'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Resource not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    DisputeUpdate:
      type: object
      properties:
        evidence:
          type: object
          properties:
            description:
              type: string
              description: Evidence description
            documents:
              type: array
              items:
                type: string
                format: uri
              description: URLs of supporting documents
        status:
          type: string
          enum:
            - EVIDENCE_SUBMITTED
            - ACCEPTED
          description: New dispute status
    Dispute:
      type: object
      properties:
        id:
          type: string
          format: uuid
        payment_id:
          type: string
          format: uuid
        status:
          type: string
          enum:
            - OPEN
            - EVIDENCE_SUBMITTED
            - WON
            - LOST
            - ACCEPTED
        amount:
          $ref: '#/components/schemas/Amount'
        reason:
          type: string
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    Error:
      type: object
      description: >-
        Standard error envelope returned by every Yuno service for any 4xx or
        5xx response. Top level. `code` is a stable SCREAMING_SNAKE_CASE
        identifier. `messages` is always an array of strings, even when there is
        only one entry. There is no `error` wrapper, no singular `message`, no
        `type`, no `details`. See the Error handling guide for the full code
        catalog.
      required:
        - code
        - messages
      properties:
        code:
          type: string
          description: >-
            Stable, machine readable identifier. Branch on this in your client.
            Common values include `BAD_REQUEST`, `VALIDATION_ERROR`,
            `INVALID_REQUEST`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`,
            `TOO_MANY_REQUESTS`, `INTERNAL_ERROR`, `BAD_GATEWAY`,
            `SERVICE_UNAVAILABLE`, plus business codes like
            `CUSTOMER_ID_DUPLICATED`, `RECIPIENT_NOT_FOUND`, `INVALID_STATE`,
            and the `PROVIDER_*` family for downstream provider errors.
          example: VALIDATION_ERROR
        messages:
          type: array
          description: >-
            Human readable details. Validation errors put one entry per failed
            field, formatted `"fieldName message"`.
          items:
            type: string
          example:
            - merchant_customer_id must not be blank
      example:
        code: VALIDATION_ERROR
        messages:
          - amount must be greater than 0
          - country must not be blank
    Amount:
      type: object
      required:
        - currency
        - value
      properties:
        currency:
          type: string
          description: ISO 4217 currency code
          example: BRL
        value:
          type: number
          description: >-
            Payment amount in major currency units (e.g., 150.00 means 150 BRL,
            not cents). For zero-decimal currencies like CLP and PYG, use whole
            numbers (e.g., 15000 means 15,000 CLP).
          example: 100
      example:
        currency: BRL
        value: 100
  securitySchemes:
    publicApiKey:
      type: apiKey
      in: header
      name: public-api-key
      description: Your public API key from the Yuno Dashboard
    privateSecretKey:
      type: apiKey
      in: header
      name: private-secret-key
      description: Your private secret key (server-side only)

````