With this update, Lumx now fully supports individual customers and natural person bank account holders, expanding flexibility for institutions that operate across retail and corporate flows.
1. Individual Customers
You can now create customers with the type INDIVIDUAL, designed for natural persons.
Instead of modeling individuals as corporate entities, institutions can now structure onboarding flows with proper data fields:
Name
Tax ID (CPF)
Birth date
A
"type": "INDIVIDUAL",
"name": "William Default",
"taxId": "100.100.100-01",
"birthDate": "1990-01-01"
}
This allows financial institutions to build compliant onboarding flows for:
Retail clients
Beneficiaries
Independent contractors
Individual counterparties
2. Individual Bank Account Holders
Bank accounts now support individual holders using the same structure.
For counterparty bank accounts, birthDate becomes optional, allowing flexibility when full data collection is not required.
This update enables more accurate representation of:
Personal payout accounts
Independent beneficiaries
Non-corporate recipients
3. CPF as a Valid PIX Identifier
Bank accounts now support CPF as a valid keyType identifier for PIX.
This improves interoperability in Brazilian payment flows and reduces friction when transacting with natural persons.
4. Expanded Relationship Types
We’ve added new relationship types for bank account holders:
FRIEND
RELATIVE
EMPLOYEE
This enhances how institutions model real-world relationships in payment structures, especially in payroll, expense management, and personal transfer scenarios.
Why This Matters
As stablecoin infrastructure converges with local payment systems, supporting both corporate and individual entities becomes essential.
This update ensures institutions can:
Build compliant onboarding flows for natural persons
Represent real-world payment relationships more accurately
Reduce modeling workarounds
Operate seamlessly within Brazilian PIX infrastructure
