caaa.010.001.09
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
%% AcceptorReconciliationResponseV09 recursion level 0 with max 0
AcceptorReconciliationResponseV09 *-- "1..1" Header59 : Header
AcceptorReconciliationResponseV09 *-- "1..1" AcceptorReconciliationResponse8 : ReconciliationResponse
AcceptorReconciliationResponseV09 *-- "0..1" ContentInformationType31 : 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
%% 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 |
ReconciliationResponse building block
Information related to the reconciliation response. Reconciliation response from the acquirer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AcceptorReconciliationResponse8 recursion level 0 with max 1
AcceptorReconciliationResponse8 *-- "1..1" CardPaymentEnvironment78 : Environment
AcceptorReconciliationResponse8 *-- "1..1" ResponseType10 : TransactionResponse
AcceptorReconciliationResponse8 *-- "1..1" TransactionReconciliation5 : Transaction
%% CardPaymentEnvironment78 recursion level 1 with max 1
CardPaymentEnvironment78 *-- "0..1" Acquirer10 : Acquirer
CardPaymentEnvironment78 *-- "0..1" Organisation41 : Merchant
CardPaymentEnvironment78 *-- "0..1" PointOfInteraction12 : POI
CardPaymentEnvironment78 *-- "0..1" PaymentCard32 : Card
CardPaymentEnvironment78 *-- "0..1" Check1 : Check
CardPaymentEnvironment78 *-- "0..0" StoredValueAccount2 : StoredValueAccount
CardPaymentEnvironment78 *-- "0..0" LoyaltyAccount3 : LoyaltyAccount
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : CustomerDevice
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : Wallet
CardPaymentEnvironment78 *-- "0..1" Token1 : PaymentToken
CardPaymentEnvironment78 *-- "0..1" MerchantToken2 : MerchantToken
CardPaymentEnvironment78 *-- "0..1" Cardholder18 : Cardholder
CardPaymentEnvironment78 *-- "0..1" ContentInformationType32 : ProtectedCardholderData
CardPaymentEnvironment78 *-- "0..1" RetailerSaleEnvironment2 : SaleEnvironment
%% ResponseType10 recursion level 1 with max 1
class ResponseType10{
Response Response9Code
ResponseReason IsoMax35Text
AdditionalResponseInformation IsoMax140Text
}
%% 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
AcceptorReconciliationResponse8 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment78 - Required 1..1 |
| TransactionResponse | Response from the acquirer to the reconciliation transaction. | ResponseType10 - 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
%% ContentInformationType31 recursion level 0 with max 1
class ContentInformationType31{
ContentType ContentType2Code
}
ContentInformationType31 *-- "1..1" AuthenticatedData8 : AuthenticatedData
%% AuthenticatedData8 recursion level 1 with max 1
class AuthenticatedData8{
Version IsoNumber
MAC IsoMax140Binary
}
AuthenticatedData8 *-- "1..0" IRecipient11Choice : Recipient
AuthenticatedData8 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData8 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType31 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). | AuthenticatedData8 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorReconciliationResponseV09 implementation follows a specific implementaiton pattern. First of all, AcceptorReconciliationResponseV09 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorReconciliationResponseV09Document implements IOuterDocument. Because AcceptorReconciliationResponseV09 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorReconciliationResponseV09.
classDiagram
class IOuterRecord
AcceptorReconciliationResponseV09 --|> IOuterRecord : Implements
AcceptorReconciliationResponseV09Document --|> IOuterDocument~AcceptorReconciliationResponseV09~ : Implements
class IOuterDocument~AcceptorReconciliationResponseV09~ {
AcceptorReconciliationResponseV09 Message
}
Document wrapper for serialization
The only real purpose AcceptorReconciliationResponseV09Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.010.001.09’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorReconciliationResponseV09.ToDocument() method. The returned AcceptorReconciliationResponseV09Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorReconciliationResponseV09Document *-- AcceptorReconciliationResponseV09 : 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.09">
<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="_-x6EsU7TEeyGi9JAv6wq7Q"
nextVersions="_QxuNYXMVEe2vXY6MoVq19w"
previousVersion="__lZ7cS4_EeunNvJlR_vCbg"
name="AcceptorReconciliationResponseV09"
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.
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="_fMW_EL1vEeKoB-JG4saAMg_-385897474"
xmlTag="AccptrRcncltnRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_-x6Es07TEeyGi9JAv6wq7Q"
type="purpose" />
<messageBuildingBlock
xmi:id="_-x6rwU7TEeyGi9JAv6wq7Q"
nextVersions="_Qxu0cXMVEe2vXY6MoVq19w"
previousVersion="__lZ7dS4_EeunNvJlR_vCbg"
name="Header"
definition="Reconciliation response message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_Rz5m4S_aEeugIJ3Gvoevmg" />
<messageBuildingBlock
xmi:id="_-x6rw07TEeyGi9JAv6wq7Q"
nextVersions="_QxvbgXMVEe2vXY6MoVq19w"
previousVersion="__lZ7dy4_EeunNvJlR_vCbg"
name="ReconciliationResponse"
definition="Information related to the reconciliation response."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RcncltnRspn"
complexType="_2W61YU7TEeyGi9JAv6wq7Q" />
<messageBuildingBlock
xmi:id="_-x6rxU7TEeyGi9JAv6wq7Q"
nextVersions="_Qxvbg3MVEe2vXY6MoVq19w"
previousVersion="__lZ7eS4_EeunNvJlR_vCbg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_dJxbAVFFEeyApZmLzm74zA" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="010"
flavour="001"
version="09" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.