Skip to main content
Every investor must clear Know Your Customer (KYC) checks before it can fund or trade. Bluum runs the compliance pipeline — you supply the investor’s identity data at creation and upload any documents the review requires.

​
How verification resolves

  1. You create the investor with identity, contact, and disclosure fields.
  2. Bluum runs automated identity, tax, and screening checks through its compliance providers.
  3. If the automated checks pass, the investor activates. If they need review, Bluum may request documents.
  4. You upload requested documents; a reviewer approves or rejects.
KYC states

​
Sandbox vs production

EnvironmentBehavior
SandboxChecks auto-approve — investors reach active immediately so you can test the full flow without real documents.
ProductionReal provider checks run. Most complete in minutes; some route to manual review and may request documents. Subscribe to webhooks rather than polling.

​
Documents

Documents are uploaded as flat objects (prefixed doc_). Set account_id to attach a document to an investor; omit it to attach to your tenant. Each document may carry a purpose:
PurposeUsed for
KYCIndividual identity verification
KYBBusiness / entity verification
EDDEnhanced due diligence
TAXTax forms (e.g. W-8BEN, W-9)
FUNDING_VERIFICATIONProof tied to a funding source
AGREEMENTSigned agreements
OTHERAnything else
Supported formats: JPEG, PNG, PDF. When a document is rejected, upload a replacement — there is no attempt limit.

​
Staying notified

Use webhooks to receive KYC decisions in real time instead of polling. Compliance decisions surface as kyc.* and compliance.* events.
For the create-investor request, the document upload call, and handling a document request, follow the journey guide: Verify identity. Document and workflow schemas are in the API reference.