This guide focuses on the USD rail. Requirements and response structure differ for other rails—see the API
Reference for complete details.
Status Overview
Business KYB applications move through the same statuses as individual KYC:| Status | Description |
|---|---|
| INACTIVE | No KYB submitted yet—call Submit KYC to begin verification |
| INCOMPLETE | Submitted data needs updates—fix flagged items and resubmit |
| PENDING | KYB submitted and is moving through automated compliance checks or bank onboarding |
| MANUAL_REVIEW | Compliance team manually reviewing before final decision |
| RFI_PENDING | Compliance requested additional information—check your compliance email |
| ACTIVE | Business passed compliance review and can use the USD rail |
| REJECTED | Permanently denied for USD rail—resubmission not permitted |
| CONTACT_SUPPORT | System couldn’t confirm status—contact HIFI support |
Contact support if a business applicant remains in
PENDING or MANUAL_REVIEW for more than 3 days.Response Structure
Top-Level Fields
The KYB status response has the same top-level structure as individual KYC, but with business-specific compliance categories in thedetails object.
Current KYB application status
Human-readable context for developers
Overall decision for the KYB submission (
APPROVED, DECLINED, or empty while pending review).Breakdown of business compliance categories and review results
Review Result
Each compliance category includes areviewResult object with a general summary of the compliance review outcome. The same schema is used for the top-level reviewResult field:
Screening outcome:
APPROVED or DECLINEDResubmission permission:
RETRY (can resubmit) or FINAL (hard rejection). Only present when reviewAnswer is DECLINED.Enumerated rejection reasons. Only present when
reviewAnswer is DECLINED.Human-readable explanation of the rejection. Only present when
reviewAnswer is DECLINED.Review Details
Thedetails object returns the compliance review outcome for each information category. Every category includes a reviewResult, and some categories provide additional nested data.
Structured business data: legal name, registered address, registration number, tax identifiers, and other non-document metadata.
Responses to the compliance questionnaire (purpose of account, expected transaction volume, counterparties, source of funds).
Document verification for the legal presence requirements.
Document verification for the ownership structure requirements.
Document verification for the company details requirements.
Document verification for the control structure requirements.
Aggregated status for all UBOs. It contains a category-level
reviewResult and a details array with one entry per UBO. Each UBO entry mirrors the individual KYC structure described in the KYC Status guide (personal info, identity documents, proof of address, questionnaire).Response Breakdown
- ACTIVE
- INACTIVE
- PENDING
- MANUAL_REVIEW
- INCOMPLETE
- RFI_PENDING
- REJECTED
- CONTACT_SUPPORT
Business passed all compliance checks and completed bank onboarding. They can now use the USD rail.