An equity contribution is the part of a loan a borrower puts in upfront. If they need 100 and contribute 20, the lender finances 80. That is easy to explain in one sentence. It is less easy when a product screen, a loan offer, a repayment schedule and the amount sent to the borrower all have their own ideas about what “80” means.
The feature existed, but its journey was fragmented. Lenders needed to set rules for a product. Borrowers needed to see what they could contribute and what they would actually receive. Admins needed to review or adjust a loan without silently changing the deal. The backend needed to enforce the same rules when money was involved. A neat slider alone was not going to settle that argument.
I refactored the flow across the admin application, the lending service and the borrower experience so those steps described the same loan.
What the lender actually configured
I brought equity configuration into product creation and editing, where a lender can choose whether a product requires a contribution and set minimums, maximums, percentages and a default. The admin flow also needs to show when those settings are invalid, instead of letting a product look ready until a borrower applies.
The interesting part was carrying those rules into an offer. A product can change after an offer is made; the offer should not quietly change with it. I used the equity settings captured with the offer to validate the borrower’s choice and later loan edits. That gives everyone a stable answer to “what were the terms when this loan was offered?”
What the borrower would receive
On the borrower side, I rebuilt the equity step around the allowed range and a live breakdown: contribution amount, its percentage and the amount left for the lender to finance. Someone choosing a larger contribution can see the consequence before continuing. If their choice is outside the product rules, the flow explains the problem there, instead of letting a later API response deliver the surprise.
This also had to survive more than the happy path. An offer might already be saved; a product might have older settings; an admin might reopen a loan and edit its schedule. The flow resolves the applicable offer terms, carries the chosen amount forward and makes the relevant details visible in the admin loan views. One contribution, one meaning, however the loan was opened.
The backend had to use the same number
The backend is where the explanation has to become arithmetic. I made the selected contribution part of loan creation and approval validation, calculated the financed principal from the requested amount minus that contribution and recalculated percentage-based fees against the amount actually financed. Admin changes are checked against the offer’s rules and the permission to manage equity.
That closes the gap between a reassuring screen and a correct loan. A borrower can understand what they put in and what they receive. A lender can configure the product and trust that the same constraints reach approval. Engineers can follow one consistent set of terms through the entire journey, instead of chasing a mismatch after a repayment schedule has already been generated.
The number on the screen and the number in the loan should be friends. I would prefer they never have to meet in an incident report.