casp.008.001.04
The SaleToPOIAdministrativeResponse message is sent by a POI System to a sale system to provide response to an administrative service.
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
%% SaleToPOIAdministrativeResponseV04 recursion level 0 with max 0
SaleToPOIAdministrativeResponseV04 *-- "1..1" Header41 : Header
SaleToPOIAdministrativeResponseV04 *-- "1..1" AdministrativeResponse5 : AdministrativeResponse
SaleToPOIAdministrativeResponseV04 *-- "0..1" ContentInformationType29 : 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 |
AdministrativeResponse building block
Information related to the response of an administrative request. This component define the type of admin service to be used with this message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AdministrativeResponse5 recursion level 0 with max 1
AdministrativeResponse5 *-- "1..1" CardPaymentEnvironment78 : Environment
AdministrativeResponse5 *-- "1..1" CardPaymentContext29 : Context
AdministrativeResponse5 *-- "1..1" ResponseType11 : Response
AdministrativeResponse5 *-- "0..0" SupplementaryData1 : SupplementaryData
%% 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
%% CardPaymentContext29 recursion level 1 with max 1
CardPaymentContext29 *-- "0..1" PaymentContext28 : PaymentContext
CardPaymentContext29 *-- "0..1" SaleContext4 : SaleContext
CardPaymentContext29 *-- "0..1" CardDirectDebit2 : DirectDebitContext
%% 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
AdministrativeResponse5 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment78 - Required 1..1 |
| Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext29 - 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
%% ContentInformationType29 recursion level 0 with max 1
class ContentInformationType29{
ContentType ContentType2Code
}
ContentInformationType29 *-- "0..1" AuthenticatedData8 : AuthenticatedData
ContentInformationType29 *-- "0..1" SignedData7 : SignedData
%% 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
%% SignedData7 recursion level 1 with max 1
class SignedData7{
Version IsoNumber
Certificate IsoMax5000Binary
}
SignedData7 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm
SignedData7 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent
SignedData7 *-- "0..0" Signer6 : Signer
ContentInformationType29 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 - Optional 0..1 |
| SignedData | Data protected by a digital signatures. | SignedData7 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the SaleToPOIAdministrativeResponseV04 implementation follows a specific implementaiton pattern. First of all, SaleToPOIAdministrativeResponseV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SaleToPOIAdministrativeResponseV04Document implements IOuterDocument. Because SaleToPOIAdministrativeResponseV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SaleToPOIAdministrativeResponseV04.
classDiagram
class IOuterRecord
SaleToPOIAdministrativeResponseV04 --|> IOuterRecord : Implements
SaleToPOIAdministrativeResponseV04Document --|> IOuterDocument~SaleToPOIAdministrativeResponseV04~ : Implements
class IOuterDocument~SaleToPOIAdministrativeResponseV04~ {
SaleToPOIAdministrativeResponseV04 Message
}
Document wrapper for serialization
The only real purpose SaleToPOIAdministrativeResponseV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:casp.008.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SaleToPOIAdministrativeResponseV04.ToDocument() method. The returned SaleToPOIAdministrativeResponseV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SaleToPOIAdministrativeResponseV04Document *-- SaleToPOIAdministrativeResponseV04 : 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.008.001.04">
<SaleToPOIAdmstvRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<AdmstvRspn>
<!-- AdministrativeResponse inner content -->
</AdmstvRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</SaleToPOIAdmstvRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_c7ODcU6ZEeyGi9JAv6wq7Q"
nextVersions="_ArzKEXPCEe2pK6udhxEaHA"
previousVersion="_Q2QMoS5KEeunNvJlR_vCbg"
name="SaleToPOIAdministrativeResponseV04"
definition="The SaleToPOIAdministrativeResponse message is sent by a POI System to a sale system to provide response to an administrative service."
registrationStatus="Registered"
messageSet="_IwdwsFSSEeqZkqCw0Z-zEQ"
xmlTag="SaleToPOIAdmstvRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_c7ODc06ZEeyGi9JAv6wq7Q"
nextVersions="_ArzKE3PCEe2pK6udhxEaHA"
previousVersion="_Q2QMoy5KEeunNvJlR_vCbg"
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="_c7ODdU6ZEeyGi9JAv6wq7Q"
nextVersions="_ArzKFXPCEe2pK6udhxEaHA"
previousVersion="_Q2QMpS5KEeunNvJlR_vCbg"
name="AdministrativeResponse"
definition="Information related to the response of an administrative request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AdmstvRspn"
complexType="_J7eb8U6ZEeyGi9JAv6wq7Q" />
<messageBuildingBlock
xmi:id="_c7ODd06ZEeyGi9JAv6wq7Q"
nextVersions="_ArzKF3PCEe2pK6udhxEaHA"
previousVersion="_Q2QMpy5KEeunNvJlR_vCbg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC or a digital signature."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_uXF14VE1EeyApZmLzm74zA" />
<messageDefinitionIdentifier
businessArea="casp"
messageFunctionality="008"
flavour="001"
version="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.