Skip to main content

Overview

A Request For Information (RFI) is a case our review or compliance teams raise when they need additional information from a customer before they can finish processing something — typically completing an onboarding application or releasing a flagged transaction. Each RFI bundles one or more questions and document requests that the customer must respond to.

As a partner, you are responsible for surfacing the RFI to the customer and submitting their responses back through the gateway. Until every item on the case is resolved and Hubpay closes the case, the underlying review (onboarding, transaction approval, etc.) remains paused.

Every RFI has a stable, human-readable caseNumber (e.g. RFI-20260611-9F3A21B7). Render it on your customer-facing UI — Hubpay ops and support teams use it as the canonical reference when discussing the case with the customer.

Where RFIs fit in the lifecycle​

RFIs are cross-cutting — they can apply to onboarding applications and to individual transactions. The diagram below shows where an onboarding-application RFI fits relative to Account onboarding; transaction RFIs follow the same respond-and-resolve shape but branch off a transaction's review path instead.

Subject types​

Each RFI carries a subjectType that identifies what the case is about and a subjectId pointing at the underlying resource. In v1 the subject is one of:

subjectTypesubjectId points to
ONBOARDING_APPLICATIONThe customer's onboarding application. Resolve by responding to the RFI so the application can resume review.
TRANSACTIONA specific transaction awaiting clearance. Resolve so the transaction can complete.

Lifecycle in brief​

  1. Hubpay raises an RFI. You receive v1.rfi.case.opened carrying the case ID, subject, item counts and a customer-display message.
  2. You fetch the case detail and surface each question and document request to the customer.
  3. The customer responds. You submit each answer or document attachment back via the respond endpoints (per-item or bulk).
  4. Each document attachment goes through the per-doc review pipeline. You receive v1.rfi.document.* events for approve/decline/validation warnings on each file.
  5. Once Hubpay accepts every item, the case is closed and you receive v1.rfi.case.closed. If the case is no longer needed, you receive v1.rfi.case.cancelled instead.

Next steps​