Skip to main content
  • English
    Discover SWIFT
  • Español
    Descubra nuestros contenidos en español
  • Français
    Découvrez notre contenu disponible en français
  • 中文
  • 日本語
This content is not available in the selected language

Steps to apply and join our community as a Swift user

1. Create your user account

I have a user account

Proceed directly to step 2.

I don't have a user account

Create your account using the user registration form.
Watch the video or read the user guide for further instructions.

Create account

Swift Scholarship

2. Register your organisation

You now need to register your organisation in the onboarding application click "New Onboarding Request" and complete the "Organisation Registration form".

A sales representative in your region will contact you to define and evaluate your Swift membership user category, as well as your Messaging and Connectivity needs.

Register organisation

3. Start the formal application

Following your discussion with a sales representative, you will receive a formal proposal to join Swift, covering the Swift Member(user)ship category, Messaging and Connectivity options. As soon as you accept the Swift proposal, Swift will validate your organisation’s registration and quotation information.

Following validation, you will receive an email from with a link (access to the Onboarding tool) to initiate the formal onboarding process to become a Swift user.

Download the Quick Starter Guide


4. Provide data and legal documents and familiarise yourself with the Customer Security Programme (CSP)

As an applicant Swift user, you need to comply with one of the defined Swift user categories as stated in the Swift Corporate Rules.
Subject to the Swift user category in which you apply, you need to provide supporting documentation and information details related to your organisation.
List of documents - Detailed guidance and requirements

Swift reserves the right to request additional documents in the scope of its Know Your Customer- usership, validation process.  Failure to provide the documents in a timely manner or insufficient evidence of its compliance with the eligibility criteria and conditions for admission may be a cause for rejection of an application file or a ground for Swift not to commence the admission process or validate the application.

You will be guided through the different steps in the Onboarding tool to provide information for the following sections: Legal, Configuration, Financial.

On your side, the person who initiated the application will be the point of contact throughout the onboarding process. However, different tasks of the application process may be delegated to a colleague, completed in parallel and submitted independently.

You will also familiarise yourself with the Customer Security Programme (CSP) and the Security controls that apply to your connectivity, to understand what is required to complete a Security Attestation and to perform an Independent Assessment regarding your compliance towards the security controls.

Prepare for a review of your infrastructure; we strongly recommend that you set up a specialist team to address this task. Note that access to specific documentation will be granted after step 5.

The submission of a security attestation is a prerequisite for your live activation on the Swift network. You will receive more information about this when you reach step 6.

Read more about the Customer Security Programme

ISO 20022 adoption

5. Receive legal acceptance and have your BIC created

Once your information and documents have been validated and are in compliance with admission conditions, Swift will confirm in writing

What is a BIC code?

6. Place your orders, proceed to implementation and submit your security attestation (CSP)

Once you have been approved as a Swift User,

  • Swift will set up your administrators including access to Support, Knowledge Centre and Swift Smart (online training platform).
  • Swift will set up your Security Officers (own Security Officers will receive secure cards and secrets which will require receipt confirmation. Once set up, they will have access to the Secure Channel and Security Officer guide document.
  • If applicable, Swift will prepare the draft order(s) based on your quotation. Your administrators need to review and approve the final order(s). See the administrator guidelines.
  • Depending on your choice of connectivity, Swift will dispatch any required components (e.g. Alliance Lite2 tokens, VPNs, software and Security Officer secure code cards and secrets). Please follow instructions in the shipment parcels carefully as some items require receipt confirmation.

Implement and install your chosen connectivity and interface products:For Swift supplied connectivity, a Swift Implementation Consultant will contact you.For shared connectivity, please consult with your connectivity provider/owner on next steps.

In parallel to implementation, as part of the Customer Security Programme (CSP), and applicable to all Swift users, in the KYC-SA application, you will:

  • Implement a set of security controls defined by Swift to protect your environment. Those controls establish a security baseline for the entire Swift community. 
  • Submit a Security Attestation in the KYC-SA application, in which you attest your level of compliance against those controls for your newly created BIC(s) and share the details of the Independent Assessment performed to evaluate your compliance towards the security controls.

KYC-SA application

Security attestation support page

Your administrators will receive an email within five working days following legal approval advising the ‘KYC-SA portal’ is open.
Your infrastructure provider will assist you with identifying your Architecture Type.

7. Get your Swift messaging service activated

Once you have installed your chosen connectivity and interface products, you can test your connection.

  • For Swift cloud-based connectivity, the activation date of your BIC will be agreed with the Swift implementation consultant .
  • For own or shared connectivity, you need to confirm your operational readiness and preferred activation within the Onboarding portal, date following satisfactory implementation and testing. To request your activation allow eight days notice (Friday of previous week).

Activations occur every Saturday, pending:

  • your successful completion of the CSP Security Attestation
  • your payment of any outstanding invoices
  • your operational readiness email confirmation by Swift

Log in to the Onboarding portal