casp.004.001.03
The SaleToPOIReconciliationResponse message is sent by a POI to provide the result of reconciliation process between sale and POI systems.
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 %% SaleToPOIReconciliationResponseV03 recursion level 0 with max 0 SaleToPOIReconciliationResponseV03 *-- "1..1" Header41 : Header SaleToPOIReconciliationResponseV03 *-- "1..1" ReconciliationResponse5 : ReconciliationResponse SaleToPOIReconciliationResponseV03 *-- "0..1" ContentInformationType25 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Set of characteristics related to the transfer of the request. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header41 recursion level 0 with max 1 class Header41{ MessageFunction RetailerMessage1Code ProtocolVersion IsoMax6Text ExchangeIdentification IsoMax35Text CreationDateTime IsoISODateTime } Header41 *-- "1..1" GenericIdentification177 : InitiatingParty Header41 *-- "0..1" GenericIdentification177 : RecipientParty Header41 *-- "0..0" Traceability8 : Traceability %% 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 %% 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
Header41 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | RetailerMessage1Code - Required 1..1 |
ProtocolVersion | Version of the acquirer protocol specifications. | IsoMax6Text - Required 1..1 |
ExchangeIdentification | Unique identification of an exchange occurrence. | IsoMax35Text - 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. | GenericIdentification177 - 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 response of a reconciliation request. This component define the type of financial service to be used with this message of Reconciliation. This is only one service : ReconcialiationResponse. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ReconciliationResponse5 recursion level 0 with max 1 ReconciliationResponse5 *-- "1..1" CardPaymentEnvironment77 : Environment ReconciliationResponse5 *-- "1..1" CardPaymentContext28 : Context ReconciliationResponse5 *-- "1..1" ReconciliationResponseData1 : ReconciliationResponseData ReconciliationResponse5 *-- "1..1" ResponseType11 : Response ReconciliationResponse5 *-- "0..0" SupplementaryData1 : SupplementaryData %% 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 %% CardPaymentContext28 recursion level 1 with max 1 CardPaymentContext28 *-- "0..1" PaymentContext27 : PaymentContext CardPaymentContext28 *-- "0..1" SaleContext4 : SaleContext CardPaymentContext28 *-- "0..1" CardDirectDebit2 : DirectDebitContext %% ReconciliationResponseData1 recursion level 1 with max 1 class ReconciliationResponseData1{ ReconciliationType ReconciliationType1Code POIReconciliationIdentification IsoMax35Text } ReconciliationResponseData1 *-- "0..0" TransactionTotalsSet1 : TransactionTotals %% ResponseType11 recursion level 1 with max 1 class ResponseType11{ Response Response11Code ResponseReason RetailerResultDetail1Code AdditionalResponseInformation IsoMax140Text } %% SupplementaryData1 recursion level 1 with max 1 class SupplementaryData1{ PlaceAndName IsoMax350Text } SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
ReconciliationResponse5 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Environment | Environment of the transaction. | CardPaymentEnvironment77 - Required 1..1 |
Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext28 - Required 1..1 |
ReconciliationResponseData | Content of the Reconciliation Response message. | ReconciliationResponseData1 - Required 1..1 |
Response | Result of the processing of the request. | ResponseType11 - Required 1..1 |
SupplementaryData | Additional information incorporated as an extension to the message. | SupplementaryData1 - Unknown 0..0 |
SecurityTrailer building block
Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing data. protected by a MAC or a digital signature. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ContentInformationType25 recursion level 0 with max 1 class ContentInformationType25{ ContentType ContentType2Code } ContentInformationType25 *-- "0..1" AuthenticatedData7 : AuthenticatedData ContentInformationType25 *-- "0..1" SignedData6 : SignedData %% 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 %% SignedData6 recursion level 1 with max 1 class SignedData6{ Version IsoNumber Certificate IsoMax5000Binary } SignedData6 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm SignedData6 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent SignedData6 *-- "0..0" Signer5 : Signer
ContentInformationType25 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 - Optional 0..1 |
SignedData | Data protected by a digital signatures. | SignedData6 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the SaleToPOIReconciliationResponseV03 implementation follows a specific implementaiton pattern. First of all, SaleToPOIReconciliationResponseV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SaleToPOIReconciliationResponseV03Document implements IOuterDocument. Because SaleToPOIReconciliationResponseV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SaleToPOIReconciliationResponseV03.
classDiagram class IOuterRecord SaleToPOIReconciliationResponseV03 --|> IOuterRecord : Implements SaleToPOIReconciliationResponseV03Document --|> IOuterDocument~SaleToPOIReconciliationResponseV03~ : Implements class IOuterDocument~SaleToPOIReconciliationResponseV03~ { SaleToPOIReconciliationResponseV03 Message }
Document wrapper for serialization
The only real purpose SaleToPOIReconciliationResponseV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:casp.004.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SaleToPOIReconciliationResponseV03.ToDocument() method. The returned SaleToPOIReconciliationResponseV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram SaleToPOIReconciliationResponseV03Document *-- SaleToPOIReconciliationResponseV03 : 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:casp.004.001.03">
<SaleToPOIRcncltnRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<RcncltnRspn>
<!-- ReconciliationResponse inner content -->
</RcncltnRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</SaleToPOIRcncltnRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_UvYk4S5LEeunNvJlR_vCbg"
nextVersions="_wGUZ0U6uEeyGi9JAv6wq7Q"
previousVersion="_2r5z8Q1UEeqjM-rxn3HuXQ"
name="SaleToPOIReconciliationResponseV03"
definition="The SaleToPOIReconciliationResponse message is sent by a POI to provide the result of reconciliation process between sale and POI systems."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="SaleToPOIRcncltnRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_UvYk4y5LEeunNvJlR_vCbg"
nextVersions="_wGVA4U6uEeyGi9JAv6wq7Q"
previousVersion="_2r5z8w1UEeqjM-rxn3HuXQ"
name="Header"
definition="Set of characteristics related to the transfer of the request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_BwWUYQuKEeqYM5yH99IYQw" />
<messageBuildingBlock
xmi:id="_UvYk5S5LEeunNvJlR_vCbg"
nextVersions="_wGVA406uEeyGi9JAv6wq7Q"
previousVersion="_2r5z9Q1UEeqjM-rxn3HuXQ"
name="ReconciliationResponse"
definition="Information related to the response of a reconciliation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RcncltnRspn"
complexType="_MTmrYS5LEeunNvJlR_vCbg" />
<messageBuildingBlock
xmi:id="_UvYk5y5LEeunNvJlR_vCbg"
nextVersions="_wGVA5U6uEeyGi9JAv6wq7Q"
previousVersion="_2r5z9w1UEeqjM-rxn3HuXQ"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC or a digital signature."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_kWoPYS8jEeu125Ip9zFcsQ" />
<messageDefinitionIdentifier
businessArea="casp"
messageFunctionality="004"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.