Overview

at the core of monoovas solution is your monoova account, or maccount this account is your central repository of funds, and it's where configuration, permissions, and authentication is stored each maccount has a unique, 16 digit maccount number which is used to identify the account, and when authenticating api access electronic payments maccounts aren't capable of receiving funds directly in order to receive payments into your maccount you'll need to set up an appropriate payment method, such as a virtual account numbers this allows customers to pay your maccount using a bsb and account number funds are stored in the maccount this is your maccount balance what if you need to segregate these funds so each customer has their own balance? you can issue a ledger accounts with its own bsb and account number, which stores the funds separately from your main maccount balance, allowing these to be tracked independently want to ensure funds are received in real time? you can issue customers with their own unique payid , which connects to a virtual account number or ledger account want to ensure customers don't overpay or underpay? set up whitelisting and reconciliation rules alongside your virtual accounts to ensure you're paid the right amount, every time on top of receiving funds by payid and bank transfer, maccounts can also receive funds via direct debit, payto, bpay, cards, and rtgs overview sending payments through monoovas api is simple; requiring only one api endpoint to send direct credit payments, realtime npp payments to a bank account or payid, bpay, abd payments between monoova accounts this endpoint also allows for direct debit payments to be recieved, and can accomodate individual and batch payments