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

# List manual refund requests (admin)

> Lists pending and historical entries from the **manual refund queue**.
Entries are created automatically when `POST /v1/charges/:id/chargeback-alert`
falls back to a manual refund (the PSP does not support API refunds or
the call failed). The balance has already been refunded to the
cardholder's account at the FastPay ledger level — the queue tracks the
out-of-band action the finance team still needs to perform.

Requires the `admin.manual_refund_requests.read` permission.



## OpenAPI

````yaml /api-reference/openapi.yaml get /v1/manual-refund-requests
openapi: 3.0.0
info:
  title: FastPay API
  version: 1.0.0
  description: >-
    API for creating and managing payment charges.


    ## Authentication


    This API uses **Basic Authentication** for direct API access, such as
    creating charges.

    Use your API key as the username and an empty string as password.

    The header should be formatted as:


    `Authorization: Basic {base64(apiKey:)}`.


    For example:


    ```

    Authorization: Basic YWxleG91dG9uOiIi

    ```


    ## Webhooks


    FastPay sends webhooks to notify your application about charge status
    changes in real-time.

    Webhooks are sent via HTTP POST requests to your configured webhook
    endpoints.


    ### Webhook Events


    The following webhook events are available for charges:


    - `charge.created` - Sent when a new charge is created

    - `charge.pending` - Sent when a charge is pending payment

    - `charge.paid` - Sent when a charge is successfully paid

    - `charge.updated` - Sent when a charge is updated


    ### Webhook Payload Structure


    All webhook payloads follow this structure:


    ```json

    {
      "id": "webhook_event_id",
      "event": "charge.paid",
      "data": {
        // Complete charge object
      }
    }

    ```


    ### Webhook Delivery


    - Webhooks are sent via HTTP POST requests

    - Content-Type: `application/json`

    - Retry logic is implemented for failed deliveries

    - Webhook events are stored in the database for audit purposes

    - Delivery logs are maintained for debugging and monitoring


    ### Webhook Security


    - Webhooks are sent to pre-configured endpoints

    - Endpoints can be enabled/disabled per merchant

    - Event filtering is supported (only receive specific events)

    - Failed deliveries are retried with exponential backoff
servers:
  - url: https://api-global.fastpaybrasil.com
    description: Produção e Sandbox (diferenciados pela API key)
security: []
paths:
  /v1/manual-refund-requests:
    get:
      tags:
        - Chargeback Alerts
      summary: List manual refund requests (admin)
      description: >-
        Lists pending and historical entries from the **manual refund queue**.

        Entries are created automatically when `POST
        /v1/charges/:id/chargeback-alert`

        falls back to a manual refund (the PSP does not support API refunds or

        the call failed). The balance has already been refunded to the

        cardholder's account at the FastPay ledger level — the queue tracks the

        out-of-band action the finance team still needs to perform.


        Requires the `admin.manual_refund_requests.read` permission.
      parameters:
        - name: status
          in: query
          description: Filter by request status.
          required: false
          schema:
            type: string
            enum:
              - pending
              - completed
              - failed
        - name: merchantId
          in: query
          description: Filter by merchant ID.
          required: false
          schema:
            type: string
            example: 2vorkDcXyvzifL63YX09S9VqcnI
        - name: page
          in: query
          description: Page number (starts at 1)
          required: false
          schema:
            type: integer
            default: 1
        - name: size
          in: query
          description: Number of items per page
          required: false
          schema:
            type: integer
            default: 20
      responses:
        '200':
          description: List of manual refund requests
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                          example: 2RhQg9M7ZCg3X3nMb9W1kX8Q
                        merchantId:
                          type: string
                        merchantLegalName:
                          type: string
                          nullable: true
                        merchantEmail:
                          type: string
                          nullable: true
                        chargeId:
                          type: string
                        refundId:
                          type: string
                        amount:
                          type: number
                          example: 199.9
                        currency:
                          type: string
                          example: BRL
                        status:
                          type: string
                          enum:
                            - pending
                            - completed
                            - failed
                        reason:
                          type: string
                          nullable: true
                        resolvedByUserId:
                          type: string
                          nullable: true
                        resolvedAt:
                          type: string
                          format: date-time
                          nullable: true
                        notes:
                          type: string
                          nullable: true
                        createdAt:
                          type: string
                          format: date-time
                  page:
                    type: integer
                  pages:
                    type: integer
                  total:
                    type: integer
                  size:
                    type: integer
                  pendingCount:
                    type: integer
                    description: >-
                      Total of requests still in `pending` status for the
                      gateway.
        '401':
          description: Unauthorized - invalid credentials
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden - missing `admin.manual_refund_requests.read` permission
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearer: []
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        statusCode:
          type: integer
          description: HTTP status code
          example: 422
        message:
          type: string
          description: Descriptive error message
          example: SubMerchant is not active
        error:
          type: string
          description: Error type
          example: Unprocessable Entity
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: |-
        JWT Bearer token authentication. Use the JWT token obtained
        from the login endpoint in the Authorization header as 'Bearer {token}'.

````