This repository houses the interactions, consultations and work management to support the maintenance of baselined components of the Consumer Data Right API Standards and Information Security profile.
Our understanding of CDR Rules (Schedule 3, clause 3.1), is that “required product data” includes “product specific data” which is information that identifies or describes the characteristics of the product and therefore includes data relating to the transaction limits for a product. There is also no defined field in GET Product Details to provide this information. Instead, it can either be provided as a constraint using the undefined max_limit fields or under features as a featureType – OTHER.
However, it is also our understanding that the max/ min_limit fields were originally designed to be applicable for credit products. Similarly, in our view, featureType – OTHER should not be used as a catch all for “required product data” that must be disclosed pursuant to the Rules but not defined under the Standards. Overall, providing additional enum types for constraintType would help provide this clarity. It would allow data holders to provide this information in a standardised manner and allow ADRs to more easily source and interpret this information.
Description
Our understanding of CDR Rules (Schedule 3, clause 3.1), is that “required product data” includes “product specific data” which is information that identifies or describes the characteristics of the product and therefore includes data relating to the transaction limits for a product. There is also no defined field in GET Product Details to provide this information. Instead, it can either be provided as a constraint using the undefined max_limit fields or under features as a featureType – OTHER.
However, it is also our understanding that the max/ min_limit fields were originally designed to be applicable for credit products. Similarly, in our view, featureType – OTHER should not be used as a catch all for “required product data” that must be disclosed pursuant to the Rules but not defined under the Standards. Overall, providing additional enum types for constraintType would help provide this clarity. It would allow data holders to provide this information in a standardised manner and allow ADRs to more easily source and interpret this information.
Area Affected
Schemas – BankingProductConstraint
Change Proposed
Add the following enumerated values and definitions to the BankingProductConstraint schema: