Iso20022

AcceptorDiagnosticRequestV03

caaa.013.001.03

The AcceptorDiagnosticRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to check the end-to-end communication, to test the availability of this acquirer, or to validate the security environment.

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
%% AcceptorDiagnosticRequestV03 recursion level 0 with max 0
AcceptorDiagnosticRequestV03 *-- "1..1" Header7 : Header
AcceptorDiagnosticRequestV03 *-- "1..1" AcceptorDiagnosticRequest3 : DiagnosticRequest
AcceptorDiagnosticRequestV03 *-- "1..1" ContentInformationType8 : SecurityTrailer

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

Header building block

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

classDiagram
   direction tb
%% Header7 recursion level 0 with max 1
class Header7{
    MessageFunction MessageFunction4Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header7 *-- "1..1" GenericIdentification32 : InitiatingParty
Header7 *-- "0..1" GenericIdentification32 : RecipientParty
Header7 *-- "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

Header7 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction4Code - Required 1..1
ProtocolVersion Version of the acquirer protocol specifications. IsoMax6Text - Required 1..1
ExchangeIdentification Unique identification of an exchange occurrence. IsoMax3NumericText - Required 1..1
CreationDateTime Date and time at which the message was created. IsoISODateTime - Required 1..1
InitiatingParty Unique identification of the partner that has initiated the exchange. GenericIdentification32 - Required 1..1
RecipientParty Unique identification of the partner that is the recipient of the message exchange. GenericIdentification32 - Optional 0..1
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability1 - Unknown 0..0

DiagnosticRequest building block

Information related to the diagnostic request. Diagnostic request from an acceptor. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorDiagnosticRequest3 recursion level 0 with max 1
AcceptorDiagnosticRequest3 *-- "1..1" CardPaymentEnvironment29 : Environment
%% CardPaymentEnvironment29 recursion level 1 with max 1
class CardPaymentEnvironment29{
    AcquirerAvailabilityRequested IsoTrueFalseIndicator
}
CardPaymentEnvironment29 *-- "1..1" Acquirer2 : Acquirer
CardPaymentEnvironment29 *-- "0..1" GenericIdentification32 : MerchantIdentification
CardPaymentEnvironment29 *-- "0..1" GenericIdentification32 : POIIdentification
CardPaymentEnvironment29 *-- "0..0" PointOfInteractionComponent4 : POIComponent

AcceptorDiagnosticRequest3 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment29 - Required 1..1

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
%% ContentInformationType8 recursion level 0 with max 1
class ContentInformationType8{
    ContentType ContentType1Code
}
ContentInformationType8 *-- "0..0" AuthenticatedData3 : AuthenticatedData
%% AuthenticatedData3 recursion level 1 with max 1
class AuthenticatedData3{
    Version IsoNumber
    MAC IsoMax35Binary
}
AuthenticatedData3 *-- "1..0" IRecipient3Choice : Recipient
AuthenticatedData3 *-- "1..1" AlgorithmIdentification10 : MACAlgorithm
AuthenticatedData3 *-- "1..1" EncapsulatedContent2 : EncapsulatedContent

ContentInformationType8 members

Member name Description Data Type / Multiplicity
ContentType Type of data protection. ContentType1Code - Required 1..1
AuthenticatedData Data protection by a message authentication code (MAC). AuthenticatedData3 - Unknown 0..0

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorDiagnosticRequestV03 --|> IOuterRecord : Implements
    AcceptorDiagnosticRequestV03Document --|> IOuterDocument~AcceptorDiagnosticRequestV03~ : Implements
    class IOuterDocument~AcceptorDiagnosticRequestV03~ {
        AcceptorDiagnosticRequestV03 Message
     }

Document wrapper for serialization

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

classDiagram
    AcceptorDiagnosticRequestV03Document *-- AcceptorDiagnosticRequestV03 : 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.013.001.03">
    <AccptrDgnstcReq>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <DgnstcReq>
            <!-- DiagnosticRequest inner content -->
        </DgnstcReq>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrDgnstcReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_nWbGATTaEeO5e9wx3yvd8g"
  nextVersions="_DZFgwWpAEeS4VPLpYyQgxQ"
  previousVersion="_7YW5gQvgEeK9Xewg3qiFQA"
  name="AcceptorDiagnosticRequestV03"
  definition="The AcceptorDiagnosticRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to check the end-to-end communication, to test the availability of this acquirer, or to validate the security environment."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrDgnstcReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_nh4IEDTaEeO5e9wx3yvd8g"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_nWbGAzTaEeO5e9wx3yvd8g"
    nextVersions="_DZFgxWpAEeS4VPLpYyQgxQ"
    previousVersion="_7YW5gwvgEeK9Xewg3qiFQA"
    name="Header"
    definition="Diagnostic request message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_UNSh8S9IEeOlZIh7PImd0A" />
  <messageBuildingBlock
    xmi:id="_nWbGBTTaEeO5e9wx3yvd8g"
    nextVersions="_DZFgx2pAEeS4VPLpYyQgxQ"
    previousVersion="_7YW5hwvgEeK9Xewg3qiFQA"
    name="DiagnosticRequest"
    definition="Information related to the diagnostic request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DgnstcReq"
    complexType="_eDmqETTKEeO5e9wx3yvd8g" />
  <messageBuildingBlock
    xmi:id="_nWbGBzTaEeO5e9wx3yvd8g"
    nextVersions="_DZFgyWpAEeS4VPLpYyQgxQ"
    previousVersion="_7YW5iwvgEeK9Xewg3qiFQA"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_KpedcTF5EeO118ZQJgaQSQ" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="013"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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