---
url: /docs/kb/instance-requests.md
description: >-
  How BlindPay compliance asks your team for additional information about your
  own account, and how to respond before the 27-day window closes.
---

An Instance RFI is a Request for Information directed at your instance (your BlindPay account) rather than at one of your customers. Compliance uses it to collect updated business information or supporting documents from your team, for example during a periodic review. For RFIs about a specific customer, see [Information requests](/docs/kb/information-requests).

## How it differs from a customer RFI

| Aspect | Customer RFI | Instance RFI |
| --- | --- | --- |
| Who it is about | One of your customers | Your own company |
| Where you answer | The customer's profile page | Your instance settings page |
| Effect while open | That customer cannot transact | No effect on your account or payments |
| Missed deadline | The customer is auto-rejected | The request expires, nothing else happens |

## When an instance RFI is created

Compliance creates an instance RFI whenever it needs information about your company itself. Common triggers include:

* A periodic review of your account requires refreshed documents
* Your business description or website no longer matches what we have on file
* Ownership changes need an updated share register or UBO documentation
* A proof of address or source of funds document needs to be renewed

Each RFI is built as a list of sections. Each section has a title, a description explaining what compliance needs, and one or more fields to fill in (text, file upload, or dropdown).

## Email notifications

When an instance RFI is opened, BlindPay emails **every active member of your instance** (unless you've scoped notifications to specific compliance emails, see below). The cadence is:

| Day | Email | Purpose |
| --- | --- | --- |
| 0 | Action Required | Lists each section and the fields requested. Includes the deadline. |
| 7 | Reminder | Sent only if the RFI is still pending. |
| 17 | Final Notice | Sent only if the RFI is still pending. |
| 27 | Expired | Sent if the deadline passes without a submission. |

All emails come from `compliance@blindpay.com` and link to your dashboard at `app.blindpay.com`.

Emails are sent to every non-deleted user in your instance, unless you've set specific **compliance emails** (up to 20 addresses) on the instance's settings. When that list is set, instance RFI notifications go only to those addresses instead of the whole team. Manage either your team's membership or the compliance email list from **Settings → Members** and **Settings → Instance**, or with [`PUT /instances/{instance_id}`](/docs/learn/instances#manage-your-instance).

## Responding to an instance RFI

1. Open **Settings → Instance** in your BlindPay dashboard. A "Request for Information" section highlights the open RFI.
2. Review each requested section and collect the documents or explanations.
3. Upload the files and submit the response in a single action.

Once submitted, the RFI moves to `submitted`, the reminder emails stop, and compliance reviews the response. If anything else is needed, a new RFI is opened.

**Submit the entire RFI at once.** The submission is single-shot. All required fields must be filled before you can send the response.

## Deadlines and expiry

If 27 days pass without a submission, the RFI is marked expired and a final email is sent to your team. Unlike customer RFIs, **nothing happens to your account automatically**: no status changes, no blocked payments. Our compliance team follows up with you directly if the information is still required.

## API integration

If you'd rather handle instance RFIs programmatically instead of through the dashboard, the same request the dashboard uses is available directly.

```bash [cURL]
curl --request GET \
  --url https://api.blindpay.com/v1/instances/in_000000000000/rfi \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

Returns the open (pending) RFI, or `null` if none is open.

```bash [cURL]
curl --request POST \
  --url https://api.blindpay.com/v1/instances/in_000000000000/rfi \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "business_description": "..."
  }'
```

The body is a flat object keyed by each field's `key`, the same shape as a [customer RFI response](/docs/learn/rfi#submit-a-response). Each field is validated against the open RFI's own request definition: a required field must be 1-4096 characters, a field with a `regex` must match it, and a field with `multiple: true` must be an array of up to 20 URLs. Keys not listed in the request are rejected.

If a section asks for an ID document with a type dropdown and a matching `..._back_file` upload field, the back file becomes required unless the selected document type is `PASSPORT`.

A submission to an RFI that's no longer open doesn't return an error: it responds `200 { "success": false, "reason": "no_pending_rfi" }` (or `"already_resolved"` if someone else just submitted it first). Check `success` in the body rather than only handling non-2xx responses.

Submitting an instance RFI never changes your instance's or onboarding status; it's a standalone compliance review, unlike a customer RFI response.

## Best practices

* **Answer from the dashboard.** The instance settings page validates every required field before letting you send.
* **Keep your member list clean.** Only members who should see compliance correspondence should remain on the instance.
* **Match the format compliance asks for.** If a section requires a utility bill, a bank statement won't satisfy it.

## Related

* [Information requests](/docs/kb/information-requests): RFIs about a specific customer
* [KYB documents](/docs/kb/kyb-documents): business verification document requirements