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:

Expose the confirmed data lookup services through a new API endpoint, and extensions to existing financial endpoints to utilise these services.

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 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.

When a Confirmation of Payee check has been carried out, customers will see one of the following outcomes:

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.





To simulate different Confirmation of Payee (CoP) responses in the Sandbox environment, you can trigger specific outcome codes by providing the test bank account data listed below.

Any requests that do not explicitly match the custom triggers below will return the default successful match response.