Monoova Automatcher (Bank Account Receivables) API
Overview Having customers paying you by bank transfer might be easy for your customers but contains a reconciliation risk for you. If your customer mistypes or forgets the reference to go with the payment, you might not know whom the payment is from. Orphaned transactions can be challenging and costly to handle. The solution is our receivables API. We allow you to assign a specific account number to each payer so you know for a fact where the received funds originated, regardless of whether they remembered to type the reference. Specifically, the bank-account receivables APIs allow the creation and maintenance of bank account numbers for the purpose of receiving and reconciling funds via direct credit. Once an account number is created, payments may be made via any banking institution in Australia to the BSB and account number provided by us to you. These account numbers can be toggled active/inactive and linked to a client provided unique ID. Once a transaction is received, Monoova provides reporting on the details of each item, and makes the funds available for disbursement in your Sign-in mAccount. Authentication is the same as for the rest of Monoova’s APIs.
Monoova Automatcher (Bank Account Receivables) API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Automatcher (Bank Account Receivables). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 15 operations across 15 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version v5.29.
Requests are made against 2 base URLs: https://api.mpay.com.au, https://api.m-pay.com.au.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Monoova Automatcher (Bank Account Receivables) API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (BasicAuth).
By default, every request must be authenticated.
Paths & Operations 15
Across 15 paths, the API surfaces 15 operations — 8 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.
Overview Having customers paying you by bank transfer might be easy for your customers but contains a reconciliation risk for you. If your customer mistypes or forgets the referen…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are receivablesStatusSetResponse_V1 (8 properties), receivablesProcessDirectDebitResponse_V1 (8 properties), receivablesCreateResponse_V1 (8 properties), receivablesRefundResponse_V1 (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Monoova 12
Other APIs Monoova publishes across the network.
This is an independent, third-party profile of Monoova Automatcher (Bank Account Receivables) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.