Business Readiness Requirements
Requirements to complete before going live with NameCheck
NameCheck Version
This page relates to the original version of NameCheck API.
If you are integrating with the NameCheck API, the following requirements should be completed as part of your go-live readiness. We recommend considering these early in your implementation journey.
Data Harvesting Control
What is it?
To prevent internal users or end-customers from repeatedly querying NameCheck to collect sensitive payee information (e.g. BSB, account number and account name), customers are required to implement a data harvesting control in their solution.
Detailed requirements are located in the Integration Centre for signed customers only.
What do you need to do?
Customers need to implement the Data Harvesting Control, demonstrate and attest to its implementation before going live.
CX Messaging Guidelines
Customers implementing NameCheck are expected to meet basic CX guidelines relevant to how matching results are displayed to users (symbols and detailed result description).
This requirement is valid for both internal and external implementation of NameCheck (i.e. internal users only vs exposed to end-customers).
Please refer to this guide for details on NameCheck’s CX guidelines.
End-customer Terms Compliance Attestation
We ask that customers update their own privacy policy, personal information collection notices and user-facing terms, in relation to their use of NameCheck in line with applicable Privacy Laws.
Once done, customers should provide a formal attestation of compliance to CommBank to confirm that the above terms have been updated. This attestation is required:
- For initial Go-Live
- Annually (first week of July)
Customers can use the attestation template below and submit it by email ([email protected])
A template is available for signed customers on the Integration Centre.