Skip to main content

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.

A customer is the legal owner of wallets, balances, and transaction history. Customers can be one of the following:
  • Your own business entity, when moving funds for your own operations.
  • The end users (individuals or businesses) onboarded through your platform. Each customer carries its own compliance status, wallets, and transaction history.

Verification

Before a customer can transact, they complete identity verification (KYC). The flow has five statuses:
StatusDescription
NOT_STARTEDCustomer created, verification pending.
UNDER_VERIFICATIONDocuments submitted, under review.
APPROVEDVerification complete, customer can transact.
RFISubmitted information is invalid or inconsistent. The customer can resubmit corrected documents.
FINAL_REJECTIONCustomer permanently rejected.
If a customer moves to RFI, you’ll be notified of the specific documents needed. Resubmit them to continue verification.
For supported documents and compliance requirements by jurisdiction, see Identity Verification.

Stablecoin wallet

Creating a customer provisions a wallet on every supported blockchain. Wallets are enabled for use once the customer reaches APPROVED. Once active, they hold stablecoin balances, send and receive crypto payments, and power instant payouts via prefunded balances. See Stablecoin Wallets for the full schema and lifecycle.
The wallets array is only returned on customer responses once verification reaches APPROVED.

Virtual accounts

A customer can also hold virtual fiat accounts to send and receive local fiat. Each account is tied to one payment rail and currency, with its own verification status independent from the customer’s. See Accounts for the full schema and lifecycle.