Identity Verification

Documentation Index

Fetch the complete documentation index at: https://docs.lumx.io/llms.txt

Use this file to discover all available pages before exploring further.

Every customer has to complete identity verification before transacting. What you need to submit depends on whether the customer is an individual or a business.

​

Prerequisites

The customer has to accept Lumx’s Terms of Service before verification can start. Acceptance is collected via POST /customers/{id}/tos. Until they accept, the TERMS_OF_SERVICE entry stays in the customer’s requirements array and verification can’t proceed. See Terms of Service for the full flow. For step-by-step API instructions on submitting data and documents, see Individual verification or Business verification.

​

Standard KYC/B

*When applicable. ¹ Company Formation Documents. In Brazil, we typically ask for: Articles of Incorporation/Bylaws, ownership chart, and (if applicable) minutes appointing/electing directors and the Share Register Book. In other jurisdictions: Articles of Association (or equivalent), Register of Members, and Register of Directors (or equivalents). ² Transactional Information. We’ll ask about source of funds, expected transaction volume, and the countries and counterparties involved. For the documentation Lumx accepts, see Source of Funds and Wealth. ³ Regulated Activity Information. We’ll ask about any regulated activities the company carries out and, when applicable, request the corresponding license. ⁴ Proof of Address. Required for every individual customer, business customer, and each associated party (UBOs, shareholders above 25%, representatives). Must be issued within the last 90 days. For accepted documents, see Proof of Address. ⁵ Associated Party Documents. Each UBO, shareholder above 25%, and representative submits a government-issued ID and a proof of address. IDs must be within their official validity period and issued no more than 10 years ago.

​

Enhanced KYC/B

Enhanced verification kicks in when a customer wants higher transaction limits than the standard thresholds. It’s run directly with the Compliance team and involves a deeper review of additional documents. For how to request higher limits and what to send, see Requesting higher limits.

​

Common rejections

A few patterns Lumx compliance flags during review. Avoiding these reduces back-and-forth:

• All pages of multi-page documents must be submitted, not just the first.
• IDs must be within their official validity period.
• Names must match across the ID, ownership documents, and onboarding submission.
• Proof of address documents must be issued within the last 90 days, regardless of category.

​

Verification SLAs

How long it takes a customer to move from UNDER_VERIFICATION to APPROVED once all required documents are submitted. Targets, not contractual guarantees.

​

Statuses

• NOT_STARTED: customer was created, but no data has been submitted yet.
• UNDER_VERIFICATION: ToS accepted, additional information and required documents submitted, review in progress.
• APPROVED: verification complete, customer can transact.
• RFI: submitted information is invalid or inconsistent (e.g. wrong tax ID, unrecognized documents). The customer can resubmit corrected documents.
• FINAL_REJECTION: verification permanently denied. The customer can’t transact.

​

Sandbox magic numbers

In sandbox, the last digit of taxId is a sentinel that drives the simulated verification outcome. Webhooks fire almost instantly with the matching status.

​

Status progression