At this time, there are six scenarios for consumption of DSB data: Users get the DSB ISIN and associated product attributes from the counterparty to the trade or the venue on which the trade was executed User Action: No contract needed with the DSB – click here for the DSB PROD Registration form and complete section […]

Given the DSB’s industry utility status, we are following standardised processes for on-boarding of users on the DSB service. To this end, we have created a standard set of documents that address the majority of the on-boarding questions we have received from industry – contained in the User Agreement, accompanying policies, the attached document and […]

Every valid ISIN request submitted to the DSB will be returned with the CFI code as part of the ISIN record. The CFI code is constructed from 6 attributes that are either explicitly submitted by the user (in cases where there are multiple choices for a specific instrument) or derived by the DSB (in cases […]

This is an attribute of the ISIN and the value of this field is to be “NA” for all OTC Derivatives as the ISIN definition does not contain any issuer information.

DSB ISINs are created for multiple purposes by users and the existence of any given ISIN does not guarantee its existence in FIRDs based on whether or not industry has a requirement to submit it to meet Reference Data Reporting obligations. FIRDs reporting requirement begins on 3rd January 2018 for all relevant parties that are […]

The primary focus of the DSB has been to ensure market participants can meet their regulatory obligations to create OTC-ISINs as and when a new instrument is quoted or traded for the first time rather than to make available the pre-seeding of the entire universe of potential OTC-ISINs. The reason for this approach is that […]