Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consumer's Data Holder(s) not available in ADR consent flow (potentially list not up-to-date) #616

Closed
anzbankau opened this issue Oct 6, 2023 · 4 comments
Labels
Consumer experience Issues related to Consumer experience Standards. Operational

Comments

@anzbankau
Copy link

Description

In the current consent flow to share data, the ADR displays a list of Data Holders that a consumer can select to share data from. There is no specific obligation for ADRs to display all Data Holders that participate in the CDR regime within this list, hence some ADRs opt to provide consumers with a list that does not include all Data Holders. This can result in consumers not being able to create a consent to share data from their Data Holder, which is confusing for the consumer, and not aligned to the intent of the principles of the CDR; in this scenario the consumer is not given the choice to share their data because their data holder is not available. Given we have received customer complaints, we are seeking feedback on this issue and suggest a change to the CX standards for ADRs to take reasonable steps to keep their data holder list complete and up-to-date.

Area Affected

CX standards

Change Proposed

Require ADRs to take reasonable steps to keep their data holder list complete and up-to-date

@WestpacOpenBanking
Copy link

We acknowledge the confusion that consumers may have when encountering this issue and that they may be unclear who is responsible for the list of Data Holders presented to the consumers for selection.

In light of last week’s discussion on this topic, we understand there are various reasons (incl commercial reasons) why ADRs do not offer a complete list of Data Holders to ingest data from. This is a policy issue for consideration by Treasury and we strongly recommend that is not something that should be addressed through standards. We suggest removing the question from Maintenance Iteration #17, referring it to Treasury, and closing the issue.

Currently there are a wide range of DPs still to address and focus on the remaining issues in the maintenance iteration would be a more effective use of time.

Thanks

@TT-Frollo
Copy link

Agree with Westpac this is a policy decision. Further for input into any suggested policy change, an ADR may have both commercial and operational or implementation issues with specific Data Holder implementations that they then choose to not make them available. Commercial services to consumers should be the choice of the ADR. There are also situations where DH implementations have errors where ADR's choose not make these DH available during those periods. Large number of consent authorisation failures can also be an example.

@markskript
Copy link

We understand the concerns of ANZ but also agree with Westpac that this is a policy issue. There are various aspects that need to be reviewed here, both commercial and operational.

@CDR-API-Stream CDR-API-Stream added the Consumer experience Issues related to Consumer experience Standards. label Feb 14, 2024
@CDR-API-Stream CDR-API-Stream moved this from Iteration Candidates to Full Backlog in Data Standards Maintenance Feb 14, 2024
@nils-work
Copy link
Member

Hi @anzbankau
Feedback to date suggests that a change to the Standards may not be a preferred solution to the stated issue.
Do you consider it should remain open for further consultation or could be closed pending any further comments by 31 May 2024?

@github-project-automation github-project-automation bot moved this from Full Backlog to Done in Data Standards Maintenance May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Consumer experience Issues related to Consumer experience Standards. Operational
Projects
Status: Done
Development

No branches or pull requests

6 participants