Skip to content
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

Closed
BH-UDA opened this issue Feb 28, 2020 · 6 comments
Closed

Lending Products and LVR tiering clarification #143

BH-UDA opened this issue Feb 28, 2020 · 6 comments

Comments

@BH-UDA
Copy link

BH-UDA commented Feb 28, 2020

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:

  1. Standard Home Loan with LVR 60% and below
  2. Standard Home Loan with LVR 60-80%
  3. Standard Home Loan with LVR 80-90%
  4. Standard Home Loan with LVR over 90%
    Our question is - will this representation be an acceptable format and conform to CDR rules?
@BH-UDA BH-UDA added the query label Feb 28, 2020
@CDR-API-Stream
Copy link
Collaborator

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:

  • a common convention for products emerges, or
  • problems begins to arise for consumers of the data with too much complexity,

then the DSB may become more specific and standardise these conventions.

@CDR-API-Stream
Copy link
Collaborator

Hi @BH-UDA if there are no more questions related to this query it will be closed in 7 days.

@markt-amp
Copy link

markt-amp commented Apr 8, 2020

@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)

@CDR-API-Stream
Copy link
Collaborator

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?

@markt-amp
Copy link

markt-amp commented Apr 21, 2020

Hi @CDR-API-Stream -
With respect to this clarification it's clear to me.

I've raised #184 for further improvement of the API structure and data within the schema

Best
-Mark

@CDR-API-Stream
Copy link
Collaborator

This issue has been answered and it is being closed accordingly.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants