How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Monoova Whitelisting for Automatcher (Bank Account Receivables) API

Overview This feature enables whitelisting of bank accounts when receiving funds in automatcher accounts. Funds received from a non-whitelisted account will be automatically returned. Using this feature, funds received can be limited to pre-approved bank accounts only. There are 2 criteria that can be set when whitelisting bank account numbers. Inbound transaction will only be accepted from:  1. An account that matches a whitelisted account name; AND/OR 2. An account that matches a whitelisted BSB and account number If pre-defined criteria are not met, the transaction will be returned to the sender automatically. If enabled, each automatcher account has its own separate whitelist. You have the option to establish a webhook subscription to receive a notification when a payment is declined as a result of whitelist restrictions. To subscribe to a webhook use the Subscriptions APIs. Event name:  InboundDirectCreditRejections

Monoova Whitelisting for 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 Whitelisting for Automatcher (Bank Account Receivables). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 7 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.

4 operations 4 paths 7 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v5.29
Base URL
https://api.mpay.com.au
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Monoova Whitelisting for 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 4

Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Whitelisting for Automatcher (Bank Account Receivables) 4

Overview This feature enables whitelisting of bank accounts when receiving funds in automatcher accounts. Funds received from a non-whitelisted account will be automatically retur…

POST
/receivables/v1/whitelisting/create
Create Whitelist Source Account
ReceivablesCreateWhitelistSourceAccount body → 200400500
POST
/receivables/v1/whitelisting/update
Update Whitelist Source Account
ReceivablesUpdateWhitelistSourceAccount body → 200400500
GET
/receivables/v1/whitelisting/list/{automatcherBankAccountNumber}
List Whitelist Source Accounts
ReceivablesListWhitelistSourceAccounts 2 params → 200400500
GET
/receivables/v2/rejectedTransactions/{startDate}
Rejected Transactions Report
ReceivablesRejectedTransactionsReport 5 params → 200400500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are receivablesGetWhiteListingAccountsResponseArrayItem1 (5 properties), receivablesGetWhiteListingAccountsResponse_V1 (5 properties), receivablesGetWhiteListingAccountsResponseArrayItem2 (5 properties), receivablesUpdateWhiteListingAccountResponse_V1 (5 properties). Each schema is shown below with its type and property counts.

receivablesCreateWhiteListingAccountResponse_V1
object
5 properties
receivablesUpdateWhiteListingAccountResponse_V1
object
5 properties
receivables.updateWhiteListingAccount
object
3 properties 1 required
receivablesGetWhiteListingAccountsResponseArrayItem2
object
Object containing source account details
5 properties
receivablesGetWhiteListingAccountsResponse_V1
object
5 properties
receivablesGetWhiteListingAccountsResponseArrayItem1
object
Object containing source account details
5 properties
receivables.createWhiteListingAccount
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

monoova-whitelisting-for-automatcher-bank-account-receivables-api-openapi.yml Raw ↑

Other APIs Monoova publishes across the network.

Monoova Automatcher (Bank Account Receivables) API
Monoova BPAY API
Monoova Create Payment Using Token API
Monoova Financial API
Monoova Generate a Bearer Token API
Monoova Generate a Client Session API
Monoova Get Async Request Status API
Monoova Get Payment Method Token Details API
Monoova Get Transaction By Date Range API
Monoova Get Transaction By Id API
Monoova Initiate a Payment API
Monoova Ledger Account API
Where this information came from

This is an independent, third-party profile of Monoova Whitelisting for 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.