CDR Reporting

The Consumer Data Right Rules (CDR Rules), under rule 9.4 explains the Reporting requirements for Data Holders and Accredited Data Recipients (ADRs).

WSO2 Open Banking for Australia provides the capability for Data Holders to fulfil this Reporting requirement. The Data Holders are expected to submit bi-annual report forms to both the Australian Competition and Consumer Commission (ACCC) and the Office of the Australian Information Commissioner (OAIC).

This documentation explains the following:

Reporting Items

The reports that Data Holders submit contain the following reporting items. These are relevant to product data sharing obligations:

Section 1:  Details of the Data Holder

Section 2: Summary of CDR complaint data 

2.1 Total number of CDR consumer complaints received
2.2 Number of CDR consumer complaints received for each complaint type, in accordance with your complaints handling process
2.3 Total number of CDR consumer complaints resolved
2.3.1 Number of CDR consumer complaints resolved that were reported in this reporting period
2.3.2 Number of CDR consumer complaints resolved that were reported in previous reporting periods
2.4 Average number of days taken to resolve CDR consumer complaints through internal dispute resolution
2.5 Number of CDR consumer complaints referred to a recognised external dispute resolution scheme
2.6 Number of CDR consumer complaints resolved by external dispute resolution
2.7 Total number of complaints made to you by other CDR participants in relation to compliance

Section 3: Number of data requests

3.1. Number of product data requests received
3.2. Number of consumer data requests received from eligible CDR consumers
3.3. Number of consumer data requests received from accredited persons on behalf of eligible CDR consumers

Section 4: Refusals to disclose

4.1. Number of times you have refused to disclose CDR data
4.2. Set out each of the CDR Rules or data standards relied upon to refuse disclosure of that data
4.3. For each CDR Rule or data standard identified in response to item 4.2, state the number of times you relied on that particular CDR rule or data standard to refuse to disclose CDR data

Reporting Database

WSO2 Open Banking uses a Siddhi app to publish the data to the databases. This app is known as GetInvocationDataApp.siddhi and the following section explains how to deploy this app.

Once this app successfully publishes the data, they are stored in the database referred by the OB_REPORTING_DB datasource. Data Holders can manipulate these stored data when preparing reports.

Data Reporting API

WSO2 Open Banking introduces an API to obtain API invocation details such as the errors occurred during APIs and the error types. 

Using the Data Reporting API, the Data Holders can retrieve statistics on API invocation data for a requested period which are required for regulatory reporting. 

1. Deploying the GetInvocationDataApp Siddhi App, which is required to publish data related to data reporting:
   1. Copy the <WSO2_OB_BI_HOME>/resources/finance/cds-siddhi-files/GetInvocationDataApp.siddhi file to the <WSO2_OB_BI_HOME>/deployment/siddhi-files directory.
   2. Restart the WSO2 Open Banking Business Intelligence, Identity and Access Management and API Management servers in the mentioned order, for the changes to take place.
2. Invoking the API:
   
   • Set the date range by changing the values in the fromDate and toDate parameters in the request. Given below is a sample request and response.

Data Reporting - Phase 2

As a part of CDR Reporting - Phase 2, WSO2 Open Banking captures CDR Rule violations that happen during API invocations and combines them into the response of the above Data Reporting API.

Given below is a sample request to retrieve bi-annual reporting data :

You need to capture the data required for the following rules from the banking backend. The scenarios are as follows:

• UNAVAILABLE_BANKING_ACCOUNT:  The consent is valid for the given account but certain data sharing is restricted due to other business validations in the bank backend.

• INVALID_RESOURCE: Trying to access an invalid resource excluding an account. For example, TransactionID. 

  • To capture data for the above scenarios, banks should reply with the correct error code otherwise those numbers will not be captured in the response.
  • For the rest of the rules, the WSO2 Open Banking solution captures data.