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

# Payout / Deposit RFI

> Published when additional documentation is required for a payout or deposit transaction.

## Event Types

| Event Type                        | Description                                                               |
| --------------------------------- | ------------------------------------------------------------------------- |
| `rfi.transaction.action_required` | Additional documentation is required for a payout or deposit transaction. |

<Warning>
  The RFI-related API endpoints (Retrieve RFI, Answer RFI) are not yet fully available in the current API version. This webhook event is documented for reference, but the complete end-to-end RFI workflow cannot be fully supported via the API at this time.
</Warning>

## Usage guidelines

Upon receiving this notification, follow the steps below:

<Steps>
  <Step title="Retrieve RFI details">
    Use the `rfi_id` provided in the notification to call the Retrieve RFI API. This returns the required file information for the current RFI.
  </Step>

  <Step title="Upload required file">
    Upload the specified file via the [Upload A File](/docs/account-center/v1.6/api-reference/upload-file) API. Upon success, a `file_id` will be returned.
  </Step>

  <Step title="Submit file via Answer RFI">
    Submit the `file_id` to UQPAY using the Answer RFI API.

    Ensure that the `answer.key` in your request matches the `question.key` returned from the Retrieve RFI response.
  </Step>
</Steps>


## OpenAPI

````yaml webhooks-banking.yaml webhook payoutDepositRfi
openapi: 3.1.0
info:
  title: Banking Webhooks
  version: 1.6.0
  description: |
    Webhook events for the Global Account product. UQPAY sends these events to
    your registered webhook endpoint as HTTP POST requests with a JSON body.

    All events share a common envelope (`event_id`, `event_name`, `event_type`,
    `source_id`, `version`) and carry event-specific data in the `data` field.
servers: []
security: []
paths: {}

````