Enhancing CDR Adoption: Streamlining Account Selection and Improving Data Transparency

[kambasiq]

Description

Currently, the CDR framework allows consumers to select specific accounts to share with Accredited Data Recipients (ADRs) as part of the flow managed by DHs. While this granular control is beneficial for consumer privacy, it poses a challenge for businesses transitioning from screen scraping to CDR. Screen scraping enables access to all accounts upon successful authentication, whereas CDR requires explicit selection, potentially leading to incomplete data sets. This discrepancy can hinder the adoption of CDR by businesses, particularly those relying on comprehensive financial data for services like affordability assessments. Additionally, inconsistencies in the user experience across different banks, such as the presence or absence of a "select all" option, can further complicate the process.

Intention and Value of Change

The proposed changes aim to streamline the account selection process for consumers and enhance data transparency for ADRs, ultimately promoting greater adoption of CDR.

• Improved User Experience: Clear and consistent user interface elements, including a prominent "select all" option, would simplify the account selection process, reducing friction and enhancing consumer experience.

• Data Completeness: Ensuring ADRs have a reliable indication of whether all available accounts have been shared would allow them to make informed decisions about data usage and service provision. This would mitigate risks associated with incomplete data sets and facilitate a smoother transition from screen scraping. ADRs can highlight the fact that the user hasn't selected all their accounts and send them back through the process.

• Increased CDR Adoption: By addressing the challenges associated with account selection and data transparency, these changes would encourage more businesses to embrace CDR, driving innovation and competition in the financial services sector.

• Alignment with priority use cases: As mentioned by Stephen Jones MP on the address for revamping CDR, Consumer Lending and Borrowing is a high value use case and without these changes it would be difficult to use CDR for this use case.

  Area Affected

• Consumer Experience (CX) Guidelines: Specific recommendations would be incorporated into the CX guidelines to standardize the account selection user interface across different banks.

• Data Standards: Modifications to the GetAccounts endpoint would include metadata fields indicating whether all available accounts have been shared.

Change Proposed

Add a new attribute called "availableRecords" to the "meta" object of GetAccounts end point. This then indicates the number of accounst that were available for sharing, the existing "totalRecords" will always be equal or less than the "availableRecords" and based on this the ADR would know if everything was shared or not.

[nils-work]

Hi @kambasiq

This seems to be related to #584 - Flag for account(s) not shared, which was wrapped into this future plan request: #130 - DSB Item - Ability for ADR to request all accounts or identify missing accounts.

#183 - Decision Proposal 183 - Purpose Based Consents may also be related.

[kambasiq]

@nils-work the topic seems to be similar but the suggested soluitions are different, also this one has a CX element of getting DHs to implement a select all bank account UI element for consumers. The purpose based consent piece is interesting but it seems like a bigger change and might take a long time to implement, has it progress from your side at all?

[CDR-CX-Stream]

Hi @kambasiq - this proposes CX guidelines changes and an endpoint change, but not a CX standards change.

The CX guidelines are optional to follow, however your proposal appears to include a requirement for DHs to implement a 'select all' action for account selection. If that is correct it would be a new CX standard that would appear here.

Are you able to clarify if that is the intended proposal?

[kambasiq]

@CDR-CX-Stream, It proposes two changes: First one to the end point so the ADR knows the consumer didn't share all their accounts so they can intervine and make it clear to the user that they need all the accounts.

Second one is a UI change to DHs account selection screen, some banks already do this but some don't. Would be great to have a consistent exprience where a consumer can easily indicate they want to share all their accounts and be able to select all their accounts in that screen with a single click/tap.

[CDR-CX-Stream]

Thanks @kambasiq - I take that to mean it is a request for CX guidelines to recommend select all functionality, which DHs can implement voluntarily, and not a proposal for CX standards to require that DHs implement select all functionality. We can progress the CX guideline portion quite easily. Thanks for the clarification.