Technical Accreditation Overview

Technical accreditation is a mandatory requirement for all systems connecting to CSP in the production environment.  Technical accreditation is to be completed by software providers, either system vendors or CHESS Users developing their own in-house system. 

Technical accreditation comprises of two components, connectivity and messaging:

• Connectivity Accreditation: testing connectivity and resiliency.

• Messaging Accreditation: demonstrating compliance with new message formats.  Messaging accreditation covers, ISO 20022 messages, FIX messaging and Ledger API commands.  As CHESS Users have optionality on how they access CSP, messaging accreditation depends on the connectivity choice you make for that functionality.

Connectivity accreditation will apply to the system directly interfacing to CHESS Replacement.

Message accreditation will apply to the system that generates the ISO 20022 message construct (either the ISO 20022 messages or DAML commands via the Ledger API)

Scenario 1: the host system generates the ISO 20022 message and sends it to the adapter, which acts as a transport layer to the CSP. Messaging accreditation will apply to the host system and connectivity accreditation will apply to the adapter system.  Noting where multiple host systems use a common adapter, each host system will be required to be message accredited for the message they support.

This scenario is also applicable to SWIFTNet usage.

Scenario 2: the host system provides the raw data to the adapter system, which then generates the ISO 20022 message to send to CSP.  Both messaging and connectivity accreditation will apply to the adapter system.

For example if a host system sends a file, proprietary message format, ISO 15022 or any other format to the adapter that is subsequently translated by the adapter to ISO20022 only the adapter is required to be message accredited.

For further information on technical accreditation, refer to the below documentation.