AcceptorConfigurationUpdateV05

catm.003.001.05

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
%% AcceptorConfigurationUpdateV05 recursion level 0 with max 0
AcceptorConfigurationUpdateV05 *-- "1..1" Header27 : Header
AcceptorConfigurationUpdateV05 *-- "1..1" AcceptorConfiguration5 : AcceptorConfiguration
AcceptorConfigurationUpdateV05 *-- "0..1" ContentInformationType12 : 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

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
%% AcceptorConfiguration5 recursion level 0 with max 1
AcceptorConfiguration5 *-- "1..1" GenericIdentification71 : TerminalManagerIdentification
AcceptorConfiguration5 *-- "1..0" TerminalManagementDataSet19 : DataSet
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% TerminalManagementDataSet19 recursion level 1 with max 1
class TerminalManagementDataSet19{
    SequenceCounter IsoMax9NumericText
    ConfigurationScope PartyType15Code
}
TerminalManagementDataSet19 *-- "1..1" DataSetIdentification6 : Identification
TerminalManagementDataSet19 *-- "0..0" GenericIdentification71 : POIIdentification
TerminalManagementDataSet19 *-- "1..1" AcceptorConfigurationContent5 : Content
  

AcceptorConfiguration5 members

SecurityTrailer building block

Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing protected data. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContentInformationType12 recursion level 0 with max 1
class ContentInformationType12{
    ContentType ContentType2Code
}
ContentInformationType12 *-- "0..1" EnvelopedData4 : EnvelopedData
ContentInformationType12 *-- "0..1" AuthenticatedData4 : AuthenticatedData
ContentInformationType12 *-- "0..1" SignedData4 : SignedData
ContentInformationType12 *-- "0..1" DigestedData4 : DigestedData
%% EnvelopedData4 recursion level 1 with max 1
class EnvelopedData4{
    Version IsoNumber
}
EnvelopedData4 *-- "1..0" IRecipient4Choice : Recipient
EnvelopedData4 *-- "0..1" EncryptedContent3 : EncryptedContent
%% AuthenticatedData4 recursion level 1 with max 1
class AuthenticatedData4{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData4 *-- "1..0" IRecipient4Choice : Recipient
AuthenticatedData4 *-- "1..1" AlgorithmIdentification15 : MACAlgorithm
AuthenticatedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData4 recursion level 1 with max 1
class SignedData4{
    Version IsoNumber
    Certificate IsoMax5000Binary
}
SignedData4 *-- "1..0" AlgorithmIdentification16 : DigestAlgorithm
SignedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
SignedData4 *-- "1..0" Signer3 : Signer
%% DigestedData4 recursion level 1 with max 1
class DigestedData4{
    Version IsoNumber
    Digest IsoMax140Binary
}
DigestedData4 *-- "1..1" AlgorithmIdentification16 : DigestAlgorithm
DigestedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
  

ContentInformationType12 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the AcceptorConfigurationUpdateV05 implementation follows a specific implementaiton pattern. First of all, AcceptorConfigurationUpdateV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorConfigurationUpdateV05Document implements IOuterDocument. Because AcceptorConfigurationUpdateV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorConfigurationUpdateV05.

classDiagram
    class IOuterRecord
    AcceptorConfigurationUpdateV05 --|> IOuterRecord : Implements
    AcceptorConfigurationUpdateV05Document --|> IOuterDocument~AcceptorConfigurationUpdateV05~ : Implements
    class IOuterDocument~AcceptorConfigurationUpdateV05~ {
        AcceptorConfigurationUpdateV05 Message
     }
  

Document wrapper for serialization

The only real purpose AcceptorConfigurationUpdateV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catm.003.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorConfigurationUpdateV05.ToDocument() method. The returned AcceptorConfigurationUpdateV05Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    AcceptorConfigurationUpdateV05Document *-- AcceptorConfigurationUpdateV05 : 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.05">
    <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="_T1XqUY32EeWRwov1g9WL_A"
  nextVersions="_wnsp0bAHEeah1_v59tW6Rg"
  previousVersion="_fjjzoWpaEeS4r8z7dKyh1g"
  name="AcceptorConfigurationUpdateV05"
  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="_T1XqU432EeWRwov1g9WL_A"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_T1XqVY32EeWRwov1g9WL_A"
    nextVersions="_wnsp1bAHEeah1_v59tW6Rg"
    previousVersion="_fjjzpWpaEeS4r8z7dKyh1g"
    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="_T1XqV432EeWRwov1g9WL_A"
    nextVersions="_wnsp17AHEeah1_v59tW6Rg"
    previousVersion="_fjjzp2paEeS4r8z7dKyh1g"
    name="AcceptorConfiguration"
    definition="Acceptor configuration to be downloaded from the terminal management system."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AccptrCfgtn"
    complexType="_aLzn8Y32EeWRwov1g9WL_A" />
  <messageBuildingBlock
    xmi:id="_T1XqWY32EeWRwov1g9WL_A"
    nextVersions="_wnsp2bAHEeah1_v59tW6Rg"
    previousVersion="_fjjzqWpaEeS4r8z7dKyh1g"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_PwIbYWmPEeS7iYydEtv3Ug" />
  <messageDefinitionIdentifier
    businessArea="catm"
    messageFunctionality="003"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.