Loan lifecycle & loan relationships
LID lifecycle
A single user can have LAMF and LAS in many shapes. Each unique loan application is identified by a lid. Based on the user's overall credit portfolio managed by Unity, these lids can either be independent or linked to each other.
Common scenarios
One LAMF loan application - one lid
- For a single lender, there can only be one
DISBURSEDloan at a time. - Topups can be applied on top of
DISBURSEDapplications.
One LAMF and one LAS loan application - two lids
- LAS and LAMF with different lenders - both lids independent (refer the one application flow above)
- If the user avails LAS and LAMF with the same lender -
- When both applications are in
PRE-SUBMITTEDstate - these are sibling lids - When one application gets
SUBMITTED, one remainsPRE-SUBMITTED- parent-child relationship is established between lids - When both lids are
SUBMITTED- the parent lid isCLOSED, the child becomesACTIVE. (Refer the previous section - there can only be oneDISBURSEDloan for a lender)
- When both applications are in
LAMF Topup over ACTIVE LAMF - 2 lids
- Parent-child relationship between lids.
- Topups are allowed for the same asset class and the same lender.
- When the topup lid is
SUBMITTED- the parent lid isCLOSED, the child becomesACTIVE. (Refer the previous section - there can only be oneDISBURSEDloan for a lender)
... and so on.
What's expected from the partner?
The Combined Credit Snapshot API response shows you which shape applies right now.
You never own LID transitions. All transitions happen server-side. Your can read the current state, if required.