-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lending Products and LVR tiering clarification #143
Comments
Hi @BH-UDA the approach you suggest is allowable under the standards. At the moment, some interpretation by data holders at the moment is expected as long as the specification is met. If in future:
then the DSB may become more specific and standardise these conventions. |
Hi @BH-UDA if there are no more questions related to this query it will be closed in 7 days. |
@BH-UDA & @CDR-API-Stream I believe the implementation of BankingProductLendingRate is somewhat inefficient and the presence or absence of BankingProductRateTier makes the API open to ambiguity. This is further confused if you apply tiers to owner occupied vs investor & have different repayment types (P&I vs IO) - however it looks like #48 will resolve that complexity. Further the removal of subTier would be helpful too (issue #103) |
Hi @markt-amp, noting that subTier has been removed as part of v1.3.0 of the standards. Similarly #48 was addressed in v1.3.0. Is there anything specifically that remains ambiguous in BankingProductLendingRate? |
Hi @CDR-API-Stream - I've raised #184 for further improvement of the API structure and data within the schema Best |
This issue has been answered and it is being closed accordingly. |
Request For Clarification
As a banking software provider we are seeking clarification on the compliance of our proposed approach for provided Product data for Lending Products with different rates based on LVR ranges.
Our system currently does not support a LVR rate tiering structure but caters for this by allowing LVR ranges to be described within the "sub" product level descriptions.
We have noted instances where the major banks provide LVR tiering rates within a single Open Banking product however due to the our current data structure this is not an option readily available and we are proposing to provide separate products for each LVR range.
As an example the following would be presented as four individual products:
Our question is - will this representation be an acceptable format and conform to CDR rules?
The text was updated successfully, but these errors were encountered: