> For the complete documentation index, see [llms.txt](https://developer.flash-payments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.flash-payments.com/compliance/request-for-information/rfi-statuses.md).

# RFI statuses

RFI lifecycle statuses

Most common RFI status transitions follow one of these paths.

**Happy path**

`PENDING` → `ASSESSING` → `CLOSED` <br>

1. It starts when our compliance review flags one of your transactions. An RFI is created with a list of questions and a response deadline.\
   \
   Status  `PENDING` means the RFI is open for your response. \
   Answer each question via [`answerRfiQuestion`](/compliance/request-for-information/answer-rfi-questions.md) before `deadline`. The status stays `PENDING` until all answers are received or the deadline passes.<br>
2. The last open question is answered.\
   \
   Status `ASSESSING` means that all your answers have been received and are under our review. No action is required from you.<br>
3. The review is completed.\
   \
   Status  `CLOSED` means that the RFI is finalised. No further answers are accepted. ***Final status.***

\
**Declined or expired path**

`PENDING` → `CLOSED`

An RFI can also move to `CLOSED` directly from `PENDING` when you [decline it](/compliance/request-for-information/decline-an-rfi.md), or when the deadline passes without a complete response from your end.

\
**Cancelled path**

`PENDING` → `CANCELLED`  or  `ASSESSING` → `CANCELLED`&#x20;

Separately from your responses, our compliance team can withdraw an RFI when the information is no longer needed — for example the underlying transaction question was resolved another way. The RFI moves to `CANCELLED`, no further answers are accepted, and any linked deposits, withdrawals, or payments are left untouched and continue on their own lifecycle. You don't need to do anything — we notify you by email and via the `rfi_cancelled` webhook. ***Final status.***

{% hint style="info" %}
`CANCELLED` status is different from `CLOSED`. The status `CLOSED` is the outcome of a review (the linked transactions are then released or rejected). `CANCELLED` means we withdrew the request itself — the linked transactions are not affected by the cancellation.
{% endhint %}

Each transition emits a [webhook event](/basics/webhooks.md#rfi_created):

| Event           | Status      |
| --------------- | ----------- |
| `rfi_created`   | `PENDING`   |
| `rfi_assessing` | `ASSESSING` |
| `rfi_closed`    | `CLOSED`    |
| `rfi_cancelled` | `CANCELLED` |

**Status message**

The `statusMessage` field carries a meaningful explanation of the current status, for example "We are waiting for your replies" while `PENDING`, or "We assessed the information you provided" once `CLOSED`. The exact wording varies with the circumstances — treat it as display text, not as a value to parse.

{% hint style="info" %}
Once an RFI is `CLOSED`, the outcome is applied to the linked transactions: they are released, or rejected with an explanatory `rejectCode` (see [Rejection codes](/moving-funds/payouts/rejection-codes.md)). The RFI itself does not expose the review verdict.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.flash-payments.com/compliance/request-for-information/rfi-statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.