Changelog

​

Account provisioning at customer creation 🏦

1. Provision accounts at customer creation

{
	"type": "BUSINESS",
	"legalName": "Lumx Tecnologia LTDA",
	"taxId": "00.000.000/0001-91",
	"incorporationDate": "2020-01-01",
	"country": "BRA",
	"email": "hello@lumx.io",
	"accounts": [
		{ "id": "8412f484-32fe-418f-80d1-99eb1b3ba7f3", "currency": "BRL" },
		{ "id": "af04e979-360a-428a-84e6-cbd8ffc4942b", "currency": "USD" },
		{ "id": "d06d342c-629a-4d99-a26f-34e8ea528403", "currency": "EUR" },
		{ "id": "16cb802f-8521-41ad-ab6e-dc40f43c0ad3", "currency": "MXN" }
	]
}

2. Read accounts

{
	"data": [
		{
			"id": "433bbe8b-feba-49e3-80f8-7bb528d3744e",
			"customerId": "3b55a2fa-57dc-48f1-ac0f-ac1d5ba4674a",
			"currency": "BRL",
			"status": "ACTIVE",
			"createdAt": "2026-05-13T20:49:13.236Z",
			"updatedAt": "2026-05-14T13:55:15.418Z"
		}
	]
}

3. Account webhook events

​

Bank accounts renamed to destinations 📦

1. Resource renamed across the API

2. bank_account.* webhook events renamed to destinations.*

3. type field removed from destination requests

​

TEMPORARY_REJECTION renamed to RFI ✏️

1. Customer and associated party status renamed

2. New customer.rfi webhook event

​

Wallets only returned for APPROVED customers 👛

1. wallets gated by verification status

​

Isolated retry for associated party verification 🔁

1. Retry verification for specific associated parties

{
	"associatedPartyIds": [
		"a1b2c3d4-e5f6-7890-abcd-ef1234567890",
		"b2c3d4e5-f6a7-8901-bcde-f12345678901"
	]
}

​

Improving customer onboarding 🛩️

1. Auto-assign UBO role to sole shareholders

2. PROOF_OF_ADDRESS document now required

{
	"type": "PROOF_OF_ADDRESS"
}

3. Terms of service acceptance required before verification

{
	"redirectUrl": "https://yourapp.com/onboarding/next-step"
}

{
	"url": "https://dashboard.lumx.io/tos/sandbox/eyJhbGciOiJSUzI1...",
	"expiresAt": "2026-04-09T16:00:00Z"
}

​

Webhooks v2 🔔

1. New webhook delivery system

2. Legacy webhook format deprecated: Migrate to the new webhook format and update your signature verification to use the webhook-id, webhook-timestamp, and webhook-signature headers. See Verifying webhook signatures for implementation examples.

​

MXN support is now live 🇲🇽

1. MXN transactions now available

{
	"sourceCurrency": "MXN",
	"sourceAmount": "10000.00",
	"targetCurrency": "USDC",
	"purpose": "PERSONAL_ACCOUNT"
}

2. MXN bank accounts now supported

{
	"customerId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
	"name": "Mexico Supplier Account",
	"type": "EXTERNAL",
	"rail": "SPEI",
	"currency": "MXN",
	"identifier": {
		"clabe": "012180001234567897"
	},
	"holder": {
		"type": "INDIVIDUAL",
		"relationship": "SUPPLIER",
		"name": "Juan Pérez",
		"taxId": "PEPJ850101ABC",
		"address": {
			"line1": "Avenida Insurgentes Sur 1458",
			"city": "Mexico City",
			"state": "CDMX",
			"postalCode": "03900",
			"country": "MEX"
		}
	}
}

​

Sandbox magic numbers for testing 🪄

1. Magic numbers for customer verification testing

{
	"type": "INDIVIDUAL",
	"name": "William Default",
	"taxId": "123.456.789-01",
	"birthDate": "1990-01-01",
	"country": "BRA",
	"email": "william.default@example.com"
}

​

Multiple roles for associated parties 🎭

1. role changed to roles array in associated parties: The POST /customers/{id}/associated-parties endpoint now requires a roles array instead of the single role string field. This allows associated parties to hold multiple roles simultaneously (e.g., both UBO and REPRESENTATIVE). Valid values: UBO, REPRESENTATIVE, SHAREHOLDER.

{
	"type": "INDIVIDUAL",
	"role": "UBO",
	"name": "Maria Santos",
	"birthDate": "1985-07-10",
	"email": "maria.santos@example.com",
	"taxId": "987.654.321-00",
	"ownershipPercentage": 40
}

{
	"type": "INDIVIDUAL",
	"roles": ["UBO"],
	"name": "Maria Santos",
	"birthDate": "1985-07-10",
	"email": "maria.santos@example.com",
	"taxId": "987.654.321-00",
	"ownershipPercentage": 40
}

{
	"type": "INDIVIDUAL",
	"roles": ["UBO", "REPRESENTATIVE"],
	"name": "Maria Santos"
}

​

KYC/KYB API and idempotency support 🤯

1. KYC/KYB verification endpoints

• PATCH /customers/{id}/additional-information — Submit KYC/KYB data
• POST /customers/{id}/documents — Upload verification documents
• POST /customers/{id}/associated-parties — Add UBOs, shareholders, and representatives
• GET /customers/{id}/associated-parties — List associated parties
• GET /customers/{id}/associated-parties/{associatedPartyId} — Read an associated party
• POST /customers/{id}/verifications — Start a verification
• GET /customers/{id}/verifications/{verificationId} — Read verification status

2. additionalInformation in customer response

3. Multi-level corporate structures

{
	"type": "INDIVIDUAL",
	"role": "SHAREHOLDER",
	"parentId": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
	"name": "John Smith",
	"ownershipPercentage": 50
}

4. Idempotency support

​

Individual customers and bank account holders 🥳

1. Individual customer type

{
	"type": "INDIVIDUAL",
	"name": "William Default",
	"taxId": "100.100.100-01",
	"birthDate": "1990-01-01"
}

2. Individual bank account holders

3. Individual bank account identifier key type as CPF

4. New relationship types for bank account holders

​

Multi-blockchain support 🔥

1. Multiple wallets per customer

{
	"wallets": [
		{
			"blockchain": "POLYGON",
			"address": "0x...",
			"blockExplorerUrl": "https://polygonscan.com/address/0x...",
			"isDefault": true,
			"balances": [{ "stablecoin": "USDC", "balance": "1000.00" }]
		}
	]
}

2. Blockchain field in transactions

{
	"blockchain": "BASE",
	"sourceCurrency": "BRL",
	"sourceAmount": "1000.00",
	"targetCurrency": "USDC"
}

3. Blockchain field in exchange rates

4. Improved balance tracking

5. wallet and balances fields deprecated on customers: Migrate to the new wallets array. Affected endpoints: POST /customers, GET /customers.
6. Default partner fee removed: If no partnerFeeId is provided, partner fees will be zero. Remove any logic that depends on a default fee. Affected endpoints: GET /partner-fees, POST /partner-fees.

​

Transaction limits response improved ⚡

1. Transaction limits now include usage tracking

{
	"transactionLimits": {
		"single": { "max": "10000.00" },
		"daily": {
			"max": "100000.00",
			"used": "0.00",
			"remaining": "100000.00"
		},
		"monthly": {
			"max": "1000000.00",
			"used": "0.00",
			"remaining": "1000000.00"
		}
	}
}

2. transactionLimits no longer returned by default: The transactionLimits field is no longer included in GET /customers/{id} responses by default. Use the new query parameter includeTransactionLimits=true to retrieve transaction limits.
3. transactionLimits removed from customer listing: The GET /customers endpoint no longer returns the transactionLimits field in the response array.
4. 10-second timelock removed from exchange rates: The 10-second timelock option is no longer available. The 30-second timelock now has no additional fees, and fees for other timelock options have been optimized.

​

SEPA and SWIFT are live 🚀

1. SEPA support now available

{
	"rail": "SEPA",
	"sourceCurrency": "EUR",
	"sourceAmount": "10000.00",
	"targetCurrency": "USDC",
	"purpose": "PERSONAL_ACCOUNT"
}

2. SWIFT support now available

{
	"rail": "SWIFT",
	"sourceCurrency": "USD",
	"sourceAmount": "10000.00",
	"targetCurrency": "USDC",
	"purpose": "PERSONAL_ACCOUNT"
}

3. Purpose field now returned in transaction responses

4. Target amount visibility improved

5. Bank account ordering updated

​

Bank Accounts are live 🎉

1. Supplier payments now available

2. PROCESSING status renamed to TRANSFERRING_STABLECOIN
3. state.blockchain moved to state.receipt

4. purpose now required for on-ramp and off-ramp transactions

5. On-ramp: payment.rail moved to request level rail
6. Off-ramp: customerId and payment object removed, use bankAccountId only
7. Exchange Rate: rail and customerId parameters now required