Skip to main content

Swift Certificate Centre

The Swift Certificate Centre is your interface for managing your personal token and the PKI credentials, which identify the owner of the token. The personal tokens allow the authentication of individuals on certain Swift services.

Swift Certificate Centre

Get started

Get the Personal Token Software
Click on Read more to reach the Download Centre, search for the Personal Token Software, download it and install it 
Read more

Get Started with Web Connect
Click on Read more to download and install Web Connect
Read more

Activate your token 
Swift Certificate Centre portal user guide 
Read more 

How to use and manage personal tokens?

When you first receive your personal token, you must activate it on the Certificate Centre. The activation process generates your PKI private key on the token and allows you to set your personal password that protects access to your token. Your system would require some configuration in order to use the Swift Personal token.  

Web Connect is a client-side Windows application that enables web applications to communicate with tokens directly in the browser.  

To activate your token, insert it into a PC on which you have installed the token software and log in to the Swift Certificate Centre. The activation process starts automatically. You will be requested to enter the activation code, which you will receive from your security officer, and the initial token password, which you will receive from Swift. 

Fingerprint value

Swift PKI is the core security infrastructure, designed to enable customers to securely access applications and exchange information. 

Swift PKI provides certification services to entities, typically end users, applications, and Swift interfaces, enabling them to securely authenticate and/or to sign traffic. 

The certification services include the issuance and management of certificates (such as business, lite, channel, and web server certificates). 

Following mentioned fingerprint value can be used to validate the integrity of the certificate before adding to the respective trust store. 

The Internet browser or the operating system shows the sha1 digest at the moment a new certificate is being installed or when user can verify a certificate that is already installed in the Internet browser database or trust store. 

 

For Swift Root Certification Authority 
Subject DN: CN = Swift Root CA, O = S.W.I.F.T. SCRL, C = BE 

  • On Production: (sha1) 5f f7 b1 38 9e b0 5f 89 1c 4a 3e c6 7e 19 42 a4 e7 7d e9 46 
     

For Swift 3SKey SubCA Certification Authority Certificate  
Subject DN: CN = 3SKey CA, O = S.W.I.F.T. SCRL, C = BE 

  • On Production: (sha1) 09 59 32 b4 07 75 73 86 2c c3 69 70 e6 a7 f1 46 50 7d 70 e5 
     

For SwiftNet Certification Authority Certificate (4096 / 4K key length certificate) 
Subject DN: o = swift 

  • On ITB: (sha1) b4 4a 02 98 0f f1 fa 68 be 90 ca 9c b6 62 cd 98 1d 9f 09 76 
  • On Production: (sha1) a1 e3 7e 32 b1 bd 7c cd 30 39 1c b7 91 87 71 70 b4 61 f9 50 
Loading...