English
Glossary
| Term | Definition |
|---|---|
| Account | Balance-owning unit associated with a customer or business uid |
USER | Customer wallet account type |
BUSINESS | Merchant or operational payment account type |
| Deposit Address | Network-specific address allocated to an account |
| Asset Type | User-facing economic asset such as USDT or ETH |
| Network | Blockchain environment such as Ethereum Sepolia |
| Asset | An asset type deployed on a particular network |
| Atomic / Raw Unit | Smallest integer unit of an asset |
| Balance | Current available and reserved position for an account and asset type |
| Ledger | Append-only journal of finalized balance movements |
| Internal Transfer | OOLIN account-to-account movement without an external blockchain transfer |
| External Withdrawal | Asynchronous transfer to an outside blockchain address |
client_request_id | Customer-generated unique mutation identifier used for recovery |
| Cursor | Last processed ID used for incremental synchronization |
| HMAC | Keyed hash used to authenticate request content |
| Nonce | Per-request unique value that prevents replay |
For field-level definitions, use the API Reference.
Relationship summary
One uid can be associated with one or more Accounts. An Account owns balances and deposit addresses. A deposit address is network-specific, while a balance is normally asset-type-specific. Deposits, internal transfers, and withdrawals are workflow records; their finalized accounting effects are immutable Ledger entries. A cursor is a synchronization checkpoint, not a transaction status.
Keeping these concepts separate prevents common modeling errors such as storing a network address as the wallet itself, treating the current balance as transaction history, or treating a list cursor as proof that a pending record completed.