CX Guidelines

Read first CX Checklist attributes ◦ Area refers to the stage in the consumer journey, such as Pre-consent, Consent, Authenticate, Authorise, or Consent Management. ◦ Focus area refers to a specific theme in each stage (e.g. 01. User Identifier). ◦ Checklist ref contains a unique reference number for the item. ▪ The first values refer to the Area (e.g. 0DL.xx.xx for data language; ***2AU.*xx.xx for authentication). ▪ The second set values refer to the Focus area (e.g. xxx.01.xx). ▪ The last values refer to the annotation number used on the wireframe, where available (e.g. xxx.xx.02; wireframes are linked to in the Example column). ◦ Type refers to the source of the statement: Rules, Standards and Guidelines. ◦ Participant refers to the relevant CDR Participant for the item. ◦ Requirement level refers to the level of obligation. For the data standards, the key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are to be interpreted as described in RFC2119. CX Guidelines provide optional examples and recommendations; as such, a MAY is used to denote a CX Guideline for the purposes of this checklist regardless of the language used in the guideline statement. ◦ Statement refers to the relevant requirement or recommendation as articulated in the rules, standards, or guidelines. ◦ References points to the requirement itself, or its location; typically a rule, standard, or research. ◦ Example links to the relevant artefact, such as the CX Guideline page, which includes wireframes of example implementations, or a table in the case of data language standards. ◦ Version introduced refers to the version of the data standards that was current when the item was introduced to the CX Guidelines, starting from version 1.4.0. Items noted as introduced in 1.4.0 or earlier are requirements that exist in v1.4.0 of the CX Guidelines (PDF). ◦ Date introduced refers to the specific date the item was introduced to the CX Checklist, using August 2020 as a starting point (when v1.4.0 was introduced). The date will typically be the date of the version release, but some new items may not constitute a standards change (e.g. a revised wireframe or rules change) and as such may not align with standards versioning. ◦ Date modified refers to when an existing CX Checklist entry was updated, which is not necessarily the date the corresponding requirement (Rule, Standard or Guideline) was changed. ◦ Status refers to whether the item is active or has been retired from the CX Guidelines. An 'active' item is applicable and current. A 'retired' item may be labelled as such because it no longer applies, has been merged with another item, or has been removed from the CX Guidelines. A 'retired' item may still be a requirement. These statuses are used in the live CX Checklist and CSV to highlight changes between versions of the CX Guidelines.

Wireframe ref	Type	Requirement level	Statement	Reference	Checklist ref	Focus area
01	CDR Rule	MUST	(1) For each joint account to which this Part applies, the data holder must provide a service to each joint account holder that allows the joint account holder to: (a) change the disclosure option that applies to the account in accordance with rule 4A.7; (b) propose a change in the disclosure option to the other joint account holders in accordance with rule 4A.8; and (c) respond to a proposal by another joint account holder to change the disclosure option. —————— (2) Such a service is a disclosure option management service.	CDR Rule 4A.6(1), (2)	5CM3.00.01	00. DOMS - general
02	CDR Rule	MUST	(3) The service must be provided online and, if there is a data holder’s consumer dashboard for a joint account holder, may be included in the dashboard. (4) The service may, but need not, also be provided other than online.	CDR Rule 4A.6(3), (4)	5CM3.00.02	00. DOMS - general
03	CDR Rule	MUST	(5) The service must give effect to a change in the disclosure option as soon as practicable.	CDR Rule 4A.6(5)	5CM3.00.03	00. DOMS - general
04	CDR Rule	MUST NOT	(6) The service must not do any of the following in relation to the processes that it provides for changing or proposing to change the disclosure option that applies to the joint account, or responding to such a proposal (the processes): (a) add any requirements to the processes beyond those specified in the data standards and these rules; (b) offer additional or alternative services as part of the processes; (c) include or refer to other documents, or provide any other information, so as to reduce comprehensibility; (d) offer any pre-selected options.	CDR Rule 4A.6(6)	5CM3.00.04	00. DOMS - general
05	CDR Rule	MUST	(7) The service must indicate to the joint account holder which disclosure option currently applies.	CDR Rule 4A.6(7)	5CM3.00.05	00. DOMS - general
06	CDR Rule	MUST	(8) The service must be in accordance with the data standards.	CDR Rule 4A.6(8)	5CM3.00.06	00. DOMS - general
07	CDR Rule	MUST	(1) Disclosure of joint account data may be authorised only as permitted by the disclosure option that applies to the joint account. This may be any of the following: (a) the pre-approval option, under which joint account data may be disclosed in response to a valid consumer data request on the authorisation of the requester without the approval of the relevant account holders; (c) the non-disclosure option, under which joint account data may not be disclosed even in response to a valid consumer data request. —————— (2) The data holder must provide for the pre-approval and non-disclosure options to be available for a joint account.	CDR Rule 4A.5(1)(a), (c) and (2)	5CM3.00.07	00. DOMS - general
08	CDR Rule	MUST	(1) A joint account holder may at any time choose that the non-disclosure option will apply to the joint account, using the disclosure option management service.	CDR Rule 4A.7(1)	5CM3.01.08	01. Change to non-disclosure option
09	CDR Rule	MUST	(3) If a joint account holder *(account holder A)* changes the disclosure option that applies to the account in accordance with this rule, the data holder must, as soon as practicable through its ordinary means of contacting the other joint account holders: (a) explain to each of them what the consumer data right is;	CDR Rule 4A.7(3)(a)	5CM3.01.09	01. Change to non-disclosure option
10	CDR Rule	MUST	(3) If a joint account holder (account holder A) changes the disclosure option that applies to the account in accordance with this rule, the data holder must, as soon as practicable through its ordinary means of contacting the other joint account holders: (b) inform them which disclosure option previously applied to the account; and (c) inform them that account holder A has changed the disclosure option, and of the disclosure option that now applies;	CDR Rule 4A.7(3)(b), (c)	5CM3.01.10	01. Change to non-disclosure option
11	CDR Rule	MUST	(3) If a joint account holder (account holder A) changes the disclosure option that applies to the account in accordance with this rule, the data holder must, as soon as practicable through its ordinary means of contacting the other joint account holders: (d) explain to them the mechanisms for changing the disclosure option again.	CDR Rule 4A.7(3)(d)	5CM3.01.11	01. Change to non-disclosure option
12	CDR Rule	MUST	ordinary means of contacting an account holder by a data holder means: (a) if the data holder has agreed with the account holder on a particular means of contacting the account holder for the purposes of the relevant provision—that means; and (b) otherwise—the default means by which the data holder contacts the account holder in relation to the account.	CDR Rule 1.7(1)	5CM3.01.12	01. Change to non-disclosure option
13	CX Standard	MUST	Data holders MUST alert a joint account holder where an action they are about to perform may result in the other joint account holder(s) being notified. This standard applies to the authorisation flow, consumer dashboards, and the disclosure option management service where notifications to the other joint account holder(s) may be triggered. The precise wording of this notification is at the discretion of the data holder.	Notification Standards, Notifications: Joint Account Alerts, Joint account notifications: Contextual alert	5CM3.01.13	01. Change to non-disclosure option
14	CX Standard	MUST	As part of the process of removing a joint account approval or changing to a more restrictive disclosure option, the data holder MUST advise the consumer: 1. that doing this may impact existing services, including arrangements initiated by the other account holder(s) 2. when removing an approval: a. that even though sharing for this service has now stopped, the other account holder(s) can still create new data sharing arrangements for the joint account b. how to change their disclosure option Note: The exact phrasing of the withdrawal message is at the discretion of the data holder. This standard does not affect data holders’ other notification obligations, including under rule 4A.7(3).	Withdrawal Standards, Withdrawal: Joint accounts	5CM3.01.14	01. Change to non-disclosure option
15	CX Standard	MAY	In relation to the joint account alert standards in this section, data holders MAY provide further information about any services or processes in place for supporting vulnerable consumers or reporting risks of physical, psychological, or financial harm or abuse to the data holder.	Notification Standards, Notifications: Joint Account Alerts, Joint account notifications: Further information	5CM3.01.15	01. Change to non-disclosure option
16	CX Guideline	MAY	Data holders may consider providing a centralised location for managing various CDR account permissions, which could, for example, allow a consumer to access and manage their joint accounts, secondary user instructions, and any appropriate partnership and non-individual permissions. The disclosure option management service (DOMS) could be accessible from this location and in relation to the consumer dashboard.		5CM3.01.16	01. Change to non-disclosure option
17	CX Guideline	MAY	Data holders should refer to disclosure options using plain language. A description of the disclosure option should be provided where possible. These artefacts use 'single consent' to represent pre-approval disclosure option, 'joint consent' to represent co-approval disclosure option, and 'stop all sharing from this account' or 'data sharing disabled' to represent a non-disclosure option.		5CM3.01.17	01. Change to non-disclosure option
18	CX Guideline	MAY	Community consultation suggested that identifying the specific account holder may raise privacy concerns in some instances. Data holders may identify the specific account holder in relation to the relevant rules requirement, but may also deem it necessary to omit these details in certain scenarios in accordance with CDR Rule 4A.15.		5CM3.01.18	01. Change to non-disclosure option
19	CX Guideline	MAY	Data holders may provide a mechanism for consumers to see a list of authorisations currently sharing data from that joint account.		5CM3.01.19	01. Change to non-disclosure option
20	CX Guideline	MAY	Data holders may offer an alternative notification schedule to apply at the account level and the customer level.		5CM3.01.20	01. Change to non-disclosure option
21	CX Guideline	MAY	To aid intuitive disclosure option management, data holders may choose to semantically distinguish pre-approval and co-approval changes from changing to a non-disclosure option.		5CM3.01.21	01. Change to non-disclosure option
22	CX Guideline	MAY	Existing approvals for specific authorisations are not automatically removed when a non-disclosure option is applied, but the joint account data cannot be shared due to the application of the non-disclosure option. If a joint account is changed from a non-disclosure to enable sharing again, joint account data sharing will recommence for any active authorisations that are associated with that joint account.		5CM3.01.22	01. Change to non-disclosure option
23	CX Guideline	MAY	Email is shown as an example notification only. Data holders must use ordinary means of contacting the relevant account holder(s) as outlined in CDR Rules 4A.7(3) and 1.7(1). A data holder may agree with the account holder on a “particular means of contacting the account holder for the purposes of the relevant provision”. Data holders are required to provide an online disclosure option management service, and may negotiate to provide joint account notifications online in line with this provision even where the consumer otherwise receives notifications via non-digital channels.		5CM3.01.23	01. Change to non-disclosure option
24	CX Guideline	MAY	Data holders can refer to accounts using recognised nicknames, icons, account numbers, and account type. They can also include information on other elements the account may refer to such as any related plans, services, properties, numbers, and products.		5CM3.01.24	01. Change to non-disclosure option