Individuals

Everything you need to know in order to verify an individual customer

As a financial institution, Fin must perform checks on users who want to transact using fiat currencies (USD, SGD, EUR, GBP etc.)

The verification process is the following:

1. Basic information:

Field

Description

first_name

Legal first name (as per ID).

last_name

Legal last name (as per ID).

dob

Date of birth.

email

Valid personal or business email.

phone

Mobile number including country code (e.g., +14155552671).

country_of_residence

Country where the person currently resides.

nationality

Citizenship of the person.

tin

Tax Identification Number or equivalent. If a customer doesn't have a tin number, please enter the passport or identity document number here.

Jurisdiction specific tin format is mandatory:

  • USA - SSN format - xxx-xx-xxxx

2. Address:

Please note this has to be the current residential address of the user.

FieldDescription
streetFull street address (house/building + road).
cityCity or locality name.
stateSubdivision or state (use ISO-3166-2 format).
postal_codePostal or ZIP code.
countryCountry code of residence.

3. Financial Profile:

FieldDescription
occupation_idID representing the person’s occupation (from Occupations).
source_of_fund_idID representing where funds originate (from Source of funds).
purpose_idID representing the purpose of using the service (from Account purposes).
monthly_volume_usdEstimated average monthly transaction amount in USD.

4. Metadata:

FieldDescription
referenceDeveloper or system-generated reference ID.

5. Uploading documents:

In order to submit documents to us for verification, it is required to be uploaded via the Upload a document to the system in our system first and then utilize the Attach documents for an individual customerto attach it for verification for an individual customer.

6. Attaching documents:

FieldDescription
customer_idUnique identifier returned from the individual KYC creation API.

6.1 Proof of identity:

FieldDescription
typeType of ID document. Allowed: PASSPORT, NATIONAL_ID, DRIVING_LICENSE, RESIDENCE_PERMIT.
numberDocument number as shown on the ID.
countryCountry of issuance.
issue_dateDate of issuance (if available on document).
expiry_dateDocument expiry date (if applicable).
filesList of uploaded file objects.

File object:

FieldDescription
sideFRONT or BACK
uriURI returned from the file upload API.

6.2 Proof of Address:

FieldDescription
typeDocument type. Allowed: BANK_STATEMENT, UTILITY_BILL, GOVERNMENT_LETTER, PASSPORT, NATIONAL_ID, DRIVERS_LICENSE, RESIDENCE_PERMIT. The document must have the full provided address of the customer with their full name on it.
countryCountry of issuance or residence, has to match the country_of_residence
filesList of uploaded file objects.

File object:

FieldDescription
uriURI returned from the file upload API.

Accepting terms of services and privacy policies:

FieldDescription
tos_policies_valueRetrieve from the response of the Create an individual customer profilewhere you will find the tos_policies_url, within that that url you will find the tos_policies_value

Developer Notes

  • All country fields must follow ISO Alpha-3 codes (e.g., BGD, SGP, USA).
  • Use predefined drop-down for occupation_id, source_of_fund_id, and purpose_id.
  • monthly_volume_usd is an estimated activity level, not account balance.
  • The API enforces field presence, types, and value validation automatically.
  • For IDs with both sides (like national IDs), include two file objects: FRONT and BACK.
  • File URIs must be generated from the Upload a document to the system API before attachment.
  • Proof of address must be issued within the last 90 days.