caaa.009.001.09
The AcceptorReconciliationRequest message is sent by an acceptor (or its agent) to the acquirer (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 %% AcceptorReconciliationRequestV09 recursion level 0 with max 0 AcceptorReconciliationRequestV09 *-- "1..1" Header59 : Header AcceptorReconciliationRequestV09 *-- "1..1" AcceptorReconciliationRequest9 : ReconciliationRequest AcceptorReconciliationRequestV09 *-- "0..1" ContentInformationType27 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Reconciliation request 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 |
ReconciliationRequest building block
Information related to the reconciliation request. Reconciliation request from an acceptor. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AcceptorReconciliationRequest9 recursion level 0 with max 1 AcceptorReconciliationRequest9 *-- "1..1" CardPaymentEnvironment77 : Environment AcceptorReconciliationRequest9 *-- "1..1" TransactionReconciliation5 : Transaction %% CardPaymentEnvironment77 recursion level 1 with max 1 CardPaymentEnvironment77 *-- "0..1" Acquirer10 : Acquirer CardPaymentEnvironment77 *-- "0..1" Organisation41 : Merchant CardPaymentEnvironment77 *-- "0..1" PointOfInteraction11 : POI CardPaymentEnvironment77 *-- "0..1" PaymentCard31 : Card CardPaymentEnvironment77 *-- "0..1" Check1 : Check CardPaymentEnvironment77 *-- "0..0" StoredValueAccount2 : StoredValueAccount CardPaymentEnvironment77 *-- "0..0" LoyaltyAccount2 : LoyaltyAccount CardPaymentEnvironment77 *-- "0..1" CustomerDevice3 : CustomerDevice CardPaymentEnvironment77 *-- "0..1" CustomerDevice3 : Wallet CardPaymentEnvironment77 *-- "0..1" Token1 : PaymentToken CardPaymentEnvironment77 *-- "0..1" MerchantToken1 : MerchantToken CardPaymentEnvironment77 *-- "0..1" Cardholder17 : Cardholder CardPaymentEnvironment77 *-- "0..1" ContentInformationType28 : ProtectedCardholderData CardPaymentEnvironment77 *-- "0..1" RetailerSaleEnvironment2 : SaleEnvironment %% TransactionReconciliation5 recursion level 1 with max 1 class TransactionReconciliation5{ ClosePeriod IsoTrueFalseIndicator ReconciliationIdentification IsoMax35Text AdditionalTransactionData IsoMax70Text } TransactionReconciliation5 *-- "1..1" TransactionIdentifier1 : ReconciliationTransactionIdentification TransactionReconciliation5 *-- "0..0" TransactionTotals12 : TransactionTotals
AcceptorReconciliationRequest9 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Environment | Environment of the transaction. | CardPaymentEnvironment77 - Required 1..1 |
Transaction | Reconciliation transaction between an acceptor an acquirer. | TransactionReconciliation5 - 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 %% ContentInformationType27 recursion level 0 with max 1 class ContentInformationType27{ ContentType ContentType2Code } ContentInformationType27 *-- "1..1" AuthenticatedData7 : AuthenticatedData %% AuthenticatedData7 recursion level 1 with max 1 class AuthenticatedData7{ Version IsoNumber MAC IsoMax140Binary } AuthenticatedData7 *-- "1..0" IRecipient10Choice : Recipient AuthenticatedData7 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm AuthenticatedData7 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType27 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). | AuthenticatedData7 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorReconciliationRequestV09 implementation follows a specific implementaiton pattern. First of all, AcceptorReconciliationRequestV09 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorReconciliationRequestV09Document implements IOuterDocument. Because AcceptorReconciliationRequestV09 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorReconciliationRequestV09.
classDiagram class IOuterRecord AcceptorReconciliationRequestV09 --|> IOuterRecord : Implements AcceptorReconciliationRequestV09Document --|> IOuterDocument~AcceptorReconciliationRequestV09~ : Implements class IOuterDocument~AcceptorReconciliationRequestV09~ { AcceptorReconciliationRequestV09 Message }
Document wrapper for serialization
The only real purpose AcceptorReconciliationRequestV09Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.009.001.09’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorReconciliationRequestV09.ToDocument() method. The returned AcceptorReconciliationRequestV09Document value will serialize correctly according to ISO 20022 standards.
classDiagram AcceptorReconciliationRequestV09Document *-- AcceptorReconciliationRequestV09 : 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.009.001.09">
<AccptrRcncltnReq>
<Hdr>
<!-- Header inner content -->
</Hdr>
<RcncltnReq>
<!-- ReconciliationRequest inner content -->
</RcncltnReq>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</AccptrRcncltnReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_j7RWsS4_EeunNvJlR_vCbg"
nextVersions="_u6PBYU7TEeyGi9JAv6wq7Q"
previousVersion="_eME54QulEeqw5uEXxQ9H4g"
name="AcceptorReconciliationRequestV09"
definition="The AcceptorReconciliationRequest message is sent by an acceptor (or its agent) to the acquirer (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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AccptrRcncltnReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_j7RWsy4_EeunNvJlR_vCbg"
type="purpose" />
<messageBuildingBlock
xmi:id="_j7RWtS4_EeunNvJlR_vCbg"
nextVersions="_u6PBZU7TEeyGi9JAv6wq7Q"
previousVersion="_eME55QulEeqw5uEXxQ9H4g"
name="Header"
definition="Reconciliation request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_Rz5m4S_aEeugIJ3Gvoevmg" />
<messageBuildingBlock
xmi:id="_j7RWty4_EeunNvJlR_vCbg"
nextVersions="_u6PBZ07TEeyGi9JAv6wq7Q"
previousVersion="_eME55wulEeqw5uEXxQ9H4g"
name="ReconciliationRequest"
definition="Information related to the reconciliation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RcncltnReq"
complexType="_ZKulQS4_EeunNvJlR_vCbg" />
<messageBuildingBlock
xmi:id="_j7RWuS4_EeunNvJlR_vCbg"
nextVersions="_u6PBaU7TEeyGi9JAv6wq7Q"
previousVersion="_eME56QulEeqw5uEXxQ9H4g"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_2S4usS8lEeu125Ip9zFcsQ" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="009"
flavour="001"
version="09" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.