Request For Information (RFI)
Request For Information (RFI) is a verification workflow triggered when DLT requires additional information or documentation from an onboarded customer (e.g., periodic reviews, transaction clarifications).
RFI entitlement cannot be initiated by the client via the API and is exclusively triggered internally by DLT.
Entitlement Summary
| Field | Value | Description |
|---|---|---|
| Name | rfi | The system name of the entitlement (exclusively triggered by DLT). |
| Applies To | Person | This entitlement is triggered for individual customers. |
| Prerequisites | 1. Onboarded: The target Person must have a successfully completed onboarding. | |
| Outcome | Upon completion, the review result is set to success. |
Triggers
The RFI entitlement is initiated by the compliance team when they require a customer to provide updated information or clarification on specific items.
Operational Workflow
When an RFI is triggered, the system may apply restrictions to the account.
1. Account Locking (Optional)
Upon initiation or during the workflow, the system may apply:
- Funding Lock: Prevents deposits and withdrawals.
- Trading Lock: Prevents the execution of new trades.
Your application will receive notifications regarding these locks via the notification system if they are applied.
2. Requirements Request
The system will issue a requirementsQuestionnaire webhook to your application.
- Webhook Reason:
request_for_information
This webhook contains the identifiers for the questionnaires or document requests that the customer must fulfill. Your application must fetch these requirements and present them to the user.
3. Reminders
The system may send periodic reminders if the customer has not yet provided the requested information. Your application will receive reminder notifications (e.g. "2-week-reminder", "4-week-reminder").
4. Submission & Review
Once the customer submits the requested data, the compliance team reviews it. This process can be iterative, and further information may be requested if the initial submission is insufficient.
Completion & Results
The workflow concludes once all requested information has been provided and reviewed.
Success
- Release of Locks: If locks were applied, their release is not automatic. The workflow waits for an explicit unlock event. Once received, Funding and Trading locks are only removed if they are not also required by other active compliance processes.
- Webhook: You will receive an
entitlementCompletedwebhook.