ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 12th of May 2022
When: Weekly every Thursday at 3pm-4.30pm AEST
Location: WebEx, quick dial +61-2-9338-2221,,1650705270##
Meeting Details:
Desktop or Mobile Devices
https://treasuryau.webex.com/treasuryau/j.php?MTID=m9614a7c6166155d3d950a8999e437f9f
Once connected to your meeting remember to start your audio and video
Please mute when you are not speaking.
Video Conferencing (VC) Rooms
Use the remote control or touch panel and dial the number indicated below:
External VC Room: 1650705270@webex.com
Phones - AUDIO ONLY
- Primary Australia: +61-2-9338-2221
- Quick Dial: +61-2-9338-2221,,1650705270##
- Other Global Numbers: https://treasuryau.webex.com/cmp3300/webcomponents/widget/globalcallin/globalcallin.do?MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&serviceType=MC&serviceType=MC&serviceType=MC&siteurl=treasuryau&siteurl=treasuryau&siteurl=treasuryau&apiname=globalcallin.php&apiname=globalcallin.php&apiname=globalcallin.php&rnd=6124483603&rnd=6124483603&rnd=6124483603&tollFree=0&tollFree=0&tollFree=0&ED=1403111402&ED=1403111402&ED=1403111402&needFilter=false&needFilter=false&needFilter=false&actappname=cmp3300&actappname=cmp3300&actname=/webcomponents/widget/globalcallin/gcnredirector.do&actname=/webcomponents/widget/globalcallin/gcnredirector.do&renewticket=0
- Meeting Number/Access Code: 165 070 5270
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- Any other business
- 5 min will be allowed for participants to join the call.
The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may contact@consumerdatastandards.gov.au should they have any further questions or wish to have any material redacted from the record.
We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.16.1 Published | Link to change log here |
| Standards | Next Update will be Version 1.17.0 | Will incorporate changes completed from the 10th Maintenance Iteration Decision Proposal 237 will contain the decision taken to to the Data Standards Chair |
| Standards |
Decision Proposal 237 - Maintenance Iteration 10 This decision was approved by the Data Standards Chair on 12 May 2022. The decision record is attached to the GitHub Issue |
Decision Proposal 237 |
| Maintenance | DSB Maintenance Iteration 11: Agenda & Meeting Notes on 11th of May 2022 | Link to the agenda and minutes |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | 6th of April 2022 | View in browser here |
| DSB Newsletter | 6th of May 2022 | View in browser here |
| Consultation | Normative Standards Review (2021) | No Close Date Link to consultation |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Consultation | Decision Proposal 240 - ADR Metrics | Feedback closes 27th of May 2022 Link to consultation |
| Consultation | Decision Proposal 245 - Enhancing Data Recipient Accreditation Negotiation | Feedback closes 27th of May 2022 Link to consultation |
Provides a weekly update on the activities of each of the CDR streams and their stream of work
| Organisation | Stream | Member |
|---|---|---|
| ACCC | CDR Register | Emma Harvey |
| ACCC | CTS | Preeti |
| DSB | CX Standards | Michael Palmyre |
| DSB | Technical Standards - Register | Ivan Hosgood |
| DSB | Technical Standards - Banking | Mark Verstege |
| DSB | Technical Standards - Engineering | James Bligh |
| ACCC | Participant Tooling | Andrew Grady |
None.
Questions will be received by the community via WebEx chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
We are using Sli.do for Question and Answer. Join our Q&A live here: https://www.sli.do/ Code: #747194
The following table will be updated after the meeting.
| Ticket # | Question | Answer |
|---|---|---|
| 1498 | For Payee information, CDS has introduced a new type called ‘DIGITAL_WALLET’ but I am unable to understand the business scenario for which it’s introduced? I normally add my cards to digital wallet so how does it related to payee information. | This was added at the request of PayPal and represents a wallet that holds value (as opposed to wallets that only hold tokenised cards). This could be a PayPal style wallet but could also be a BNPL account for instance. In these situations top ups are possible so the wallet becomes a payee. If you do not support this scenario then you would never need to return the DIGITAL_WALLET type so no change is needed. |
| 1507 | For a large customer (corporate), a common mode of payment is through File Upload, which can be manual (user present and manually uploading the file) or host-to-host (automated bulk payment requests, system to system). In some cases individual instructions in the Files may be visible to a user, but in most cases, the requests (for both immediate and future dated payment) after validation are sent straight to the Back Office. My question is should all these future payment instructions (coming through File) be sent in response to get/scheduled_Payment ? Keeping in mind that these can run into several thousands for a large corporate account, these may not be visible to the user giving the consent etc. |
No. These are not scheduled payments under the CDR standards as they are not technically recurring. Although files may be sent on a regular schedule the content of payment files are usually variable at the level of specific payments. |
| 1511 | When a token revocation is done, should the refresh token be revoked as well? If so, what is the error message to be returned for a token call using the refresh grant for a revoked access token? | I assume you are talking about a revocation arising from a call to the OIDC token revocation endpoint. In this case, the client specifies the token to be revoked and if a refresh token is specified then it should be revoked. Does this answer the question or are you talking about a different scenario? |
View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.