Where a Data Holder offers a single product with only one lending rate, or with an array of rates that do not differ based on LVR, multiple MAX_LVR constraints can be provided to indicate that there are other non- rate-based LVR constraints on applications for the product.
By following this convention, the ADR/client will be made aware of the need to interpret or present all applicable constraint details to ensure they are sufficiently considered depending on the consumer's requirements.
An example of this convention may be:
"constraints": [{ "constraintType": "MAX_LVR", "additionalValue": "0.7", "additionalInfo": "Applies to loans for commercial property.", "additionalInfoUri": "https://dh.example.com/product-x#commercial-loan-conditions" }, { "constraintType": "MAX_LVR", "additionalValue": "0.8", "additionalInfo": "Applies to loans for residential property.", "additionalInfoUri": "https://dh.example.com/product-x#residential-loan-conditions" } ]
Note: where the available rates for a product are differentiated by LVR, any applicable minimum or maximum LVR associated with the respective rate should be defined using the PERCENT unitOfMeasure rate tier detail.
Participants are encouraged to provide feedback on this guidance by raising a Zendesk ticket.
Comments
0 comments
Please sign in to leave a comment.