Info Center

The Info Center provides a compact overview of the basic requirements for participating in the SIC system, as well as the initial steps for connecting to the system.

Quick Access

Participation in the SIC System

Requirements for participation in the SIC system are the fulfilment of the SNB’s (Swiss Na-tional Bank) criteria in accordance with its instruction sheet on admission to the SIC system and sight deposit accounts and that of SIC Ltd.  A participant always takes part in the SIC RTGS service. If customer payments (pacs.008) are used, the participant must also join the SIC IP service (instant payments) and be reachable for at least IP customer payments.

Requests to participate in SIC should always be addressed to the SNB (customer@snb.ch). After confirmation of admission by the SNB and SIC Ltd and the signing of contract, it will take approximately six to ten weeks (depending on the participant’s infrastructure and gateway as well as successfully completed testing) until the new participant is connected to the system and the two services (RTGS and, if applicable, IP service).

As a rule, participation can only begin on the first bank working day of a new month. The prerequisite to this is that all necessary technical and legal requirements have been met and confirmed by the 10th of the previous month. If this has not been done, the participation date will be postponed by at least one month. New participants and their participation dates are published under “Mutations in the Bank Master" on our website bankenstamm.ch.

A participant may terminate their participation in writing with three months’ notice, effective at the end of a month. Termination notices must be addressed to both the SNB and SIC Ltd, as contractual relationships exist with both parties. The same applies in the case of a merger between two participants.

If a participant no longer meets the participation requirements, the SNB may exclude them from the system. The SNB also reserves the right to issue extraordinary termination, for example, if a participant significantly violates the system’s regulations.

Connection to the SIC System

Each participant requires technical access ("access route") to the respective SIC service. A participant triggers an action in the respective service via an access route, e.g. by submitting a payment or query. They also receive messages, e.g. payments made by another participant in their favour or information generated by the service. An access route requires a corresponding network. Standard participants must choose between the following two access routes: Messaging Gateway or Swift.

If applicable, technical access is provided via a service bureau. This ensures system connectivity for participants without their own infrastructure.

Access routes

Messaging Gateway is used if the participant is connected to SIC via Secure Swiss Finance Network (SSFN) or P2P networks.

Participants with a direct connection via the SSFN network must be connected redundantly and via multiple carriers. This requirement also applies to the connection of service bureaux that offer SIC connectivity to their customers.

Connection software from third-party companies
If a software manufacturer develops the connection software on behalf of one or more participants, SIC Ltd requires a letter of confirmation from one of the participants. It should be noted that any testing line to a third-party company as well as authentication and encryption equipment can only be ordered on behalf of and at the expense of a participant.

A service bureau ensures that participants without a direct connection are connected to the relevant service via the Messaging Gateway. The service bureau receives the transactions shared by the participant themselves or their service provider and delivers them to the SIC system. The transactions delivered by the SIC system are forwarded to the participant themselves or to their service provider. The service bureau is connected to the SIC system with its own communication interface without being a participant itself.

Message exchange with a service bureau
Regardless of the access route: if the connection is made via a service bureau, message exchanges with the service bureau must be made via the same secure network as message exchanges from that service bureau with the SIC system. The SSFN is recommended for this purpose. The exchange of messages via internet connections is not allowed.

The connection from the participant to the service bureau and the integrity and authenticity of the data are exclusively the responsibility of the participant.

Requirements for service bureaux
Only service bureaux that meet the requirements defined by the SNB are permitted. The minimum requirements and the description of the certification (attestation) process can be found in the requirements document. The list of approved service bureaux is shown below.

The following rule applies when selecting the access route Messaging Gateway or Swift: Participants must connect to the SIC system via the access route Messaging Gateway. Exception: Standard participants with an average of less than 1,000 outgoing transactions and less than CHF 100 million turnover per clearing day may use the access route Swift. Different Swift services are used depending on the SIC service and the use case.

Web portal

The web portal is a supplement to the Messaging Gateway and Swift gateways. This allows certain use cases to be triggered manually, the settlement account to be queried and investigations to be carried out online. Access is via IP networks such as SSFN or the internet with a corresponding browser  and is secured by a certificate or SwissID issued by third-party providers.

The web portal cannot be used as exclusive access and is mandatory for participants via Swift.

Security Solution for the SIC System

SIX Advanced Security Server (SASS) security solution, which consists of software and hardware components and organisational measures, is used for the Messaging Gateway and for backup submission and delivery. SASS It guarantees the secure and unadulterated transmission of messages within the Swiss financial center infrastructure.

A participant is obliged to make the mandatory and optional arrangements for the installation and operation of SASS – with the CH-HSM and SASS software components.

Please note that SIX has not tested all combinations of HSM firmware versions and SASS software versions. SIX communicates the combinations of SASS software and HSM firmware that have undergone extensive testing. Other combinations are possible, but we recommend conducting thorough tests.

Primus S2-Serie HSM (CH-HSM)

Securosys has designed the Primus S2-Series HSM specifically for the SIC system. The three available models S4, S6, and S6P are all PQC ready and can be managed by the Decanus Remote Access Management Device. Detailed information and technical specifications can be found on the Securosys website.

Ordering
To order the HSM, please use the corresponding form available on the SIC Extranet. The signed form is to be sent directly to Securosys (sales@securosys.ch).

Documentation and firmware
Documentations and HSM firmware versions (firmware updates) can be downloaded from the Securosys Support Center at any time.

SASS software

The SASS software – deployed by Elca Informatik AG – is used as the software module. In the password-protected SIC Extranet, the following information can be found and accessed:

  • Onboarding/Setup Instructions for SASS 2.x
  • SASS software and release documentation
  • Public SASS certificates 
  • Form: Confirmation of Security Officer
Any questions?

We are happy to help

Get in touch