Submit account KYC

post

https://api-sandbox.interlace.money/open-api/v3/accounts/{accountId}/kyc

Submit KYC information for the specified account.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

CaaS Integration Tutorial

A step-by-step guide for setting up card programs, managing cardholders, and issuing cards within the CaaS workflow.

BaaS Integration Tutorial

A step-by-step guide for onboarding entities, creating virtual accounts, and initiating fund transfers.

Occupation Code

Valid occupation codes for the occupation field.
You can find the full list of valid codes here.

Supported ID Types by Country/Region

Mainland China
- CN-RIC
- PASSPORT
Hong Kong
- HK-HKID
- PASSPORT
United States
- DLN
- PASSPORT
- Government-Issued ID Card
Other Countries/Regions
- DLN
- PASSPORT
- Government-Issued ID Card
- EU Residency Permit
- UAE Residency Permit

Important Notice

To ensure data consistency and global compliance, all phone number fields in Cardholder and KYC-related APIs are validated and parsed using Google’s official libphonenumber library.

The submitted phone number (countryCode + phoneNumber) will be validated according to the library’s rules, including but not limited to:

• Validity of the country/region calling code
• Correctness of the phone number format
• Whether the number can be parsed as a valid international phone number

All phone numbers are formatted and normalized through this library before entering the system, ensuring reliability for authentication, notifications, and risk-control processes.

Path Params

accountId

string

required

The UUID of the account.

Body Params

KYC completed via Interlace. Used when the KYC process is performed directly in our system.

firstName

string

required

User's first name. Example: John

lastName

string

required

User's last name. Example: Smith

dateOfBirth

string

required

Date of birth in YYYY-MM-DD format. Example: 1990-01-01

gender

string

enum

required

User’s gender. Use "M" for male or "F" for female. Example: M

Allowed:

occupation

string

User's occupation code. Refer to the "Occupation Code" section on the top of the page for valid codes. Example: 11-1011

annualSalary

string

User’s annual salary. Example: 10000 USD

accountPurpose

string

Purpose of the user's account. Example: Living Expense

expectedMonthlyVolume

string

Expected monthly spending. Example: 1000 USD

nationality

string

required

Two-letter country code of nationality, as defined in ISO 3166-1 alpha-2. Example: US

nationalId

string

required

ID number. Required for passport/driver’s license/national ID.

idType

string

enum

required

Type of ID.

Allowed:

ssn

string

9-digit SSN if the country is US. Example: 123456789

issueDate

string

required

ID issue date in YYYY-MM-DD format. Example: 2018-05-10

expiryDate

string

required

ID expiry date in YYYY-MM-DD format. Example: 2028-05-10

address

object

required

Address

idFrontId

string

required

File ID of the front side of the ID document (from Upload files API).

idBackId

string

File ID of the back side of the ID document (returned by the Upload files API). This field is not required for passports. For driver's licenses and non-mainland China ID cards, provide the back-side file ID if available; otherwise, reuse the front-side file ID.

selfie

string

required

File ID of the applicant selfie (from Upload files API).

phoneNumber

string

required

length ≤ 15

User's phone number without the country code, length ≤ 15. Example: 13800138000

phoneCountryCode

string

required

length ≤ 3

The international dialing code of the user's mobile number, numbers only, no "+", length ≤ 3. Example: 86

sourceType

string

required

Defaults to api

"api"

Responses

CaaS Integration Tutorial

BaaS Integration Tutorial

Occupation Code

Supported ID Types by Country/Region

Important Notice

200OK

400Bad Request