Summary: SEBI’s circular dated 1 October 2026 changes the display arrangement for stock-broker websites and trading apps from 1 November 2026. A broker’s website must place the investor-awareness message specified by SEBI on its landing page. A trading app, where the broker has one, must show the specified investor-awareness message and the existing risk disclosures on alternate days, also on the landing page. The October transition rule ends on 31 October: website display of both sets of material is then replaced by the landing-page requirement, while app display moves from voluntary to mandatory alternate-day rotation. The compliance task is therefore not merely uploading text; it requires controlled content, correct surface placement, an auditable rotation calendar, release testing and evidence that the live customer journey displays the required material without alteration.
- The 1 November Cutover Changes Two Customer Surfaces
- A Website Landing Page Needs a Controlled Compliance Component
- Placement must be tested on the page customers actually enter
- The SEBI-supplied wording needs version control
- Alternate-Day App Display Requires a Deterministic Calendar
- Define what an alternate day means before deployment
- Landing-page visibility must survive login states and app versions
- Implementation Register for Compliance Technology and Product Teams
- Evidence Should Reconstruct What a Client Saw on a Particular Day
- Common Misreadings That Can Produce a November Breach
- Frequently Asked Questions
- 1. What must change on a stock-broker website on 1 November 2026?
- 2. Is the trading-app display still optional in November?
- 3. Can the broker rewrite the SEBI message in its own tone?
- 4. Does a link in the app menu satisfy the landing-page rule?
- 5. What evidence is strongest for alternate-day compliance?
- 6. What if SEBI changes the awareness message later?
- 7. Does the 2026 circular cancel the 2023 risk-disclosure circular?
- Key Takeaways
The 1 November Cutover Changes Two Customer Surfaces
SEBI Circular No. HO/38/24/(15)2026-MIRSD-PODMMC/I/22872/2026 was issued on 1 October 2026 under section 11(1) of the SEBI Act, 1992. It applies through recognised stock exchanges and depositories to stock brokers. The circular supplements the 19 May 2023 risk-disclosure framework; it does not withdraw that earlier framework. The operational question is therefore how the new investor-awareness messages and the existing risk disclosures must coexist on each digital surface.
The transition window runs from 5 October through 31 October 2026. During that period, every broker website must display the SEBI-shared investor-awareness messages together with the existing risk disclosures. An app may display the awareness message voluntarily during the transition; if it does so on a particular day, the risk disclosure is optional for that day. From 1 November, a different permanent arrangement applies. Teams should not carry the transition logic into November by mistake.
| Surface | 5–31 October 2026 | From 1 November 2026 |
|---|---|---|
| Broker website | Investor-awareness message and risk disclosures must be displayed | Investor-awareness message must appear on the landing page |
| Trading app, if any | Awareness message voluntary; risk disclosure optional on a day the message is shown | Awareness message and risk disclosures must be shown on alternate days on the landing page |
| Exchange or depository | Notify members, disseminate the circular and display the SEBI message | Continue the directed dissemination and framework support |
A Website Landing Page Needs a Controlled Compliance Component
Placement must be tested on the page customers actually enter
The circular specifies the landing page from 1 November. A broker should identify the actual entry page reached by customers on desktop and mobile web, including redirects from marketing domains, login links and regional pages. A message hidden in a footer, help centre or investor-awareness library does not demonstrate that it is on the landing page. Compliance, technology and product owners should agree the precise component, page template and release owner before the cutover.
The SEBI-supplied wording needs version control
SEBI states that the investor-awareness messages may be modified from time to time. The broker should therefore store the source file or communication received through the exchange, record its effective date, preserve the displayed version and prohibit unapproved paraphrasing. The display engine should separate content from code so that a later message update can be implemented without an uncontrolled website release. A content register should record the message identifier, receipt date, approving officer, deployment time and superseded version.
Alternate-Day App Display Requires a Deterministic Calendar
Define what an alternate day means before deployment
The app requirement is not satisfied by random rotation. The broker should adopt a written calendar that assigns the investor-awareness message and the risk disclosure to alternate calendar days from 1 November 2026. The control should specify the operating time zone, midnight boundary, treatment of maintenance windows and the content that appears immediately after an update. Using Indian Standard Time is operationally sensible for an India-facing broker, but the chosen rule should be documented and applied consistently.
Landing-page visibility must survive login states and app versions
Testing should cover a logged-out customer, an authenticated customer, a first-time user, an existing user with cached content and supported Android and iOS versions. If the app has different home screens by client segment, the required display should be tested for each relevant path. A server-side content switch reduces dependence on customers installing a new build, but the broker must confirm that the older supported build can render the message. Screenshots alone are useful evidence, yet server logs and release records provide stronger proof of the date and version served.
Implementation Register for Compliance Technology and Product Teams
| Control | Owner | Evidence to retain |
|---|---|---|
| Obtain exact SEBI message through the exchange channel | Compliance | Source communication, checksum or controlled copy |
| Map website and app landing pages | Product | Approved journey map and screen inventory |
| Configure 1 November website change | Technology | Release ticket, deployment log and live-page capture |
| Configure alternate-day app schedule | Technology and compliance | Calendar, rule configuration and daily event logs |
| Test supported devices and login states | Quality assurance | Test cases, results and defect closure |
| Monitor message updates | Compliance | Periodic review log and replacement approvals |
| Escalate display failure | Operations | Incident ticket, duration, affected surface and remediation |
The register should distinguish a content failure from an availability failure. A content failure includes wrong wording, wrong daily rotation or display on the wrong page. An availability failure includes a broken component, blank space, blocked asset or a message that cannot load when other trading functions remain available. The escalation threshold should be sufficiently short because the requirement applies continuously, not merely at market open.
Evidence Should Reconstruct What a Client Saw on a Particular Day
A defensible audit trail should allow a reviewer to answer five questions: which content version was approved, which surface was configured, when it went live, which day of the app rotation applied and whether monitoring detected a failure. Useful evidence includes the exchange communication, approved copy, deployment ticket, automated screen capture, content-delivery logs, app analytics event and incident record. Personal client data should not be collected merely to prove the display; test or synthetic accounts can establish the customer journey without expanding privacy risk.
Internal audit or compliance testing can sample dates on both sides of the cutover. A 31 October capture should show the transition treatment, while 1 and 2 November captures should show the new website placement and the two app states. If the investor-awareness message changes later, the test should confirm the new version on the effective date and preserve the retired copy. The evidence period should align with the broker’s applicable record-retention and supervisory framework rather than an invented universal duration.
Common Misreadings That Can Produce a November Breach
The first error is treating the app requirement as voluntary after October. Voluntary app display applies only during 5–31 October; from 1 November, the alternate-day display is mandatory for a broker that has a trading app. The second error is showing both items permanently on a secondary page. The circular specifically refers to the app landing page and to alternate days. The third is removing the older risk-disclosure control entirely. The circular says all other provisions of the 2023 circular remain unchanged.
Another error is assuming that one successful release closes the obligation. SEBI may modify the awareness messages, and apps may fail differently across versions. Brokers need monitoring, controlled updates and incident handling. Finally, entities should not infer that the circular changes trading-risk disclosures, suitability duties or grievance procedures beyond what it expressly states. This article addresses the display mechanism and its implementation evidence, not the entire conduct framework applicable to a broker.
Frequently Asked Questions
1. What must change on a stock-broker website on 1 November 2026?
The specified SEBI investor-awareness message must be displayed on the landing page. The team should retire the October transition configuration only after confirming the new live placement.
2. Is the trading-app display still optional in November?
No. For a broker with a trading app, the investor-awareness message and the risk disclosures must be displayed on alternate days from 1 November 2026.
3. Can the broker rewrite the SEBI message in its own tone?
The safer control is to use the exact message supplied through the regulatory channel. The circular refers to messages shared by SEBI, and any modification should come from the authorised source rather than marketing editing.
4. Does a link in the app menu satisfy the landing-page rule?
A menu link alone does not establish landing-page display. The required content should be visible through the landing-page experience specified by the circular.
5. What evidence is strongest for alternate-day compliance?
A combination of approved calendar, configuration record, timestamped server or content-delivery logs and daily rendered-page evidence is stronger than an isolated screenshot.
6. What if SEBI changes the awareness message later?
The broker should trigger its controlled content-update process, verify the authoritative version and effective timing, deploy it, test both surfaces and preserve the superseded version.
7. Does the 2026 circular cancel the 2023 risk-disclosure circular?
No. It expressly keeps the other provisions of the 19 May 2023 circular unchanged while prescribing the new display arrangement.
Key Takeaways
- The website and app move to different permanent display rules from 1 November 2026.
- Trading apps must rotate the SEBI awareness message and risk disclosures on alternate days.
- Landing-page mapping, exact content control and supported-version testing are central compliance steps.
- The audit trail should reconstruct the content, surface, date, rotation state and any incident.
- A later SEBI message change requires controlled replacement and fresh verification.
*****
Disclaimer: This article is a general editorial explanation of SEBI Circular No. HO/38/24/(15)2026-MIRSD-PODMMC/I/22872/2026 dated 1 October 2026 and the practical controls that may help a stock broker prepare for the display arrangement effective from 1 November 2026. It is not a substitute for the circular, the continuing 19 May 2023 risk-disclosure framework, exchange or depository communications, a broker’s registration conditions, applicable cybersecurity and outsourcing controls, or any later regulatory clarification or message version. The precise implementation depends on the broker’s website architecture, app versions, client journeys, exchange memberships, internal governance, content-delivery arrangements and incident procedures. References to calendars, logs, screenshots, test accounts and control ownership are implementation considerations, not additional legal requirements attributed to SEBI. A broker should obtain the exact message from its authorised regulatory channel, confirm the live requirement and effective timing, test every relevant surface and retain evidence under its own applicable record-retention framework. Technology failures, cached pages, third-party components, time-zone configuration and incomplete app adoption can alter what clients actually see, so a paper approval alone should not be treated as proof of live compliance. Readers should seek advice from qualified securities-law, compliance, technology, privacy and audit professionals before relying on this material or changing a production system. TaxGuru accepts no responsibility or liability for any loss, regulatory action, service interruption, implementation defect or decision arising from use of this article, omission of a later update, or reliance on a summary instead of the current primary source.
