RFI Cases
Learn about RFI Cases (Request for Information) - when they're triggered, how to respond, and the complete workflow for handling transaction-related information requests.
An RFI Case (Request for Information) is raised by Banking Circle when information is required from you. Information can be requested for several reasons based on the type of RFI.
An RFI Case always requires an action from you and remains "OPEN" until the required information is submitted or the deadline has passed. The consequence of not submitting answers will depend on the type of RFI.
Action Required: All RFI Cases require a response from you. Failure to respond may result in transaction delays, rejections, or account restrictions depending on the RFI type.
Transaction RFI
An RFI of type "TRANSACTION" is sent when an incoming or outgoing payment as been caught in our sanctions screening process. This will prevent the payment from being sent/received from/to your account until we have received answers to the questions being asked.
The subject on an RFI is the individual or company in question. I.e. if subject is an individual the questions being asked is in context of that individual.
Responding to an Transaction RFI
Step 1: Retrieve RFI Details
Use the GET RFI Case endpoint to get the full case details, including:
- List of questions to answer (see Types of Questions)
- Subject and Transaction information
Step 2: Submit Your Response
You respond to an RFI via the Submit RFI Answers endpoint. You can respond to an RFI in two ways:
- Request a return: You indicate to us that you want the payment in question returned. No answers needed.
- Answer the questions: All questions must be answered. If you can't or refuse to answer a particular question, you can leave the answer empty but all questions asked, must have a matching answer in the list.
To answer a question with index "1" you add an entry to the answers list in the RFI submission request with index "1". If the question type is not an attachment, you provide your actual answer in the "answer" property which is within the limitations of the particular type of question.
For questions of type attachment you need to first upload attachments to the RFI Case via the Upload attachment endpoint. The response will contain an attachment id which you can the add to the attachmentIds list in the list of answers in the RFI submission request.
Types of Questions
The various types of questions that may be asked can be retrieved through the GET RFI Question Types endpoint. See the endpoint specification for examples.
Most questions are free-text fields limited only by a maximum length, but some use different input formats:
| Question Id | Description | Example |
|---|---|---|
dateOfBirth | yyyy-MM-dd | "1994-06-01" |
nationality | Comma-separated ISO3166 two letter country codes | "GB,DK,US" |
other | Free text. The actual question is "dynamic" and will be present in the "Label" property in the question list on the actual RFI | |
attachment | This is a question that is answered with attachments. Similar to other, the "Label" property contains information about what files are requested. |
Workflow
The diagram below illustrates the lifecycle of an RFI Case.
sequenceDiagram
participant BC as Banking Circle
participant Client as Client
BC->>BC: Create RFI Case
alt Client uses webhook data
BC-->>Client: Send webhook case-event (Case Opened)
Client->>Client: Extract Case ID from webhook
else Client polls for cases
Client->>BC: GET Cases (/api/v1/cases)
BC-->>Client: Return case list (including new Case ID)
end
Client->>BC: GET RFI Case (/api/v1/cases/rfi/{case-id})
loop Upload 0 or more attachments
Client->>BC: Upload Attachment (/api/v1/cases/{case-id}/attachments)
BC-->>Client: Attachment ID returned
end
Client->>Client: Link attachments to RFI questions
Client->>BC: Submit RFI response<br/>POST /api/v1/cases/rfi/{case-id}/submissions
BC->>BC: RFI Status Updated to<br/> 'SUBMITTED' or 'RETURN_REQUESTED'
BC->>BC: Review RFI response
BC-->>Client: Send webhook case-event (Case Closed)
Updated 4 days ago
