caaa.014.001.09
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
%% AcceptorDiagnosticResponseV09 recursion level 0 with max 0
AcceptorDiagnosticResponseV09 *-- "1..1" Header59 : Header
AcceptorDiagnosticResponseV09 *-- "1..1" AcceptorDiagnosticResponse8 : DiagnosticResponse
AcceptorDiagnosticResponseV09 *-- "0..1" ContentInformationType31 : 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
%% Header59 recursion level 0 with max 1
class Header59{
MessageFunction MessageFunction42Code
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoNumber
ReTransmissionCounter IsoMax3NumericText
CreationDateTime IsoISODateTime
}
Header59 *-- "1..1" GenericIdentification176 : InitiatingParty
Header59 *-- "0..1" GenericIdentification177 : RecipientParty
Header59 *-- "0..0" Traceability8 : Traceability
%% GenericIdentification176 recursion level 1 with max 1
class GenericIdentification176{
Identification IsoMax35Text
Type PartyType33Code
Issuer PartyType33Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
%% GenericIdentification177 recursion level 1 with max 1
class GenericIdentification177{
Identification IsoMax35Text
Type PartyType33Code
Issuer PartyType33Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
GenericIdentification177 *-- "0..1" NetworkParameters7 : RemoteAccess
GenericIdentification177 *-- "0..1" Geolocation1 : Geolocation
%% Traceability8 recursion level 1 with max 1
class Traceability8{
ProtocolName IsoMax35Text
ProtocolVersion IsoMax6Text
TraceDateTimeIn IsoISODateTime
TraceDateTimeOut IsoISODateTime
}
Traceability8 *-- "1..1" GenericIdentification177 : RelayIdentification
Header59 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | MessageFunction42Code - Required 1..1 |
| ProtocolVersion | Version of the acquirer protocol specifications. | IsoMax6Text - Required 1..1 |
| ExchangeIdentification | Unique identification of an exchange occurrence. | IsoNumber - Required 1..1 |
| ReTransmissionCounter | Number of retransmissions of the message. | IsoMax3NumericText - Optional 0..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. | GenericIdentification176 - Required 1..1 |
| RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification177 - Optional 0..1 |
| Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability8 - Unknown 0..0 |
DiagnosticResponse building block
Information related to the diagnostic response. Diagnostic response from the acquirer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AcceptorDiagnosticResponse8 recursion level 0 with max 1
class AcceptorDiagnosticResponse8{
AcquirerAvailable IsoTrueFalseIndicator
}
AcceptorDiagnosticResponse8 *-- "1..1" CardPaymentEnvironment78 : Environment
AcceptorDiagnosticResponse8 *-- "0..1" TMSTrigger1 : TMSTrigger
%% CardPaymentEnvironment78 recursion level 1 with max 1
CardPaymentEnvironment78 *-- "0..1" Acquirer10 : Acquirer
CardPaymentEnvironment78 *-- "0..1" Organisation41 : Merchant
CardPaymentEnvironment78 *-- "0..1" PointOfInteraction12 : POI
CardPaymentEnvironment78 *-- "0..1" PaymentCard32 : Card
CardPaymentEnvironment78 *-- "0..1" Check1 : Check
CardPaymentEnvironment78 *-- "0..0" StoredValueAccount2 : StoredValueAccount
CardPaymentEnvironment78 *-- "0..0" LoyaltyAccount3 : LoyaltyAccount
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : CustomerDevice
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : Wallet
CardPaymentEnvironment78 *-- "0..1" Token1 : PaymentToken
CardPaymentEnvironment78 *-- "0..1" MerchantToken2 : MerchantToken
CardPaymentEnvironment78 *-- "0..1" Cardholder18 : Cardholder
CardPaymentEnvironment78 *-- "0..1" ContentInformationType32 : ProtectedCardholderData
CardPaymentEnvironment78 *-- "0..1" RetailerSaleEnvironment2 : SaleEnvironment
%% TMSTrigger1 recursion level 1 with max 1
class TMSTrigger1{
TMSContactLevel TMSContactLevel1Code
TMSIdentification IsoMax35Text
TMSContactDateTime IsoISODateTime
}
AcceptorDiagnosticResponse8 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment78 - Required 1..1 |
| TMSTrigger | Instructions for contacting the terminal management host. | TMSTrigger1 - Optional 0..1 |
| AcquirerAvailable | Indicates if the acquirer is available. | IsoTrueFalseIndicator - Optional 0..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
%% ContentInformationType31 recursion level 0 with max 1
class ContentInformationType31{
ContentType ContentType2Code
}
ContentInformationType31 *-- "1..1" AuthenticatedData8 : AuthenticatedData
%% AuthenticatedData8 recursion level 1 with max 1
class AuthenticatedData8{
Version IsoNumber
MAC IsoMax140Binary
}
AuthenticatedData8 *-- "1..0" IRecipient11Choice : Recipient
AuthenticatedData8 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData8 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType31 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). | AuthenticatedData8 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorDiagnosticResponseV09 implementation follows a specific implementaiton pattern. First of all, AcceptorDiagnosticResponseV09 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorDiagnosticResponseV09Document implements IOuterDocument. Because AcceptorDiagnosticResponseV09 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorDiagnosticResponseV09.
classDiagram
class IOuterRecord
AcceptorDiagnosticResponseV09 --|> IOuterRecord : Implements
AcceptorDiagnosticResponseV09Document --|> IOuterDocument~AcceptorDiagnosticResponseV09~ : Implements
class IOuterDocument~AcceptorDiagnosticResponseV09~ {
AcceptorDiagnosticResponseV09 Message
}
Document wrapper for serialization
The only real purpose AcceptorDiagnosticResponseV09Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.014.001.09’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorDiagnosticResponseV09.ToDocument() method. The returned AcceptorDiagnosticResponseV09Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorDiagnosticResponseV09Document *-- AcceptorDiagnosticResponseV09 : 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.09">
<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="_QrJMkU7TEeyGi9JAv6wq7Q"
nextVersions="_r4TxcXMbEe2vXY6MoVq19w"
previousVersion="_GhwTcS5JEeunNvJlR_vCbg"
name="AcceptorDiagnosticResponseV09"
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="_fMW_EL1vEeKoB-JG4saAMg_-385897474"
xmlTag="AccptrDgnstcRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_QrJMk07TEeyGi9JAv6wq7Q"
type="purpose" />
<messageBuildingBlock
xmi:id="_QrJMlU7TEeyGi9JAv6wq7Q"
nextVersions="_r4TxdXMbEe2vXY6MoVq19w"
previousVersion="_GhwTdS5JEeunNvJlR_vCbg"
name="Header"
definition="Diagnostic response message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_Rz5m4S_aEeugIJ3Gvoevmg" />
<messageBuildingBlock
xmi:id="_QrJMl07TEeyGi9JAv6wq7Q"
nextVersions="_r4Txd3MbEe2vXY6MoVq19w"
previousVersion="_GhwTdy5JEeunNvJlR_vCbg"
name="DiagnosticResponse"
definition="Information related to the diagnostic response."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="DgnstcRspn"
complexType="_HrRukU7TEeyGi9JAv6wq7Q" />
<messageBuildingBlock
xmi:id="_QrJMmU7TEeyGi9JAv6wq7Q"
nextVersions="_r4TxeXMbEe2vXY6MoVq19w"
previousVersion="_GhwTeS5JEeunNvJlR_vCbg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_dJxbAVFFEeyApZmLzm74zA" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="014"
flavour="001"
version="09" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.