SaleToPOIDeviceResponseV05

casp.017.001.05

The SaleToPOIDeviceResponse message is sent by a POI System to sale system to provide result of a device request.

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
%% SaleToPOIDeviceResponseV05 recursion level 0 with max 0
SaleToPOIDeviceResponseV05 *-- "1..1" Header41 : Header
SaleToPOIDeviceResponseV05 *-- "1..1" DeviceResponse6 : DeviceResponse
SaleToPOIDeviceResponseV05 *-- "0..1" ContentInformationType33 : 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

DeviceResponse building block

Information related to the response of a device request. Provides the response of a previous device request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DeviceResponse6 recursion level 0 with max 1
class DeviceResponse6{
    ServiceContent RetailerService9Code
}
DeviceResponse6 *-- "0..1" CardPaymentEnvironment79 : Environment
DeviceResponse6 *-- "0..1" CardPaymentContext30 : Context
DeviceResponse6 *-- "0..1" DeviceDisplayResponse2 : DisplayResponse
DeviceResponse6 *-- "0..1" DeviceInputResponse5 : InputResponse
DeviceResponse6 *-- "0..1" DevicePrintResponse1 : PrintResponse
DeviceResponse6 *-- "0..1" DeviceSecureInputResponse5 : SecureInputResponse
DeviceResponse6 *-- "0..1" DeviceInitialisationCardReaderResponse2 : InitialisationCardReaderResponse
DeviceResponse6 *-- "0..1" DeviceSendApplicationProtocolDataUnitCardReaderResponse1 : CardReaderApplicationProtocolDataUnitResponse
DeviceResponse6 *-- "0..1" DeviceTransmitMessageResponse1 : TransmissionResponse
DeviceResponse6 *-- "1..1" ResponseType11 : Response
DeviceResponse6 *-- "0..0" SupplementaryData1 : SupplementaryData
%% CardPaymentEnvironment79 recursion level 1 with max 1
CardPaymentEnvironment79 *-- "0..1" Acquirer10 : Acquirer
CardPaymentEnvironment79 *-- "0..1" Acquirer10 : ServiceProvider
CardPaymentEnvironment79 *-- "0..1" Organisation41 : Merchant
CardPaymentEnvironment79 *-- "0..1" PointOfInteraction13 : POI
CardPaymentEnvironment79 *-- "0..1" PaymentCard33 : Card
CardPaymentEnvironment79 *-- "0..1" Check1 : Check
CardPaymentEnvironment79 *-- "0..0" StoredValueAccount2 : StoredValueAccount
CardPaymentEnvironment79 *-- "0..0" LoyaltyAccount3 : LoyaltyAccount
CardPaymentEnvironment79 *-- "0..1" CustomerDevice3 : CustomerDevice
CardPaymentEnvironment79 *-- "0..1" CustomerDevice3 : Wallet
CardPaymentEnvironment79 *-- "0..1" Token1 : PaymentToken
CardPaymentEnvironment79 *-- "0..1" MerchantToken2 : MerchantToken
CardPaymentEnvironment79 *-- "0..1" Cardholder20 : Cardholder
CardPaymentEnvironment79 *-- "0..1" ContentInformationType35 : ProtectedCardholderData
CardPaymentEnvironment79 *-- "0..1" RetailerSaleEnvironment2 : SaleEnvironment
%% CardPaymentContext30 recursion level 1 with max 1
CardPaymentContext30 *-- "0..1" PaymentContext29 : PaymentContext
CardPaymentContext30 *-- "0..1" SaleContext4 : SaleContext
CardPaymentContext30 *-- "0..1" CardDirectDebit2 : DirectDebitContext
%% DeviceDisplayResponse2 recursion level 1 with max 1
DeviceDisplayResponse2 *-- "1..0" OutputResult2 : OutputResult
%% DeviceInputResponse5 recursion level 1 with max 1
DeviceInputResponse5 *-- "0..1" OutputResult2 : OutputResult
DeviceInputResponse5 *-- "1..1" InputResult5 : InputResult
%% DevicePrintResponse1 recursion level 1 with max 1
class DevicePrintResponse1{
    DocumentQualifier DocumentType7Code
}
%% DeviceSecureInputResponse5 recursion level 1 with max 1
DeviceSecureInputResponse5 *-- "0..1" OnLinePIN10 : CardholderPIN
%% DeviceInitialisationCardReaderResponse2 recursion level 1 with max 1
class DeviceInitialisationCardReaderResponse2{
    CardEntryMode CardDataReading8Code
    AdditionalInformation IsoMax10000Binary
}
DeviceInitialisationCardReaderResponse2 *-- "0..1" ICCResetData1 : ICCResetData
%% DeviceSendApplicationProtocolDataUnitCardReaderResponse1 recursion level 1 with max 1
class DeviceSendApplicationProtocolDataUnitCardReaderResponse1{
    Data IsoMin1Max256Binary
    CardStatus IsoMin1Max256Binary
}
%% DeviceTransmitMessageResponse1 recursion level 1 with max 1
class DeviceTransmitMessageResponse1{
    ReceivedMessage IsoMax100KBinary
}
%% 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
  

DeviceResponse6 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment79 - Optional 0..1
Context Context in which the transaction is performed (payment and sale). CardPaymentContext30 - Optional 0..1
ServiceContent Define the type of service answered. RetailerService9Code - Required 1..1
DisplayResponse Content of the Display Response message. DeviceDisplayResponse2 - Optional 0..1
InputResponse Content of the Input Response message. DeviceInputResponse5 - Optional 0..1
PrintResponse Content of the Print Response message. DevicePrintResponse1 - Optional 0..1
SecureInputResponse Response to a secure input request. DeviceSecureInputResponse5 - Optional 0..1
InitialisationCardReaderResponse Content received after a card initialisation. DeviceInitialisationCardReaderResponse2 - Optional 0..1
CardReaderApplicationProtocolDataUnitResponse Content of the Card Reader APDU (Application Protocol Data Unit) response message. DeviceSendApplicationProtocolDataUnitCardReaderResponse1 - Optional 0..1
TransmissionResponse Content of the Transmit Response message. DeviceTransmitMessageResponse1 - Optional 0..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
%% ContentInformationType33 recursion level 0 with max 1
class ContentInformationType33{
    ContentType ContentType2Code
}
ContentInformationType33 *-- "0..1" AuthenticatedData9 : AuthenticatedData
ContentInformationType33 *-- "0..1" SignedData8 : SignedData
%% AuthenticatedData9 recursion level 1 with max 1
class AuthenticatedData9{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData9 *-- "1..0" IRecipient14Choice : Recipient
AuthenticatedData9 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData9 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData8 recursion level 1 with max 1
class SignedData8{
    Version IsoNumber
    Certificate IsoMax5000Binary
}
SignedData8 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm
SignedData8 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent
SignedData8 *-- "0..0" Signer7 : Signer
  

ContentInformationType33 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). AuthenticatedData9 - Optional 0..1
SignedData Data protected by a digital signatures. SignedData8 - Optional 0..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SaleToPOIDeviceResponseV05 --|> IOuterRecord : Implements
    SaleToPOIDeviceResponseV05Document --|> IOuterDocument~SaleToPOIDeviceResponseV05~ : Implements
    class IOuterDocument~SaleToPOIDeviceResponseV05~ {
        SaleToPOIDeviceResponseV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SaleToPOIDeviceResponseV05Document *-- SaleToPOIDeviceResponseV05 : 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.017.001.05">
    <SaleToPOIDvcRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <DvcRspn>
            <!-- DeviceResponse inner content -->
        </DvcRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </SaleToPOIDvcRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_FZbgYXPOEe2pK6udhxEaHA"
  previousVersion="_8NC34U6qEeyGi9JAv6wq7Q"
  name="SaleToPOIDeviceResponseV05"
  definition="The SaleToPOIDeviceResponse message is sent by a POI System to sale system to provide result of a device request."
  registrationStatus="Registered"
  messageSet="_O55JAIX9EemxIqbaFEE8-w"
  xmlTag="SaleToPOIDvcRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_FZbgY3POEe2pK6udhxEaHA"
    previousVersion="_8NC3406qEeyGi9JAv6wq7Q"
    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="_FZbgZXPOEe2pK6udhxEaHA"
    previousVersion="_8NC35U6qEeyGi9JAv6wq7Q"
    name="DeviceResponse"
    definition="Information related to the response of a device request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="DvcRspn"
    complexType="_pJ06oXGqEe2TbaNWBpRZpQ" />
  <messageBuildingBlock
    xmi:id="_FZbgZ3POEe2pK6udhxEaHA"
    previousVersion="_8NC3506qEeyGi9JAv6wq7Q"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_sqC0wXDIEe2MCaKO5AtGsA" />
  <messageDefinitionIdentifier
    businessArea="casp"
    messageFunctionality="017"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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