Post-Disbursal Servicing | Credit Platform | Documentation

Post-disbursal servicing is part of the Aarthik Labs credit journey. Borrowers do not need to leave the platform experience after disbursal to ask for help, raise a grievance, foreclose a loan, make a pre-part payment, or clear a missed EMI.

For Hosted Experience integrations, these modules are available inside the Aarthik-managed borrower surface. Your app should provide a clear way for borrowers to return to the Hosted Experience or loan details surface after disbursal.

For Hybrid Experience integrations, the same modules run inside the hosted handoff experience. Your back-end may orchestrate journey creation and offer selection, but post-disbursal servicing is still handled in the Aarthik-hosted borrower surface.

What Is Included

Module	What it helps with	Availability
Issues & Grievances Management	Borrower issues, complaints, grievances, support tracking, and resolution lifecycle.	Personal Loan and Gold Loan, across online and offline journeys.
Collections & Repayment Actions	Borrower-initiated repayment actions after disbursal.	Personal Loan and Gold Loan online journeys, including single-redirection and multiple-redirection journeys. Availability is lender-dependent.

Why This Matters

Most credit journeys focus heavily on application, offer selection, KYC, e-mandate, e-sign, and disbursal. Borrowers still need help after that point. They may have questions about their loan, need to raise an issue, want to repay early, or need to clear an overdue installment.

Aarthik Labs keeps these post-disbursal actions inside the same journey layer so your product can offer a more complete credit experience without rebuilding each lender-specific servicing flow from scratch.

Servicing Flow

How Customers Should Think About It

Post-disbursal servicing should be treated as a first-class part of the credit journey, not a separate support fallback.

Your app should:

give borrowers a clear path back to their active loans
open the Hosted Experience when the borrower needs servicing actions
keep back-end API keys private
avoid rebuilding lender-specific support or repayment logic unless your integration scope explicitly requires it
route borrower support teams to the issue or journey context instead of asking borrowers to repeat details

Modules

Issues & Grievances Management explains how borrowers raise issues and how statuses such as PROCESSING, RESOLVED, and CLOSED should be understood.
Collections & Repayment Actions explains foreclosure, pre-part payment, and missed EMI payment flows.