An ISIN is the identifier that allows a security to be held and settled in dematerialised form. For an issuer in GIFT City, obtaining one is rarely a single-step exercise: it sits at the end of a chain of corporate approvals, registrar appointments and depository documentation.
This guide sets out how issuers generally approach the process and where engagements most often lose time.
When an ISIN is required
Broadly, an ISIN is needed wherever a security must exist in dematerialised form — including debt instruments, units and equity, depending on the structure.
- Issuance of debt securities or notes
- Preparation for listing on an exchange
- Creation of dematerialised units in a fund structure
- Corporate actions affecting existing securities
The documentation chain
Most delays are documentation delays. Corporate authorisations must match the instrument being issued, the registrar agreement must be in place, and KYC records for authorised signatories must be current.
- Constitutional documents and incorporation records
- Board or committee resolutions authorising the issue
- Instrument term sheet or offer documentation
- Registrar and transfer agent agreement
Where issuers lose time
Three patterns recur: approvals drafted before instrument terms are final, registrar appointment left too late, and signatory records that have not been refreshed. Each requires a resubmission cycle rather than a clarification.
How Gateway handles it
Gateway runs ISIN as an event-based execution: requirement analysis, a documentation pack built against your specific instrument, coordination with the registrar and depository, and handover of the final records — tracked in your client portal throughout.
