AcceptorReconciliationResponseV06

caaa.010.001.06

The AcceptorReconciliationResponse message is sent by the acquirer (or its agent) to an acceptor (or its agent), to ensure that the debits and credits performed by the acceptor matches the computed balances of the acquirer for the debits and credits performed during the same reconciliation period. If the acceptor or the acquirer notices a difference in totals, the discrepancy will be resolved by other means, outside the scope of the protocol.

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
%% AcceptorReconciliationResponseV06 recursion level 0 with max 0
AcceptorReconciliationResponseV06 *-- "1..1" Header35 : Header
AcceptorReconciliationResponseV06 *-- "1..1" AcceptorReconciliationResponse5 : ReconciliationResponse
AcceptorReconciliationResponseV06 *-- "0..1" ContentInformationType16 : SecurityTrailer
  

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

Header building block

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

classDiagram
   direction tb
%% Header35 recursion level 0 with max 1
class Header35{
    MessageFunction MessageFunction14Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    CreationDateTime IsoISODateTime
}
Header35 *-- "1..1" GenericIdentification53 : InitiatingParty
Header35 *-- "0..1" GenericIdentification94 : RecipientParty
Header35 *-- "0..0" Traceability5 : Traceability
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification94 recursion level 1 with max 1
class GenericIdentification94{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification94 *-- "0..1" NetworkParameters5 : RemoteAccess
%% Traceability5 recursion level 1 with max 1
class Traceability5{
    ProtocolName IsoMax35Text
    ProtocolVersion IsoMax6Text
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability5 *-- "1..1" GenericIdentification76 : RelayIdentification
  

Header35 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction14Code - 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
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. GenericIdentification53 - Required 1..1
RecipientParty Unique identification of the partner that is the recipient of the message exchange. GenericIdentification94 - Optional 0..1
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability5 - Unknown 0..0

ReconciliationResponse building block

Information related to the reconciliation response. Reconciliation response from the acquirer. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorReconciliationResponse5 recursion level 0 with max 1
AcceptorReconciliationResponse5 *-- "1..1" CardPaymentEnvironment69 : Environment
AcceptorReconciliationResponse5 *-- "1..1" ResponseType5 : TransactionResponse
AcceptorReconciliationResponse5 *-- "1..1" TransactionReconciliation4 : Transaction
%% CardPaymentEnvironment69 recursion level 1 with max 1
CardPaymentEnvironment69 *-- "0..1" GenericIdentification53 : AcquirerIdentification
CardPaymentEnvironment69 *-- "0..1" GenericIdentification32 : MerchantIdentification
CardPaymentEnvironment69 *-- "0..1" GenericIdentification32 : POIIdentification
CardPaymentEnvironment69 *-- "0..1" PaymentCard28 : Card
CardPaymentEnvironment69 *-- "0..1" CardPaymentToken4 : PaymentToken
%% ResponseType5 recursion level 1 with max 1
class ResponseType5{
    Response Response4Code
    ResponseReason IsoMax35Text
    AdditionalResponseInformation IsoMax140Text
}
%% TransactionReconciliation4 recursion level 1 with max 1
class TransactionReconciliation4{
    ClosePeriod IsoTrueFalseIndicator
    ReconciliationIdentification IsoMax35Text
    AdditionalTransactionData IsoMax70Text
}
TransactionReconciliation4 *-- "1..1" TransactionIdentifier1 : ReconciliationTransactionIdentification
TransactionReconciliation4 *-- "0..0" TransactionTotals7 : TransactionTotals
  

AcceptorReconciliationResponse5 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment69 - Required 1..1
TransactionResponse Response from the acquirer to the reconciliation transaction. ResponseType5 - Required 1..1
Transaction Reconciliation transaction between an acceptor an acquirer. TransactionReconciliation4 - 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
%% ContentInformationType16 recursion level 0 with max 1
class ContentInformationType16{
    ContentType ContentType2Code
}
ContentInformationType16 *-- "1..1" AuthenticatedData5 : AuthenticatedData
%% AuthenticatedData5 recursion level 1 with max 1
class AuthenticatedData5{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData5 *-- "1..0" IRecipient6Choice : Recipient
AuthenticatedData5 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData5 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
  

ContentInformationType16 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). AuthenticatedData5 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorReconciliationResponseV06 --|> IOuterRecord : Implements
    AcceptorReconciliationResponseV06Document --|> IOuterDocument~AcceptorReconciliationResponseV06~ : Implements
    class IOuterDocument~AcceptorReconciliationResponseV06~ {
        AcceptorReconciliationResponseV06 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AcceptorReconciliationResponseV06Document *-- AcceptorReconciliationResponseV06 : 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.010.001.06">
    <AccptrRcncltnRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <RcncltnRspn>
            <!-- ReconciliationResponse inner content -->
        </RcncltnRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrRcncltnRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_kUoWYds5Eee9e6xduATmQg"
  nextVersions="_Iz-ecQumEeqw5uEXxQ9H4g"
  previousVersion="_8Wl3gY1MEeWXALXlV0Ei2w"
  name="AcceptorReconciliationResponseV06"
  definition="The AcceptorReconciliationResponse message is sent by the acquirer (or its agent) to an acceptor (or its agent), to ensure that the debits and credits performed by the acceptor matches the computed balances of the acquirer for the debits and credits performed during the same reconciliation period.&#xD;&#xA;If the acceptor or the acquirer notices a difference in totals, the discrepancy will be resolved by other means, outside the scope of the protocol."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrRcncltnRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_kUoWY9s5Eee9e6xduATmQg"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_kUoWZds5Eee9e6xduATmQg"
    nextVersions="_Iz-edQumEeqw5uEXxQ9H4g"
    previousVersion="_8Wl3hY1MEeWXALXlV0Ei2w"
    name="Header"
    definition="Reconciliation response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_igU6wdnGEeeN3v2fup_Shw" />
  <messageBuildingBlock
    xmi:id="_kUoWZ9s5Eee9e6xduATmQg"
    nextVersions="_Iz-edwumEeqw5uEXxQ9H4g"
    previousVersion="_8Wl3h41MEeWXALXlV0Ei2w"
    name="ReconciliationResponse"
    definition="Information related to the reconciliation response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RcncltnRspn"
    complexType="_e1P4UN51EeeCre2qFaLC2A" />
  <messageBuildingBlock
    xmi:id="_kUoWads5Eee9e6xduATmQg"
    nextVersions="_Iz-eeQumEeqw5uEXxQ9H4g"
    previousVersion="_8Wl3iY1MEeWXALXlV0Ei2w"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_Wb7MEds3Eee9e6xduATmQg" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="010"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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