An Alias Account links a Holder to an underlying Midaz Account and stores customer-facing account identifiers separately from ledger balances.Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Before you start
You need an existing Holder and an existing Midaz Account. Keep the Account alias available because this page connects Holder information to the ledger Account.
Create the Alias Account
Field guide
| Field | What to enter | Example |
|---|---|---|
| Holder | Holder that owns or controls this Alias Account. | John Doe |
| Account alias | Midaz Account alias to connect to this Alias Account. Include the @ prefix when required. | @customer_123_checking |
| Alias name | Friendly name operators can recognize. | John Doe Checking |
| Branch or bank fields | External banking information when your use case needs it. | 0001 |
| Account number | Customer-facing account number or external account identifier. | 123456-7 |
| Type | Classification of the account relationship. | checking |
| Metadata Key | Optional classification or integration field name. | sourceSystem |
| Metadata Value | Value for the metadata key. | crm |
What to do next
After creating the Alias Account, use it to identify the customer account in operational flows, or return to Managing Alias Accounts to review the record.