Some ledgers require account-level setup before an account can send assets or use ledger-specific features. These setup tasks create transaction orders, but the purpose is account enablement rather than payment initiation.
| Action | UI procedure | API procedure |
|---|---|---|
| Initialize a Hedera account | Initialize Hedera accounts in the UI | Initialize Hedera accounts with the API |
| Initialize a Stellar account | Initialize Stellar accounts in the UI | Initialize Stellar accounts with the API |
| Reveal a Tezos account public key | Reveal Tezos accounts in the UI | Reveal Tezos accounts with the API |
| Update XRPL account settings | Update XRPL account settings in the UI | Update XRPL account settings with the API |
| Ledger | Setup task | Use when |
|---|---|---|
| Hedera | Account initialization | A newly created Hedera account must be registered on chain before it can send assets. |
| Stellar | Account initialization | A newly created Stellar account must be funded from an existing Stellar account before it can transact. |
| Tezos | Public key reveal | A Tezos account must reveal its public key on chain before validators can check transactions from the account. |
| XRPL | Account settings | XRPL account settings control optional behavior such as issuer freeze settings, trust line authorization, destination tags, and deposit authorization. |
These tasks follow the same intent approval model as other governed changes. For the account model, see Accounts. For transaction orders, see Transaction workflow.