casr.002.001.02
The SettlementReportingResponse message is sent by any party (acquirer, agent or issuer) to an agent in response to a SettlementReportingInitiation message.
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
%% SettlementReportingResponseV02 recursion level 0 with max 0
SettlementReportingResponseV02 *-- "1..1" Header66 : Header
SettlementReportingResponseV02 *-- "1..1" SettlementReportingResponse2 : Body
SettlementReportingResponseV02 *-- "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 fee collection message. ISO 8583 MTI For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Header66 recursion level 0 with max 1
class Header66{
MessageFunction MessageFunction29Code
ProtocolVersion IsoMax2048Text
ExchangeIdentification IsoMax35Text
ReTransmissionCounter IsoMax3NumericText
CreationDateTime IsoISODateTime
}
Header66 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation
Header66 *-- "1..1" GenericIdentification183 : InitiatingParty
Header66 *-- "0..1" GenericIdentification183 : RecipientParty
Header66 *-- "0..0" AdditionalData1 : TraceData
Header66 *-- "0..0" Traceability9 : Traceability
%% BatchManagementInformation1 recursion level 1 with max 1
class BatchManagementInformation1{
CollectionIdentification IsoMax35Text
BatchIdentification IsoMax35Text
MessageSequenceNumber IsoMax15NumericText
MessageChecksumInputValue IsoMax140Binary
}
%% GenericIdentification183 recursion level 1 with max 1
class GenericIdentification183{
Identification IsoMax35Text
Type PartyType17Code
OtherType IsoMax35Text
Assigner PartyType18Code
Country ISOMax3ACountryCode
ShortName IsoMax35Text
}
%% GenericIdentification183 recursion level 1 with max 1
class GenericIdentification183{
Identification IsoMax35Text
Type PartyType17Code
OtherType IsoMax35Text
Assigner PartyType18Code
Country ISOMax3ACountryCode
ShortName IsoMax35Text
}
%% AdditionalData1 recursion level 1 with max 1
class AdditionalData1{
Type IsoMax35Text
Value IsoMax2048Text
}
%% Traceability9 recursion level 1 with max 1
class Traceability9{
TraceDateTimeIn IsoISODateTime
TraceDateTimeOut IsoISODateTime
}
Traceability9 *-- "1..1" GenericIdentification183 : RelayIdentification
Header66 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | MessageFunction29Code - 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. | GenericIdentification183 - Required 1..1 |
| RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification183 - 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. | AdditionalData1 - Unknown 0..0 |
| Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability9 - Unknown 0..0 |
Body building block
Information related to the response to the settlement initiation.
ISO 8583:87 bit 110 ISO 8583:93 bit 111 ISO 8583:2003 bit 50 Information related to the settlement response message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SettlementReportingResponse2 recursion level 0 with max 1
SettlementReportingResponse2 *-- "1..1" Environment27 : Environment
SettlementReportingResponse2 *-- "0..1" Context17 : Context
SettlementReportingResponse2 *-- "1..1" Transaction139 : Transaction
SettlementReportingResponse2 *-- "1..1" ProcessingResult13 : ProcessingResult
SettlementReportingResponse2 *-- "0..0" ProtectedData1 : ProtectedData
SettlementReportingResponse2 *-- "0..0" SupplementaryData1 : SupplementaryData
%% Environment27 recursion level 1 with max 1
Environment27 *-- "0..1" PartyIdentification263 : SettlementInstitution
Environment27 *-- "0..1" PartyIdentification263 : Originator
Environment27 *-- "0..1" PartyIdentification263 : Sender
Environment27 *-- "0..1" PartyIdentification263 : Receiver
Environment27 *-- "0..1" PartyIdentification263 : Destination
Environment27 *-- "0..1" FinancialInstitution6 : FinancialInstitution
Environment27 *-- "0..1" PartyIdentification258 : OtherInstitution
%% Context17 recursion level 1 with max 1
Context17 *-- "0..1" TransactionContext10 : TransactionContext
%% Transaction139 recursion level 1 with max 1
class Transaction139{
TransactionDescription IsoMax1000Text
}
Transaction139 *-- "1..1" TransactionIdentification12 : TransactionIdentification
Transaction139 *-- "0..0" AdditionalFee2 : AdditionalFee
Transaction139 *-- "0..0" AdditionalData1 : AdditionalData
%% ProcessingResult13 recursion level 1 with max 1
class ProcessingResult13{
ApprovalCode IsoExact6AlphaNumericText
}
ProcessingResult13 *-- "0..1" ApprovalEntity2 : ResponseSource
ProcessingResult13 *-- "1..1" ResultData8 : ResultData
ProcessingResult13 *-- "0..0" ErrorDetails2 : ErrorDetail
ProcessingResult13 *-- "0..1" ResultData7 : OriginalResultData
ProcessingResult13 *-- "0..0" AdditionalInformation29 : AdditionalInformation
%% 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
SettlementReportingResponse2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | Environment27 - Required 1..1 |
| Context | Contains or describes conditions and characteristics of the transaction. | Context17 - Optional 0..1 |
| Transaction | Card transaction for which an authorisation is requested. | Transaction139 - Required 1..1 |
| ProcessingResult | Processing results of the settlement service. | ProcessingResult13 - 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 SettlementReportingResponseV02 implementation follows a specific implementaiton pattern. First of all, SettlementReportingResponseV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SettlementReportingResponseV02Document implements IOuterDocument. Because SettlementReportingResponseV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SettlementReportingResponseV02.
classDiagram
class IOuterRecord
SettlementReportingResponseV02 --|> IOuterRecord : Implements
SettlementReportingResponseV02Document --|> IOuterDocument~SettlementReportingResponseV02~ : Implements
class IOuterDocument~SettlementReportingResponseV02~ {
SettlementReportingResponseV02 Message
}
Document wrapper for serialization
The only real purpose SettlementReportingResponseV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:casr.002.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SettlementReportingResponseV02.ToDocument() method. The returned SettlementReportingResponseV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SettlementReportingResponseV02Document *-- SettlementReportingResponseV02 : 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:casr.002.001.02">
<SttlmRptgRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<Body>
<!-- Body inner content -->
</Body>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</SttlmRptgRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_VxHn5Mr9EeuNe7RtB4qFHw"
name="SettlementReportingResponseV02"
definition="The SettlementReportingResponse message is sent by any party (acquirer, agent or issuer) to an agent in response to a SettlementReportingInitiation message.
"
registrationStatus="Registered"
messageSet="_kT2-dARsEeWTJNHF-ohSqw"
xmlTag="SttlmRptgRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_VxHn5cr9EeuNe7RtB4qFHw"
name="Header"
definition="Information related to the management of the protocol."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_aRA58RynEeyVgKPonV4SjQ" />
<messageBuildingBlock
xmi:id="_VxHn5sr9EeuNe7RtB4qFHw"
name="Body"
definition="Information related to the response to the settlement initiation.

ISO 8583:87 bit 110
ISO 8583:93 bit 111
ISO 8583:2003 bit 50"
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Body"
complexType="_KfS0QYwFEeugeuahCxXQ-Q" />
<messageBuildingBlock
xmi:id="_VxHn58r9EeuNe7RtB4qFHw"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC"
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
<messageDefinitionIdentifier
businessArea="casr"
messageFunctionality="002"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.