Monoova BPAY API
Overview The BPAY APIs do not perform any financial transactions and are used to validate BPAY information that is used in the /financial/v2/transaction/execute API. The /financial/v2/transaction/validate APIs also validates BPAY information using the same sub-system as documented in this section before performing any financial transactions. Important Notes By design, BPAY validation can be time sensitive. If you cache valid BPAY information for later use, it may become invalid due to time expiry. By design, BPAY validation can be amount sensitive. If you cache valid BPAY information for later use and change the amount to pay then this could be invalid. BPAY validation should be performed immediately before calling the /financial/v2/transaction/execute API to perform the bill payment. You have the option of calling /financial/v2/transaction/validate (The first validation error will be returned which may not be a BPAY error)
Monoova BPAY API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include BPAY. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 6 operations across 6 paths, and defines 10 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 BPAY API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (BasicAuth).
By default, every request must be authenticated.
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 5 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Overview The BPAY APIs do not perform any financial transactions and are used to validate BPAY information that is used in the /financial/v2/transaction/execute API. The /financia…
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are DTO.BPAYBiller_V1 (13 properties), DTO.BPAYBillersResponse_V1 (8 properties), DTO.BPAYValidation_V1 (7 properties), DTO.BPAYReceipt_V1 (7 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 BPAY 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.