Confirmation of Payee

confirmation of payee (cop) matches the account details you’ve entered, with the details held by the recipient’s bank, when you’re sending money to a business or person using their bsb and account number confirmation of payee (cop) can help verify the payee and protect you from scams and mistaken payments the current version of cop supports the “ verify address book ” use case verification and update of the payee name for an existing address book entry, where the user is not changing the account number for example verify the payee every 6 months user requested 'refresh' of a single address book entry one click bulk 'verify contacts' from the address book what does confirmation of payee do? expose the confirmed data lookup services through a new api endpoint, and extensions to existing financial endpoints to utilise these services monoova api authentication authentication for the cop api will be handled in auth0, and api access will be based on a bearer token the bearer token can be retrieved using the token api monoova api documentation https //developer monoova com/api by passing the username as maccount and the latest api key as password in the header the access token expires after 3600 seconds (60 minutes), at which point the customer’s application should generate a new one confirmation of payee match statuses when a confirmation of payee check has been carried out, customers will see one of the following outcomes match – the information entered matches the record of the recipient account close match – the information is close, for example, your friend’s name is john, and you entered their name as johny no match – the information entered does not match the data against the account you’re sending funds to error – the cop service was unable to confirm account details account closed – the account you are attempting to send a payment to is closed for joint accounts, only one name needs to be supplied to get a match or close match result, and names that include apostrophes or hyphens will match both with and without punctuation marks included for a match and a close match, the recipient’s name will be displayed for no match results, the recipient’s name will not be displayed unless it is a business or government organisation cx result code code name description tick green tick ( \<font color="#15803d">✓\</font> ) icon confirmed data match info blue info ( \<font color="#2166ae">i\</font> ) icon observed data match excm orange exclamation ( \<font color="#c2410c">!\</font> ) icon close match, weak match or not enough info cros red cross ( \<font color="#b91c1c">x\</font> ) icon no match dash orange dash ( \<font color="#c2410c"> \</font> ) icon opt out, account not found, account closed or generic errors combined result code code name description mtch match confirmed the account name matches the account in confirmed data mtco match observed the account name seems to match the account in observed data cmtc close match confirmed this is a close or very probable match in confirmed data wmtc weak match observed there's a different name more commonly used for this account in observed data ninf not enough info observed not enough payments in observed data to indicate if the account details look correct nmtc no match confirmed the account name entered does not match the account in the confirmed data nmto no match observed the account name doesn't seem to match the account in observed data nfnd account not found account not found in the confirmed data holder system clsd account closed account closed in the confirmed data holder system errr error or opt out opt out and generic errors result data type code code name cnfd confirmed data only obsd observed data only both both confirmed and observed data none neither confirmed nor observed data error reason codes code name description bsbn bsb not found account bsb not found in npp brdt this could be an invalid bsb or a valid bsb that is not present in npp brdt ncop not cop enabled the account servicer is not yet enabled as a cop confirmed data holder navl not available confirmed data holder has advised that they are operationally unavailable to respond to cop lookup requests oout opt out account's cop status is opt out cnpf cop not performed confirmed data holder is unable to provide cop data for the account this could also be an account not found in the confirmed data holder system rfsl data holder refusal the confirmed data holder refused to respond (e g suspicious request, session enumeration control of confirmed data holder) tmny too many transactions the confirmed data holder or cop central matching service detected too many transactions from the data requester institution time time out time out or connection issue to the confirmed/observed data holder tech technical error technical or unknown error returned by confirmed/observed data holder