changelog

Product Update

Content

Guides

KYC reuse with Sumsub share tokens

Abstract changelog cover for account provisioning at customer creation

Import existing Sumsub verifications when creating individual customers by passing a share token, skipping document collection for users who already completed KYC on your own Sumsub account.

Reuse an existing Sumsub verification

If your customers already completed KYC on your own Sumsub account, pass a Sumsub share token in the new optional shareToken field when creating a customer to import the existing verification instead of collecting documents again. Lumx detects the verification and reuses it, so onboarding is completed with fewer documents and less waiting.

Availability: KYC reuse is only available for INDIVIDUAL customers at this stage. Business customers (KYB) are not covered, including individual associated parties within a business verification flow. It also requires a data-sharing agreement between you and Lumx. See the KYC Reuse guide for more information.

A

{
"shareToken": "_act-sbx-jwt-token-from-sumsub",
"type": "INDIVIDUAL",
"name": "William Default",
"taxId": "123.456.789-00",
"birthDate": "1990-01-01",
"country": "BRA",
"email": "william.default@example.com",
"accounts": ["BRL"]
}

Stable News

In this page

Content

Product

Feb 18, 2026

Account provisioning at customer creation

Create customer accounts by currency during provisioning, read linked accounts, and subscribe to account lifecycle webhooks as verification moves accounts to active status.

Stable News

In this page

Content

API

Feb 18, 2026

Bank accounts renamed to destinations

The bank accounts resource has been renamed to destinations across API fields, routes, and webhook events, with a transition period for existing integrations.

Stable News

In this page

Content

API

Feb 18, 2026

TEMPORARY_REJECTION renamed to RFI

The temporary rejection status has been renamed to RFI across customer verification, associated parties, and webhook events.

Stable News

In this page

Content

API

Feb 18, 2026

Wallets only returned for APPROVED customers

Customer wallet data is now returned only after verification is approved, with webhook and read-customer flows recommended for availability updates.

Stable News

In this page

Content

API

Feb 18, 2026

Isolated retry for associated party verification

Retry verification for specific associated parties without changing the status of unaffected parties, enabling more targeted business customer review flows.

Stable News

In this page

Content

Product

Feb 18, 2026

Improving customer onboarding

Customer onboarding now includes automatic UBO role assignment, proof-of-address requirements, and terms-of-service acceptance before verification.

Stable News

In this page

Content

API

Feb 18, 2026

Webhooks V2

Webhooks now use a new delivery system with consistent event structure, retry reliability, and updated signature verification headers.

Stable News

In this page

Content

Product

Feb 18, 2026

MXN is live: transactions in Mexican pesos, SPEI transfers, and accounts with CLABE

You can now create MXN transactions through the Dashboard and API, enable MXN on/off ramps, execute bank transfers in Mexico via SPEI, and enable MXN Virtual Accounts with unique CLABE numbers for your customers.

Stable News

In this page

Content

MCP

Feb 18, 2026

KYC/KYB API, Idempotency and MCP Server

Strengthening Lumx’s infrastructure across compliance orchestration, operational safety, and AI-native integration.

Stable News

In this page

Content

API

Feb 18, 2026

Supporting Individual Customers and Bank Account Holders

Financial infrastructure doesn’t operate only between companies.

Stable News

In this page