SWIFT Microgateway

Installation Guide

SWIFT Microgateway

Installation and Configuration Guide

This guide demonstrates how to install and configure SWIFT Microgateway. This document is intended for the
SWIFT Microgateway user community, and more specifically for the people appointed and SWIFT Microgateway
owners who will install and configure the software.

8 April 2022

Page 1
SWIFT Microgateway
Installation Guide

Table of Contents
1 Preface ............................................................................................................................................ 3
1.1 About this Document ............................................................................................................... 3
1.2 Purpose of this document ....................................................................................................... 3
1.3 Audience ................................................................................................................................. 3
1.4 SWIFT-Defined Terms ............................................................................................................ 3
1.5 Related Documentation ........................................................................................................... 3
2 Introduction to SWIFT Microgateway .......................................................................................... 4
3 How to use this Document ............................................................................................................ 5
3.1 SWIFT Microgateway Prerequisites ........................................................................................ 5
3.2 SWIFT Microgateway Software............................................................................................... 5
3.3 API Client Credentials ............................................................................................................. 5
3.4 SWIFT Microgateway Bootstrap Configuration ....................................................................... 5
3.5 SWIFT Microgateway Configuration and Operations.............................................................. 6
3.6 SWIFT Microgateway Open API Specification (OAS)............................................................. 6
4 Prerequisites .................................................................................................................................. 7
5 Downloading and Installing the SWIFT Microgateway package ............................................... 7
5.1 Download the SWIFT Microgateway ....................................................................................... 7
5.2 Verify JAR File Integrity ........................................................................................................... 9
5.3 Preparing the required TLS certificates .................................................................................. 9
6 SWIFT Microgateway bootstrap configuration ......................................................................... 10
6.1 Front-End GUI 1.0.6 .............................................................................................................. 10
6.1.1 SWIFT Microgateway Application Configuration ............................................................... 10
6.1.2 How to add an API GW, SAG or Software Certificate to SWIFT Microgateway 2.0 ......... 11
6.1.3 Alliance Gateway Configuration ........................................................................................ 13
6.1.4 Business Application Configuration................................................................................... 13
6.1.5 Forward Proxy Configuration ............................................................................................ 14
6.2 Front-End GUI 2.0.2 .............................................................................................................. 15
6.2.1 How to add an API GW, Alliance Gateway or Software Certificate to SWIFT
Microgateway 2.0 ........................................................................................................................... 15
6.2.2 Set Up API GW Configuration ........................................................................................... 17
6.2.3 Alliance Gateway Configuration ........................................................................................ 18
6.2.4 Business Application Configuration................................................................................... 18
6.2.5 Set Up SAG/SOFT Profiles ............................................................................................... 19
6.2.6 Forward Proxy Configuration ............................................................................................ 20
7 Making API calls to SWIFT Microgateway using Postman application .................................. 20
Legal Notices ....................................................................................................................................... 23

Page 2
SWIFT Microgateway
Installation Guide

1 Preface

1.1 About this Document

This document describes the installation and initial configuration of SWIFT Microgateway in
connection with its use to access SWIFT services and products that may be consumed through
SWIFT APIs.

This document is an extract of several sections of the SWIFT Microgateway Getting Started Guide.

SWIFT Microgateway is available in the form of a Java-based Spring Boot application.

Note: This installation guide, together with the SWIFT General Terms and Conditions and other
relevant SWIFT contractual documentation, is an important part of the contractual arrangements
between SWIFT and its customers for the provision and the use of SWIFT Microgateway to access
SWIFT Services through SWIFT APIs.

1.2 Purpose of this document

This document includes the following information:

1. Requirements for SWIFT Microgateway

2. How to download and install SWIFT Microgateway
3. How to set up SWIFT Microgateway bootstrap configuration
4. How to configure SWIFT Microgateway for consuming APIs made available through SWIFT API
platform
5. How to download and install SWIFT Microgateway Front-End GUI
6. How to use curl commands to configure SWIFT Microgateway using Microservices

1.3 Audience
This document is for appointed people who will install, configure, and manage the SWIFT
Microgateway for the customer institution.

1.4 SWIFT-Defined Terms

In the context of SWIFT documentation, certain terms have a specific meaning. These terms are
called SWIFT-defined terms (for example, customer, user, or SWIFT services and products). The
definitions of SWIFT-defined terms appear in the SWIFT Glossary.

1.5 Related Documentation

For an overview of the features and functions of SWIFT Microgateway, please refer to the
Microgateway Getting Started Guide.

Page 3
SWIFT Microgateway
Installation Guide

2 Introduction to SWIFT Microgateway

The following table demonstrates the similarities and differences between Microgateway versions
1.0.6 and 2.0.

Page 4
SWIFT Microgateway
Installation Guide

3 How to use this Document

Welcome to the SWIFT Microgateway Installation Guide. The aim of this document is to guide you
through the installation and initial configuration of the SWIFT Microgateway. This document will cover
versions 1.0.6 and 2.0.2, which are the current versions of the SWIFT Microgateway. It will also
include a note for customers migrating from SWIFT Microgateway 2.0.

Following the brief introduction to the SWIFT Microgateway as a product, several steps are outlined to
help complete the installation and configuration process.

3.1 SWIFT Microgateway Prerequisites

The hardware intended to run the SWIFT Microgateway must be installed in the SWIFT Secure zone.

Task 1: Meeting the Prerequisites

3.2 SWIFT Microgateway Software

Next is to acquire and install the SWIFT Microgateway package as explained in the tasks below. Once
accomplished, you will have the Getting Started Guide in the “docs” subfolder, which we will refer to
during the rest of the SWIFT Microgateway configuration.

Task 2: Downloading and Verifying the SWIFT Microgateway package

3.3 API Client Credentials

The next task involves identification of your API client application on the SWIFT Developer Portal. In
the Getting Started Guide, the sections to follow are in Setting up API Credentials and SWIFT
Microgateway.

Task 3: Follow the instructions in the following sections of the Getting Started Guide

o Sign up for SWIFT API Services

o Set Up Client Application Credentials
o Promote Client Application Credentials to Pilot and Live Environments

Note for migration: The application credentials can be reused if upgrading from SWIFT
Microgateway 1.0.6 to 2.0.2. If a separate installation of 2.0.2 is installed alongside an
existing SWIFT Microgateway instance, then an additional set of application credentials is
required.

3.4 SWIFT Microgateway Bootstrap Configuration

The SWIFT Microgateway configuration is contained in the application properties YAML file “config-
swift-mgw”, which is in the config folder of the SWIFT Microgateway installation. This file is encrypted
by the SWIFT Microgateway owner for additional protection on the configuration. The following sub-
tasks will explain the configurable parameters to start the SWIFT Microgateway. The configuration

Page 5
SWIFT Microgateway
Installation Guide

can be done through front-end configuration or manual editing. To use the Front-end, SWIFT
Microgateway must be up and running.

Task 4: Follow the instructions in the following sections of the Getting Started Guide

o Configure Application Properties

o Encrypt the properties file
o Decrypt the properties file
o Set Environment Variables
o API Sandbox Connectivity

Some of the configuration parameters for connectivity to SWIFT may require additional prerequisite
steps. You may have to provision a Business Certificate with the API roles for your Alliance Gateway
or configure a proxy in front of your VPN box.

o Setting up a Business Certificate

o Set Up Firewall and Forward Proxy Infrastructure

Note for migration: Most application properties can be reused from previous versions of SWIFT
Microgateway. For example, the one-way or two-way TLS setting can remain unchanged if the
keystore is copied to the location of the new SWIFT Microgateway instance.

3.5 SWIFT Microgateway Configuration and Operations

The next section will complete the SWIFT Microgateway configuration. This involves configuration of
internal connectivity (Alliance Gateway), security, and application profile mapping.

The parameters can be configured either through the Front-End GUI, or through direct interaction with
the Microservices with the REST examples provided.

Task 5: Follow the instructions in the following sections of the Getting Started Guide

o Starting the SWIFT Microgateway

o Stopping the Microgateway

Note for migration: The existing 1.0.6.x database cannot be reused for SWIFT Microgateway 2.0,
which uses the different data model. Configuration of application information in 2.0 is like the method
followed for previous versions. Screenshots and short explanations of how to use the Front-end GUI
can be found in the section: Configuring SWIFT Microgateway using the Front-End GUI.

Note for Linux users: The Microservices are also available through script.
Configuring Microgateway using Microservices (in Getting Started Guide)

3.6 SWIFT Microgateway Open API Specification (OAS)

SWIFT Microgateway, at regular intervals, automatically downloads the latest API
Specifications from SWIFT’s Central API Repository and refreshes itself on a regular basis.
This feature ensures SWIFT Microgateway is fully up-to-date with the API services and the
versions supported by the API Service Providers.

Task 6: Follow the instructions in the following sections of the Getting Started Guide

Page 6
SWIFT Microgateway
Installation Guide

o Open API Specification (OAS) Repository APIs

4 Prerequisites
The server in the SWIFT Secure zone hosting the SWIFT Microgateway must meet the following
requirements:

Operating system: Red Hat Enterprise Linux release 7.4 or later, IBM/AIX 7.2 or Microsoft Windows
10

Java Development Kit: For Windows 10 - Oracle Java Software Development Kit version for Java 8
For Linux - OpenJDK version 8
For AIX - IBM Java SE Version 8 on AIX

Minimum Recommended Hardware Requirements: 8 GB of RAM, 4 physical CPUs and 20 GB of

disk space

Preparatory information for SWIFT Microgateway configuration

SWIFT Microgateway has two configurations:

1. Bootstrap configuration: The bootstrap configuration is a YAML (Yet Another Markup Language) file
residing in the config directory of SWIFT Microgateway. This file contains the preliminary information
required to start the SWIFT Microgateway application.

This bootstrap configuration file can be edited using a text editor or SWIFT Microgateway Front-End
GUI.

2. Database configuration: SWIFT Microgateway uses an H2 database to store the information related
to the applications, certificates, API specification, and other things required to make a successful
business API call. SWIFT Microgateway provides Microservices with a way to manage the information
in the database.

The information in SWIFT Microgateway database can be configured using one of the following
options:

a) SWIFT Microgateway Front-End GUI

b) Postman - API client application

c) Configuration Utility script - configure-mgw.sh script is available under mgw-cli folder. This script is
for Linux and AIX OS.

d) Curl: you can use Curl commands to configure the H2 database.

If you choose to use Postman, then please refer to information provided by Postman references on
the Internet and plan accordingly. It is not a SWIFT product.

5 Downloading and Installing the SWIFT Microgateway

package

5.1 Download SWIFT Microgateway

Page 7
SWIFT Microgateway
Installation Guide

This topic describes how to download SWIFT Microgateway.

• SWIFT Microgateway is available for download through SWIFT Developer Portal:

https://developer.swift.com. You can sign up for an account or use your www.swift.com
credential to access the portal.

• SWIFT approves your account in SWIFT Developer Portal.

• Select and download the version of SWIFT Microgateway package.

• Extract the composite SWIFT Microgateway archive to a folder that is owned by the appointed
SWIFT Microgateway user at the Operating System level.

• After verification in the following section, you will see the “docs” subfolder from the extracted
archive, which has the Getting Started Guide and other documents applicable for SWIFT
Microgateway which can be used for reference.

Page 8
SWIFT Microgateway
Installation Guide

5.2 Verify JAR File Integrity

You can verify SWIFT Microgateway software integrity by executing the following command:

jarsigner -verbose -verify <jar name>

Note: “jarsigner” is a Java command. Therefore, be sure to locate this command in Java
Development Kit (JDK) bin directory.

The output includes:

• the X.509 certificate used for signing the .jar files

• the certificate validity period
• Digest algorithm (SHA-256)
• Signature algorithm and key length (SHA-256 with RSA and 2048 bits)
• Outcome of signature verification (verified or invalid)

5.3 Preparing the required TLS certificates

1. TLS certificate of SWIFT Microgateway application
This certificate is used by SWIFT Microgateway application during its startup. The certificate is stored
in a JKS keystore. You can use either a self-signed TLS certificate or a TLS certificate issued by your
own CA authority.

2. SWIFTNet 4K CA (Certificate Authority) certificate

This certificate can be downloaded from swift.com Download Centre or from the swift.com Knowledge
Base article 5024117. SWIFT Microgateway uses a one-way TLS connection to connect to SWIFT
API Gateway (in SWIFT Operating Centre) to make business API calls. For this purpose, you must
import the downloaded SWIFTNet 4K CA certificate to a JKS truststore.

3. Alliance Gateway certificate

This certificate is required only if you are using an HSM-based certificate for authentication and
authorisation of SWIFT API services. SWIFT Microgateway uses a one-way TLS connection to
connect to Alliance Gateway. For this purpose, you must import either Alliance Gateway certificate (if
self-signed) or the issuer of Alliance Gateway certificate into a JKS truststore.

4. TLS certificate of your back-office application

This certificate is required only when you use a two-way TLS connection between SWIFT
Microgateway and your back-office application. You must import the TLS certificate of your back-office
application into a JKS truststore so SWIFT Microgateway can trust the connection to your back-office
application.

Page 9
SWIFT Microgateway
Installation Guide

6 SWIFT Microgateway bootstrap configuration

6.1 Front-End GUI 1.0.6

The Microgateway Front-End permits an interactive configuration of Microgateway setting and
Business API applications. It is available with your MGW installation.

6.1.1 SWIFT Microgateway Application Configuration

The Bootstrap configuration provides the GUI with a way to configure both application properties in
the YAML file (note that this can also be done manually) and the application configuration parameters
that are stored in the embedded encrypted database on the local file system.

The default properties are given as an example in the “config-swift-mgw.yaml” file found in the config
directory of the installation. This can be modified or overwritten using the values that you provide in
the GUI.

In the “Create New Bootstrap Configuration” window, provide the inputs in the fields appropriately.
After the inputs are provided, click the “Generate content” button. The configuration file will be
generated in the large text box on that page.

You can download the generated configuration file when you click the “Download Unencrypted File”
button. You can copy this file to the config directory of your SWIFT Microgateway application.

If you are running SWIFT Microgateway on a Linux or AIX Operating System, then copy the
downloaded unencrypted file to the SWIFT Microgateway config directory on the Linux or AIX host
appropriately.

If you are running SWIFT Microgateway Front-End GUI and SWIFT Microgateway on the same
Windows host, then you can use the option to encrypt the configuration file directly by providing the
file path information, password for encryption and clicking on “Encrypt & Download Files.”

Start SWIFT Microgateway application

You will need the encrypted bootstrap configuration file (config-swift-mgw.yaml) to successfully start
the SWIFT Microgateway application.

Page 10
SWIFT Microgateway
Installation Guide

To encrypt SWIFT Microgateway bootstrap configuration file, you can use encrypt.sh (in Linux or AIX)
or encrypt.cmd (in Windows). You must provide a password (16-character length) for encryption. You
must remember this password for decryption later. If you have SWIFT Microgateway Front-End GUI to
create the encrypted configuration file, then you do not have to run this encrypt.cmd command.

Execute start.sh (in Linux or AIX) or start.cmd (in Windows).

6.1.2 How to add an API GW, SAG or Software Certificate to SWIFT

Microgateway 2.0

Configure the keystore and certificate information accordingly.

Page 11
SWIFT Microgateway
Installation Guide

a. For users using HSM-based certificates for authentication and authorisation to API services

a. Select menu Configure -> Keystore

b. Provide the JKS truststore file (full path with filename) that contains the SWIFT API
Gateway 4K CA certificate, as well as the alias name of the certificate, and set the
type as APIGW

c. Select menu Configure -> SAG

d. Provide the JKS truststore file (full path with filename) that contains the Alliance
Gateway certificate, as well as the alias name of the certificate, and set the type as
SAG

b. For users using Channel certificates (or Software certificates) for authentication and
authorisation to API services

a. Provide the JKS keystore file (full path with filename) that contains the channel
certificate (software certificate), as well as the alias name of the certificate, and set
the type as SOFT_CERT.

Use curl commands for SWIFT Microgateway configuration

If you are using Linux or AIX operating systems, and you are unable to have SWIFT Microgateway
Front-End GUI running on a Windows host to connect to the SWIFT Microgateway running on Linux
or AIX, then you can choose to use curl commands for SWIFT Microgateway configuration.

To configure SWIFT Microgateway, you have the option to use curl commands to invoke
Microservices.

The SWIFT Microgateway package includes configure-mgw.sh under folder packages -> mgw-cli.

This script provides curl commands with sample input data for the commands. You can edit the input
data and use the commands to do the configuration appropriately.

The execution of the curl command sequence must comply with the database schema definition of
SWIFT Microgateway to ensure appropriate configuration. Below is the sequence of information
updates that must be followed when invoking the Microservices for configuration using curl
commands.

1. Business Application Configuration

2. Business Application Client Credentials Configuration
3. Keystore Configuration for Alliance Gateway
4. Keystore Configuration for API Gateway
5. Alliance Gateway Configuration

Page 12
SWIFT Microgateway
Installation Guide

6. HTTP Proxy Configuration

You can execute the script as shown below:

configure-mgw.sh <ApplicationName> <profileId> <sharedSecret> <MGW host> <MGW port>

6.1.3 Alliance Gateway Configuration

If you are using a certificate stored on HSM hardware appliances (not USB tokens) to obtain an
OAuth token to perform Business API calls, then you must perform Alliance Gateway configuration.
Upload the public certificate used to establish a TLS connection between Alliance Gateway and
SWIFT Microgateway.

Go to “SAG” in the left menu and complete the Alliance Gateway, Message Partner, LAU and TLS
certificate information:

Note: At least one Alliance Gateway configuration must be marked as “Active.”

6.1.4 Business Application Configuration

To create a Business Application configuration used for Business API calls on SWIFT Microgateway,
go to “Business Application” in the left menu.

Select “Create New Business Application” and provide Application Name and Shared Secret with
values.

Each Application name must be associated with a Profile ID name. The DN associated with the Profile
ID will refer to a channel certificate, or a certificated stored on the Alliance Gateway HSM. The Profile
ID must have its own RBAC scope. It is recommended to use a specific RBAC scope for better
performance. See the Getting Started Guide for RBAC scope configuration.

Page 13
SWIFT Microgateway
Installation Guide

Each Business Application must have its related Application Credentials, which are the Consumer
Key and Consumer Secret. Select “Create” and complete the Application Credentials with the
Customer Key and Customer Secret obtained from the Developer Portal:

6.1.5 Forward Proxy Configuration

If you are using a proxy to handle the HTTP traffic, then provide the information using the Forward
Proxy link. Provide proxies: hostname/port and, if required, username/password.

Select “Create New Forward Proxy” and configure host, port, username and password:

Page 14
SWIFT Microgateway
Installation Guide

Continue to Postman Configuration to validate the SWIFT Microgateway configuration.

6.2 Front-End GUI 2.0.2

The Microgateway Front-End 2.0 permits an interactive configuration of Business API applications.
It is available with your MGW installation in the “front-end” subfolder. If there is a previous version of
the Front-End installed, then the Microgateway Front-End 2.0 will replace it. If you want to keep the
old installation, then please create a copy of the old Front-End directory and use the old version of the
GUI from this back-up folder.

After installation of SWIFT Microgateway Front-End 2.0, you can start the GUI application and
connect to the SWIFT Microgateway 2.0 instance of your choice. For this, you must specify the
correct host and port.

6.2.1 How to add an API GW, Alliance Gateway or Software Certificate to

SWIFT Microgateway 2.0

Previous versions of SWIFT Microgateway 2.0 have a different data model. SWIFT Microgateway 2.0
stores almost all certificates (except ones used to set up one-way or two-way TLS connections to
SWIFT Microgateway 2.0 instance) in the encrypted database. This means that you must provide a
public certificate (and a private key if required) in PEM format. For this purpose, you can use the
SWIFT Microgateway Front-End 2.0. It enables you to choose a keystore (a certificate through GUI). It
also reads certificate data in the correct format.

Go to the “Configuration” tab and select “Certificate” from the left menu.
Select “Create New Certificate” to make a new certificate.

Page 15
SWIFT Microgateway
Installation Guide

Select “Load from JKS” and provide a path to keystore, alias and password. If you add a Software
certificate, then you must provide a private key password as well. Select “Read” to load the certificate.

If everything is correct, then you will see that related fields will be filled with required values. Next,
select “Create:”

Page 16
SWIFT Microgateway
Installation Guide

6.2.2 Set Up API GW Configuration

To set up the certificate for TLS connection between SWIFT Microgateway and API GW host, go to
“API Gateway” in the left menu, select “Create New API Gateway” and import the SWIFT 4K CA
certificate.

Select the environment you want from the Environment dropdown, as well as the certificate to be
used to authenticate on the API Gateway. Then, select “Create.”

Page 17
SWIFT Microgateway
Installation Guide

6.2.3 Alliance Gateway Configuration

If you are using a hardware certificate footprint to obtain an OAuth token to perform Business API
calls, then you must perform Alliance Gateway configuration. Upload the Alliance Gateway public
certificate used to establish a TLS connection between Alliance Gateway and SWIFT Microgateway.

Go to “SAG” in the left menu.

Select “Create New SAG” and fill the required information with values. They may be the same as the
ones used for previous SWIFT Microgateway versions. In addition, you must choose the correct
certificate used for TLS connection with Alliance Gateway from the drop-down list.

Note: At least one Alliance Gateway configuration must be marked as “Active.”

6.2.4 Business Application Configuration

To create a Business Application configuration (used for Business API calls) and authenticate the
Back-Office application on SWIFT Microgateway 2.0, go to “Business Application” in the left menu.

Select “Create New Business Application” and complete the Business Application name and Shared
Secret values, which may have been used in a previous SWIFT Microgateway version. The values
must match the values configured in the API Business Application.

Page 18
SWIFT Microgateway
Installation Guide

Select “Create” and complete the Application Credentials with the Customer Key and Customer
Secret, obtained either from previous SWIFT Microgateway versions or the Developer Portal:

6.2.5 Set Up SAG/SOFT Profiles

The SAG/SOFT profiles will name a business application and link to the application profile previously
created. It includes the scope configuration, which can be used to restrict the scope of the business
application. It is recommended to restrict the scope as much as possible for better performance. See
the Getting Started Guide for RBAC scope configuration.

Select “SAG/SOFT Profiles” from the left menu and press “Create New SAG/SOFT Profile.”
Choose the profile type you want through the “Profile type” dropdown: SAG or SOFT.

Page 19
SWIFT Microgateway
Installation Guide

Provide all required credentials with values used for previous SWIFT Microgateway versions or new
values from drop-down lists: Business App name, RBAC scope, User DN or Certificate, and so on.

6.2.6 Forward Proxy Configuration

Configuration for forward proxy: if you need a forward proxy, then add hostname/port and, if required,
username/password.

For this, you must go to “Forward Proxy” in the left menu.

Select “Create New Forward Proxy” and configure host, port, username, and password:

7 Making API calls to SWIFT Microgateway using Postman

application
Postman is an API testing tool which is used by SWIFT for testing some of the API functionalities. The
Postman software can be obtained from https://www.postman.com. Note, SWIFT does not
recommend any API testing tool.

SWIFT Microgateway package contains Postman collection which can be imported to Postman
application. The Postman collection can be found in front-end folder in SWIFT Microgateway package,
with the file name “swift-mgw-1.0.6.x.postman_collection.json”.

The Postman collection has pre-built API requests grouped into folders based on their use case. This
Postman collection includes:
• API requests for invoking Microservices of SWIFT Microgateway: These API requests are
used for configuring and monitoring SWIFT Microgateway. The Microserver API requests are
authorised using API keys. These API keys are set in SWIFT Microgateway bootstrap
configuration file. You must configure the Postman collection's Microservice calls to use the
appropriate API key.
• API requests which submit business API calls to SWIFT Microgateway - These API requests
are used to make business calls to gpi APIs, gCASE APIs, and so on. You must configure
Postman collection's business API calls to have appropriate information about back-office
(back-office application name, profile ID, shared secret). The Postman collection includes
Pre-request scripts which set the configured back-office information as claims in the JWS
bearer token used for business API calls.

Page 20
SWIFT Microgateway
Installation Guide

To verify the SWIFT Microgateway 2.0 configuration, you can use the Postman collection, available in
the front-end-directory of the SWIFT Microgateway 2.0 package.

Upload it into Postman through the “Import” function and do not forget to specify connection values for
the whole Postman collection: Business Application name, Profile ID and Shared Secret. (Note that
the JSON collection is stored in the config folder of the MGW installation.)

You can invoke and make Microservice API calls from the Postman collection microservices folder.

Your bootstrap configuration will either be for the Live or Pilot environment. You can use Postman to
send an API call to either environment.

Page 21
SWIFT Microgateway
Installation Guide

Status codes 200 and 204 both mean that the Business API call is successful, and configuration has
been done correctly.

Page 22
SWIFT Microgateway
Installation Guide

Legal Notices
Copyright
SWIFT © 2022. All rights reserved.

Restricted Distribution
Do not distribute this publication outside your organisation unless your
subscription or order expressly grants you that right, in which case ensure you
comply with any other applicable conditions.

Disclaimer
The information in this publication may change from time to time. You must always
refer to the latest available version.

Translations
The English version of SWIFT documentation is the only official and binding version.

Trademarks
SWIFT is the trade name of S.W.I.F.T. SC. The following are registered trademarks of
SWIFT: 3SKey, Innotribe, MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the
Standards Forum logo, the SWIFT logo, SWIFT gpi with logo, the SWIFT gpi logo, and
UETR. Other product, service,or company names in this publication are trade names,
trademarks, or registered trademarks of their respective owners.

Page 23