Request for Information
Requests for Information (RFIs) often slows down onboarding and transactions, frustrates customers, and requires teams to manually chase documents or details.
Traditionally, clients managed RFIs by either:
- Building custom UI flows on top of Nium’s APIs.
- Collecting documents manually via email or spreadsheets.
Both approaches require ongoing development, maintenance, and operational effort.
The Pre-built RFI Form changes this with a plug-and-play, Nium-hosted interface that lets customers or internal teams respond to RFIs instantly—no custom UI or backend setup required.
When to use RFI Forms
Use RFI Forms to collect required information from customers without building or maintaining a custom user experience.
RFI Forms help when you want:
- Minimal development work: Nium hosts and maintains the form, which can be embedded in your application or shared as a link.
- Branding consistency: Logos and fonts can be applied without additional frontend work.
- Cross-device support: Forms are optimized for both web and mobile by default.
- Secure and compliant data handling: Submissions flow directly into Nium for processing.
- Fast deployment: Forms can be published and used immediately, with no setup overhead.
Using RFI Forms
Customers
For organizations that enable customers to complete RFIs via an external app or a customer dashboard:
- Embed the form in your app or dashboard.
- Customers complete RFIs in-app.
- Nium manages hosting and data transmission.
Operations
For organizations that manage RFIs internally:
- Your analysts trigger a hosted link.
- Share the link with the customer who completes the RFI Form.
- Information returns to Nium instantly.
Getting started
To get started with RFI Forms:
Step 1: Get access
Contact your Nium account manager or Nium Support to enable and customize Pre-built Forms for your account.
The logo you provide during this initial setup appears at the top left corner of the form.
Step 2: Receive callbacks
Nium provides callbacks that notifies you when new RFIs are raised.
Use these callbacks to:
- Immediately alert customers or internal teams.
- Display RFI status in your external app or internal dashboard.
Step 3: Authenticate
When a customer wants to view or complete an RFI:
- Make sure they’re logged into your app or dashboard.
- Use the Create a Session request to generate a
sessionId. ThesessionIdsecurely binds the customer'ssessionto Nium’s hosted component.
Request example
curl --location --globoff 'https://gateway.nium.com/api/v1/client/{clientHashId}/sessions' \
--header 'Content-Type: application/json' \
--header 'x-api-key: B20iXk3Qma2KB29zwuP5S9P7YSUBiMAp6lQCggKH' \
--data '{
"featureType": "string",
"customerHashId": "string",
"walletHashId": "string",
"authCode": "string",
"integrationType": "string",
"expiry": "date-time",
"rollingDurationMinutes": "long",
"domain": "string",
"onBehalf": "boolean",
"email": "email"
}'
| Field | Type | Description | Values |
|---|---|---|---|
featureType | String | Type of form to generate. |
|
customerHashId | String | the unique customer identifier generated at the time of customer creation. It's received in the response of the Onboard Corporate Customer request. | |
walletHashId | String |
| |
authCode | String |
| |
integrationType | String | Defines where the form opens.
|
|
expiry | String | The date and time the form will expire. If the form expires, create a new sessionId. | Must follow ISO-8601 date-time format: yyyy-MM-dd'T'HH:mm:ssXXX |
rollingDurationMinutes | String | How much time can pass before the form expires due to inactivity. |
|
domain | String | Domain where the form is embedded when using the embedded integration type. |
|
onBehalf | — | Not used for RFI Forms. | — |
email | — | Not used for RFI Forms. | — |
Response example
{
"sessionId": "string",
"externalId": "string",
"featureType": "string",
"metadata": {
"customerHashId": "string",
"authCode": "string",
"integrationType": "string",
"onBehalf": "boolean",
"walletHashId": "string",
"clientHashId": "string"
},
"status": "string"
}
| Field | Type | Description |
|---|---|---|
sessionId | String | A unique identifier for the session, generated by your application. |
externalId | String | A unique identifier provided by you to track sessions and forms. |
featureType | String | The type of form that was generated. |
metadata | String | An object containing details about the customer. |
customerHashId | String | The unique customer identifier generated at the time of customer creation. It's received in the response of the Onboard Corporate Customer request. |
authCode | String |
|
integrationType | String | Defines where the form opens.
|
onBehalf | Boolean | Not used for RFI Forms. |
walletHashId | String | The unique identifier of the customer’s wallet linked to the transaction. |
clientHashId | String | Unique client identifier generated and shared upon client creation. |
status | String | Status of the form. |
Step 4: Open the form
Pass the sessionId to the static Pre-built RFI Form URL:
- Production:
https://nformify.nium.com/rfi?sessionId= - Sandbox URL:
https://nformify-preprod.nium.com/rfi?sessionId=
The Pre-built Form loads automatically — no additional requests or development required.
Behind the scenes, the Pre-built RFI Form:
- Dynamically display required fields and document types.
- Performs instant validation (format, completeness, file type).
- Submits data securely to Nium in real time.
- Updates your app and dashboards automatically.
- Maintains full audit history for every RFI that's raised.