caad.007.001.02
The Error message is sent by any party to any party (acquirer, agent or issuer) to indicate a message error.
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 %% ErrorV02 recursion level 0 with max 0 ErrorV02 *-- "1..1" Header45 : Header ErrorV02 *-- "1..1" Error1 : Body ErrorV02 *-- "0..1" ContentInformationType20 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Information related to the management of the protocol. Set of characteristics related to the protocol. Header for a rejection message. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header45 recursion level 0 with max 1 class Header45{ MessageFunction MessageFunction39Code ProtocolVersion IsoMax2048Text ExchangeIdentification IsoMax35Text ReTransmissionCounter IsoMax3NumericText CreationDateTime IsoISODateTime } Header45 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation Header45 *-- "1..1" GenericIdentification172 : InitiatingParty Header45 *-- "0..1" GenericIdentification172 : RecipientParty Header45 *-- "0..0" AdditionalData1 : TraceData Header45 *-- "0..0" Traceability7 : Traceability %% BatchManagementInformation1 recursion level 1 with max 1 class BatchManagementInformation1{ CollectionIdentification IsoMax35Text BatchIdentification IsoMax35Text MessageSequenceNumber IsoMax15NumericText MessageChecksumInputValue IsoMax140Binary } %% GenericIdentification172 recursion level 1 with max 1 class GenericIdentification172{ Identification IsoMax35Text Type PartyType17Code OtherType IsoMax35Text Assigner PartyType18Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% GenericIdentification172 recursion level 1 with max 1 class GenericIdentification172{ Identification IsoMax35Text Type PartyType17Code OtherType IsoMax35Text Assigner PartyType18Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% AdditionalData1 recursion level 1 with max 1 class AdditionalData1{ Type IsoMax35Text Value IsoMax2048Text } %% Traceability7 recursion level 1 with max 1 class Traceability7{ TraceDateTimeIn IsoISODateTime TraceDateTimeOut IsoISODateTime } Traceability7 *-- "1..1" GenericIdentification172 : RelayIdentification
Header45 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | MessageFunction39Code - Required 1..1 |
ProtocolVersion | Version of the acquirer to issuer protocol specifications. | IsoMax2048Text - Required 1..1 |
ExchangeIdentification | Unique identification of an exchange of messages between two parties. | IsoMax35Text - Optional 0..1 |
ReTransmissionCounter | Number of retransmission of the message. Incremented by one for each retransmission. | IsoMax3NumericText - Optional 0..1 |
CreationDateTime | Date and time at which the message was sent. | IsoISODateTime - Required 1..1 |
BatchManagementInformation | Information related to the batch and the collection to which the message belongs if any. | BatchManagementInformation1 - Optional 0..1 |
InitiatingParty | Unique identification of the partner that has initiated the exchange. | GenericIdentification172 - Required 1..1 |
RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification172 - Optional 0..1 |
TraceData | Information sent in the request message to be returned in the response one, for instance to help in the retrieval of the context of the exchange. ISO 8583:93/2003 bit 59 | AdditionalData1 - Unknown 0..0 |
Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability7 - Unknown 0..0 |
Body building block
Details of the rejection or message errors. Details of the error. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Error1 recursion level 0 with max 1 Error1 *-- "0..1" Context8 : Context Error1 *-- "1..1" Transaction101 : Transaction Error1 *-- "0..0" ProtectedData1 : ProtectedData Error1 *-- "0..0" SupplementaryData1 : SupplementaryData %% Context8 recursion level 1 with max 1 Context8 *-- "0..1" TransactionContext5 : TransactionContext %% Transaction101 recursion level 1 with max 1 class Transaction101{ OriginalMessage IsoMax100KBinary } Transaction101 *-- "1..1" TransactionIdentification12 : TransactionIdentification Transaction101 *-- "1..0" ErrorDetails1 : ErrorDetail Transaction101 *-- "0..0" AdditionalFee1 : AdditionalFees Transaction101 *-- "0..0" AdditionalData1 : AdditionalData %% ProtectedData1 recursion level 1 with max 1 class ProtectedData1{ ContentType ContentType3Code } ProtectedData1 *-- "0..1" EnvelopedData6 : EnvelopedData ProtectedData1 *-- "0..1" EncryptedData1 : EncryptedData %% SupplementaryData1 recursion level 1 with max 1 class SupplementaryData1{ PlaceAndName IsoMax350Text } SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
Error1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Context | Contains or describes conditions and characteristics of the transaction. | Context8 - Optional 0..1 |
Transaction | Error or rejection transaction. | Transaction101 - Required 1..1 |
ProtectedData | Contains protected data and the attributes used to protect the data. | ProtectedData1 - Unknown 0..0 |
SupplementaryData | Additional information that can not be captured in the structured fields and/or other specific block. | SupplementaryData1 - Unknown 0..0 |
SecurityTrailer building block
Trailer of the message containing a MAC. General cryptographic message syntax (CMS) containing encrypted data. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ContentInformationType20 recursion level 0 with max 1 class ContentInformationType20{ MAC IsoMax8HexBinaryText } ContentInformationType20 *-- "1..1" MACData1 : MACData %% MACData1 recursion level 1 with max 1 class MACData1{ Control IsoExact1HexBinaryText KeySetIdentifier IsoMax8NumericText DerivedInformation IsoMax32HexBinaryText Algorithm IsoMax2NumericText KeyLength IsoMax4NumericText KeyProtection IsoMax2NumericText KeyIndex IsoMax5NumericText PaddingMethod IsoMax2NumericText InitialisationVector IsoMax32HexBinaryText }
ContentInformationType20 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MACData | Type of data protection. ISO 8583:87 bit 53 or 110 ISO 8583:93 bit 53 or 111 ISO 8583:2003 bit 53 or 50 | MACData1 - Required 1..1 |
MAC | Message Authentication Code data. Binary, length of 8 ISO 8583 bit 64 or bit 128 | IsoMax8HexBinaryText - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the ErrorV02 implementation follows a specific implementaiton pattern. First of all, ErrorV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ErrorV02Document implements IOuterDocument. Because ErrorV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ErrorV02.
classDiagram class IOuterRecord ErrorV02 --|> IOuterRecord : Implements ErrorV02Document --|> IOuterDocument~ErrorV02~ : Implements class IOuterDocument~ErrorV02~ { ErrorV02 Message }
Document wrapper for serialization
The only real purpose ErrorV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caad.007.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ErrorV02.ToDocument() method. The returned ErrorV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram ErrorV02Document *-- ErrorV02 : 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:caad.007.001.02">
<Err>
<Hdr>
<!-- Header inner content -->
</Hdr>
<Body>
<!-- Body inner content -->
</Body>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</Err>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_ow6JocsZEeizUq4cFQ71-Q"
nextVersions="_27ZQwYgoEeu8-LhY4KPfWg"
previousVersion="_ohEDEHvSEeS2PZh7wUMQog"
name="ErrorV02"
definition="The Error message is sent by any party to any party (acquirer, agent or issuer) to indicate a message error. "
registrationStatus="Registered"
messageSet="_oFVkcKmaEeqA4rV5xCgycA"
xmlTag="Err"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_ow6wscsZEeizUq4cFQ71-Q"
nextVersions="_RHF8wdkcEeizh_fAW7LywQ _XWt78_5kEeiLerArw36g0w _27ZQw4goEeu8-LhY4KPfWg"
name="Header"
definition="Information related to the management of the protocol."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_VMnZ4VWsEeeiG_nL4vgKnQ" />
<messageBuildingBlock
xmi:id="_ow6ws8sZEeizUq4cFQ71-Q"
nextVersions="_XWujAf5kEeiLerArw36g0w _27Z30YgoEeu8-LhY4KPfWg"
name="Body"
definition="Details of the rejection or message errors."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Body"
complexType="_Eg5TJmqZEema8a4DGUe7Lw" />
<messageBuildingBlock
xmi:id="_ow6wtcsZEeizUq4cFQ71-Q"
nextVersions="_RHF8xdkcEeizh_fAW7LywQ _XWujA_5kEeiLerArw36g0w _27Z304goEeu8-LhY4KPfWg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
<messageDefinitionIdentifier
businessArea="caad"
messageFunctionality="007"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.