Energy 'Get Agreed Payment Schedule' - BSB and Account Number Tokenisation/non-Tokenisation

[jsaxon-red]

Description

Under the Energy 'Get Agreed Payment Schedule' API where a consumer has a Direct Debit configured the Data Holder is required to provide the BSB and Account Number, unless the Data Holder stores this information in a Tokenised form, in which case these details are not provided and a 'isTokenised' boolean flag is set to 'True' instead.

This presents an undesired technical implementation quirk where a Data Holder stores these details in a secured but untokenised way, the Data Holder needs to choose between a material relaxing of the secured storage of the details to make these available or an implementation of Tokenisation.
If the latter option is chosen then once the details are Tokenised, they are no longer required to be provided.

Area Affected

/energy/accounts/{accountId}/payment-schedule

Change Proposed

Whilst there may be other viable options, two readily identified options suggested are:

1. Updating of the description/requirement for the 'isTokenised' flag to include cases where the details are Tokenised or otherwise held in an secured store.
2. Removal of the requirement to provide BSB/Account Number

DSB Proposed Solution

The DSB proposed solution for this issue is in #591 (comment)

[CDR-API-Stream]

The DSB recommends option 1 and updating the description of the isTokenised flag as follows:

• "Flag indicating that the account details are tokenised, or held in a closed system, and is not accessible through any other channels"

This would help clarify that the isTokenised can be used in scenarios where the account details (bsb and account number) cannot be shared due to being held in a closed system and is not shared via any other channels.

Feedback on the proposal is welcome.

[biza-io]

Biza.io supports the proposal to adopt Option 1 of modifying the description.

[CDR-API-Stream]

This issue has been staged and can be viewed here - ConsumerDataStandardsAustralia/standards-staging@b3e10da

[nils-work]

Standards version 1.25.0 has now been published, incorporating this change.