Monoova Verify API
Overview Bank Account Ownership Verification The purpose of this API is to verify access to a bank account or PayID details, which has several compliance and risk-mitigation applications.If the NppCreditPayID method is used, the API response will include the PayID name. In scenarios where the PayID is either unidentified or not configured, you can verify if the payer/payee has access to the account using a secret code.By passing the BSB and account number, the account verification API will credit a target bank account with a secret code in the remitter name and lodgement reference. This code can only be viewed by someone who has access to the target bank account by accessing and viewing their bank statement. The code can then be submitted against our records, and if it matches, Monoova will persist a verification token against that specific account.How it works Initiate a verification transaction on the target bank account. Monoova will credit the target bank account with a 1c amount and a secret remitter code (may take up to 48 hours for the code to show on the target bank account). Below image is how a sample verification code appears on a bank statement. In YELLOW is the code your client will need to return, in BLUE is your remitter name. For NPP verification transactions, the secret code can also be found in the lodgement reference. Owner of the target bank account views the statement to obtain the secret code. Submit the secret code to Monoova via POST verify/v1/aba/validate. In the sandbox, use code "555555" to test successful validation of an account verification. If the submitted code and amount are correct, the target bank account is designated as verified.
Monoova Verify API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Verify. 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 11 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 Verify 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 — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.
Overview Bank Account Ownership Verification The purpose of this API is to verify access to a bank account or PayID details, which has several compliance and risk-mitigation appli…
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are DTO.VerifyAccountDetails (22 properties), verify.initiate2 (8 properties), DTO.VerifyAccountInitiateResponse_V2 (8 properties), DTO.VerifyAccountInitiateResponse_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 Verify 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.