catm.003.001.08
Update of the acceptor configuration to be downloaded by the terminal management system.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram direction LR %% AcceptorConfigurationUpdateV08 recursion level 0 with max 0 AcceptorConfigurationUpdateV08 *-- "1..1" Header27 : Header AcceptorConfigurationUpdateV08 *-- "1..1" AcceptorConfiguration8 : AcceptorConfiguration AcceptorConfigurationUpdateV08 *-- "0..1" ContentInformationType18 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Set of characteristics related to the transfer of the acceptor parameters. Set of characteristics related to the transfer of transactions. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header27 recursion level 0 with max 1 class Header27{ DownloadTransfer IsoTrueFalseIndicator FormatVersion IsoMax6Text ExchangeIdentification IsoNumber CreationDateTime IsoISODateTime } Header27 *-- "1..1" GenericIdentification71 : InitiatingParty Header27 *-- "0..1" GenericIdentification92 : RecipientParty %% GenericIdentification71 recursion level 1 with max 1 class GenericIdentification71{ Identification IsoMax35Text Type PartyType5Code Issuer PartyType6Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% GenericIdentification92 recursion level 1 with max 1 class GenericIdentification92{ Identification IsoMax35Text Type PartyType5Code Issuer PartyType6Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } GenericIdentification92 *-- "0..1" NetworkParameters5 : RemoteAccess
Header27 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
DownloadTransfer | Indicates if the file transfer is a download or an upload. | IsoTrueFalseIndicator - Required 1..1 |
FormatVersion | Version of file format. | IsoMax6Text - Required 1..1 |
ExchangeIdentification | Unique identification of an exchange occurrence. | IsoNumber - Required 1..1 |
CreationDateTime | Date and time at which the file or message was created. | IsoISODateTime - Required 1..1 |
InitiatingParty | Unique identification of the partner that has initiated the exchange. | GenericIdentification71 - Required 1..1 |
RecipientParty | Unique identification of the partner that is the recipient of the exchange. | GenericIdentification92 - Optional 0..1 |
AcceptorConfiguration building block
Acceptor configuration to be downloaded from the terminal management system. Acceptor configuration to be downloaded from the terminal management system. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AcceptorConfiguration8 recursion level 0 with max 1 AcceptorConfiguration8 *-- "1..1" GenericIdentification71 : TerminalManagerIdentification AcceptorConfiguration8 *-- "1..0" TerminalManagementDataSet27 : DataSet %% GenericIdentification71 recursion level 1 with max 1 class GenericIdentification71{ Identification IsoMax35Text Type PartyType5Code Issuer PartyType6Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% TerminalManagementDataSet27 recursion level 1 with max 1 class TerminalManagementDataSet27{ SequenceCounter IsoMax9NumericText ConfigurationScope PartyType15Code } TerminalManagementDataSet27 *-- "1..1" DataSetIdentification7 : Identification TerminalManagementDataSet27 *-- "0..0" GenericIdentification71 : POIIdentification TerminalManagementDataSet27 *-- "1..1" AcceptorConfigurationContent8 : Content
AcceptorConfiguration8 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
TerminalManagerIdentification | Identification of the terminal management system (TMS) sending the acceptor parameters. | GenericIdentification71 - Required 1..1 |
DataSet | Data set containing the acceptor parameters of a point of interaction (POI). | TerminalManagementDataSet27 - Unknown 1..0 |
SecurityTrailer building block
Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing data. protected by a MAC or a digital signature. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ContentInformationType18 recursion level 0 with max 1 class ContentInformationType18{ ContentType ContentType2Code } ContentInformationType18 *-- "0..1" AuthenticatedData5 : AuthenticatedData ContentInformationType18 *-- "0..1" SignedData5 : SignedData %% AuthenticatedData5 recursion level 1 with max 1 class AuthenticatedData5{ Version IsoNumber MAC IsoMax140Binary } AuthenticatedData5 *-- "1..0" IRecipient6Choice : Recipient AuthenticatedData5 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm AuthenticatedData5 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent %% SignedData5 recursion level 1 with max 1 class SignedData5{ Version IsoNumber Certificate IsoMax5000Binary } SignedData5 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm SignedData5 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent SignedData5 *-- "0..0" Signer4 : Signer
ContentInformationType18 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
AuthenticatedData | Data protection by a message authentication code (MAC). | AuthenticatedData5 - Optional 0..1 |
SignedData | Data protected by a digital signatures. | SignedData5 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorConfigurationUpdateV08 implementation follows a specific implementaiton pattern. First of all, AcceptorConfigurationUpdateV08 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorConfigurationUpdateV08Document implements IOuterDocument. Because AcceptorConfigurationUpdateV08 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorConfigurationUpdateV08.
classDiagram class IOuterRecord AcceptorConfigurationUpdateV08 --|> IOuterRecord : Implements AcceptorConfigurationUpdateV08Document --|> IOuterDocument~AcceptorConfigurationUpdateV08~ : Implements class IOuterDocument~AcceptorConfigurationUpdateV08~ { AcceptorConfigurationUpdateV08 Message }
Document wrapper for serialization
The only real purpose AcceptorConfigurationUpdateV08Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catm.003.001.08’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorConfigurationUpdateV08.ToDocument() method. The returned AcceptorConfigurationUpdateV08Document value will serialize correctly according to ISO 20022 standards.
classDiagram AcceptorConfigurationUpdateV08Document *-- AcceptorConfigurationUpdateV08 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:catm.003.001.08">
<AccptrCfgtnUpd>
<Hdr>
<!-- Header inner content -->
</Hdr>
<AccptrCfgtn>
<!-- AcceptorConfiguration inner content -->
</AccptrCfgtn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</AccptrCfgtnUpd>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_yuPRkdXyEeia9rtBTv_9KA"
nextVersions="_EBcV0QuhEeqw5uEXxQ9H4g"
previousVersion="_Uqp2QdqIEeearpaEPXv9UA"
name="AcceptorConfigurationUpdateV08"
definition="Update of the acceptor configuration to be downloaded by the terminal management system."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AccptrCfgtnUpd"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_yuP4odXyEeia9rtBTv_9KA"
type="purpose" />
<messageBuildingBlock
xmi:id="_yuQfsdXyEeia9rtBTv_9KA"
nextVersions="_EBc84wuhEeqw5uEXxQ9H4g"
previousVersion="_Uqp2RdqIEeearpaEPXv9UA"
name="Header"
definition="Set of characteristics related to the transfer of the acceptor parameters."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_4lU_YY3bEeW32YMP0mBeyw" />
<messageBuildingBlock
xmi:id="_yuQfs9XyEeia9rtBTv_9KA"
nextVersions="_EBc85QuhEeqw5uEXxQ9H4g"
previousVersion="_Uqp2R9qIEeearpaEPXv9UA"
name="AcceptorConfiguration"
definition="Acceptor configuration to be downloaded from the terminal management system."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AccptrCfgtn"
complexType="_U7DgMdXzEeia9rtBTv_9KA" />
<messageBuildingBlock
xmi:id="_yuQftdXyEeia9rtBTv_9KA"
nextVersions="_EBc85wuhEeqw5uEXxQ9H4g"
previousVersion="_Uqp2SdqIEeearpaEPXv9UA"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC or a digital signature."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="__DJZ4dtZEee9e6xduATmQg" />
<messageDefinitionIdentifier
businessArea="catm"
messageFunctionality="003"
flavour="001"
version="08" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.