Data holders in the CDR report information about their CDR performance, including:
- the percentage of time their systems are available to share CDR data; and
- their response time — how long they take to respond to CDR requests for sharing CDR data.
The following tables provide this information for each data holder, noting some data holders are not yet providing this data to the ACCC. In relation to the data:
- the higher the availability percentage, the better the outcome for consumers receiving data from this data holder — there is a higher likelihood data holders’ systems are providing CDR data when a consumer is seeking access to it.
- the shorter the response time, the better the outcome for consumers, because their data is shared more quickly with their accredited data recipient.
CDR performance dashboard
- Green statistics - Data that is within the Non-Functional Requirements as defined in the Consumer Data Standards
- Red statistics - Data that is outside of the Non-Functional Requirements as defined in the Consumer Data Standards
- To Validate - An unexpected response received that requires investigation
Data holders are required to have their systems available, and able to service consumer data requests 99.5% of the time, measured monthly. This means when consumers try to share their CDR data with accredited data recipients, 99.5% of the time it should be successful. The definition of a period of unavailability is any period of time when any of the API end points defined in the standard is unable to reliably provide a successful response to an appropriately constructed request.
The availability requirement applies to both authenticated and unauthenticated end points.
Average response times
Average response times are measured by calculating the time it takes data holders to respond to a request for data (such as a request for consumer data) from the time they receive the request. The average response time target thresholds differ depending on the performance tier of the data request:
- High priority average response times should remain below 1 second (this includes consumer data requests for a list of their bank accounts)
- Low priority average response times should remain below 1.5 seconds (this includes consumer data requests for detail about their bank account, account balance information, transactions history and payees list)
- Unauthenticated end point response times should remain below 1.5 seconds (this includes requests for publicly available banking product information)
- Unattended calls to end points that are not large payloads should remain below 4 seconds (this includes consumer data requests initiated by a data recipient to refresh data through their software products in an automated scenario)
For more information about the different types of performance tiers and the types of API calls included within each tier, please see the Consumer Data Standards.
Data will be updated periodically.
Data holder brands that are not active
You can view a list of data holder brands that are not yet active on the find a provider page, as well as data holders that are active but that have self-reported potential gaps in their CDR systems, through the Rectification Schedule on the ACCC website.
The material published on this website relies on information and data received from data holders. The material published may be subsequently amended or updated to correct any errors that become apparent in it.
The ACCC makes no representation or warranty, express or implied, and does not provide any guarantee, as to the currency, accuracy, reliability or completeness of the material, or as to its suitability for any purpose. To the maximum extent permitted by law, the ACCC and its officers, employees, consultants and contractors are not liable for any errors, omissions, defects or misrepresentations in the material, or for any loss or damage suffered by persons who use or rely on such information (including by reason of negligent act, omission or misstatement or otherwise).