Skip to main content
When a customer is routed into enhanced due diligence (EDD) at onboarding, or flagged during ongoing transaction monitoring, Lumx may request documentation showing where their funds come from and how their wealth was built. This page lists what to provide.

​
Source of funds vs. source of wealth

  • Source of funds. How the specific money moving through Lumx was generated. For example: operating revenue, customer payments, or investment capital.
  • Source of wealth. How the customer or its owners accumulated their overall wealth. For example: business earnings, prior ventures, or long-term investments.
Both may be requested during onboarding or as part of an ongoing review.

​
When this is requested

Lumx asks for source of funds or wealth documentation in a few scenarios:
  • The customer falls into an EDD tier based on country, industry, or risk score. See Supported countries for the country-level tiers.
  • High transaction volumes or complex funding structures need additional validation.
  • A material change in expected activity, ownership, or business model.
  • A regulatory or compliance obligation requires it.
When documentation is needed, you’ll be notified through an RFI listing the specific documents to submit.

​
Acceptable documentation

Documents should clearly show where funds come from, how they were generated, and how they’ll move to Lumx. Everything should align with the customer’s declared business activity.

​
Fiat funding sources

​
Crypto and digital asset funding sources

​
Document standards

To keep review moving, make sure each document:
  • Is issued in the name of the business or the relevant funding entity.
  • Clearly shows the source and flow of funds.
  • Is legible and complete, with no material redactions.
  • Is submitted as PDF, JPG, or PNG.
Lumx may request additional supporting documentation if more clarification is needed during review.

Request for Information

How Lumx notifies you when documents are needed.

Identity Verification

KYC and KYB requirements per customer type.

Document Types

Enum reference for the type field on document uploads.

Onboarding Fields

Self-disclosure enums including sourceOfFunds.