Create Account Validation

POST

https://sand-api.monoova.com/au/cop/payman-v2/AccountValidation

Creates a Confirmation of Payee account validation.

Submit the BSB, account number and the account name you hold for the payee. The service compares the supplied name against the name registered with the recipient's financial institution and returns a match result, a customer-facing message and an icon code you can surface in your own UI.

Keep the accountValidationUniqueId you send — it is the key used to retrieve this validation later through Get Account Validation by Id.

bodyobjectThe account details to validate.

200200 OK. The validation was processed. Read <code>resultData.resultCode</code> for the machine outcome and <code>resultData.cxResultMessage</code> for the wording to show the payer. A 200 confirms the request was accepted and answered — it does not by itself mean the name matched.

400400 Bad Request. The request failed validation before it reached the name-matching service. The <code>errors</code> array names each failing field through <code>errorCode</code>, with a human-readable <code>errorMessage</code>. Correct the values and resend — retrying the identical request returns the same 400.

401401 Unauthorized. The bearer token is missing, malformed, or has expired. Generate a new token from the Monoova developer portal and send it in the <code>Authorization</code> header as <code>Bearer <token></code>. Do not retry with the same token.

403403 Forbidden. The token was accepted, but the account behind it is not permitted to perform this call — Confirmation of Payee is not enabled on the account, is not yet configured, or the <code>subMerchantId</code> supplied is not associated with it. This is an entitlement problem, not a data problem: the same request will keep returning 403 until Monoova updates the account configuration. Do not retry automatically.

404404 Not Found. No validation matches the <code>id</code> in the path — either it was never created, or it belongs to a different account. Check the value against the <code>accountValidationUniqueId</code> sent on the create request. A filter search that matches nothing returns 200 with an empty <code>resultData</code> array instead of a 404.

500500 Internal Server Error. An unexpected error occurred while processing an otherwise valid request. The request may or may not have been recorded, so re-send it with the same <code>accountValidationUniqueId</code> rather than a new one. Quote the <code>traceId</code> when contacting Monoova support.

502502 Bad Gateway. The request was valid, but an upstream service — the NPP gateway that performs the name match — returned an error, so no result could be produced. The validation was not completed. Retry with the same <code>accountValidationUniqueId</code> after a short delay, and escalate with the <code>traceId</code> if it persists.

504504 Gateway Timeout. An upstream service did not respond in time. Unlike a 502, the outcome is genuinely unknown — the validation may still have been recorded. Re-send with the same <code>accountValidationUniqueId</code> rather than a new one so the original record is reused, or call Get Account Validation by Id first to see whether a result already exists.

curl --request POST \
     --url https://sand-api.monoova.com/au/cop/payman-v2/AccountValidation \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{
     "accountValidationUniqueId": "AV-2026-0923-000185",
     "subMerchantId": "SUBM-0001234",
     "bsb": "032-002",
     "accountNumber": "123456789",
     "accountName": "Monoova Payments Pty Ltd",
     "requestPurposeCode": "VADR"
     }'