Requests for Information (RFIs)

When a reviewer needs more information to finish a compliance review, they raise a request for information (RFI). The review moves to additionalInformationRequested. It does not continue until you answer, unless the RFI is withdrawn after Mural rejects the Compliance Review (see the lifecycle).

An RFI is its own resource, addressed by its own id. It lists the attestations the reviewer wants again, and how much of each one to send. Some attestations need a full resupply. Others need only the named fields. A reviewer can also ask for something outside the standard attestations: a supplemental document or a written answer. It appears in the same list, and each of its details names one thing to send.

Supporting-document attestations, such as proof of address or UBO ownership documents, and answers to supplemental requests can include an optional additionalInformation note for the reviewer, for example to point at the page of a document that answers the request.

StepEndpoint
Read the RFIget RFI endpoint
Upload attestationsupload RFI attestations endpoint
Submit your responsesubmit RFI endpoint

The lifecycle

  1. A reviewer evaluates your compliance review. The review is in inReview.
  2. When the reviewer requires more information, the Compliance Review status moves to additionalInformationRequested. Mural emits two webhook events: compliance_review_status_changed, whose currentStatus carries the rfiId, and rfi_created.
  3. You get the RFI by the id, upload the necessary attestations, then submit the RFI.
  4. Submitting validates your response. The result is one of:
    • They pass. The RFI moves to submitted and the Compliance Review returns to inReview.
    • They fail. The RFI moves to submissionValidationsFailed and the Compliance Review status does not change. Correct the data and submit again.
    • The review is rejected. The RFI moves to submitted and the Compliance Review moves to rejected.
  5. If Mural rejects the Compliance Review while the RFI is open, the review stays in additionalInformationRequested and you can still answer it. A submission that passes validation returns the review to inReview. A submission that fails validation leaves the review in additionalInformationRequested, and the RFI stays open. If no submission has passed validation 20 business days (US banking days, Eastern Time) after the rejection, Mural withdraws the RFI: it moves to cancelled with reason WITHDRAWN_FOR_NO_RESPONSE, and the Compliance Review moves to rejected. Mural emits rfi_status_changed and compliance_review_status_changed. The withdrawal happens on or after midnight ET at the start of the 20th business day after the rejection. Sandbox does not withdraw RFIs this way.

You answer an RFI once. If the reviewer needs more information after your response, they will raise a new RFI and the Compliance Review reports a new rfiId.

To respond to an RFI step by step, see the Responding to RFIs Programmatically integration guide.


Did this page help you?