Logo
  • Overview
  • Consent
  • Authenticate
  • Authorise
  • Consent Management
  • Notifications

00. Fallback Authentication Framework

Checklist ref

2AU0.00.13

Area
2AU0. Fallback Authentication Framework
Wireframe ref

13

Type
CX Standard
Requirement level
MUST NOT
Participant
Data Holder
Statement

Data holders MUST NOT introduce unwarranted friction into the authentication process. In line with CDR Rule 4.24 on restrictions when asking CDR consumers to authorise disclosure of CDR data, unwarranted friction for authentication flows and methods is considered to include, but is not limited to: • The addition of any requirements beyond normal data holder practices for authenticating the consumer, including, but not limited to, One Time Password (OTP) verification code delivery. • Providing or requesting additional information beyond normal data holder practices for authenticating the consumer including, but not limited to, OTP verification code delivery. • Offering additional or alternative services. • Referencing or including other documents.

Reference

Authentication Standards, Common Authentication Standards, Authentication: Friction

Example

Authenticate: Fallback Authentication Framework

Version introduced
1.35.0
Date introduced

22 September 2025

Date modified

Status
Active
Data Standards Body | CX Guidelines

CX Guidelines

Overview

Consent

Authenticate

Authorise

Consent Management

Notifications

Keep in touch

DSB Newsletter

Website use

Accessibility Statement

Copyright

Privacy

Disclaimer

In the spirit of reconciliation, the Data Standards Body acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples.