Orchimate 1.4.2 /

JSE External Messaging API2.8.9

Orchestra Hub

Is used to identify the parent object (is set to null if this is the root object). This field is set by RTC, only set on outgoing messages on the reference data flow.

Is used to identify the reference data cache. This field is set by RTC, only set on outgoing messages on the reference data flow.

Identify the reason for the cache action (CACHE_ACTION), i.e. if it is an addition of a new reference data object, an update of an existing object or a removal of an object from the reference data cache. This field is set by RTC, only set on outgoing messages on the reference data flow.

A sequence number that is incremented with each reference data update, i.e. a version number for the cache contents. The sequence number series is common for all caches. This means that for a specific cache instance, the sequence number is not necessarily consecutive (but constantly increasing). This field is set by RTC, only set on outgoing messages on the reference data flow.

The id is unique among all objects and may be used to retrieve a specific instance. Do not however, try to interpret the contents. This field is set by RTC, only set on outgoing messages on the reference data flow.

The date and time of the latest modification for this reference data object. Format: yyyy-mm- ddTHH.MM.SS.sss. May be null if the object never has been updated. This field is set by RTC, only set on outgoing messages on the reference data flow.

The public ID of the participant. This id has to be unique.

Complete name of the member firm

Company postal address.

Company phone number.

Company fax address.

Name of contact person in compliance matters

Phone number to the compliance contact person

Mail address to the compliance contact person

Matching/BackOffice contact person

Phone number to the Matching/BackOffice contact person

Mail address to Matching/BackOffice contact person

Set to true if this member has been disabled.

The parent member, for example the parent of a trading member branch or a client.

The type of member. N.B. in the documentation member type is also known as Participant type.

The date from which the member is valid. The format is yyyy-MM-dd

A list of other markets'/exchanges' ID of this member in the format: market1:memberid1,market2:memberid2,... "maket1" is assumed to be a market defined in the "local" system and is automatically converted to uppercase, since this is the conversion for market ids in the system.

A comma separated list of Member Ids for which this member may act on behalf of.

The type of this participant unit.

Is Staff, true or false

Is Beneficial, true or false

Sub accounts are allowed, true or false

VAT registration number

Broker Deal Account number

Email

Country Code, e.g. ZA

Is Non Resident is true if country for the client is not equal to ZA

MemberId of the nominated member, fulfilling physical settlement when the actual member is not in the Equities market. Otherwise, set to the member itself.

Code of client or member at CSD.

If RTC should expect net payment from the JSE integration layer for this member. Required for clearing members.

This is set for clearing members only, to indicate its own trading member.

This field is mandatory for CMs. If true, RTC will expect system-to-system communication on size of FX collateral payments.

A comma-delimited list of market codes that the client is allowed to have trades and positions in.

This field is mandatory for CMs. If true, RTC will expect the CM to send in a response to a balancing event.

For clients only - type of client. Information to surveillance. Required for all clients.

For clients only - ID number. Required for local individual clients: Client Type = Individual AND isNonResident = FALSE

For clients only - Passport number. Required for foreign individual clients: Client Type = Individual AND isNonResident = TRUE

For clients only - Company registration number. Required for all company clients: Client Type = Company

For clients only - Information to surveillance. Required for all clients.

For clients only - Information to surveillance. Required for all clients.

Is Discretionary, true or false

Currency used for start of day collateral processing. Needs to be an eligible FX collateral currency (or ZAR, this will be the default though).

For TM branches only. Unique within a TM. Valid number is between 01 and 99.