Skip to content
English - New Zealand
Sign in
Contact us
  • There are no suggestions because the search field is empty.

UX / UI Guide for Confirmation of Payee

Messaging for the NZ Confirmation of Payee service is consistent across providers. Please follow the specifications in this guide.

Purpose of this guide

To ensure messaging is consistently delivered across the Confirmation of Payee service each Participant must, before implementation:

  • Provide GetVerified with a representative sample of their proposed customer messaging for our approval, or
  • Confirm to GetVerified in writing that the customer messaging is in accordance with the requirements set out in this Guide.
Further to this:
  • Each notification must use consistent iconology including colour as specified in the guide i.e. green tick for Match, red exclamation mark for Not a match etc.
  • Each notification design must use the bold headings as specified in this guide.
  • Each notification unbolded messaging can be edited to align with their own brand voice and UX journey as well as convey the messaging statements in accordance with the advice given against each outcome in this guide.

Reason code and description

Reason

Code

      

Code

Description

Matched

Long Description

Bank Result

MATCH

Full Match

TRUE

The CoP Responder has performed the matching and confirms it’s a match

Match

ANNM

Account Name Does Not Match

FALSE

The CoP Responder has performed the matching and confirms it’s not a match

No Match

MBAM

There may be a match on the account name

FALSE

The CoP Responder has performed the matching and it’s a close match

Partial Match

BANM

Business account, name matches

FALSE

The CoP Requester indicated that the Payer intends to pay a personal account, but the actual account is a business account, and the name matches

Match

PANM

Personal account, name matches

FALSE

The CoP Requester indicated that the Payer intends to pay a business account, but the actual account is a personal account, and the name matches

Match

BAMM

Business account, name may be a match

FALSE

The CoP Requester indicated that the Payer intends to pay a personal account, but the actual account is a business account, and the name might be a match

Partial Match

PAMM

Personal account, name may be a match

FALSE

The CoP Requester indicated that the Payer intends to pay a business account, but the actual account is a personal account, and the name might be a match

Partial Match

AC01

Incorrect Account Number

FALSE

Account does not exist in the CoP Responder’s books

Error

ACNS

Account type not supported for CoP

FALSE

Account not supported for CoP by the CoP Responder

Error

BSBF

Branch state branch fault - not supported at endpoint

FALSE

The CoP responder has incorrectly received a CoP request for a Branch code that does not belong to them

Error

Notification guidelines

'Match' CoP Response: When a Participant, as CoP Requester, receives a 'match' CoP Response, the CoP Requester must:

  1. Display a green tick as shown in the example;
  2. Provide a statement to the effect that the name entered matches  the Account Name and Account Number in records held by the Payee's account provider; and
  3. Consider including information about a 'match' response that encourages the Payer to check they know who the Payee is. 
 Matcha

‘Partial Match' CoP Response: When a Participant, as CoP Requester, receives a ‘partial match' CoP Response, the Requester must:

  1. Display a yellow or amber warning symbol as shown; and
  2. Provide a statement to the effect that the name entered only partially matches the Account Name and Account Number in records held by the Payee's account provider (as per example provided); and
  3. Provide a statement to the effect that the Customer should check the payment details and, if needed, update those payment details and complete a new CoP Check (as per example provided).

 

 PartialMatcha

'Not a Match' CoP Response: When a Participant, as CoP Requester,

receives a 'not a match' CoP Response, the CoP Requester must:

  1. Display a red warning symbol as shown below;
  2. Provide a statement to the effect that the name entered does not match the Account Name and Account Number in the records held by the Payee's account provider (as per example provided); and
  3. Provide a statement to the effect that if the Payer goes ahead with the Payment Instruction the Participant may not be able to recover their money if they pay the wrong person (as per example provided); and
  4. Provide a statement to the effect that the Customer should check the payment details and, if needed, update those payment details and complete a new CoP Check (as per example provided).

 

 Not a match longa

‘Unable to Provide a CoP Verification’

Where it is not possible to provide a CoP Response, the CoP Requester must provide the following messaging as applicable:

Account Type can’t be checked: a statement must be provided to the effect that a CoP Check cannot be completed. (As per example provided).

 Exception 2a

Can’t check payee details: a statement must be provided to the effect that a CoP Check cannot be completed because the Account being paid is with an account provider that is not a Participant. (As per example provided).

 

 Exception 3a

Can’t check payee details right now: a statement must be provided to the effect that a CoP Check cannot be completed for another reason (e.g. where the CoP Service is temporarily unavailable, as per example provided).

 

 Exception 1a