Bit2Me APIKYB (company subaccount)
Onboard a legal entity as type company — no identity webview.
This page describes the published API. It is not legal advice. Bit2Me Legal and Compliance must review KYC, KYB, Travel Rule, and 2FA copy before this portal is announced to partners.
Do not call POST /v3/account/verify/identity/init for companies. Do not use the person KYC widget for administrator IDs.
Overview
Collect general and privacy-policy acceptance in your application before create. Terms download and acceptance-check paths are not in this OpenAPI snapshot.
POST /v1/account/subaccountRequired: email, name, surname, phone, and type: company. Response: userId. Then send X-SUBACCOUNT-ID.
PUT /v1/account/updateSet type: "company" and fill the company object from the snapshot (CompanyParam). Do not send accountCompleted on this PUT — that field appears on GET /v3/account. Do not use the person verification path.
POST /v2/account/address with the same required fields as person KYC (streetAddress, city, stateCode, zip, countryCode, nationalityCountryCode).
Specific document-type enums (administratorDni, registeredAddress, kycPoliciy) are not in this snapshot. Submit the pack your Bit2Me onboarding contact specifies. Compliance will approve, reject, or request more.
Companies are reviewed from the document pack, not ID + liveness.
Person KYC success (verified + tier 2) does not apply here. Confirm the corporate status signal with your Bit2Me onboarding contact — a dedicated public status path is not published in the same form as person KYC.
KYC vs KYB
| KYC (person) | KYB (company) | |
|---|---|---|
Subaccount type | Person | company |
| Identity webview | Required | Forbidden |
| Primary evidence | ID + liveness + address | Corporate document pack (types from your onboarding contact) |
| Completion | verified + tier 2 | Compliance approval — no public equivalent in this snapshot |