SaleToPOIServiceResponseV02

casp.002.001.02

The SaleToPOIServiceResponse message is sent by a POI to provide the outcome of a financial 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
%% SaleToPOIServiceResponseV02 recursion level 0 with max 0
SaleToPOIServiceResponseV02 *-- "1..1" Header41 : Header
SaleToPOIServiceResponseV02 *-- "1..1" ServiceResponse3 : ServiceResponse
SaleToPOIServiceResponseV02 *-- "0..1" ContentInformationType21 : 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 response. 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

ServiceResponse building block

Information related to the response of a service request. This component contains the response of the corresponding service request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ServiceResponse3 recursion level 0 with max 1
class ServiceResponse3{
    ServiceContent RetailerService3Code
}
ServiceResponse3 *-- "1..1" CardPaymentEnvironment75 : Environment
ServiceResponse3 *-- "1..1" CardPaymentContext28 : Context
ServiceResponse3 *-- "0..1" PaymentResponse2 : PaymentResponse
ServiceResponse3 *-- "0..1" ReversalResponse3 : ReversalResponse
ServiceResponse3 *-- "0..1" BalanceInquiryResponse2 : BalanceInquiryResponse
ServiceResponse3 *-- "0..1" LoyaltyResponse2 : LoyaltyResponse
ServiceResponse3 *-- "0..1" StoredValueResponse3 : StoredValueResponse
ServiceResponse3 *-- "0..1" BatchResponse2 : BatchResponse
ServiceResponse3 *-- "0..1" CardAcquisitionResponse2 : CardAcquisitionResponse
ServiceResponse3 *-- "1..1" ResponseType9 : Response
ServiceResponse3 *-- "0..0" SupplementaryData1 : SupplementaryData
%% CardPaymentEnvironment75 recursion level 1 with max 1
CardPaymentEnvironment75 *-- "0..1" Acquirer10 : Acquirer
CardPaymentEnvironment75 *-- "0..1" Organisation32 : Merchant
CardPaymentEnvironment75 *-- "0..1" PointOfInteraction10 : POI
CardPaymentEnvironment75 *-- "0..1" PaymentCard30 : Card
CardPaymentEnvironment75 *-- "0..1" Check1 : Check
CardPaymentEnvironment75 *-- "0..0" StoredValueAccount2 : StoredValueAccount
CardPaymentEnvironment75 *-- "0..0" LoyaltyAccount2 : LoyaltyAccount
CardPaymentEnvironment75 *-- "0..1" CustomerDevice1 : CustomerDevice
CardPaymentEnvironment75 *-- "0..1" CustomerDevice1 : Wallet
CardPaymentEnvironment75 *-- "0..1" CardPaymentToken5 : PaymentToken
CardPaymentEnvironment75 *-- "0..1" Cardholder16 : Cardholder
CardPaymentEnvironment75 *-- "0..1" ContentInformationType22 : ProtectedCardholderData
CardPaymentEnvironment75 *-- "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
%% PaymentResponse2 recursion level 1 with max 1
class PaymentResponse2{
    SaleReferenceIdentification IsoMax35Text
    POIReconciliationIdentification IsoMax35Text
    IssuerReferenceData IsoMax140Text
}
PaymentResponse2 *-- "1..1" TransactionIdentifier1 : SaleTransactionIdentification
PaymentResponse2 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
PaymentResponse2 *-- "1..1" RetailerPaymentResult2 : RetailerPaymentResult
PaymentResponse2 *-- "0..0" PaymentReceipt2 : PaymentReceipt
PaymentResponse2 *-- "0..0" LoyaltyResult2 : LoyaltyResult
PaymentResponse2 *-- "0..0" CustomerOrder1 : CustomerOrder
%% ReversalResponse3 recursion level 1 with max 1
class ReversalResponse3{
    SaleReferenceIdentification IsoMax35Text
    POIReconciliationIdentification IsoMax35Text
    IssuerReferenceData IsoMax35Text
    ReversedAmount IsoImpliedCurrencyAndAmount
}
ReversalResponse3 *-- "1..1" TransactionIdentifier1 : SaleTransactionIdentification
ReversalResponse3 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
ReversalResponse3 *-- "1..1" RetailerReversalResult2 : ReversalTransactionResult
ReversalResponse3 *-- "0..0" PaymentReceipt2 : Receipt
%% BalanceInquiryResponse2 recursion level 1 with max 1
BalanceInquiryResponse2 *-- "0..1" PaymentAccount3 : PaymentAccount
BalanceInquiryResponse2 *-- "0..1" LoyaltyAccount2 : LoyaltyAccount
BalanceInquiryResponse2 *-- "0..0" StoredValueAccount2 : StoredValueAccount
BalanceInquiryResponse2 *-- "0..0" PaymentReceipt2 : Receipt
%% LoyaltyResponse2 recursion level 1 with max 1
class LoyaltyResponse2{
    POIReconciliationIdentification IsoMax35Text
}
LoyaltyResponse2 *-- "1..1" TransactionIdentifier1 : SaleTransactionIdentification
LoyaltyResponse2 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
LoyaltyResponse2 *-- "0..0" LoyaltyResult2 : Result
%% StoredValueResponse3 recursion level 1 with max 1
StoredValueResponse3 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
StoredValueResponse3 *-- "0..0" StoredValueData3 : Result
StoredValueResponse3 *-- "0..0" PaymentReceipt2 : Receipt
%% BatchResponse2 recursion level 1 with max 1
BatchResponse2 *-- "0..0" PerformedTransaction2 : PerformedTransaction
%% CardAcquisitionResponse2 recursion level 1 with max 1
class CardAcquisitionResponse2{
    PaymentBrand IsoMax35Text
    CustomerLanguage LanguageCode
}
CardAcquisitionResponse2 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
CardAcquisitionResponse2 *-- "0..0" LoyaltyAccount2 : LoyaltyAccount
CardAcquisitionResponse2 *-- "0..0" CustomerOrder1 : CustomerOrder
%% ResponseType9 recursion level 1 with max 1
class ResponseType9{
    Response Response5Code
    ResponseReason RetailerResultDetail1Code
    AdditionalResponseInformation IsoMax140Text
}
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

ServiceResponse3 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment75 - Required 1..1
Context Context in which the transaction is performed (payment and sale). CardPaymentContext28 - Required 1..1
ServiceContent Define the type of service response. RetailerService3Code - Required 1..1
PaymentResponse Data to respond to a Payment request. PaymentResponse2 - Optional 0..1
ReversalResponse Response Data to a Reversal request. ReversalResponse3 - Optional 0..1
BalanceInquiryResponse Response data to a balance inquiry service request. BalanceInquiryResponse2 - Optional 0..1
LoyaltyResponse Response data to a loyalty service request. LoyaltyResponse2 - Optional 0..1
StoredValueResponse Response data to a Stored Value request. StoredValueResponse3 - Optional 0..1
BatchResponse Content of the Batch Response message. BatchResponse2 - Optional 0..1
CardAcquisitionResponse Content of the Card Acquisition Response message. CardAcquisitionResponse2 - Optional 0..1
Response Result of the processing of the request. ResponseType9 - 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
%% ContentInformationType21 recursion level 0 with max 1
class ContentInformationType21{
    ContentType ContentType2Code
}
ContentInformationType21 *-- "0..1" AuthenticatedData6 : AuthenticatedData
ContentInformationType21 *-- "0..1" SignedData5 : SignedData
%% AuthenticatedData6 recursion level 1 with max 1
class AuthenticatedData6{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData6 *-- "1..0" IRecipient8Choice : Recipient
AuthenticatedData6 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData6 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData5 recursion level 1 with max 1
class SignedData5{
    Version IsoNumber
    Certificate IsoMax5000Binary
}
SignedData5 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm
SignedData5 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent
SignedData5 *-- "0..0" Signer4 : Signer
  

ContentInformationType21 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). AuthenticatedData6 - Optional 0..1
SignedData Data protected by a digital signatures. SignedData5 - Optional 0..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SaleToPOIServiceResponseV02 --|> IOuterRecord : Implements
    SaleToPOIServiceResponseV02Document --|> IOuterDocument~SaleToPOIServiceResponseV02~ : Implements
    class IOuterDocument~SaleToPOIServiceResponseV02~ {
        SaleToPOIServiceResponseV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SaleToPOIServiceResponseV02Document *-- SaleToPOIServiceResponseV02 : 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.002.001.02">
    <SaleToPOISvcRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <SvcRspn>
            <!-- ServiceResponse inner content -->
        </SvcRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </SaleToPOISvcRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_umpHkQ1VEeqjM-rxn3HuXQ"
  nextVersions="_7itroS5LEeunNvJlR_vCbg"
  previousVersion="_Qjrp8YYAEemxIqbaFEE8-w"
  name="SaleToPOIServiceResponseV02"
  definition="The SaleToPOIServiceResponse message is sent by a POI to provide the outcome of a financial service."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="SaleToPOISvcRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_umpuoQ1VEeqjM-rxn3HuXQ"
    nextVersions="_7itroy5LEeunNvJlR_vCbg"
    previousVersion="_Qjrp84YAEemxIqbaFEE8-w"
    name="Header"
    definition="Set of characteristics related to the transfer of the response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_BwWUYQuKEeqYM5yH99IYQw" />
  <messageBuildingBlock
    xmi:id="_umpuow1VEeqjM-rxn3HuXQ"
    nextVersions="_7itrpS5LEeunNvJlR_vCbg"
    previousVersion="_Qjrp9YYAEemxIqbaFEE8-w"
    name="ServiceResponse"
    definition="Information related to the response of a service request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SvcRspn"
    complexType="_0fJMAQ1VEeqjM-rxn3HuXQ" />
  <messageBuildingBlock
    xmi:id="_umpupQ1VEeqjM-rxn3HuXQ"
    nextVersions="_7itrpy5LEeunNvJlR_vCbg"
    previousVersion="_Qjrp94YAEemxIqbaFEE8-w"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_gkSEMQuhEeqw5uEXxQ9H4g" />
  <messageDefinitionIdentifier
    businessArea="casp"
    messageFunctionality="002"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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