Updated @February 22, 2024
These guidelines provide examples for how to implement the authorisation flow for common scenarios.
On this page
Overview
This example of the authorisation process covers account selection and confirmation for individual accounts.
Wireframes and guidelines
Default example
The following wireframes show a basic example of the authorisation process. Variations can be found in the below sections.
Note: Some interactions and screens have been omitted for simplicity.
Unavailable accounts
An account may be considered unavailable for various reasons. Unavailable accounts may include eligible accounts that cannot be shared, such as where
- a data holder deems it necessary to prevent financial harm or abuse, or
- account users do not have sharing rights.
Unavailable accounts may also include ineligible accounts which data holders may show to mitigate confusion, such as where a consumer expects to see their accounts but cannot select them because they are ineligible for CDR.
The following wireframes show examples of the account selection step when a consumer has accounts unavailable for data sharing.
All accounts can be shown
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Standard | MUST | Data holders MUST allow the consumer to select which of their accounts to share data from if the data request includes account-specific data and if there are multiple accounts available. The Data holder MAY omit this step if none of the data being requested is specific to an account (e.g. Saved Payees). | 3AU.03.01 | ||
02 | CX Standard | MUST | If certain accounts are unavailable to share, data holders SHOULD show these unavailable accounts in the account-selection step.
Data holders SHOULD communicate why these accounts cannot be selected, and this SHOULD be communicated as in-line help or as a modal to reduce on-screen content.
Data holders MAY provide instructions on how to make these accounts available to share, and this SHOULD be communicated as in-line help or as a modal to reduce on-screen content.
Note: Unavailable accounts are to be interpreted in accordance with the rules on eligible consumers and required consumer data. | 3AU.03.02 | ||
03 | CX Guideline | MAY | Data holders may list specific accounts that are unavailable to share, or a generic explanation for unspecified accounts.
Unavailable accounts may include eligible accounts that cannot be shared, such as where a data holder deems it necessary to prevent financial harm or abuse.
Unavailable accounts may also include ineligible accounts which data holders may show to mitigate confusion, such as where a consumer expects to see their accounts but cannot select them because they are ineligible for CDR sharing. | 3AU.03.03 | ||
04 | CX Standard | MAY | If unavailable accounts cannot be shown in the account selection step, data holders MAY display a generic explanation and instructions. | 3AU.03.04 | ||
05 | CX Standard | MAY | If a successfully authenticated user cannot proceed to establish an authorisation in accordance with the rules on eligible consumers and required consumer data, data holders MAY provide the option of concluding the authorisation process. | 3AU.03.05 | ||
06 | CX Standard | MAY | If a user does not have sharing rights for a particular account or set of accounts, data holders MAY invite the user to request sharing rights from the authorisation flow. The presentation of this mechanism MUST NOT introduce unwarranted friction as defined in rule 4.24 on restrictions. | 3AU.03.06 | ||
07 | CX Guideline | MAY | If an account holder has not given a secondary user instruction for an account with a secondary user, that account will appear as unavailable to the secondary user. | 3AU.03.07 | ||
08 | CX Guideline | MAY | The request function is optional but permitted in the standards. This functionality could be presented in the authorisation flow or elsewhere at the DH's discretion. The purpose of this concept would be to allow non-nominated persons and/or secondary users without sharing rights to send a request to the account owner(s) or administrators of the account. This request could alert the account owner(s) or administrators of the steps they need to take to provide those users with sharing rights. This could then lead the account owner or administrator to their respective services for secondary user instructions and nominated representatives. | 3AU.03.08 |
Unavailable accounts cannot be shown
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Standard | MUST | Data holders MUST allow the consumer to select which of their accounts to share data from if the data request includes account-specific data and if there are multiple accounts available. The Data holder MAY omit this step if none of the data being requested is specific to an account (e.g. Saved Payees). | 3AU.03a.01 | ||
02 | CX Standard | MAY | If unavailable accounts cannot be shown in the account selection step, data holders MAY display a generic explanation and instructions. | 3AU.03a.02 | ||
03 | CX Guideline | MAY | Data holders may list specific accounts that are unavailable to share, or a generic explanation for unspecified accounts.
Unavailable accounts may include eligible accounts that cannot be shared, such as where a data holder deems it necessary to prevent financial harm or abuse.
Unavailable accounts may also include ineligible accounts which data holders may show to mitigate confusion, such as where a consumer expects to see their accounts but cannot select them because they are ineligible for CDR sharing. | 3AU.03a.03 |
No accounts can be shown
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Standard | MAY | If unavailable accounts cannot be shown in the account selection step, data holders MAY display a generic explanation and instructions. | 3AU.03b.01 | ||
02 | CX Standard | MAY | If a successfully authenticated user cannot proceed to establish an authorisation in accordance with the rules on eligible consumers and required consumer data, data holders MAY provide the option of concluding the authorisation process. | 3AU.03b.02 | ||
03 | CX Standard | MAY | If a user does not have sharing rights for a particular account or set of accounts, data holders MAY invite the user to request sharing rights from the authorisation flow. The presentation of this mechanism MUST NOT introduce unwarranted friction as defined in rule 4.24 on restrictions. | 3AU.03b.03 | ||
04 | CX Guideline | MAY | Some scenarios may result in a user without sharing rights not seeing any accounts in the account selection step. Data holders may provide a generic explanation and instructions in place of the account selection step and/or unavailable account pattern. | 3AU.03b.04 | ||
05 | CX Guideline | MAY | Data holders should provide additional information to help users without sharing rights understand how they might gain sharing rights. This may, for example, state that the account owner has to grant them sharing rights before data sharing can occur. Similarly, data holders may include instructions for how to request sharing rights from the account owner(s) or administrator if that functionality is provided by the data holder. | 3AU.03b.05 | ||
06 | CX Guideline | MAY | If no accounts can be shown, data holders should provide a message to consumers confirming that data will not be shared during this process. | 3AU.03b.06 | ||
07 | CX Guideline | MAY | Some scenarios may result in a user without sharing rights not seeing any accounts in the account selection step. A data holder may choose to provide optional functionality to allow a user without sharing rights to send a request to the account owner(s) or administrators from the authorisation flow. | 3AU.03b.07 | ||
08 | CX Guideline | MAY | The request function is optional but permitted in the standards. This functionality could be presented in the authorisation flow or elsewhere at the DH's discretion. The purpose of this concept would be to allow non-nominated persons and/or secondary users without sharing rights to send a request to the account owner(s) or administrators of the account. This request could alert the account owner(s) or administrators of the steps they need to take to provide those users with sharing rights. This could then lead the account owner or administrator to their respective services for secondary user instructions and nominated representatives. | 3AU.03b.08 | ||
09 | CX Guideline | MAY | If a data holder provides the optional request functionality and a user acts upon it, the data holder should provide a message to confirm that the request has been sent. This message should be clearly visible and shown as soon as the action has taken place. | 3AU.03b.09 |
Data related to one or no accounts
The following wireframes show an example of authorisation when the consumer only has one account and an example of when data does not relate to any accounts (e.g. saved payees).
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Standard | MUST | Data holders MUST allow the consumer to select which of their accounts to share data from if the data request includes account-specific data and if there are multiple accounts available. The Data holder MAY omit this step if none of the data being requested is specific to an account (e.g. Saved Payees). | 3AU.04.01 | ||
02 | CX Standard | MUST | Data holders MUST show which accounts the data is being shared from prior to confirming authorisation if the data request includes account-specific data. The data holder MAY omit this information if none of the data being requested is specific to an account (e.g. Saved Payees). | 3AU.04.02 | ||
03 | CX Guideline | MAY | Where a consumer only has one account, data holders can meet CX Standards for Authorisation by omitting the account selection step and only displaying the account on the final confirmation page. | 3AU.04.03 |
Profile selection
The following wireframes show an example of adding a profile selection step in authorisation.
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Standard | MAY | Data holders MAY add a 'profile selection' step or equivalent prior to the account selection step if a single identifier provides access to different customer accounts. For example, one customer ID may give access to business customer and individual customer accounts.
The 'profile selection' step SHOULD only be considered if it is an existing customer experience, and SHOULD be as minimal as possible to avoid introducing unwarranted friction (having regard to CDR Rule 4.24). | 3AU.05.01 |
Duration
The following wireframes show examples where authorisation is being sought for disclosure on a single occasion and for ongoing collection.
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CDR Rule | MUST | (1) When asking a CDR consumer to authorise the disclosure of CDR data, or amend a current authorisation, a data holder must give the CDR consumer the following information about the authorisation or amendment:
(e) if authorisation is being sought for disclosure over a period of time―what that period is; | CDR Rule 4.23(1)(e) | 3AU.06.01 | |
02 | CDR Rule | MUST | (1) When asking a CDR consumer to authorise the disclosure of CDR data, or amend a current authorisation, a data holder must give the CDR consumer the following information about the authorisation or amendment:
(d) whether the authorisation is being sought for:
(i) disclosure of CDR data on a single occasion; or
(ii) disclosure of CDR data over a period of time of not more than 12 months;
Note: While certain consents by a CDR business consumer can have a period of 7 years, a corresponding authorisation cannot be for more than 12 months before renewal under subparagraph (1)(d)(ii). | CDR Rule 4.23(1)(d) | 3AU.06.02 | |
03 | CX Guideline | MAY | If the duration of an authorisation request is absent or 0, data holders are to assume that the ADR is collecting the data on a 'single occasion' as per CDR Rule 4.23(1)(d).
Data holders may consider communicating the sharing period as a single disclosure instance, but the phrasing is at the discretion of the data holder. | 3AU.06.03 | ||
04 | CX Guideline | MAY | If the duration of an authorisation request is greater than 0 but less than 24 hours, data holders are to assume that the ADR is collecting the data on a 'single occasion' as per CDR Rule 4.23(1)(d).
Data holders may consider communicating the sharing period as a single disclosure instance occurring within a specific timeframe, but the phrasing is at the discretion of the data holder. | 3AU.06.04 |
Layout variation
The CX Guidelines demonstrate extensive requirements for completeness. CX research suggests that breaking content into several steps facilitates comprehension and usability.
The following wireframes suggest alternative patterns for the authorisation.
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Guideline | MAY | Data holders should align the authorisation flow to their design systems and/or experience languages to facilitate familiar, intuitive, and trustworthy authorisations | 3AU.07.01 |
Note: Some interactions and screens have been omitted for simplicity.
Cancellation
The following wireframes show an example of cancelling authorisation.
Wireframe ref | Type | Requirement level | Statement | Reference | Checklist ref | Focus area |
---|---|---|---|---|---|---|
01 | CX Guideline | MAY | Data holders should outline the consequences of choosing to cancel throughout the authentication and authorisation process. | 3AU.08.01 | ||
02 | CX Guideline | MAY | If a consumer cancels at some point in the Consent Flow, CDR participants should confirm that data was not or will not be shared.
The CDR receipt should be given in writing. | CX of Error Handling Workshop | 3AU.08.02 |
Download open source asset
Open sources design assets are created in Figma for the purposes of assisting implementation. This Figma file contain annotated wireframes and working prototypes for Authorisation to disclose, including:
- Default example
- Unavailable accounts
- All accounts can be shown
- Unavailable accounts cannot be shown
- No accounts can be shown
- Data related to one or no accounts
- Profile selection
- Duration
- Layout variation
- Cancellation
Item | File | Date released | Version introduced |
---|---|---|---|
February 22, 2024 | 1.29.0 |
For past versions, refer to
Open sources design assets are provided in the form of version-controlled Figma files. These assets contain the annotated wireframe and working prototype published on this page, and have been reviewed for accessibility compliance. Assets are partially conformant to Web Content Accessibility Guidelines (WCAG) 2.1 level AA. These assets do not tend to accessible code and instead focus on visual presentation and readability.
The assets use the GOLD Design System; component rationale, accessibility support, and code documentation is available in the GOLD Design System website.
For more details, see
References
These CX Guidelines were informed by consultations and research conducted in 2019 to 2021, including the following:
- Consultations
- DSB 2020, Decision Proposal 127 - CX Guidelines for Enhanced Error Handling and CX Workshop: Error handling
- DSB 2021, Noting Paper 157 - CX Standards Arising from v2 Rules
- DSB 2021, Decision Proposal 160 - CX Standards | Non-individuals | Partnerships | Secondary users (see concepts 1.1 Accounts not shown | Generic message, 1.2 Sharing rights request, 1.3 Accounts shown | Generic message - overlay)
- CX research
- Tobias 2019, Phase 1 CX report
- GippsTech 2019, Phase 2, Stream 1 report
- Greater than X 2019, Phase 2, Stream 2 report
- Tobias 2019, Phase 2, Stream 3 report
- Other
- DSB, Technical Standards: Request Object
- Nielsen Norman Group 2019, 10 Usability Heuristics for User Interface Design (Error prevention)
- Nielsen Norman Group 2019, 10 Usability Heuristics for User Interface Design (Visibility of system status)
Quick links to CX Guidelines: