Market Basics & Operations

Market Basics & Operations

Enabled Market Segments

Cash Market (CM)

Derivatives (FO)

After Market Orders (AMO)

AMO orders allow users to place orders when markets are closed. The system automatically handles AMO detection and processing.

AMO Logic

1. Holiday Check: System checks holiday master to determine if current day is a trading holiday
2. Timing Check: If not a holiday, system checks current time against market hours
3. Storage: AMO orders are stored locally or sent to Kambala based on timing
4. Processing: Airflow DAGs push orders to exchange during next trading session

AMO Processing Schedule

Trading App Features

Core Trading Features

Search & Discovery

• Download and parse security master files
• Real-time search using Typesense

Watchlist

• Wealthy watchlist management
• Expired and banned scrip tracking
• Upcoming scrip monitoring

Order Types (Order Flow Details)

• Single Leg orders
• 2-Leg orders
• 3-Leg orders
• GTT (Good Till Triggered)
• BO/CO with trailing stop loss
• Exit all positions (bulk square-off)

Reports & Portfolio

• Holdings
• Positions
• Order Book
• Transaction History

Additional Features

• CDSL EDIS (e-DIS authorization)
• Margin pledge management
• Payment gateway integration
• Advanced charting
• IPO, SGB, NCD applications
• Backoffice operations
• KYC push to exchanges

Order Flow Architecture

Order Types Supported

Normal Orders

• Automatically converted to AMO when placed outside market hours
• Various price types: Market, Limit, Stop Loss Market, Stop Loss Limit

Cover Orders (CO)

• Intraday multi-leg orders
• Mandatory stop loss leg
• Parent order spawns child stop loss order

Bracket Orders (BO)

• Intraday multi-leg orders
• Both target and stop loss legs
• Optional trailing stop loss
• Auto square-off on target/stop loss hit

GTT Orders

• Good Till Triggered orders
• Persistent until triggered or cancelled

Basket Orders

• Multiple orders in a single basket
• 2-Leg and 3-Leg strategies

Order Placement Flow

New Order Request
    ↓
Check AMO Time
    ↓
┌─────────────────────────────────┬─────────────────────────────────┐
│   NOT AMO Time                  │   AMO Time                      │
├─────────────────────────────────┼─────────────────────────────────┤
│ 1. Generate Falcon Order ID     │ 1. Generate Falcon Order ID     │
│ 2. Keep in cache                │ 2. Keep in cache                │
│ 3. Send to Kambala OMS          │ 3. Map Falcon to OMS ID         │
│ 4. Map Falcon to OMS ID         │ 4. Store in orders table        │
│ 5. Store in orders table        │ 5. Return response to client    │
│ 6. Return response to client    │ 6. Queue for next session       │
└─────────────────────────────────┴─────────────────────────────────┘

Order Modification Flow

During Market Hours (Not AMO Time)

• Direct modification sent to Kambala OMS
• Immediate confirmation

Outside Market Hours (AMO Time)

• Check if order is AMO order
• If AMO: Modify in local storage
• If Regular: Handle based on current order status

User Details API

Endpoint: GET https://api.wealthydev.in/broking/api/v0/user/

Response Structure:

 1{
 2   "name": "Investor Name",
 3   "mobile_number": "9XXXXXXXXX",
 4   "exchange": [1, 2, 3],
 5   "order_types": [
 6       {
 7           "order_type": 1,
 8           "exchange": [1, 3]
 9       }
10   ],
11   "broker_name": "WEALTHY",
12   "branch_id": "HO",
13   "email": "user@example.com",
14   "pan": "AAAAA1111L",
15   "mandate_list": [],
16   "BankDetails": null
17}

IPO Operations

Supported IPO Types

• Normal IPO: Mainboard offerings
• SME IPO: Small and Medium Enterprise segment

Application Categories

IPO Application Process

Prerequisites:

• DP Status: Active
• PAN Status: Verified
• Payment Status: Sufficient funds (100% upfront)

Application Steps:

1. Fetch IPO master from exchange
2. Get application number
3. Place order with application details
4. UPI mandate approval
5. Allotment on listing day

Payment Systems

Payment Modes

UPI

• Provider: HDFC UPI
• Processing: Real-time
• Callback: Immediate status update

Net Banking

• HDFC Net Banking: Production
• Pine Labs: Production
• Future Integrations: Pending finance team approval

NEFT/RTGS (Offline)

• Processing Time: 30 minutes - 1 hour
• Manual Update: Via DPulse
• Flow: Update in DPulse → Atlas creates payin record → Increase funds in Kambala

Payment Callback Flow

Bank Callback (CRN, Amount, Source Account)
    ↓
Store in DB/Queue (Status: Pending)
    ↓
Process Oldest 10 Records
    ↓
TPV Check (Third Party Verification)
    ↓
┌──────────────────────┬──────────────────────┐
│  TPV Success         │  TPV Failed          │
├──────────────────────┼──────────────────────┤
│ Update in Kambala    │ Mark as Failed       │
│ Increase Funds       │ Notify User          │
└──────────────────────┴──────────────────────┘

TPV (Third Party Verification)

• Fetch all registered bank accounts from user’s broking profile
• Verify source bank account is in registered accounts list
• If verified: Update funds in Kambala
• If failed: Reject transaction

Fund Management

Payin Flow

Atlas Operations:

1. List supported payment modes (UPI, Net Banking, NEFT/RTGS)
2. Fetch saved UPI IDs and bank details
3. Create order ID and call Collector service
4. Frontend polls status + Airflow job monitoring
5. On success: Update status in Atlas → Increase funds in Kambala
   • Exception: No fund increase between 00:00 AM - 08:00 AM IST

Payout Schedule

Payout Logic

Evening Payout:

• Skip users with margin utilization
• Sync remaining withdrawal requests

Payout Calculation:

Payout Amount = MIN(Existing Balance, Requested Amount)

Process:

1. Atlas fetches withdrawal requests
2. Decrease balance in Kambala
3. Push data to TechXL
4. Upload file to sync actual payout amounts from TechXL

Future Enhancement

• 1-Hour Payout: Fast withdrawal processing under development

Margin Calculation

Example Calculation

Inputs:

• Cash: ₹40,000
• Payin: +₹5,000
• Payout: -₹20,000
• Margin Pledge: ₹150,000 (Usable: ₹137,500, Remaining: ₹12,500)
• Margin Used: ₹25,000

Note: Only 50% of margin pledge can be used. The 50% comes from cash.

Calculations

Cash Used:

₹12,500 (from cash) + ₹12,500 (from margin pledge) = ₹25,000

Actual Cash Balance:

₹40,000 + ₹5,000 - ₹20,000 - ₹12,500 = ₹25,000

Available Margin:

₹25,000 (cash) + ₹150,000 (pledge) - ₹25,000 (used) = ₹150,000

Withdrawable Balance:

₹40,000 + ₹5,000 - ₹20,000 - ₹12,500 = ₹7,500

Daily Operations

Daily File Downloads & Processing

Exchange Master Files:

• NSE CM: Security.txt (via API)
• NSE FO: Contract.txt (via API)
• NSE FO: Spread.txt (not currently used)
• BSE: Download from BSE Help Desk

Processing:

1. Download files
2. Parse and validate
3. Store in Typesense for real-time search

Daily Scheduled Jobs

Monthly Operations

Monthly File Uploads

EDIS Settlement Master:

• Upload monthly settlement file
• Required for CDSL e-DIS operations

Margin Pledge Eligible Scrips:

• Upload list of eligible securities for margin pledge
• Updated monthly based on exchange notifications

Related Documentation

• Trading API - Complete API documentation
• BOD Checklist - Daily operational checklist
• Order Flow Details - Detailed order type specifications