This is the part of the business that quietly eats a week of somebody's time every month. Here it runs on its own, in your name, and leaves a record you could hand to an auditor. Below is every step, in the order your client meets it.
No step here is a diagram. Each one is a screen, and each one leaves a record.
Your site, your logo, your colours. One of seventeen portal themes, light or dark. The internal routes are hidden behind opaque tokens, so nothing about the plumbing shows. If they ever find out we exist, we have failed at our job.
Both are verified at signup with a one-time code. Afterwards they can sign in with either one. The moment either is verified, they exist as a lead against your business — with the referral code of whichever of your staff brought them.
They type the PAN; the official name comes back from CVL KRA and fills the form itself. No more a typo discovered three weeks later as a KYC rejection. The KRA credentials are yours, under your own POS code — we never sit in the middle of your KYC.
The agreement and the Investor Charter open in a viewer that tracks how far they have actually read. The OTP box does not appear until both documents are at least 90% read. They cannot scroll to the bottom and sign blind.
One signed PDF: the agreement and the Charter, each stamped, and a final page carrying the certificate ID, their name, email and phone, the timestamp in IST, their IP address and city, the SHA-256 hash of the exact document signed, the seconds they spent on each document, when the code was sent, when they first opened it, and your company name and SEBI registration number.
Razorpay, PhonePe, Cashfree or a UPI QR — each switchable, each with your own credentials. Your invoice prefix, your sequence, your GST treatment. The money never routes through us, so the gateway's charge stays between you and them.
SEBI caps what one PAN may pay an RA at ₹1,51,000 excluding GST per 365 days. We compute the approved payments of the last year plus the cart, on your own GST rate — never an assumed 18% — and stop the purchase before payment starts. It fails open by design: a new client, a missing PAN or a slow check is allowed through. Only a computed, confident breach is refused.
The KRA document is the activation artifact. Activation is gated on that file existing — not on an API having answered cheerfully. No document, no activation. It is a deliberately strict design and it is the one worth saying out loud.
Anyone who started and stopped stays on your leads list with a note field, a next-follow-up date and a not-interested flag — beside the leads your free webinars brought in. Automated reminders go out to people mid-way through signing up.
Ten tabs in your own console. Nothing on this list needs a support ticket.
Logo, favicon, company name, tagline, owner and licence, SEBI registration number and date, BSE enlistment, billing state, address, GSTIN, PAN, support email and phone, bank details, your report disclaimer, the MITC PDF itself and where its stamp lands, and seven social links.
Your own SMTP for agreements and receipts, and an entirely separate promotional SMTP. One bad campaign can never stop a client receiving their agreement.
Four gateways with your own encrypted credentials, sandbox or production, invoice prefix and next number, a coupon field toggle, and the checkout theme your client sees.
Your Meta Cloud API phone number, token, app id and secret, webhook and template names — plus your Telegram bot, username, token and chat id.
A digital signature certificate with its issuer, serial and validity captured for audit, a signature image, its placement, and whether it applies automatically.
Personal details, KYC, agreement, first payment, e-sign — in any order, any subset, each one individually switchable, with a progress indicator your client can see.
Append-only, and built into the data model rather than bolted on afterwards.
Every consent, and every change to one, with its time.
Device logins and session history per client.
Every action an operator takes, under their own login.
Per message, per channel, with what happened to it.
Line-level, with an invoice sequence that is yours.
Archived, and regenerated automatically if a render ever fails.
No. Your domain, your logo, your theme, your payment gateway, your WhatsApp number and your SEBI registration number on every document. The platform runs underneath and stays there.
Yes. Each step is individually switchable and the sequence is yours. Some desks take payment first and complete KYC afterwards; others will not let anyone near a plan until the agreement is signed.
You open one PDF. It shows their IP address, their city, the exact second they signed, the SHA-256 hash of the document they signed, and how many seconds they spent reading each document before the OTP box even appeared.
Yours. You enter your own credentials and POS code, and choose live or sandbox per registry. We never sit in the middle of your KYC.
Never. Payments go to your own merchant account on your own gateway credentials. Nothing routes through an OptumFlex account.
About three hours once your credentials are in hand — domain, logo and company details, gateway keys, SMTP, WhatsApp, KRA credentials and your MITC PDF. The clock starts when that list arrives, not when a contract is signed.
They are already a lead on your list, with whatever they verified, and reminders go out automatically. Most desks discover this is the cheapest source of clients they have.
All of them on one checkout, one invoice and one set of clients.
Fifteen minutes, your logo already on it. If it is not obvious in fifteen minutes, it is not for you.
A walkthrough takes about thirty minutes: onboarding and a signed agreement, a live publish, a portfolio rebalance, and the records behind them — with your first month costed on the spot.