AcceptorDiagnosticResponseV02

caaa.014.001.02

The AcceptorDiagnosticResponse message is sent by the acquirer (or its agent) to provide to the acceptor the result of the diagnostic request.

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
%% AcceptorDiagnosticResponseV02 recursion level 0 with max 0
AcceptorDiagnosticResponseV02 *-- "1..1" Header1 : Header
AcceptorDiagnosticResponseV02 *-- "1..1" AcceptorDiagnosticResponse2 : DiagnosticResponse
AcceptorDiagnosticResponseV02 *-- "1..1" ContentInformationType6 : SecurityTrailer
  

Now, we will zero-in one-by-one on each of these building blocks.

Header building block

Diagnostic response message management information. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header1 recursion level 0 with max 1
class Header1{
    MessageFunction MessageFunction1Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header1 *-- "1..1" GenericIdentification32 : InitiatingParty
Header1 *-- "0..1" GenericIdentification32 : RecipientParty
Header1 *-- "0..0" Traceability1 : Traceability
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% Traceability1 recursion level 1 with max 1
class Traceability1{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability1 *-- "1..1" GenericIdentification31 : RelayIdentification
  

Header1 members

DiagnosticResponse building block

Information related to the diagnostic response. Diagnostic response from the acquirer. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorDiagnosticResponse2 recursion level 0 with max 1
AcceptorDiagnosticResponse2 *-- "1..1" CardPaymentEnvironment17 : Environment
AcceptorDiagnosticResponse2 *-- "0..1" TMSTrigger1 : TMSTrigger
%% CardPaymentEnvironment17 recursion level 1 with max 1
class CardPaymentEnvironment17{
    AcquirerParametersVersion IsoMax35Text
}
CardPaymentEnvironment17 *-- "0..1" GenericIdentification32 : MerchantIdentification
CardPaymentEnvironment17 *-- "1..1" GenericIdentification32 : POIIdentification
%% TMSTrigger1 recursion level 1 with max 1
class TMSTrigger1{
    TMSContactLevel TMSContactLevel1Code
    TMSIdentification IsoMax35Text
    TMSContactDateTime IsoISODateTime
}
  

AcceptorDiagnosticResponse2 members

SecurityTrailer building block

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

classDiagram
   direction tb
%% ContentInformationType6 recursion level 0 with max 1
class ContentInformationType6{
    ContentType ContentType1Code
}
ContentInformationType6 *-- "0..0" AuthenticatedData2 : AuthenticatedData
%% AuthenticatedData2 recursion level 1 with max 1
class AuthenticatedData2{
    Version IsoNumber
    MAC IsoMax35Binary
}
AuthenticatedData2 *-- "1..0" IRecipient2Choice : Recipient
AuthenticatedData2 *-- "1..1" AlgorithmIdentification3 : MACAlgorithm
AuthenticatedData2 *-- "1..1" EncapsulatedContent1 : EncapsulatedContent
  

ContentInformationType6 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorDiagnosticResponseV02 --|> IOuterRecord : Implements
    AcceptorDiagnosticResponseV02Document --|> IOuterDocument~AcceptorDiagnosticResponseV02~ : Implements
    class IOuterDocument~AcceptorDiagnosticResponseV02~ {
        AcceptorDiagnosticResponseV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AcceptorDiagnosticResponseV02Document *-- AcceptorDiagnosticResponseV02 : 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:caaa.014.001.02">
    <AccptrDgnstcRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <DgnstcRspn>
            <!-- DiagnosticResponse inner content -->
        </DgnstcRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrDgnstcRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="__eyjYQvgEeK9Xewg3qiFQA"
  nextVersions="_Rt4lYTTcEeO5e9wx3yvd8g"
  previousVersion="_QI8DtaMVEeCJ6YNENx4h-w_1442328644"
  name="AcceptorDiagnosticResponseV02"
  definition="The AcceptorDiagnosticResponse message is sent by the acquirer (or its agent) to provide to the acceptor the result of the diagnostic request."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrDgnstcRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="__eyjYwvgEeK9Xewg3qiFQA"
    nextVersions="_Rt4lYzTcEeO5e9wx3yvd8g"
    name="Header"
    definition="Diagnostic response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_SvV__wEcEeCQm6a_G2yO_w_677025486" />
  <messageBuildingBlock
    xmi:id="__eyjZwvgEeK9Xewg3qiFQA"
    nextVersions="_Rt4lZTTcEeO5e9wx3yvd8g"
    name="DiagnosticResponse"
    definition="Information related to the diagnostic response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DgnstcRspn"
    complexType="_ryRAURz1EeK5OKMB21JFBg" />
  <messageBuildingBlock
    xmi:id="__eyjawvgEeK9Xewg3qiFQA"
    nextVersions="_Rt4lZzTcEeO5e9wx3yvd8g"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_6DM4sQvFEeKzJ69IWwzB9Q" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="014"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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