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

# Iniciar uma devolução em uma recuperação de valores

> Inicia uma devolução para uma recuperação de valores no estado ANALYSED, dentro do escopo do participante determinado pelo tenant autenticado. A recuperação muda para REFUNDING e é retornada atualizada com HTTP 200. Retorna 404 quando nenhuma recuperação ativa com esse ID pertence ao participante e 409 quando seu estado atual não permite uma devolução. A resposta é uma representação resumida da recuperação de valores.



## OpenAPI

````yaml pt/openapi/v3-current/pix-lerian-dict.yaml POST /dict/funds-recoveries/{id}/refund
openapi: 3.1.0
info:
  contact:
    name: Lerian Studio
    url: https://lerian.studio
  description: >-
    API pública para chaves Pix, reivindicações, marcadores de fraude, relatos
    de infração e recuperação de valores do MED.
  license:
    name: Elastic License 2.0
    url: https://www.elastic.co/licensing/elastic-license
  title: Pix Lerian — DICT
  version: release-candidate
servers:
  - url: https://api.example.com/dict-hub/v1
    description: Substitua o host de exemplo pela URL fornecida no onboarding do ambiente.
security:
  - BearerAuth: []
tags:
  - description: Registro, consulta, listagem, atualização e remoção de chaves Pix.
    name: Entries
  - description: Consulta de chaves Pix e verificação de existência no diretório DICT.
    name: Keys
  - description: Gestão de reivindicações de posse e portabilidade de chaves Pix.
    name: Claims
  - description: Gestão de recuperações de valores do MED 2.0 no escopo do participante.
    name: Funds Recoveries
  - description: Gestão de relatos de infração do MED 2.0 para a organização autenticada.
    name: Infraction Reports
  - description: Criação, consulta, cancelamento e liquidação de devoluções do MED 2.0.
    name: Refunds
  - description: >-
      Criação, consulta, listagem e cancelamento de marcadores de fraude do
      DICT.
    name: Fraud Markers
paths:
  /dict/funds-recoveries/{id}/refund:
    post:
      tags:
        - Funds Recoveries
      summary: Iniciar uma devolução em uma recuperação de valores
      description: >-
        Inicia uma devolução para uma recuperação de valores no estado ANALYSED,
        dentro do escopo do participante determinado pelo tenant autenticado. A
        recuperação muda para REFUNDING e é retornada atualizada com HTTP 200.
        Retorna 404 quando nenhuma recuperação ativa com esse ID pertence ao
        participante e 409 quando seu estado atual não permite uma devolução. A
        resposta é uma representação resumida da recuperação de valores.
      operationId: refundFundsRecovery
      parameters:
        - description: >-
            Chave criada pelo cliente para repetir com segurança exatamente a
            mesma requisição.
          in: header
          name: Idempotency-Key
          required: true
          schema:
            maxLength: 64
            minLength: 1
            type: string
            description: >-
              Chave criada pelo cliente para repetir com segurança exatamente a
              mesma requisição.
          example: pix-demo-20260903-000001
        - description: Funds recovery internal ID (UUID format)
          in: path
          name: id
          required: true
          schema:
            description: Funds recovery internal ID (UUID format)
            examples:
              - 018f8c1d-1234-7abc-9def-000000000001
            type: string
          example: 01960718-a213-2435-6078-901234567123
        - description: >-
            Best-effort business correlation id (observability only; never
            fabricated).
          in: header
          name: X-Correlation-Id
          schema:
            description: >-
              Best-effort business correlation id (observability only; never
              fabricated).
            examples:
              - 7c9e6679742540de944be07fc1f90ae7
            type: string
          example: 7c9e6679742540de944be07fc1f90ae7
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RefundFundsRecoveryResponse'
              examples:
                exemploFicticio:
                  summary: Exemplo fictício
                  value:
                    bacenFundsRecoveryId: 9f3a8b7e-2c1d-4e5a-8b6f-1a2b3c4d5e6f
                    contactInformation:
                      email: user@example.com
                      phone: '+5511999999999'
                    correlationId: 7c9e6679742540de944be07fc1f90ae7
                    createdAt: '2026-05-17T13:30:00Z'
                    id: 018f8c1d-1234-7abc-9def-000000000001
                    reportDetails: Victim of a WhatsApp scam
                    reporterParticipant: '12345678'
                    rootTransactionId: E12345678202605171530aB3xK9mWq2z
                    situationType: SCAM
                    status: REFUNDING
          description: OK
        '400':
          content:
            application/json:
              example:
                code: PIX-0030
                title: Idempotency Key Required
                message: >-
                  The Idempotency-Key header is required for this operation and
                  must be within the accepted length.
              schema:
                $ref: '#/components/schemas/LegacyErrorEnvelope'
          description: >-
            Idempotency-Key absent or longer than 64 bytes (PIX-0030). Legacy
            {code,title,message} envelope, NOT problem+json.
        '412':
          content:
            application/json:
              example:
                code: PIX-0031
                title: Idempotency Key Conflict
                message: The Idempotency-Key was already used with a different request.
              schema:
                $ref: '#/components/schemas/LegacyErrorEnvelope'
          description: >-
            Idempotency-Key replayed with a divergent request -- a different
            method, URL (including the path parameter), body, or identity header
            among X-Account-Id / X-Reason / X-End-To-End-Id (PIX-0031). Legacy
            {code,title,message} envelope, NOT problem+json.
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
      x-codeSamples:
        - lang: bash
          label: cURL com dados fictícios
          source: |-
            curl --request POST \
              --url https://api.example.com/dict-hub/v1/dict/funds-recoveries/01960718-a213-2435-6078-901234567123/refund \
              --header 'Authorization: Bearer demo-access-token' \
              --header 'Idempotency-Key: pix-demo-20260903-000001' \
              --header 'X-Correlation-Id: 7c9e6679742540de944be07fc1f90ae7'
components:
  schemas:
    RefundFundsRecoveryResponse:
      additionalProperties: false
      properties:
        bacenFundsRecoveryId:
          examples:
            - 9f3a8b7e-2c1d-4e5a-8b6f-1a2b3c4d5e6f
          type: string
        contactInformation:
          $ref: '#/components/schemas/ContactInformationOutput'
        correlationId:
          examples:
            - 7c9e6679742540de944be07fc1f90ae7
          type: string
        createdAt:
          examples:
            - '2026-05-17T13:30:00Z'
          format: date-time
          type: string
        id:
          examples:
            - 018f8c1d-1234-7abc-9def-000000000001
          type: string
        reportDetails:
          examples:
            - Victim of a WhatsApp scam
          type: string
        reporterParticipant:
          examples:
            - '12345678'
          type: string
        rootTransactionId:
          examples:
            - E12345678202605171530aB3xK9mWq2z
          type: string
        situationType:
          enum:
            - SCAM
            - ACCOUNT_TAKEOVER
            - COERCION
            - FRAUDULENT_ACCESS
            - OTHER
            - UNKNOWN
          examples:
            - SCAM
          type: string
        status:
          enum:
            - CREATED
            - TRACKED
            - AWAITING_ANALYSIS
            - ANALYSED
            - REFUNDING
            - COMPLETED
            - CANCELLED
          examples:
            - REFUNDING
          type: string
      required:
        - id
        - bacenFundsRecoveryId
        - rootTransactionId
        - situationType
        - contactInformation
        - status
        - reporterParticipant
        - createdAt
      type: object
    LegacyErrorEnvelope:
      additionalProperties: false
      properties:
        code:
          description: PIX-XXXX error code
          type: string
        message:
          description: Human-readable error message
          type: string
        title:
          description: Short error title
          type: string
      required:
        - code
        - title
        - message
      type: object
    Detail:
      additionalProperties: false
      properties:
        code:
          description: >-
            Stable, machine-readable domain error code scoped to the emitting
            service (format: <SERVICE>-NNNN).
          examples:
            - ERR-0001
          type: string
        detail:
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
          examples:
            - Property foo is required but is missing.
          type: string
        errors:
          description: Optional list of individual error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type:
            - array
            - 'null'
        instance:
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem.
          examples:
            - https://example.com/error-log/abc123
          format: uri
          type: string
        status:
          description: HTTP status code
          examples:
            - 400
          format: int64
          type: integer
        title:
          description: >-
            A short, human-readable summary of the problem type. This value
            should not change between occurrences of the error.
          examples:
            - Bad Request
          type: string
        type:
          default: about:blank
          description: A URI reference to human-readable documentation for the error.
          examples:
            - https://example.com/errors/example
          format: uri
          type: string
        upstream:
          $ref: '#/components/schemas/Upstream'
          description: >-
            RFC 9457 extension member: the error a proxied third-party provider
            reported. Absent unless the emitting service explicitly surfaced
            one.
      type: object
    ContactInformationOutput:
      additionalProperties: false
      properties:
        email:
          examples:
            - user@example.com
          type: string
        phone:
          examples:
            - '+5511999999999'
          type: string
      required:
        - email
        - phone
      type: object
    ErrorDetail:
      additionalProperties: false
      properties:
        location:
          description: >-
            Where the error occurred, e.g. 'body.items[3].tags' or
            'path.thing-id'
          type: string
        message:
          description: Error message text
          type: string
        value:
          description: The value at the given location
      type: object
    Upstream:
      additionalProperties: false
      properties:
        code:
          description: The upstream provider's own error code, verbatim.
          examples:
            - E4001
          type: string
        message:
          description: >-
            The upstream provider's own error message, verbatim (bounded, never
            its raw response body).
          examples:
            - account not found at provider
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      bearerFormat: JWT
      description: JWT bearer token issued by the identity provider.
      scheme: bearer
      type: http

````