DocumentationHosted ExperiencePost-Disbursal Servicing

Collections & Repayment Actions

Collections & Repayment Actions help borrowers manage important repayment events after loan disbursal. These flows are available for Personal Loan and Gold Loan online journeys, including single-redirection and multiple-redirection journeys.

The exact actions available to a borrower are lender-dependent. If a lender does not support a particular action for a loan, the action should be treated as unavailable for that borrower.

Supported Actions

ActionBorrower needAvailability
ForeclosureThe borrower wants to close the loan early by paying the full payable amount.Lender-dependent.
Pre-Part PaymentThe borrower wants to make a partial repayment before final closure.Lender-dependent.
Missed EMI PaymentThe borrower needs to clear an overdue or missed installment.Lender-dependent and based on loan repayment state.

Collections Flow

Foreclosure

Foreclosure lets a borrower close an active loan early. When supported by the lender, the borrower can view the payable closure amount and complete the payment from the hosted servicing flow.

Customer-facing notes:

  • Foreclosure should be shown only when the lender supports it for the loan.
  • Charges or fees may vary by lender and product terms.
  • The borrower should be guided back to the hosted loan details surface after payment.

Pre-Part Payment

Pre-Part Payment lets a borrower make a partial repayment against an active loan. When supported by the lender, the borrower enters or confirms the repayment amount and completes the payment inside the hosted servicing flow.

Customer-facing notes:

  • Pre-part payment requires a valid amount.
  • The lender may define minimum amounts, timing rules, or eligibility conditions.
  • Your app should avoid calculating the final repayment effect independently unless your integration has a separate lender-confirmed contract for that.

Missed EMI Payments

Missed EMI Payments help borrowers clear overdue installments. When the platform identifies an unpaid overdue installment and the lender supports collection for it, the borrower can complete the payment from the hosted servicing flow.

Customer-facing notes:

  • Missed EMI actions depend on the lender and the current repayment state.
  • The borrower should see a clear path to pay the overdue amount.
  • Support teams should be able to identify whether the missed EMI action is pending, paid, or unavailable.

Customer Responsibilities

Your app does not need to rebuild these lender-specific repayment flows when using the Hosted Experience.

Your app should:

  • provide a clear route back to the borrower’s active loans
  • open the Hosted Experience when the borrower needs servicing actions
  • support browser or mobile surfaces required by lender payment pages
  • avoid showing collection actions that are not available for the borrower
  • use platform state as the source of truth for payment progress and servicing status

Testing Checklist

Before launch, test these scenarios with supported lenders:

  • borrower can find active loan details after disbursal
  • foreclosure is visible only when available
  • pre-part payment requires a valid amount
  • missed EMI payment appears only when an eligible installment is overdue
  • payment links open correctly on web and mobile
  • borrower can return after completing or abandoning payment
  • support teams can identify the latest action and payment status