RFI automation: compliance requests through your API
A request for information (RFI) is a compliance request for additional details and documents about a user or a transaction. It can arrive during onboarding, or against a transfer that is already in flight. Until it is resolved, the user or the payment waits.
For developers on HIFI, RFI handling now runs through your integration.
Receiving the request
When an RFI is issued for one of your users, HIFI notifies you two ways: by email, and by webhook for clients who want to handle RFIs programmatically.
Each RFI specifies its requested documents item by item, so your user sees exactly what is being asked for.
Collecting the response
You have two ways to respond. You can submit the requested items through the API, collecting documents however you already do and passing them to HIFI without sending your user anywhere. Or your user can complete the RFI through a link, which can be embedded directly in your own interface so they stay inside your product for the exchange.
Either way, each requested document can carry a written explanation alongside it, giving compliance the context behind what was submitted.
RFIs support multiple rounds. If a review calls for a follow-up, that follow-up opens as a new round on the same RFI rather than as a separate request your user has to reconcile against the first one.
A complete record
Every RFI carries its full history: each requested item, each response submitted against it, and each review outcome. When compliance resolves an RFI, the verdict is recorded against the same RFI and synced to that user's verification record.
The record is what changes structurally. The entire exchange between your user, you, and HIFI compliance sits in one place with a full audit trail.
What this means for developers
The full round trip is available programmatically. You receive the webhook, submit the requested items through the API, and receive the resolution against the same RFI. If you would rather your user upload directly, present the link inside your onboarding or transaction flow and watch for the same resolution.
RFI links are separate from KYC links, so an RFI raised against an already-verified user does not disturb their verification flow.
→ Docs: https://docs.hifi.com/v3/core/compliance/rfi
FAQ
What is an RFI on HIFI?
A request for information (RFI) is a compliance request for additional details and documents about a user or a transaction. It can arrive during onboarding or against a transfer that's already in flight, and until it's resolved, the user or the payment waits.
How does a developer receive an RFI?
HIFI notifies you by email, and by webhook for clients who want to handle RFIs programmatically. Each RFI specifies its requested documents item by item, so your user sees exactly what is being asked for.
How does a developer respond to an RFI?
There are two ways to respond. You can submit the requested items through the API, collecting documents however you already do and passing them to HIFI without sending your user anywhere, or your user can complete the RFI through a link, which can be embedded directly in your own interface so they stay inside your product for the exchange. Either way, each requested document can carry a written explanation alongside it, giving compliance the context behind what was submitted.
What happens if compliance needs a follow-up after the first response?
RFIs support multiple rounds. If a review calls for a follow-up, that follow-up opens as a new round on the same RFI rather than as a separate request your user has to reconcile against the first one.
What does an RFI's record contain?
Every RFI has its full history containing each requested item, each response submitted against it, and each review outcome. When compliance resolves an RFI, the verdict is recorded against the same RFI and synced to that user's verification record, so the entire exchange between the user, the developer, and HIFI compliance sits in one place with a full audit trail.
Does an RFI affect a user's existing KYC verification?
No. RFI links are separate from KYC links, so an RFI raised against an already-verified user does not disturb their verification flow.
What does RFI handling through the integration mean for developers?
The full round trip is available programmatically: you receive the webhook, submit the requested items through the API, and receive the resolution against the same RFI. If you'd rather your user upload directly, you present the link inside your onboarding or transaction flow and watch for the same resolution.
