Introduction—ISO 20022 Financial Messages
The section introduces ISO 20022 financial messages and usage practices within TKEY7.

The ISO 20022 standard is a modern and universal financial messaging format of a new generation, which is being introduced to standardize payment processing rules, regardless of geographical region. The structure of the messages used in the exchange of information must correspond to the structure of the messages of the electronic repository posted on the site www.iso20022.org.
TKEY7 supports the generally accepted financial messages pacs.002, pacs.004, pacs.008, pacs.009, camt.026, camt.029, camt.030, camt.056, camt.087, as well as its messages tkey.001, tkey.002, developed based on the methodology of the ISO international standard 20022 and taking into account internal practices for use within the system. Business messages should be generated by the server part of the Member and sent to TKEY7 for transmission to another Member.
Message Catalog
The TKEY7 electronic repository on the GitHub resource contains templates of financial XML messages, XML schemas (XSD), and examples of ISO 20022 messages used by TKEY7 Members.
Examples of using financial messages are provided in the Scenarios section.
Message Structure
TKEY7 Members use business messages to exchange information. Messages are generated by the target automated server system of the Member and sent to TKEY7 for transmission to another Member.
A business message consists of two blocks: a business header and business content.
- The ISO 20022 head.001.001.03 message is used as the business header.
- ISO 20022 financial messages are used as business content. The message’s names and designations are given in the electronic repository.
Business Message Structure
<Message xmlns="urn:tkeysettlement"><AppHdr><!-- Business Header --></AppHdr><Document><!-- Business Content --></Document></Message>
When forming the structure of business messages, all namespaces must be qualified; it is necessary to use the namespace prefix in the data elements in the XML document.
Namespace Table
Prefix | Namespace |
---|---|
head | urn:iso:std:iso:20022:tech:xsd:head.001.001.03 |
tscisn | urn:iso:std:iso:20022:tech:xsd:tkey.001.001.01 |
tstsn | urn:iso:std:iso:20022:tech:xsd:tkey.002.001.01 |
tspsr | urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11 |
tspr | urn:iso:std:iso:20022:tech:xsd:pacs.004.001.10 |
tscct | urn:iso:std:iso:20022:tech:xsd:pacs.008.001.09 |
tsct | urn:iso:std:iso:20022:tech:xsd:pacs.009.001.09 |
tsuta | urn:iso:std:iso:20022:tech:xsd:camt.026.001.09 |
tsroi | urn:iso:std:iso:20022:tech:xsd:camt.029.001.11 |
tsnoca | urn:iso:std:iso:20022:tech:xsd:camt.030.001.05 |
tspcr | urn:iso:std:iso:20022:tech:xsd:camt.056.001.10 |
tsrtmp | urn:iso:std:iso:20022:tech:xsd:camt.087.001.08 |
A configuration XSD file has been prepared for TKEY7 Members for reading, checking, and creating XML messages. It is necessary to change the value of /path/to
in the schemaLocation
attribute according to the directory of the Member’s server system where the XSD files are located.
Configuration XSD File
<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns="urn:tkeysettlement"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:head="urn:iso:std:iso:20022:tech:xsd:head.001.001.03"xmlns:tscisn="urn:iso:std:iso:20022:tech:xsd:tkey.001.001.01"xmlns:tstsn="urn:iso:std:iso:20022:tech:xsd:tkey.002.001.01"xmlns:tspsr="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11"xmlns:tspr="urn:iso:std:iso:20022:tech:xsd:pacs.004.001.10"xmlns:tscct="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.09"
Rules Filling Business Header: Main Data Elements
<AppHdr><head:Fr><head:FIId><head:FinInstnId><!-- Registered BIC Code of the Message Sender --><head:BICFI>{bicfi}</head:BICFI><head:Othr><!-- Message Sender Member Identifier in TKEY7 --><head:Id>{member_identification}</head:Id>
Type | Description | Structure | Example |
---|---|---|---|
BizMsgIdr | Unique Business Message Identifier assigned by the message sender | B + TKEY + YYYYMMDD + BICFI + Prefix + RandomNumber. | BTKEY20220717BLUEUSNY001B0123456789 |
MsgDefIdr | Message Definition Identifier. | Business area + Message identifier + Variant + Version | pacs.008.001.09 |
CreDt | Date and time of business message creation. The time is normalized to the zero time zone — Z . | Year + Month + Day + T + Time + Z. | 2022-07-17T13:29:00Z |
BizMsgIdr Regex
^BTKEY([12]\d{3}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01]))([a-zA-Z]{4})([a-zA-Z]{2})(([2-9a-zA-Z]{1})([0-9a-np-zA-NP-Z]{1}))((([0-9a-wy-zA-WY-Z]{1})([0-9a-zA-Z]{2}))|([xX]{3})|11)[B,T]{1}[0-9]{10}$
BizMsgIdr Structure Description
Type | Description | Number of Characters |
---|---|---|
B | Business Message. | 1 |
TKEY | System Identifier. | 4 |
YYYYMMDD | Creation Date: year, month, day. | 8 |
BICFI | Registered BIC Code of the Financial Institution. | 11 |
Prefix | Prefix Identifying who created the message. B — Member, T — TKEY7. | 1 |
RandomNumber | Random Number. | 10 |
Data Elements and Filling Identifiers Rules
Type | Description | Structure | Example |
---|---|---|---|
MsgId | Unique Message Identifier. | YYYYMMDD + CcyCode + assetGroupId + RandomNumber + BICFI | 20220717USDDSO0123456789BLUEUSNY001 |
Id | Unique Case/Message/Notification Identifier. | YYYYMMDD + CcyCode + assetGroupId + RandomNumber + BICFI | 20220718USDDSA2772750489GRENCHZZ002 |
InstrId | Unique Instruction Identifier. | CcyCode + assetGroupId + YYYYMMDD + BICFI + Prefix + RandomNumber | USDDSO20220717BLUEUSNY001B123456789 |
EndToEndId | Unique End-To-End Identifier. | xxxxxxxxxxxx4xxxyxxxxxxxxxxxxxxx (UUIDv4) | 6cf0a51c25d6451cb6a5c2d684e70ae8 |
TxId | Unique Transaction Identifier. | xxxxxxxxxxxx4xxxyxxxxxxxxxxxxxxx (UUIDv4) | b6274536bdd247d4a671c5150e107dc5 |
EndToEndId/TxId Regex
^[0-9A-F]{8}[0-9A-F]{4}4[0-9A-F]{3}[89AB][0-9A-F]{3}[0-9A-F]{12}$
MsgId/Id Structure Description
Type | Description | Number of Characters |
---|---|---|
YYYYMMDD | Creation Date: year, month, day. | 8 |
CcyCode | Settlement Currency Three-letter Code. | 3 |
assetGroupId | Asset Group Identifier. | 3 |
RandomNumber | Random Number. | 10 |
BICFI | Registered BIC Code of the Financial Institution. | 11 |
MsgId/Id Regex
^([12]\d{3}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01]))[A-Z]{3}(DSO|DSA|XXX)[0-9]{10}([a-zA-Z]{4})([a-zA-Z]{2})(([2-9a-zA-Z]{1})([0-9a-np-zA-NP-Z]{1}))((([0-9a-wy-zA-WY-Z]{1})([0-9a-zA-Z]{2}))|([xX]{3})|11)$
InstrId Structure Description
Type | Description | Number of Characters |
---|---|---|
CcyCode | Settlement Currency Three-letter Code. | 3 |
assetGroupId | Asset Group Identifier. | 3 |
YYYYMMDD | Creation Date: year, month, day. | 8 |
BICFI | Registered BIC Code of the Financial Institution. | 11 |
Prefix | Prefix identifying who created the message. B — Member, T — TKEY7. | 1 |
RandomNumber | Random Number. | 9 |
InstrId Regex
^[A-Z]{3}(DSO|DSA|XXX)([12]\d{3}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01]))([a-zA-Z]{4})([a-zA-Z]{2})(([2-9a-zA-Z]{1})([0-9a-np-zA-NP-Z]{1}))((([0-9a-wy-zA-WY-Z]{1})([0-9a-zA-Z]{2}))|([xX]{3})|11)[B,T]{1}[0-9]{9}$