Account Hierarchy

monoova lets you create different hierarchies within your account maccount the main central repository of funds it stores configuration, permissions, authentication tokens, and the main balance ledger accounts sub accounts that store and segregate customer funds independently, with their own bsb and account number virtual account numbers / payids unique identifiers and payment methods linked to your maccount or ledger accounts to receive real time payments from customers how it works the diagram below shows how the structure nests inside monoova company → maccount → (optionally ledgers) → virtual accounts → payids layer by layer your company (monoova portal sign in) — the top level customer entity access at this level is via portal login maccount — the funded account two things are attached to it in both branches available funds balance api key — access is scoped per maccount, not per company portal login is company wide, but each maccount carries its own api key, so integrations are isolated per maccount ledger — an maccount can have 1\ n to ledgers each ledger holds its own balance, and the ledger balance is separate to the parent maccount balance virtual accounts — the addressable receiving identity (bsb and account number) these addresses do not hold balances unless linked to a ledger ledger based setup ledger 1 1 to virtual account — exactly one virtual account per ledger in this set up, the ledger effectively tracks the balance and transaction history for the virtual account virtual account only setup maccount 1\ n to virtual accounts — many virtual accounts can connect straight off the maccount, and none of them holds a balance all inbound funds will settle to the maccount balance in this case payid — each virtual account can have 1\ n to payids a single virtual account can have multiple payid aliases