Skip to main content
To comply with financial regulations, HIFI enforces KYC (Know Your Customer) and KYB (Know Your Business) checks before a User can receive funds from fiat (onramps) or pay out to fiat (offramps).

KYC & Rails

A Rail is a payment corridor that enables payins or payouts to specific regions. Each rail has different KYC requirements depending on what it enables.
RailAccessNotes
USD RailPayins and payouts to the US via ACH and wireFull USD coverage, includes virtual accounts
Global Network RailPayouts to select corridors in Asia and AfricaMulti-currency support across key markets
Africa RailPayins and payouts across supported African countriesLocal currency settlement

Explore rails

View supported rails and their KYC requirements

KYC Requirements

Before submitting KYC information, call the KYC Requirements endpoint to see what documents and information are needed for a specific user and rail combination.
GET https://sandbox.hifibridge.com/v2/users/{userId}/kyc/requirements?rails=USD
Authorization: Bearer <token>

KYC Requirements Guide

Learn about the endpoint and response structure

Submit KYC

Once you’ve gathered and uploaded the required information for the User, submit it using the KYC Submit endpoint. What happens next:
  • Successful submission: Status progresses to pending and enters compliance review
  • Unsuccessful submission: Status moves to incomplete with details about what’s missing or invalid

Track KYC Status

After you submit KYC data, use the KYC Status endpoint to monitor review progress and see any follow-up actions. When the status reaches active, the user can now access the functionalities of that rail. This guide lists every possible status, explains review results, and shows complete response examples.

KYC Status Guide

Learn more about the endpoint and response structure
If you don’t want to handle KYC submission via API, generate a KYC link for users to complete verification through a web interface.

Create KYC Link

Learn how to onboard users using a link