🚀 Executive Overview
India's Mutual Fund AUM has crossed ₹81 lakh crore, powered by a rapidly expanding base of nearly 6 crore unique mutual fund investors. This represents India's largest untapped lending pool. The market for Loan Against Mutual Funds (LAMF) is reaching a structural breakthrough, maintaining a consistent 30% YoY growth.
A few years ago, the industry saw fewer than 100 loan originations a day. Today, we have surpassed 500 loans a day, on a clear path to exceed 1,000 daily loans by the end of the next financial year.
Finsire’s New-to-Bank (NTB) Loan Against Mutual Funds (LAMF) infrastructure enables distributors to capitalize on this momentum and unlock this liquidity. Instead of clients redeeming their investments during a cash crunch, they can borrow against their portfolio—keeping their compounding intact and your AUM secure.
🛠️ Distributor Product Suite & Features
Everything you need to go live fast, engineered specifically for your distribution channels and operational models.
🔗 Integration Capabilities: Redirection vs. Native
Choose the integration path that best fits your engineering bandwidth and go-to-market strategy:
- Originator Onboarding (Redirection Flows): Achieve an instant go-live. Designed specifically for B2B2C and MFD channels, utilizing out-of-the-box redirection links with zero front-end heavy lifting.
- Native Journeys (LSP Mode): Build your own fully branded, in-app borrower experience. Choose between direct Lender CMS-only APIs or our unified Finsire-Platform Lender APIs for a streamlined, multi-lender build.
💻 Multi-Tier Portal Access
Tailored access controls designed for Admins, RMs, Distributors, Platforms/Aggregators, and Sub-MFD Partners. Get a complete 360° lifecycle view - monitor every step by leads, eligibility, applications, disbursement, repayment, and portfolio analytics in one centralized dashboard.
⚡ Comprehensive Journey Control & Tracking
- Real-Time Customer Tracking: Utilize our comprehensive Webhooks and APIs to map the loan lifecycle directly into your internal systems. Track exact customer steps, journey drop-offs, and originator earnings in real time.
- Assisted Journeys: Empower your on-ground teams with RM-Assisted and Partner-Assisted flows to actively handhold high-value clients through the loan origination process.
🤝 Support & Conversion Assist
Get a dedicated SPOC across tech, product, and training. Leverage our Conversion Assist Pack to ensure your operational teams are never blocked and your LAMF portfolio adoption scales predictably.
🎯 Who is this for?
Built to fit your exact operational model and technical bandwidth.
| Partner Type | Tailored Product Suite Features |
|---|---|
| Dedicated LAMF & Individual MFDs | Utilize Distributor Portal Access and standard Redirection Flows for an instant go-live. Perfect for enabling RM & Partner Assisted Journeys to handhold retail investors effortlessly. |
| MFD Platforms & Referral Aggregators | Manage complex B2B2C hierarchies with Multi-Tier Portal Access (Platform & Sub-Partner levels). Drive volume across your network using our Originator Onboarding flows and Conversion Assist Pack. |
| Fintechs & General Superapps | Embed high-value credit seamlessly via Redirection flows or Native Journeys (LSP Mode). Synchronize data using Real-Time Webhooks for loan lifecycle and earnings tracking, while managing operations via comprehensive Admin Portal access. |
📊 Choosing Your Integration Strategy
Launch in days, not months. Whether you have a full technical team or
zero engineering bandwidth, our infrastructure is designed to get you
live in just 21 days:
Week 1: Commercial Agreement & UAT Environment
Setup
Week 2: Production API Access & Integration Build
Week 3: End-to-End Testing & Go-Live
To ensure the best fit for your operational model, choose between our two core redirection integration paths:
| Feature | Direct Model (V1) | Referral/Network Model (V2) |
|---|---|---|
| Business Context | Ideal for direct distributor-to-customer (B2C) relationships. | Built specifically for platforms and aggregators managing sub-partner networks (B2B2C). |
| Implementation & User Experience | Lightweight registration. The customer authenticates and selects their assets directly via the provided Finsire link. |
Rich data enrichment. Allows you to pass a
partner_code, pre-fill
mf_details (portfolios), and inject
bank_details to minimize user friction.
|
| Prerequisites | Standard API Authentication. | Requires the Partner Onboarding API to generate sub-partner attribution codes. |
🔐 Authentication
Finsire APIs utilize Basic Authentication via Base64 encoded credentials in the Authorization header. This single authentication method applies to both Direct (V1) and Referral (MFD/V2) integrations.
Header Format
Combine your Client ID and Client Secret with a colon, then Base64 encode the resulting string.
Authorization: Basic <Base64(client_id:client_secret)>
1. Credentials: Client ID: "YOUR_CLIENT_ID" Client Secret: "YOUR_CLIENT_SECRET" 2. Combined String: "YOUR_CLIENT_ID:YOUR_CLIENT_SECRET" 3. Base64 Encoded Result: "WU9VUl9DTElFTlRfSUQ6WU9VUl9DTElFTlRfU0VDUkVU" 4. Final Header: Authorization: Basic WU9VUl9DTElFTlRfSUQ6WU9VUl9DTElFTlRfU0VDUkVU
🟦 User Creation V1 (Direct)
The User Creation API helps you set up new customer profiles in your system directly under a DSA/Lender. By gathering their essential information, you register users and generate a secure journey link.
finsire_id. This unique identifier is crucial for
identifying the customer within your system and
must be securely stored on your server. No other APIs can be
accessed without it.
| Field | Type | Requirement | Professional Context |
|---|---|---|---|
| phone | String | Mandatory | Primary customer mobile for OTP/Communications. |
| pan | String | Mandatory | Tax identifier for real-time asset fetching. |
| latitude | String | Mandatory | Geo-location for regulatory compliance. |
| longitude | String | Mandatory | Geo-location for regulatory compliance. |
| name | String | Optional | Legal name as per PAN records. |
| String | Optional | Customer email for transaction notifications. | |
| dob | Date (YYYY-MM-DD) | Optional | Customer date of birth. |
{
"user": {
"phone": "9876543210",
"pan": "ABCDE1234F",
"latitude": "12.9716",
"longitude": "77.5946",
"name": "John Doe",
"email": "john.doe@example.com",
"dob": "1990-01-01"
}
}
{
"status": true,
"finsire_id": "44f4bc0dc887714440a6001731a454b4c4",
"link": "https://dsa.dpiwealth.com/api/link/XXXX"
}
{
"status": true,
"message": "Phone number already exists",
"finsire_id": "47a712f2cb4f774a7c9b6c8934b6d365fb",
"link": "https://dsa.dpiwealth.com/api/link/XXXX"
}
🟩 Partner Onboarding
Used to onboard Referral Partners. This implies a
"Multi-Tier Network Model" of distribution—a
distributor that manages other distributors. It’s designed for large
platforms that have hundreds of sub-MFDs or referral partners
onboarded. This is a mandatory prerequisite for V2 onboarding.
Successful creation generates a partner_code.
FIN-{Last 4 Digits of ClientID}-{MFD code}.
{
"mfd": {
"mfd_code": "FIN-6c52-MFD90876",
"partner_email": "partner@example.com",
"mapping_id": "MAP001",
"arn_no": "ARN12345",
"company_name": "ABC Financials",
"gst_no": "29ABCDE1234F1Z5",
"pan_no": "ABCDE1234F",
"pan_type": "INDIVIDUAL",
"partner_name": "John Doe",
"partner_mobile_number": "9876543210",
"partner_alternate_mobile_number": "9876500000",
"address_line1": "Level 1, Tech Park",
"address_line2": "MG Road",
"address_line3": "Sector 4",
"city": "Bangalore",
"state": "Karnataka",
"country": "India",
"pincode": "560001",
"bank_account_number": "1234567890",
"bank_ifsc_code": "ICIC0000002"
}
}
{
"status": true,
"message": "MFD onboarded successfully",
"partner_code": "FNSR_PARTNER_XXXXXXXX"
}
{
"status": false,
"errors": "Partner email already exists for this account"
}
🟨 User Creation V2 (Referral)
Onboard customers mapped to a specific referral partner, with rich
data enrichment capabilities that allow passing a
partner_code, pre-filling mutual fund portfolio details,
and injecting bank details-significantly reducing user friction and
improving onboarding efficiency.
| Field | Type | Requirement | Professional Context |
|---|---|---|---|
| phone, pan, lat, long | String | Mandatory | Core registration identity and location data. |
| partner_code | String | Mandatory (From Partner API) | Partner attribution code from Onboarding API. |
| name, email, dob, address, aadhar | String | Optional | Secondary identity points. |
| mf_details | Array of Objects | Optional | Pre-filled asset list to reduce user friction. |
| bank_details | Array of Objects | Optional | Target bank details for the credit line. |
{
"user": {
"phone": "9876543210",
"pan": "ABCDE1234F",
"latitude": "12.9716",
"longitude": "77.5946",
"partner_code": "FNSR_PARTNER_82JS92K",
"name": "Jane Smith",
"email": "jane@example.com",
"address": "Bangalore",
"dob": "1992-05-15",
"aadhar": "[Aadhaar Redacted]",
"mf_details": [
{
"repository": "CAMS",
"isinno": "INF209K01YY2",
"scheme_name": "SBI Bluechip Fund",
"lein_eligible_units": "150.500",
"mode_of_holding": "SI",
"folio": "1234567890",
"tax_status": "01",
"scheme_type": "Equity",
"scheme_code": "D010",
"amc_code": "S",
"amc_name": "SBI Mutual Fund",
"nav": "85.25"
},
{
"repository": "KFIN",
"isinno": "INF846K01DP8",
"scheme_name": "HDFC Top 100",
"lein_eligible_units": "120.750",
"mode_of_holding": "Individual",
"folio": "9876543210",
"tax_status": "1",
"scheme_type": "Equity",
"scheme_code": "HDF123",
"amc_code": "H",
"amc_name": "HDFC Mutual Fund",
"nav": "95.40"
}
],
"bank_details": [
{
"bank_name": "State Bank of India",
"account_number": "1234567890123",
"ifsc": "SBIN0001234",
"account_type": "SAVINGS"
}
]
}
}
{
"status": true,
"finsire_id": "904390sdfbk0403ndf00093490u0",
"link": "https://DOMAIN/api/link/ID?token=JWE"
}
{
"status": false,
"error": "mf_details[0]: isinno is required"
}
📖 Business & API Glossary
Zero-assumption definitions for key financial and technical terms used in the Finsire LAMF ecosystem.
| Term | Definition |
|---|---|
| AUM (Assets Under Management) | The total market value of investments managed. LAMF protects AUM from being liquidated during a client's cash crunch. |
| Auto-Renewable Overdraft | A revolving credit line that allows distributor revenue (spread) to compound quietly without needing loan renewals. |
| Lien Marking | A digital hold placed on mutual fund units as collateral. The customer retains ownership and keeps compounding intact. |
| Haircut (Risk Margin) | The safety margin deducted from collateral value. If a fund is ₹100 with a 20% haircut, the borrowable amount is ₹80. |
| LTV (Loan-to-Value Ratio) | The percentage of the mutual fund's market value sanctioned as credit (e.g., 50% for Equity, 80% for Debt). |
| RTA (Registrar and Transfer Agent) | Institutions (CAMS, KFintech) that maintain investor records. We integrate with them for real-time data and digital lien marking. |
| AMC (Asset Management Company) | The fund house managing the mutual fund schemes (e.g., SBI Mutual Fund, HDFC Mutual Fund). |
| ISIN | A unique 12-character alphanumeric code identifying a specific mutual fund scheme. |
| Folio Number | A unique account number assigned to an investor by an AMC, representing their holdings in specific schemes. |
| LSP (Loan Service Provider) | A regulated entity acting as a technology/distribution agent for a lender. Native Flow partners act as LSPs. |
| V-KYC (Video KYC) | The RBI-mandated video identification process for new-to-bank customers before final loan approval. |
| Drawing Power | The real-time usable credit limit, which slightly adjusts daily based on the mutual fund portfolio's live market value. |
| NAV (Net Asset Value) | The current market price of a single mutual fund unit. |
| Pledge / Revocation | Pledge: Locking units as collateral. Revocation: Releasing the lien once the loan is repaid. |
| Sanction Limit vs. Utilized Amount | Sanction Limit: Maximum approved credit. Utilized Amount: Funds actually withdrawn (interest is only charged on this). |
| finsire_id | The primary unique identifier generated upon User Creation, mandatory for tracking the user and making subsequent API calls. |
| partner_code | The attribution identifier generated during MFD Onboarding, required in V2 endpoints to map loans to sub-partners. |
| Mode of Holding | Indicates if the mutual fund is held by a "Single" individual or "Jointly" (which impacts digital pledging eligibility). |
| DigiSign (E-Sign) | The digital signing of the final loan agreement by the customer using Aadhaar-based OTP, triggering the DIGISIGN_COMPLETED webhook. |
| Journey Status | The specific milestone event payload (e.g., PLEDGE_CONFIRMED, OD_APPROVED) pushed via webhooks to track real-time user progress. |
🔄 Detailed Journey Status Guide
Track your customer's exact position in the loan lifecycle via webhooks or the distributor portal. Below is the end-to-end milestone mapping.
| Journey Status Code | Milestone Description |
|---|---|
USER_CREATED |
Profile created in the lender's system (e.g., CUB) and ID successfully verified via Aadhaar/PAN APIs. |
HOLDINGS_FETCHED |
RTA data (CAMS & KFIN) successfully retrieved for the user. |
PLEDGE_CONFIRMED |
User completed the pledging page and RTAs confirmed the mutual fund pledges. |
BANK_DETAILS_ADDED |
Target bank account information submitted for the loan disbursal. |
DIGISIGN_COMPLETED |
The final loan agreement has been digitally signed by the customer. |
VKYC_COMPLETED |
Video KYC processing successfully completed. |
OD_APPROVED |
Overdraft loan facility officially approved by the lender. |
WITHDRAWAL_INITIATED |
Processing fee is debited, funds are available, and the user can withdraw their liquidity. |