StatusReportV04

catm.001.001.04

Informs the master terminal manager (MTM) or the terminal manager (TM) about the status of the acceptor system including the identification of the POI, its components and their installed versions.

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
%% StatusReportV04 recursion level 0 with max 0
StatusReportV04 *-- "1..1" Header14 : Header
StatusReportV04 *-- "1..1" StatusReport4 : StatusReport
StatusReportV04 *-- "1..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 status report. Set of characteristics related to the transfer of transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header14 recursion level 0 with max 1
class Header14{
    DownloadTransfer IsoTrueFalseIndicator
    FormatVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header14 *-- "1..1" GenericIdentification71 : InitiatingParty
Header14 *-- "0..1" GenericIdentification71 : RecipientParty
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
  

Header14 members

StatusReport building block

Status of the point of interaction (POI), its components and their installed versions. Status of the acceptor system containing the identification of the POI (Point Of Interaction), its components and their installed versions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% StatusReport4 recursion level 0 with max 1
StatusReport4 *-- "1..1" GenericIdentification71 : POIIdentification
StatusReport4 *-- "0..1" GenericIdentification71 : TerminalManagerIdentification
StatusReport4 *-- "1..1" TerminalManagementDataSet13 : DataSet
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% TerminalManagementDataSet13 recursion level 1 with max 1
class TerminalManagementDataSet13{
    SequenceCounter IsoMax9NumericText
}
TerminalManagementDataSet13 *-- "1..1" DataSetIdentification4 : Identification
TerminalManagementDataSet13 *-- "1..1" StatusReportContent4 : Content
  

StatusReport4 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 StatusReportV04 implementation follows a specific implementaiton pattern. First of all, StatusReportV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StatusReportV04Document implements IOuterDocument. Because StatusReportV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StatusReportV04.

classDiagram
    class IOuterRecord
    StatusReportV04 --|> IOuterRecord : Implements
    StatusReportV04Document --|> IOuterDocument~StatusReportV04~ : Implements
    class IOuterDocument~StatusReportV04~ {
        StatusReportV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    StatusReportV04Document *-- StatusReportV04 : 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.001.001.04">
    <StsRpt>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <StsRpt>
            <!-- StatusReport inner content -->
        </StsRpt>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </StsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_aFhi0WpIEeSxBNa3WmxpmQ"
  nextVersions="_XnwLEY3bEeW56qaqQ8B0kQ"
  previousVersion="_9sSXsTV9EeODSIIQsYYKhw"
  name="StatusReportV04"
  definition="Informs the master terminal manager (MTM) or the terminal manager (TM) about the status of the acceptor system including the identification of the POI, its components and their installed versions."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="StsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_aFhi02pIEeSxBNa3WmxpmQ"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_aFhi1WpIEeSxBNa3WmxpmQ"
    nextVersions="_XnwLFY3bEeW56qaqQ8B0kQ"
    previousVersion="_9sSXszV9EeODSIIQsYYKhw"
    name="Header"
    definition="Set of characteristics related to the transfer of the status report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_2MOHwWpIEeSR-ZWLvO-1dg" />
  <messageBuildingBlock
    xmi:id="_aFhi12pIEeSxBNa3WmxpmQ"
    nextVersions="_XnwLF43bEeW56qaqQ8B0kQ"
    previousVersion="_9sSXtTV9EeODSIIQsYYKhw"
    name="StatusReport"
    definition="Status of the point of interaction (POI), its components and their installed versions."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StsRpt"
    complexType="_yceqIWpJEeSR-ZWLvO-1dg" />
  <messageBuildingBlock
    xmi:id="_aFhi2WpIEeSxBNa3WmxpmQ"
    nextVersions="_XnwLGY3bEeW56qaqQ8B0kQ"
    previousVersion="_9sSXtzV9EeODSIIQsYYKhw"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_PwIbYWmPEeS7iYydEtv3Ug" />
  <messageDefinitionIdentifier
    businessArea="catm"
    messageFunctionality="001"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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