> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a payout RFI > Retrieves the active Request for Information (RFI) for the specified fiat payout. An RFI is issued when the compliance team requires additional information before the payout can proceed. Check the `fieldRequirements.schema` to determine which fields must be submitted via `POST /v1/payouts/{id}/rfi/submit`. ## OpenAPI ````yaml openapi/payouts.yaml get /v1/payouts/{id}/rfi openapi: 3.0.2 info: version: ${version} title: Crypto Payouts API description: >- The Circle Payouts API allows you to programmatically make fast, global payouts to your customers, vendors, and suppliers. Make payouts on supported blockchains. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Payouts description: Create and get information on address book payouts. - name: Crypto Address Book description: Manage blockchain addresses with metadata. paths: /v1/payouts/{id}/rfi: get: tags: - Payouts summary: Get a payout RFI description: > Retrieves the active Request for Information (RFI) for the specified fiat payout. An RFI is issued when the compliance team requires additional information before the payout can proceed. Check the `fieldRequirements.schema` to determine which fields must be submitted via `POST /v1/payouts/{id}/rfi/submit`. operationId: getPayoutRfi parameters: - $ref: '#/components/parameters/IdPath' responses: '200': description: Successfully retrieved the payout RFI. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: GetPayoutRfiResponse properties: data: $ref: '#/components/schemas/PayoutRfi' examples: Payout RFI: value: data: id: b8627ae8-732b-4d25-b947-1df8f4007a29 paymentId: f4b26b87-0000-4c42-a8d6-000000000001 status: INFORMATION_REQUIRED level: LEVEL_1 expiresAt: '2020-04-17T02:13:30.000Z' fieldRequirements: version: 1 schema: type: object required: - purposeOfFunds properties: purposeOfFunds: type: string fileRequirements: [] '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' security: - bearerAuth: [] components: parameters: IdPath: name: id description: Universally unique identifier (UUID v4) of a resource. in: path required: true schema: type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: PayoutRfi: type: object description: >- Details of a Request for Information (RFI) associated with a fiat payout. properties: id: type: string format: uuid description: Unique identifier for the RFI. example: b8627ae8-732b-4d25-b947-1df8f4007a29 paymentId: type: string format: uuid description: Identifier of the payout this RFI is associated with. example: f4b26b87-0000-4c42-a8d6-000000000001 status: $ref: '#/components/schemas/PayoutRfiStatus' level: $ref: '#/components/schemas/PayoutRfiLevel' expiresAt: type: string format: date-time description: ISO 8601 timestamp after which the RFI can no longer be submitted. example: '2020-04-17T02:13:30.000Z' fieldRequirements: type: object nullable: true description: >- Schema describing the fields that must be submitted to resolve the RFI. properties: version: type: integer description: Schema version number. example: 1 schema: type: object description: >- JSON Schema object defining the required fields and their validation rules. additionalProperties: true fileRequirements: type: array nullable: true description: List of file attachments required to resolve the RFI. items: type: object properties: fileKey: type: string description: > Identifier for this file requirement. Pass this value as `fileMetadata.fileKey` when calling `POST /v1/payouts/{id}/rfi/files`. example: proofOfFunds fileName: type: string description: Human-readable label for the required file. example: Proof of Funds required: type: boolean description: Whether this file is mandatory. example: true certificate: type: object nullable: true description: > Encryption certificate used to secure file uploads for BFI-generated RFIs. Present when `fileRequirements` is non-empty and the RFI was generated by a BFI (external). Absent for internally-generated RFIs — files for those RFIs are stored with standard encryption-at-rest and do not require client-side encryption. The `jwk` field contains an EC public key in JWK format — use it to wrap the AES-128 file-encryption key via ECDH-ES+A128KW before calling `POST /v1/payouts/{id}/rfi/files`. properties: jwk: type: object description: EC public key in JSON Web Key (JWK) format. additionalProperties: true example: kty: EC crv: P-256 x: f83OJ3D2xF1Bg8vub9tLe1gHMzV76e8Tus9uPHvRVEU 'y': x_FEzRu9m36HLN_tue659LNpXW6pCyStikYjKIWI5a0 PayoutRfiStatus: type: string description: >- Lifecycle status of a payout RFI. `INFORMATION_REQUIRED` means the user must submit answers; `IN_REVIEW` means answers were received and are under review; `APPROVED` means the RFI was resolved successfully; `REJECTED` means the RFI was closed without approval. enum: - INFORMATION_REQUIRED - IN_REVIEW - APPROVED - REJECTED example: INFORMATION_REQUIRED PayoutRfiLevel: type: string description: >- Severity level of a payout RFI, indicating the depth of information required. `LEVEL_1` requires basic identity details; `LEVEL_2` requires source-of-funds documentation; `LEVEL_3` requires full enhanced due diligence. enum: - LEVEL_1 - LEVEL_2 - LEVEL_3 example: LEVEL_1 responses: NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. NotFound: description: The specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotFound required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 404 message: Not found. examples: response: value: code: 404 message: Not found. securitySchemes: bearerAuth: type: http scheme: bearer ````