Requests for Information (RFI)

Learn how BlindPay requests additional documentation when KYC or KYB needs more detail, how your team is notified, and how to respond before the deadline.

Overview

A Request for Information (RFI) is how BlindPay's compliance team asks for missing or clarifying details when a receiver's KYC or KYB review is incomplete. Instead of rejecting an application outright, we put it on hold and ask you, the partner, to collect the specific documents or explanations we need from your customer.

When an RFI is created

Compliance creates an RFI whenever a receiver's submission is missing information, contradicts another document, or falls into a category that requires extra context. Common triggers include:

  • A business description that doesn't match the company's website or industry
  • A proof of address document that doesn't match the registered address
  • An identity document that's expired, blurry, or partially visible
  • An ownership structure that needs an updated share register or UBO documentation
  • Source of funds or source of wealth that needs supporting evidence

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 the customer must fill in (text, file upload, or dropdown). A single RFI can mix document uploads with free-text explanations.

What happens to the receiver

When an RFI is created, the receiver's kyc_status flips from verifying (or whatever its prior status was) to compliance_request. While in this status:

  • The receiver cannot send or receive funds
  • The customer sees a banner in their dashboard prompting them to submit the requested information
  • A 27-day countdown starts. If no response is submitted, the receiver is automatically rejected

The receiver's previous status is snapshotted when the RFI is created. If your compliance contact cancels the RFI, the receiver returns to that prior status instead of staying in compliance_request.

Email notifications

When an RFI is opened, BlindPay emails every active member of your instance so your team can coordinate with the customer. We do not email the receiver directly, since collecting the documents and uploading them is your responsibility as the partner.

The cadence is:

DayEmailPurpose
0Action RequiredLists each section and the fields requested. Includes the deadline.
7ReminderSent only if the RFI is still pending.
17Final NoticeSent only if the RFI is still pending. Warns of automatic rejection.
27Auto-RejectedSent if the deadline passes without a submission. The receiver is rejected.

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. To control who receives them, manage your team's membership in Settings → Members.

Responding to an RFI

  1. Open the receiver in your BlindPay dashboard. A banner highlights the open RFI.
  2. Review each requested section with your customer and collect the documents or explanations.
  3. Upload the files and submit the response in a single action.

Once submitted:

  • The receiver's kyc_status returns to verifying
  • BlindPay's compliance team re-reviews the application along with the new information
  • The pending email reminders for this RFI are stopped immediately

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

What happens after submission

After you submit, compliance reviews the response and either approves the receiver or requests another round of information. Most RFIs are resolved within a few business days. If the response still doesn't meet our requirements, a new RFI may be opened with the additional questions.

Deadlines and auto-rejection

If 27 days pass without a submission, BlindPay automatically rejects the receiver. The receiver's kyc_status becomes rejected and a final email is sent to your team. To restart the KYC process for that customer, contact our compliance team.

Best practices

  • Keep your member list clean. Only members who should see compliance correspondence should remain on the instance. Remove former teammates promptly.
  • Coordinate with your customer early. The 27-day window is firm, and most rejections happen because the customer wasn't reached in time.
  • Match the format compliance asks for. If a section requires a utility bill, a bank statement won't satisfy it. Re-read each section before uploading.
  • Submit complete responses. Partial submissions are not accepted; the dashboard validates every required field before letting you send.

For document quality requirements, see the Basic Customer Information (KYC) and Basic Business Information (KYB) guides.