Wealthcrop — Help & Knowledge Center

1. Create company profile & add authorised user (email + mobile + role).
2. Complete KYC collection form — PAN, Aadhaar, address proof, photo, bank details.
3. Run eKYC via Aadhaar (if supported) or manual KYC upload.
4. Verify bank account via micro-deposit or UPI OTP depending on payment provider.
5. Assign UCC and map to customer profile for downstream transfer/transaction flows.

Pro tip: Keep scanned documents less than 2MB and in PDF/JPG. Keep a mapping table of UCC → PAN for reconciliation.

• PAN: clear scan, .pdf/.jpg, readable characters
• Aadhaar: masked copy allowed (last 4 digits visible)
• Address proof: passport/driver’s license/utility bill (not older than 3 months)
• Cancelled cheque: required for mandate/auto-debit

Typically, KYC verification takes 24–72 hours depending on the method. For eKYC via Aadhaar OTP, verification is instant (minutes). For manual verification, ensure documents are legible and UCC mapping is provided.

1. User selects scheme & plan (Direct/Regular) — select option (Growth/Dividend).
2. User chooses SIP amount, start date and frequency (monthly/quarterly).
3. Mandate setup: UPI or NACH/autodebit. NACH mandates require bank verification and mandate registration.
4. On successful mandate, SIP becomes active. Provide confirmation & schedule next date.

Edge cases: failed mandate retries, bank returned mandates, and SIP pause/resume functionality must be surfaced to users.

Lumpsum uses the payment gateway (BSE STAR / payment provider). Steps:

1. User picks scheme, fills amount, and verifies PAN/KYC status.
2. Redirect to payment gateway (payment flows: UPI / netbanking / cards as enabled).
3. On success, BSE/order reference is stored; units are allocated on NAV date.

• Top-up: recurring percentage or fixed amount increase (monthly/quarterly)
• Pause: user can pause SIP (no debit) for N cycles
• Cancel: immediate cancellation (pending mandates remain)
• Modify: change amount/date; ensure next debit is scheduled accordingly

NAV — Net Asset Value; per-unit value of the scheme, updated daily after market close.

Return metrics — Absolute return and CAGR (compound annual growth rate). Use exact date math and trading-day aware calculations for production.

Wealthcrop supports:

• UPI (fast, recommended)
• NACH / ECS / AutoDebit (for SIP mandates)
• Netbanking / Cards (for lumpsum)

BSE STAR MF is commonly used for final settlement for AMCs.

1. Store gateway transaction id & status (pending/failed/settled).
2. Map payment to UCC & user id for audit trails.
3. Set up webhook endpoints for gateway events and signature verification.

• Equity funds (holding >60%): Long term capital gains (LTCG) — 10% above ₹1 lakh without indexation (since FY 2018).
• Debt funds: LTCG taxed @20% with indexation benefit; STCG taxed as per slab.
• ELSS: Eligible for Section 80C deduction (limit ₹1.5 lakh).

Tax guidance above is summary only — consult a tax advisor for specifics and local variations.

• Record retention policy for transactions & KYC (retain per regulator — typically 8 years)
• Consent records for eKYC & marketing (timestamped)
• AML/KYB for corporate accounts
• Periodic reconciliation with AMCs & CAMS/BSE feeds

1. Confirm endpoint path and query param names — e.g. /schemes/schemes/search?q= vs /schemes/search?q=.
2. Check CORS settings on API host; ensure WP origin is allowed.
3. Use browser devtools → Network to inspect raw response and HTTP status.
4. Temporarily test curl from server to confirm endpoint is reachable (use same path & query).

This usually means saved HTML/JS contains an unescaped character or WP has modified quotes. Fixes:

• Use a Custom HTML block or raw template (avoid Visual editor).
• Wrap long template strings carefully; avoid inline backticks where WP may sanitize.
• Check console for line number and paste the snippet into a JS validator.

Solution: ensure research page reads ?code=WR000... from URL and calls details/returns endpoints with that code. Persist last selected code in localStorage so homepage → research works seamlessly.

Return payloads expected: data.returns object + data.nav_history array with {date, nav} entries.

• Always URL-encode query params using URLSearchParams.
• Use fallback endpoints if primary returns 422/404.
• Cache scheme list on client for a session to reduce calls.
• Use server-side caching (materialized views) for nav history heavy queries.

1. API TLS certificate valid & CORS configured
2. Rate-limits & throttling in place
3. Audit logs for all create/modify flows
4. Load test nav_history endpoints (large queries)