Every customer has to accept Lumx’s Terms of Service before they can complete identity verification and move money. Acceptance is collected programmatically through the API. Until the customer accepts, theDocumentation Index
Fetch the complete documentation index at: https://docs.lumx.io/llms.txt
Use this file to discover all available pages before exploring further.
TERMS_OF_SERVICE entry stays in their requirements array and verification can’t proceed.
Generating the acceptance link
Send aPOST request to /customers/{id}/tos to generate an acceptance URL for a specific customer. Optionally include a redirectUrl to send the customer back to your app after they accept.
Request
Response
url expires after 24 hours. If it expires before the customer accepts, generate a new one.
Sharing the link with your customer
The acceptance flow lives on a Lumx-hosted page. Share the returnedurl with the customer through whichever channel fits your product: email, SMS, in-app link, or as part of an onboarding redirect.
When the customer opens the link, they review the Terms of Service and accept. If a redirectUrl was provided, they’re sent back to your app afterwards.
Tracking acceptance status
Terms of Service appears as aTERMS_OF_SERVICE entry inside the customer’s requirements array, alongside other onboarding requirements. Subscribe to customer webhooks to be notified as the customer progresses through verification, or read the customer at any time to inspect the current requirements.
Request
Response (excerpt)
Related resources
Legal Documents
Full list of Lumx’s legal documents and policies.
Identity Verification
Data requirements for KYC/KYB after acceptance.
Individual verification
End-to-end onboarding flow for individual customers.
Business verification
End-to-end onboarding flow for business customers.