Submits a business document on behalf of an entity, or an identity document on behalf of a control person or a beneficial owner of the entity, if you operate a platform on zerohash.
EU NNP onboarding. For an entity onboarded through an EU-region platform, the required document set is lei_certificate, excerpt_of_the_chamber_of_commerce, annual_accounts, and power_of_authorization (a power of attorney or a board resolution authorising the submitter). When the entity was created with is_complex_structure: true, a legal_opinion document is additionally required before the entity can be approved. Any document without a dedicated type can be uploaded as supporting_document with a free-text document_description.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
For document uploads to a participant, you must include the header 'X-SCX-FILE-HASH' and pass the value of your hashed document.
File Hashing
Step 1
Read File Content and Base64 EncodeThe first step is to read the entire file as binary data (bytes) and immediately convert this raw data into a Base64-encoded string.
- Action: Open the target file in binary read mode ("rb") and read its entire content into memory.
- Transformation: Take the raw binary data and apply a Base64 encoding function to it. This produces a string composed of standard ASCII characters.
- Purpose: This Base64 string is the unique intermediate representation that will be used as the input for the cryptographic hash function.
Step 2
Hash the Base64 String (SHA-256)Next, the intermediate Base64 string is used as the input for the SHA-256 algorithm.
- Pre-Hashing Prep: The Base64 string must be converted back into bytes using a standard character encoding (e.g., UTF-8) before being fed into the SHA-256 function.
- Hashing: The SHA-256 algorithm processes these input bytes to generate a fixed-size 32-byte hash value, also known as the digest.
Step 3
Base64 Encode the Final DigestThe final step is to take the raw 32-byte digest generated in Step 2 and convert it into a string format that is easily stored and shared.
- Action: Apply a second Base64 encoding operation, but this time to the raw 32-byte SHA-256 digest (not the original file content).
- Result: This yields the final Base64-encoded hash string, which is the result of your specific three-step hashing process.
Document Requirements
Entity Type (entity_type) | Required Documents |
|---|---|
LLC (llc) |
|
Corporation (corporation) |
|
Partnership (partnership) |
|
Sole Proprietorship (sole_proprietorship) |
|
Non-Profit (non_profit) |
|