Iso20022

ReconciliationResponse

cain.008.001.01

The ReconciliationResponse message is sent by an issuer or an agent to return the reconciled totals for debits, credits, chargebacks and other transactions.

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
%% ReconciliationResponse recursion level 0 with max 0
ReconciliationResponse *-- "1..1" Header17 : Header
ReconciliationResponse *-- "1..1" AcquirerReconciliationResponse1 : ReconciliationResponse
ReconciliationResponse *-- "0..1" ContentInformationType15 : SecurityTrailer

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

Header building block

Information related to the protocol management. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header17 recursion level 0 with max 1
class Header17{
    MessageFunction MessageFunction6Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    ReTransmissionCounter IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header17 *-- "1..1" GenericIdentification73 : InitiatingParty
Header17 *-- "0..1" GenericIdentification73 : RecipientParty
Header17 *-- "0..0" Traceability3 : Traceability
%% GenericIdentification73 recursion level 1 with max 1
class GenericIdentification73{
    Identification IsoMax35Text
    Type PartyType9Code
    Issuer PartyType9Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification73 recursion level 1 with max 1
class GenericIdentification73{
    Identification IsoMax35Text
    Type PartyType9Code
    Issuer PartyType9Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% Traceability3 recursion level 1 with max 1
class Traceability3{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability3 *-- "1..1" GenericIdentification74 : RelayIdentification

Header17 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction6Code - Required 1..1
ProtocolVersion Version of the acquirer to issuer protocol specifications. IsoMax6Text - Required 1..1
ExchangeIdentification Unique identification of an exchange occurrence. IsoMax3NumericText - Required 1..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
InitiatingParty Unique identification of the partner that has initiated the exchange. GenericIdentification73 - Required 1..1
RecipientParty Unique identification of the partner that is the recipient of the message exchange. GenericIdentification73 - Optional 0..1
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability3 - Unknown 0..0

ReconciliationResponse building block

Information related to the response to a reconciliation. Information related to the response to a reconciliation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcquirerReconciliationResponse1 recursion level 0 with max 1
AcquirerReconciliationResponse1 *-- "1..1" CardTransactionEnvironment5 : Environment
AcquirerReconciliationResponse1 *-- "1..1" CardTransaction10 : Transaction
%% CardTransactionEnvironment5 recursion level 1 with max 1
CardTransactionEnvironment5 *-- "1..1" GenericIdentification73 : SendingInstitution
CardTransactionEnvironment5 *-- "1..1" GenericIdentification73 : ReceivingInstitution
CardTransactionEnvironment5 *-- "1..1" GenericIdentification73 : SettlementInstitution
%% CardTransaction10 recursion level 1 with max 1
class CardTransaction10{
    InterBankSettlementDate IsoISODate
    InitiatorTransactionDateTime IsoISODateTime
    InitiatorTransactionIdentification IsoMax35Text
    TransactionLifeCycleIdentification IsoMax35Text
}
CardTransaction10 *-- "0..1" TransactionIdentifier2 : Reconciliation
CardTransaction10 *-- "0..1" TransactionTotals4 : ReconciliationTotals
CardTransaction10 *-- "0..1" AmountAndDirection41 : AmountNetReconciliation
CardTransaction10 *-- "1..1" ResponseType2 : TransactionResponse

AcquirerReconciliationResponse1 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardTransactionEnvironment5 - Required 1..1
Transaction Reconciliation transaction. CardTransaction10 - 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
%% ContentInformationType15 recursion level 0 with max 1
class ContentInformationType15{
    ContentType ContentType2Code
}
ContentInformationType15 *-- "1..1" AuthenticatedData4 : AuthenticatedData
%% AuthenticatedData4 recursion level 1 with max 1
class AuthenticatedData4{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData4 *-- "1..0" IRecipient4Choice : Recipient
AuthenticatedData4 *-- "1..1" AlgorithmIdentification15 : MACAlgorithm
AuthenticatedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent

ContentInformationType15 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). AuthenticatedData4 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ReconciliationResponse --|> IOuterRecord : Implements
    ReconciliationResponseDocument --|> IOuterDocument~ReconciliationResponse~ : Implements
    class IOuterDocument~ReconciliationResponse~ {
        ReconciliationResponse Message
     }

Document wrapper for serialization

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

classDiagram
    ReconciliationResponseDocument *-- ReconciliationResponse : 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:cain.008.001.01">
    <RcncltnRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <RcncltnRspn>
            <!-- ReconciliationResponse inner content -->
        </RcncltnRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </RcncltnRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_A6xeEHvBEeSLmfFG0DG7zQ"
  nextVersions="_7OfdhVUHEeetiruPyDPo0Q"
  name="ReconciliationResponse"
  definition="The ReconciliationResponse message is sent by an issuer or an agent to return the reconciled totals for debits, credits, chargebacks and other transactions."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="RcncltnRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_QMmpYHvBEeSLmfFG0DG7zQ"
    name="Header"
    definition="Information related to the protocol management."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_l60LgXq_EeSA34QF-FhTBw" />
  <messageBuildingBlock
    xmi:id="_ZV0QoHvBEeSLmfFG0DG7zQ"
    name="ReconciliationResponse"
    definition="Information related to the response to a reconciliation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RcncltnRspn"
    complexType="_R8Nl0HvBEeSLmfFG0DG7zQ" />
  <messageBuildingBlock
    xmi:id="_Z6ywgHvCEeSLmfFG0DG7zQ"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_uSOuUCrHEeWRf8RNsvC5fQ" />
  <messageDefinitionIdentifier
    businessArea="cain"
    messageFunctionality="008"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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