Closed CDR-API-Stream closed 2 years ago
CBA appreciates the opportunity to provide feedback on this Noting Paper.
Of the possible convention scenarios set out in this noting paper, CBA believes that implementing scenario 2 could help the ecosystem and participants address some of the issues raised in DP 225, as long as the customer is able to easily identify the party that is receiving the data via the Data Holder dashboard, and the ADR dashboard (for example by the naming of the software product in a way that makes it clear for a customer what use case it is related to and what entity has access to their data).
More specifically, we believe this option will help address security and privacy concerns relating to: (1) distinct ID permanence IDs linked to the Affiliate/Representative; and (2) providing the ability to suspend a particular affiliate/representative (based on the software product) without having to suspend all affiliate/representatives associated with a given ADR.
Thanks to CBA for the feedback. We will work to publish this guidance on the CDR portal and will emphasise the need for a customer to easily identify the party.
We will now close this feedback thread.
This noting paper has been created to provide interim guidance on how the Register standards should be utilised to represent experiences for Affiliates and CDR Representatives. Noting Paper - Representatives and Affiliates Conventions.pdf
Note:
We will leave this thread open for feedback until 21st January so that the guidance can be finalised and posted on the Support Portal before 1st February.