Mutual Fund Distributor Platform Development

Mutual Fund Distribution Platform (B2B2C Model)
1. BUSINESS OBJECTIVE
Build a digital wealth distribution platform (similar to AssetPlus model) enabling:
• Investor on boarding
• KYC processing
• eSign
• Lumpsum & SIP transactions
• Mandate creation (eNACH / UPI Autopay)
• Portfolio tracking
• Distributor dashboard
• Commission tracking
• Admin & compliance monitoring
Platform must support:
• Web (Investor + Distributor + Admin)
• Android App
• iOS App
• Multi-tenant SaaS capability (future-ready)
2. USER ROLES
2.1 Investor
• Register & complete KYC
• Invest in mutual funds
• Create SIP
• View portfolio
• Download statements
2.2 Distributor / Advisor
• Onboard investors
• Track client portfolio
• Track commission
• View transaction reports

2.3 Super Admin
• User management
• AMC configuration
• Commission configuration
• Reconciliation dashboard
• Compliance monitoring
AUTHENTICATION MODULE
Features
• Mobile OTP login
• Email login
• JWT authentication
• Role-based access control

APIs
POST /auth/register
POST /auth/login
POST /auth/verify-otp
POST /auth/refresh
POST /auth/logout
________________________________________
USER & KYC MODULE
Functional Requirements
• PAN validation
• Fetch existing KYC from KRA
• New KYC submission
• Document upload
• Video KYC (optional)
• KYC status tracking
APIs
POST /kyc/initiate
POST /kyc/upload-doc
POST /kyc/submit
GET /kyc/status
External Integrations
• KRA API (CAMS / KFin)
• PAN Verification API
• Aadhaar eKYC (optional)
________________________________________
eSIGN MODULE
Use Cases
• KYC declaration
• Mandate signing
• Risk disclosure consent
APIs
POST /esign/initiate
POST /esign/callback
Signed documents stored securely (encrypted S3).
________________________________________
MANDATE & PAYMENT MODULE
Functional Requirements
• Create eNACH mandate
• Create UPI Autopay mandate
• Validate mandate before SIP
• Handle payment webhooks
• Refund support (if required)
APIs
POST /mandate/create
GET /mandate/status
POST /payment/initiate
POST /payment/webhook
GET /payment/status
Integrations
• Payment Gateway
• eNACH provider
• UPI Autopay API
________________________________________
4.5 ORDER MANAGEMENT SYSTEM (OMS)
Functional Requirements
• Lumpsum order placement
• SIP registration
• SIP cancellation
• Order status tracking
• Webhook handling from RTA
• Retry mechanism for failures
APIs
POST /orders/lumpsum
POST /orders/sip
GET /orders/status
POST /orders/cancel-sip
POST /orders/webhook
Integrations
• MFU API or RTA APIs (CAMS / KFin)
________________________________________
4.6 PORTFOLIO MODULE
Features
• Portfolio summary
• Holdings view
• Transaction history
• NAV updates
• Capital gain estimation
APIs
GET /portfolio/summary
GET /portfolio/holdings
GET /portfolio/transactions
________________________________________
4.7 DISTRIBUTOR MODULE
Features
• Client list
• Commission tracking
• Revenue reports
• ARN management
• Onboard sub-distributors (future)

APIs
POST /distributor/register
GET /distributor/clients
GET /distributor/commission
________________________________________
4.8 ADMIN PANEL
Features
• Manage users
• Manage schemes
• Manage commissions
• Reconciliation dashboard
• Audit logs
• Compliance flags
________________________________________
5. SEQUENCE FLOW (CRITICAL FOR DEV)
________________________________________
5.1 Onboarding → KYC → eSign Flow
1. User registers
2. PAN validation
3. KRA lookup
4. If not KYC → submit KYC
5. Upload documents
6. eSign consent
7. KRA status = Verified
________________________________________
5.2 Lumpsum Investment Flow
1. User selects scheme
2. Create order in OMS
3. Payment initiated
4. PG webhook confirms success
5. OMS places order to RTA
6. RTA confirms order
7. Portfolio updated

5.3 SIP Flow
1. Create mandate
2. Mandate becomes ACTIVE
3. Create SIP order
4. RTA registers SIP
5. On due date auto debit
6. Transaction confirmation via webhook
________________________________________
6. DATABASE STRUCTURE (SUMMARY)
Users
id, mobile, email, role, kyc_status, created_at
KYC
id, user_id, pan, status, esign_doc_id
Mandate
id, user_id, bank_name, mandate_ref, status
Orders
id, user_id, scheme_code, type, amount, status
Transactions
id, order_id, nav, units, date
Portfolio
user_id, scheme_code, total_units, market_value
Distributor
id, arn_number, commission_rate
________________________________________
7. SECURITY REQUIREMENTS
• AES-256 encryption for PAN & bank data
• HTTPS only
• JWT with short expiry
• Webhook signature validation
• Audit trail logging
• Rate limiting
• Role-based access control
• No card data storage
• PCI DSS compliance via PG
________________________________________
8. PERFORMANCE REQUIREMENTS
• Response time < 500ms
• Concurrent users support 10,000+
• 99.9% uptime
• Auto scaling enabled
________________________________________
9. DEVOPS & INFRA
Cloud: AWS / GCP
Containerization: Docker + Kubernetes
Database: PostgreSQL
Cache: Redis
Storage: S3
CI/CD: GitHub Actions / GitLab
Monitoring: Prometheus + Grafana
Logging: ELK stack