Working with Calendars in SWIFT

You can set up multiple calendars for a given year. This enables logical terminals to have their own calendar, which can be useful if the LTs are located in different countries, with different working days or public holidays. If multiple calendars have been defined, then the available calendars are displayed when the Calendar application is started. This list also shows which Calendar is currently set as the default.You can use the Calendar application to create additional calendars.You have to set up a calendar if you want users to be able to schedule Alliance Access processes to occur automatically. Alliance Access … Continue reading Working with Calendars in SWIFT

MT 110 Advice of Cheque(s)

MT 110 Scope This multiple message is sent by a drawer bank, or a bank acting on behalf of the drawer bank to the bank on which a/several cheque(s) has been drawn (the drawee bank).It is used to advise the drawee bank, or confirm to an enquiring bank, the details concerning the cheque(s) referred to in the message. MT 110 Format Specifications Status Tag Field Name Content/Options No. M 20 Sender’s Reference 16x 1 O 53a Sender’s Correspondent A, B, or D 2 O 54a Receiver’s Correspondent A, B, or D 3 O 72 Sender to Receiver Information 6*35x 4 … Continue reading MT 110 Advice of Cheque(s)

MT 103 Single Customer Credit Transfer – Explanation for some important fields

MT 103: (1) Field 20: Sender’s Reference Format 16x Presence Mandatory Definition This field specifies the reference assigned by the Sender to unambiguously identify the message. Network Validated Rules This field must not start or end with a slash ‘/’ and must not contain two consecutive slashes ‘//’ (Error code(s): T26). Usage Rules This reference must be quoted in any related confirmation or statement, for example, MT 900, 910 and/or 950. When the cover method is used for a customer credit transfer, this reference must be quoted unchanged in field 21 of the related MT 202 COV. Example :20:Ref254 MT 103: … Continue reading MT 103 Single Customer Credit Transfer – Explanation for some important
fields

MT 700 Issue of a Documentary Credit – Explansation of important fields

MT 700: (6) Field 40E: Applicable Rules Format Option E 30x[/35x] (Applicable Rules)(Narrative) Presence Mandatory Definition This field specifies the rules the credit is subject to. Codes One of the following codes must be used in Applicable Rules (Error code(s): T59) EUCP LATEST VERSION The credit is subject to the version of the Supplement of the ICC Uniform Customs and Practice for Documentary Credits for Electronic Presentations, International Chamber of Commerce, Paris, France, which is in effect on the date of issue. EUCPURR LATEST VERSION The credit is subject to the version of the Supplement of the ICC Uniform Customs and … Continue reading MT 700 Issue of a Documentary Credit – Explansation of important fields

MT 202 General Financial Institution Transfer – Explanation of important fields

MT 202: (2) Field 21: Related Reference Format 16x Presence Mandatory Definition This field contains a reference to the related transaction Codes If the Sender is not the originator of the transaction and no related reference is received, the code NONREF must be used in this field. Network Validated Rules This field must not start or end with a slash ‘/’ and must not contain two consecutive slashes ‘//’ (Error code(s): T26). Usage Rules This field will contain a reference to the related transaction which is meaningful to the beneficiary institution, for example, the common reference in an MT 300 Foreign … Continue reading MT 202 General Financial Institution Transfer – Explanation of
important fields

SWIFT message block structure

SWIFT Financial Application (FIN) messages. They have the following structure:{1: Basic Header Block} {2: Application Header Block} {3: User Header Block} {4: Text Block or body} {5: Trailer Block}These five SWIFT message blocks include header information, the body of the message, and a trailer. All blocks have the same basic format:{ n:…}The curly braces ({}) indicate the beginning and end of a block. n is the block identifier, in this case a single integer between 1 and 5. Each block identifier is associated with a particular part of the message. There is no carriage return or line feed (CRLF) between blocks.Blocks 3, 4, and 5 may contain … Continue reading SWIFT message block structure

Hardware Security Modules

Hardware Security Modules (HSMs) are tamper-resistant hardware devices that customers useto safestore SWIFTNet Public Key Infrastructure (PKI) security profiles. The keys are generatedinside the HSM and stored encrypted in this device. SWIFT provides HSMs for use withSWIFTNet PKI. The installation and configuration of the HSM is embedded in the SWIFTNetLink. Access and use of the HSM is solely through the SWIFTNet Link . HSM products The following three HSM products store SWIFTNet PKI security profiles and are supported inSWIFTNet Link:• HSM tokena USB-based device which is supported in a Windows environment• HSM card and card readera USB-based device that is … Continue reading Hardware Security Modules

Creation of FIN Messages Page

Page Description ‘Create FIN Message’ Sender Logical Terminal (Top Right)The logical terminal that you want the message to be sent from. You can only send a messagefrom a logical terminal that is licensed for your installation. The value selected in SenderLogical Terminal determines the message syntax version to use.FIN Category (Top Right)You can select a message category from the ones that are available. Each category containsonly the messages that you are allowed to create (as defined in your operator profile).NameThe message type.IdentifierThe internal name of the message type.•DescriptionText that explains the business purpose of the message type.•VersionMessage Creation StepsTo create a new … Continue reading Creation of FIN Messages Page

SWIFTNET LINK: Features and Functions

Basic functionalityThe basic functionality of SWIFTNet Link includes transport, formatting, security, and servicemanagement. Through the SWIFTNet Link single-window concept, customers have a re-usableaccess infrastructure to SWIFTNet messaging services. Technical features SWIFTNet Link has the following features:• technical interoperability• application programming interfaces (APIs)• application programming interface functions• availability options• security management The role of SWIFTNet Link in the SWIFTNet architectureThe diagram illustrates the 3-layer SWIFTNet architecture. SWIFTNet Link resides in thecommunication level, which is level 2 of the network model. Continue reading SWIFTNET LINK: Features and Functions

What Is SWIFTNet Link?

Business software applications use the SWIFTNet Link (SNL) application programming interface (API) to access and use SWIFTNet services. The SNL is the mandatory network interface to SWIFTNet. SWIFTNet requires SNL for all external interfaces. The SNL also includes background processes that support messaging, security, and service management functions. The SNL is incorporated into SWIFTAlliance WebStation and SWIFTAlliance Gateway (SAG). SNL establishes a loosely coupled client/server relationship between business application components. Instead of directly invoking methods or functions, the interaction is message-oriented: structured messages are passed between client and server. A business application designed for SWIFTNet services generally consists of a … Continue reading What Is SWIFTNet Link?