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 Reconciliation Rules API

Overview This feature enables customers to specify the criteria for accepting incoming NPP and DE payments in real time. The customer will be able to advise Monoova about the exact amount they expect to receive in their ABA/PayId in an agreed timeframe. This information would be used to determine whether to accept or reject a payment. There are 2 criteria that can be set when specifying the reconciliation rules. Inbound transactions will only be accepted if Bsb - Account Number and amount matches an active reconciliation rule. OR PayId and amount match an active reconciliation rule If pre-defined criteria are not met, the transaction will automatically be returned to the sender. These rules will not be applied to NPP PayTo Receivables.

Monoova Reconciliation Rules API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reconciliation Rules. 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 1 schema. 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 1 schemas 2 GET1 PATCH1 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 Reconciliation Rules 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, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Reconciliation Rules 4

Overview This feature enables customers to specify the criteria for accepting incoming NPP and DE payments in real time. The customer will be able to advise Monoova about the exac…

POST
/receivables/v1/reconciliationrules/create
Create Reconciliation Rule
ReconciliationRulesCreate body → 200400
PATCH
/receivables/v1/reconciliationrules/{ReconciliationRuleReference}
Cancel Reconciliation Rule
ReconciliationRulesCancel 1 param → 200400
GET
/receivables/v1/reconciliationrules/list/{dateTime}
Get the list of Reconciliation Rules by Date/Time
ReconciliationRulesSearchByDate 7 params → 200
GET
/receivables/v1/reconciliationrules/{id}
Get Reconciliation Rule By ID
ReconciliationRulesSearchByID 1 param → 200400

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is receivables.reconRulesCreate (6 properties). Each schema is shown below with its type and property counts.

receivables.reconRulesCreate
object
6 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

monoova-reconciliation-rules-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 Reconciliation Rules 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.