Skip to main content
When a User needs to interact with a fiat account (for onramps or offramps), HIFI enforces KYC (Know Your Customer) and KYB (Know Your Business) checks to comply with financial regulations. During the onboarding process, you’ll be asked to provide a compliance email address. This email will be used to contact you for any additional information requests during KYC review.
KYC verification typically takes a few minutes for Individual Users and between 1 to 3 days for Business Users, depending on structure.

​
Rails

KYC requirements are grouped by Rail - each rail has specific compliance requirements based on the regions and currencies it supports. Users must complete KYC for each rail they want to use. Rail-specific KYC:
  • USD Rail: US compliance requirements for ACH, RTP, and Wire transfers
  • Global Network Rail: Multi-region requirements for Asia and Africa payouts
  • Africa Rail: Local African market compliance requirements
  • South America Rail: South American market compliance requirements

Rails

Learn more about our fiat capabilities

​
KYC Requirements

The KYC Requirements endpoint lets you retrieve what documents and information are required, optional, or invalid for a specific user and rail combination. If you want to figure out what to submit for a user’s KYC, you can fetch the requirements first to understand exactly what information and documents are needed. What you get:
  • Required: Documents and information that must be provided
  • Optional: Additional documents that can help with verification
  • Invalid: Documents that are not accepted for this rail/user combination
This endpoint helps you understand exactly what to collect from users before submitting their KYC information.
These fields must be provided for KYC submission:
  • Personal Information: firstName, lastName, email, phone
  • Address: Complete address with required fields (addressLine1, city, stateProvinceRegion, postalCode, country)
  • Identity: dateOfBirth, taxIdentificationNumber, govIdType, govIdFrontUrl, govIdCountry
  • Proof of Address: proofOfAddressType, proofOfAddressUrl
Address has both required and optional fields. Required fields must be provided, while optional fields like addressLine2 can be included if available.
These fields can be provided to enhance verification: - Source of Funds Questionnaire: Complete sofEuQuestionnaire with employment status, expected monthly payments, primary purpose, and source of funds - Additional Documents: govIdBackUrl for back side of government ID
The Source of Funds questionnaire has its own required and optional sub-fields. All required questionnaire fields must be completed if you choose to submit this information.
These fields are either missing or invalid and need to be corrected:The API response will include a list of fields that are missing or invalid, along with the specific reason (e.g., “missing” or “invalid format”).
You must address all invalid fields before KYC submission can be successful. Check the invalid fields list and provide the missing information or correct any formatting issues.

Get KYC Requirements

Explore API Reference

​
KYC Status

Once you submit KYC information, it enters the compliance review process. Use the KYC Status endpoint to track the progress and get real-time updates. Status updates include:
  • Pending: KYC is under review
  • Approved: User is verified and can use the rail
  • Rejected: Additional information or documents are needed
  • Under Review: Compliance team is actively reviewing
The status endpoint provides detailed information about what’s happening during the review process and any actions required from you or the user.

Get KYC Status

Explore API Reference
 If you don’t want to use the API directly, you can generate a KYC link and share it with your users. This approach allows users to complete their KYC verification through a web interface without requiring API integration on your end.

Create KYC Link

Learn how to onboard users using a link
⌘I