Get Account Validation by Id

code examples curl request get \\ \ url https //sand api monoova com/au/cop/payman v2/accountvalidation/{id} \\ \ header 'accept application/json'var myheaders = new headers(); myheaders append("accept", "application/json"); myheaders append("content type", "application/json"); var requestoptions = { method 'get', headers myheaders, redirect 'follow' }; fetch("https //sand api monoova com/au/cop/payman v2/accountvalidation/{id}", requestoptions) then(response => response text()) then(result => console log(result)) catch(error => console log('error', error));require "uri" require "json" require "net/http" url = uri("https //sand api monoova com/au/cop/payman v2/accountvalidation/{id}") https = net http new(url host, url port) https use ssl = true request = net http get new(url) request\["accept"] = "application/json" request\["content type"] = "application/json" response = https request(request) puts response read body import requests import json url = "https //sand api monoova com/au/cop/payman v2/accountvalidation/{id}" payload = {} headers = { 'accept' 'application/json', 'content type' 'application/json' } response = requests request("get", url, headers=headers, data=payload) print(response text) responses // 200 ok the validation was processed read resultdata resultcode for the machine outcome and resultdata cxresultmessage 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 { "traceid" "0hn7gq2l4k9ab 00000001", "resultdata" { "cxresulticoncode" "tick", "cxresultmessage" "the account name matches the account details provided ", "cxresultdisplayaccountname" "monoova payments pty ltd", "resultcode" "mtch", "accountvalidationuniqueid" "av 2026 0923 000185", "submerchantid" "subm 0001234" } }// 400 bad request the request failed validation before it reached the name matching service the errors array names each failing field through errorcode, with a human readable errormessage correct the values and resend — retrying the identical request returns the same 400 { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 401 unauthorized the bearer token is missing, malformed, or has expired generate a new token from the monoova developer portal and send it in the authorization header as bearer \<token> do not retry with the same token { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 403 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 submerchantid 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 { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 404 not found no validation matches the id in the path — either it was never created, or it belongs to a different account check the value against the accountvalidationuniqueid sent on the create request a filter search that matches nothing returns 200 with an empty resultdata array instead of a 404 { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 500 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 accountvalidationuniqueid rather than a new one quote the traceid when contacting monoova support { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 502 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 accountvalidationuniqueid after a short delay, and escalate with the traceid if it persists { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }// 504 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 accountvalidationuniqueid 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 { "traceid" "0hn7gq2l4k9ab 00000003", "errors" \[ { "errorcode" "pay bsb invalid", "errormessage" "the field bsb must match the pattern ^\[0 9]{3} \[0 9]{3}$ " } ] }