KYC before payment: the order that keeps an RA compliant
For a SEBI-registered Research Analyst, onboarding a paying client has a fixed order: complete KYC, take the client's consent on your terms and MITC, and only then collect the fee. Get the order wrong, by sending a payment link first and asking for documents later, and you have charged a fee before consent. That is one of the first things a compliance auditor checks.
This guide covers what SEBI requires for RA client KYC, how the KRA system fits in, and how to design an onboarding flow that keeps KYC and e-sign ahead of payment. The rules are from the RA Regulations and SEBI's Master Circular for Research Analysts dated 6 February 2026.
What SEBI requires
- KYC for fee-paying clients. Regulation 25(1) requires RAs to follow the KYC procedure for their fee-paying clients and keep KYC records as SEBI specifies. SEBI's FAQs clarify that KYC applies to clients paying fees directly for research services.
- Through a KRA. The standard terms say the RA shall collect, store, upload and check KYC records of clients with a KYC Registration Agency (KRA) as SEBI specifies.
- Consent before service or fee. No research service may be rendered and no fee charged until the client consents to the terms and conditions, including the MITC.
- Records for five years. KYC records, signed terms and records of interactions with clients and prospective clients must be kept for at least five years, and longer if a dispute is open.
Who needs KYC
| Client type | KYC needed? | Terms and MITC | Interaction records |
|---|---|---|---|
| Fee-paying individual or HUF | Yes, through a KRA | Disclose and take signed consent before service or fee | Yes |
| Fee-paying non-individual | Yes, through a KRA | Disclose and take signed consent | Yes |
| Institutional investor or QIB | Yes, if it pays fees directly | Disclose; signed consent not mandatory | Yes (call recordings not mandatory from 9 November 2026) |
| Non-fee-paying client (research as a value-added service) | Not required | As per your terms | Yes |
Count families correctly at onboarding. The fee cap of ₹1,51,000 a year applies per family for individual and HUF clients, and for client-level segregation PAN is the control record and a family counts as one client. Capture PAN and family links in the same step as KYC. See what an RA may charge.
How KRA KYC works for an RA
KYC Registration Agencies hold KYC records for investors in the securities market. Many of your clients will already have a KRA record from opening a demat or mutual fund account. For an RA, that means:
- Check first. Look up the client's PAN with a KRA. If a valid record exists, you can generally use it rather than collecting documents again. Follow the KRA's rules on which record statuses can be relied on.
- Upload when needed. If the client has no record, or the record is incomplete, collect the KYC documents and upload the record to the KRA.
- Store what you used. Keep the KYC data or record you relied on, with the date of the check, in the client's file.
Access to KRA systems usually comes through a KRA directly or through a technology provider that is connected to one. Ask your provider which KRA it uses and what it stores.
An onboarding flow that keeps payment last
| Step | What happens | Rule behind it |
|---|---|---|
| 1. Details | Client enters PAN, name, date of birth, email and mobile | Needed for KYC and the per-family fee check |
| 2. KYC check | Look up the client's KYC record with a KRA. If there is a valid record, use it. If not, collect the documents and upload a new record | RAs collect, store, upload and check KYC records with a KRA |
| 3. Terms and MITC | Show the full terms, the MITC, the plan and the fee, with the investor charter | Terms must be disclosed to the client |
| 4. E-sign | Client gives consent by Aadhaar-based e-sign through DigiLocker, or another legally acceptable mode | No service and no fee until consent is received |
| 5. Payment | Collect the fee by a non-cash mode and issue an invoice | Cash is not allowed |
| 6. Access | Start the service for the paid period | Service follows KYC and consent |
Mistakes to avoid
- Payment link first. Collecting money from a payment page shared on social media or messaging, then asking for KYC and consent. This charges a fee before consent.
- Access before KYC. Adding a client to a paid Telegram channel or app before KYC is complete.
- Renewals without fresh consent. For existing clients, terms must be disclosed and consent taken on or before the renewal date or next fee due date, whichever is earlier.
- Losing the link. Not being able to show which KYC check and which signed version of the terms came before which payment.
Protecting client data
KYC data is personal and sensitive. The investor charter gives clients a right to privacy and confidentiality, and requires RAs to protect clients' confidential information from unauthorised use. In practice:
- Collect only what KYC and your services need.
- Restrict access to KYC files to the people who need them.
- Check where your software vendors store client data. RAs give SEBI a half-yearly undertaking on compliance with the CERT-In advisory on Software as a Service solutions, which is concerned with critical data leaving India.
- Never ask for, or accept, clients' trading, demat or bank logins or OTPs. The MITC says the RA will never ask for them.
What the auditor will check
The annual compliance audit will typically sample client files and look for:
- completed KYC, checked with a KRA, for every fee-paying client;
- signed terms and MITC dated before the first payment;
- invoices and payment records matching the plan the client signed for;
- records of interactions kept for five years.
KYC before payment on AlphaQuark
AlphaQuark runs onboarding for RAs in this order under their own brand: KYC with KRA lookup, MITC e-sign, then payment and invoice, with each step timestamped against the client. Access to plans, Telegram channels and alerts starts only after payment and ends with the paid period. See the RA platform, and our guide to collecting subscription payments.
Onboard in the right order, every time
AlphaQuark runs KYC with KRA lookup, MITC e-sign and then payment for SEBI-registered Research Analysts, with every step recorded.
See the RA platformFrequently Asked Questions
Do research analysts have to do KYC of clients?
Yes, for fee-paying clients. Regulation 25(1) requires RAs to follow the KYC procedure for fee-paying clients and keep KYC records. The standard terms say RAs collect, store, upload and check KYC records with a KYC Registration Agency (KRA).
Do non-fee-paying clients need KYC?
No. SEBI's FAQs say KYC applies to clients paying fees directly for research services. Records of interactions must still be kept for non-fee-paying clients.
Can a research analyst collect payment before KYC and MITC consent?
No. No research service may be rendered and no fee charged until the client consents to the terms and conditions, including the MITC. Complete KYC and e-sign first, then collect payment.
How long must an RA keep KYC records?
At least five years. If a dispute has been raised, keep the records until it is resolved, or longer if SEBI asks.
Is Aadhaar e-sign accepted for RA client consent?
Yes. Consent can be given through any legally acceptable mode, including DigiLocker-enabled Aadhaar-based e-signature.