IFSCA: Issues algorithmic trading guidelines for IFSCs

The International Financial Services Centres Authority (IFSCA) has issued guidelines for algorithmic trading on stock exchanges in International Financial Services Centres (IFSCs), aiming to promote orderly and transparent automated trading. The supplied official extract confirms the issuance and purpose, but does not state the circular’s date or detailed requirements. ^[1]

A secondary account identifies the circular as dated 16 October 2026 and describes requirements covering exchange approval, risk controls, emergency shutdowns and system audits. That date and those provisions could not be independently verified against the complete IFSCA circular. They are not presented here as confirmed compliance requirements. ^[2]

For exchanges, brokers and trading-software providers, the issues concern both permission to operate automated systems and responsibility when those systems malfunction. Approval procedures assess whether systems satisfy prescribed conditions; order checks and shutdown controls address their behaviour during trading.

Live research was not available for this article. The reporting draws on the supplied documents and extracts, including the complete Securities and Exchange Board of India (SEBI) circular dated 30 March 2012. That historical document explains several safeguards discussed below, but does not establish the contents or current legal effect of IFSCA’s latest framework. ^[3]

How algorithmic trading differs from manual order entry

Algorithmic trading uses software to generate orders through automated instructions. SEBI’s 2012 circular defined it by reference to orders generated using automated execution logic. The distinction concerns how the trading instruction originates, rather than simply whether it reaches an exchange electronically. ^[3]

An algorithm can apply predefined rules to market information and generate an order without a person manually entering each instruction. This creates a need to distinguish an intended trading decision from a software error, repeated instruction or uncontrolled sequence of orders.

SEBI’s historical circular addressed those risks at both exchange and broker level. Exchanges were directed to manage system load, monitor performance and maintain surveillance capable of handling the speed and data volume associated with automated trading. They also had to pursue consistent system response times for brokers. ^[3]

These are documented historical SEBI requirements, not independently verified provisions of the latest IFSCA guidelines. They explain the operational problems behind the controls described in the secondary account of IFSCA’s framework.

Exchange approval and controls over system changes

IFSCA’s circular is claimed to require prior express exchange approval before a market participant deploys, offers or facilitates algorithmic trading. The secondary account also describes exchange powers to evaluate and monitor systems, suspend their operation or withdraw approval. These provisions have not been independently verified against the original circular. ^[2]

Technical approval is distinct from an assessment of whether a strategy will make money. The relevant questions include whether the system meets prescribed requirements, whether its order checks work and whether its behaviour can be monitored.

SEBI’s 2012 circular required prior exchange permission and initial conformance tests, meaning checks that a broker’s system satisfied specified requirements. Exchanges had to schedule those tests and communicate their outcome to the broker. ^[3]

Approval also involved continuing oversight. SEBI required brokers to inform exchanges about modifications to approved algorithms or the systems used to run them. Exchanges could require further testing of a modified algorithm or system against the circular’s requirements. ^[3]

A change to trading software can affect how orders are generated or checked. Notification and testing therefore address the system that is actually operating, rather than only the version examined when permission was first granted.

Emergency shutdowns and outstanding orders

IFSCA’s circular is claimed to include kill switches, or emergency controls for stopping automated trading. Their precise scope and activation requirements have not been independently verified from the complete document. ^[2]

Stopping new instructions and removing orders already submitted are separate operations. A system may cease generating orders while earlier instructions remain pending at the exchange.

SEBI’s 2012 circular expressly addressed both concerns. It required exchanges to identify dysfunctional algorithms, including those caught in a loop or runaway situation, and take suitable measures to stop them and remove their outstanding orders. Exchanges also had to be able to shut down a broker’s terminal in an emergency. ^[3]

At broker level, SEBI required predefined parameters for an automatic stop when an algorithm entered a loop or runaway situation. Brokers also had to maintain real-time monitoring to identify unexpected algorithm behaviour and immediately inform the exchange of such incidents. ^[3]

Those requirements separated automated safeguards from the responsibility to detect and report a malfunction. A stopping mechanism did not replace monitoring or incident reporting.

Price, quantity and pending-order checks

IFSCA’s circular is claimed to prescribe exchange-level price and quantity controls, alongside participant-level safeguards. The detailed requirements have not been independently verified against the original document. ^[2]

SEBI’s historical framework provides a documented explanation of the different checks. Its price check prevented an order from breaching exchange-defined price bands, which set permitted price boundaries. Its quantity check limited the amount of a security that could be included in an order. A separate order-value check restricted the monetary value of an individual instruction. ^[3]

For securities without price bands, SEBI required filters to act as an early warning system for sudden price increases. These were distinct from the fixed boundaries applied where an exchange had established a price band. ^[3]

An order can satisfy a price restriction but still contain an excessive quantity. Individual orders can also meet their limits while collectively creating a large volume of pending commitments.

SEBI therefore allowed brokers to prescribe a client-level check on cumulative open-order value: the total value of that client’s unexecuted orders released by the broker’s system. Algorithms also had to account for executed, unexecuted and unconfirmed orders before releasing further instructions. ^[3]

The distinction between those order states matters. An instruction awaiting confirmation cannot safely be treated as though it was never submitted.

Order flooding and the reported suspension threshold

IFSCA’s circular is claimed to allow graded charges for excessive order-to-trade ratios and to require real-time controls against order flooding. The secondary account describes a possible suspension of proprietary trading for the opening hour of the next session after penalties on more than ten occasions in a rolling 30-day period. These thresholds and consequences have not been independently verified. ^[2]

The order-to-trade ratio compares order activity with completed trades. It helps assess message traffic that does not result in a corresponding volume of executions. Proprietary trading means trading for a firm’s own account rather than for clients.

SEBI’s 2012 circular required economic disincentives for high daily order-to-trade ratios and monitoring systems to identify and impede possible order flooding. It did not specify the numerical suspension trigger described in the secondary account of IFSCA’s framework. ^[3]

The historical requirement and the reported IFSCA threshold should therefore remain distinct. The earlier SEBI document supports the background to order-flooding controls, but cannot verify the terms of the latest IFSC measure.

Audit trails, system reviews and unresolved transition rules

Records allow an exchange or auditor to reconstruct what an automated system did. SEBI required algorithmic orders to carry exchange-provided unique identifiers and required brokers to maintain logs of trading activity, control parameters, orders, trades and associated data. These records form an audit trail. ^[3]

IFSCA’s circular is claimed to require annual system audits, restrictions on consecutive appointments of the same auditor, and deadlines for reporting and correcting deficiencies. Those obligations have not been independently verified against the complete circular. ^[2]

A system audit examines technology and controls rather than merely checking financial accounts. Under SEBI’s 2012 circular, a broker’s annual system audit had to include a specific assessment of algorithmic-trading checks. Exchanges could require more frequent system audits where necessary. ^[3]

The secondary account also claims that IFSCA’s circular takes immediate effect, replaces earlier SEBI algorithmic-trading circulars insofar as they applied in the IFSC, and gives exchanges three months to implement necessary arrangements. Those commencement, replacement and transition provisions remain unverified. ^[2]

An effective date establishes when a measure takes effect, while an implementation deadline may allow time for specified operational changes. Without the complete IFSCA text, it remains unresolved how those provisions interact, which existing permissions continue and whether participants must obtain fresh approval for systems already operating.

References

1. International Financial Services Centres Authority, circular. Supplied official extract confirming issuance and the stated purpose of the guidelines; date not supplied. Publisher address: ifsca.gov.in.
2. CorpLawUpdates.in, secondary account of IFSCA’s algorithmic-trading guidelines for GIFT IFSC. The supplied account identifies a circular dated 16 October 2026 and states that it was last verified on that date. Publisher address: corplawupdates.in.
3. Securities and Exchange Board of India, Broad Guidelines on Algorithmic Trading, Circular CIR/MRD/DP/09/2012, dated 30 March 2012, pages 1-4. Supplied official text. Publisher address: sebi.gov.in.