| Term | Meaning |
|---|---|
| Access token | The bearer token from POST /oauth2/token, sent as Authorization: Bearer on every request; it lasts 2 hours |
| Beneficial owner (UBO) | A natural person who ultimately owns or controls a company. Declared as a person key party with isBeneficialOwner: true |
| Client credentials | The client id and secret Securitize issues you, one pair per environment, exchanged for an access token |
| Company document | A document about a company: registration, articles, shareholder register and the like. One file per call, PDF allowed |
| Corporate shareholder | A company that holds shares in the company being onboarded. Declared as a company key party; reviewed by Securitize compliance |
| Correlation id | The id of one request, in every API error (correlationId) and in the x-correlation-id response header. Quote it to Securitize support |
| DLT test | A knowledge test about distributed ledger technology, required for investors whose address is in the European Economic Area. Three attempts, then locked |
| Entity | An investor that is a company, trust, fund or other legal person |
externalInvestorId, externalKeyPartyId | Your own ids for an investor or a key party, chosen at the create |
| Gateway | The layer in front of the API that checks your access token. Its errors carry no code |
| Hosted onboarding | A page Securitize hosts with only the onboarding steps, which you link investors to instead of building onboarding with the API. Securitize verifies the investor itself, and the investor comes back to your partnerUrl |
| Identity document | A passport, driving licence, national identity card or residence permit, read optically |
| Individual | An investor that is a natural person |
investorId, keyPartyId | Securitize’s ids for an investor or a key party, returned by the create and specific to your account |
| Key party | A person or company an entity is verified through: its beneficial owners, shareholders, signers and corporate shareholders |
| Limited access | What you have on an investor whose verification another party leads: its status, wallets, whitelisting, suitability and DLT test, but not its data, documents or tax form |
manual-review | A Securitize compliance operator is reviewing the investor, usually after a screening hit. Not a rejection |
| PEP | Politically exposed person. Securitize screens every investor and every person behind a company against PEP and sanctions lists |
| Sandbox | The test environment. Real records against a test identity check; nothing reaches production |
| Settled | A verification that has a verdict. Its data can no longer change |
| Submit | POST /investors/{investorId}/verification/submit: the call that starts a verification. You asserting the data, and for a company the list of key parties, is final |
| Suitability | Securitize’s investor profile: experience, finances, risk profile, plus your attestation that the investor reviewed Securitize’s documents. Required for whitelisting |
| Tax form | The IRS form an investor signs so Securitize can apply the right withholding to their distributions: W-9 for a US person, W-8BEN for a foreign individual, W-8BEN-E for a foreign entity. Sent as a signed PDF, or a W-9 as JSON fields; one on file per investor |
| Token | A security token issued through Securitize, identified by its contract address (tokenAddress) |
| Wallet | A blockchain address associated with one investor, evm or solana |
| Whitelisting | Registering an investor’s EVM wallet on a token’s on-chain registry, so the wallet can receive and hold the token |
Help
Glossary
The terms these docs use, in one place.