SaleToPOIServiceResponseV03

casp.002.001.03

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
%% SaleToPOIServiceResponseV03 recursion level 0 with max 0
SaleToPOIServiceResponseV03 *-- "1..1" Header41 : Header
SaleToPOIServiceResponseV03 *-- "1..1" ServiceResponse5 : ServiceResponse
SaleToPOIServiceResponseV03 *-- "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 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
%% ServiceResponse5 recursion level 0 with max 1
class ServiceResponse5{
    ServiceContent RetailerService3Code
}
ServiceResponse5 *-- "1..1" CardPaymentEnvironment77 : Environment
ServiceResponse5 *-- "1..1" CardPaymentContext28 : Context
ServiceResponse5 *-- "0..1" PaymentResponse3 : PaymentResponse
ServiceResponse5 *-- "0..1" ReversalResponse5 : ReversalResponse
ServiceResponse5 *-- "0..1" BalanceInquiryResponse3 : BalanceInquiryResponse
ServiceResponse5 *-- "0..1" LoyaltyResponse2 : LoyaltyResponse
ServiceResponse5 *-- "0..1" StoredValueResponse4 : StoredValueResponse
ServiceResponse5 *-- "0..1" BatchResponse3 : BatchResponse
ServiceResponse5 *-- "0..1" CardAcquisitionResponse2 : CardAcquisitionResponse
ServiceResponse5 *-- "1..1" ResponseType11 : Response
ServiceResponse5 *-- "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
%% PaymentResponse3 recursion level 1 with max 1
class PaymentResponse3{
    SaleReferenceIdentification IsoMax35Text
    POIReconciliationIdentification IsoMax35Text
    IssuerReferenceData IsoMax140Text
}
PaymentResponse3 *-- "1..1" TransactionIdentifier1 : SaleTransactionIdentification
PaymentResponse3 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
PaymentResponse3 *-- "1..1" RetailerPaymentResult3 : RetailerPaymentResult
PaymentResponse3 *-- "0..0" PaymentReceipt3 : PaymentReceipt
PaymentResponse3 *-- "0..0" LoyaltyResult2 : LoyaltyResult
PaymentResponse3 *-- "0..0" CustomerOrder1 : CustomerOrder
%% ReversalResponse5 recursion level 1 with max 1
class ReversalResponse5{
    SaleReferenceIdentification IsoMax35Text
    POIReconciliationIdentification IsoMax35Text
    IssuerReferenceData IsoMax140Text
    ReversedAmount IsoImpliedCurrencyAndAmount
}
ReversalResponse5 *-- "1..1" TransactionIdentifier1 : SaleTransactionIdentification
ReversalResponse5 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
ReversalResponse5 *-- "1..1" RetailerReversalResult3 : ReversalTransactionResult
ReversalResponse5 *-- "0..0" PaymentReceipt3 : Receipt
%% BalanceInquiryResponse3 recursion level 1 with max 1
BalanceInquiryResponse3 *-- "0..1" PaymentAccount3 : PaymentAccount
BalanceInquiryResponse3 *-- "0..1" LoyaltyAccount2 : LoyaltyAccount
BalanceInquiryResponse3 *-- "0..0" StoredValueAccount2 : StoredValueAccount
BalanceInquiryResponse3 *-- "0..0" PaymentReceipt3 : 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
%% StoredValueResponse4 recursion level 1 with max 1
StoredValueResponse4 *-- "1..1" TransactionIdentifier1 : POITransactionIdentification
StoredValueResponse4 *-- "0..0" StoredValueData4 : Result
StoredValueResponse4 *-- "0..0" PaymentReceipt3 : Receipt
%% BatchResponse3 recursion level 1 with max 1
BatchResponse3 *-- "0..0" PerformedTransaction3 : 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
%% 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
  

ServiceResponse5 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
ServiceContent Define the type of service response. RetailerService3Code - Required 1..1
PaymentResponse Data to respond to a Payment request. PaymentResponse3 - Optional 0..1
ReversalResponse Response Data to a Reversal request. ReversalResponse5 - Optional 0..1
BalanceInquiryResponse Response data to a balance inquiry service request. BalanceInquiryResponse3 - Optional 0..1
LoyaltyResponse Response data to a loyalty service request. LoyaltyResponse2 - Optional 0..1
StoredValueResponse Response data to a Stored Value request. StoredValueResponse4 - Optional 0..1
BatchResponse Content of the Batch Response message. BatchResponse3 - Optional 0..1
CardAcquisitionResponse Content of the Card Acquisition Response message. CardAcquisitionResponse2 - 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
%% 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 SaleToPOIServiceResponseV03 implementation follows a specific implementaiton pattern. First of all, SaleToPOIServiceResponseV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SaleToPOIServiceResponseV03Document implements IOuterDocument. Because SaleToPOIServiceResponseV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SaleToPOIServiceResponseV03.

classDiagram
    class IOuterRecord
    SaleToPOIServiceResponseV03 --|> IOuterRecord : Implements
    SaleToPOIServiceResponseV03Document --|> IOuterDocument~SaleToPOIServiceResponseV03~ : Implements
    class IOuterDocument~SaleToPOIServiceResponseV03~ {
        SaleToPOIServiceResponseV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SaleToPOIServiceResponseV03Document *-- SaleToPOIServiceResponseV03 : 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.03">
    <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="_7itroS5LEeunNvJlR_vCbg"
  nextVersions="_RvI2wU0_Eeybj420QgWBkA"
  previousVersion="_umpHkQ1VEeqjM-rxn3HuXQ"
  name="SaleToPOIServiceResponseV03"
  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="_7itroy5LEeunNvJlR_vCbg"
    nextVersions="_RvI2w00_Eeybj420QgWBkA"
    previousVersion="_umpuoQ1VEeqjM-rxn3HuXQ"
    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="_7itrpS5LEeunNvJlR_vCbg"
    nextVersions="_RvI2xU0_Eeybj420QgWBkA"
    previousVersion="_umpuow1VEeqjM-rxn3HuXQ"
    name="ServiceResponse"
    definition="Information related to the response of a service request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SvcRspn"
    complexType="_l07w0VS8EeuUvsVXOV79DQ" />
  <messageBuildingBlock
    xmi:id="_7itrpy5LEeunNvJlR_vCbg"
    nextVersions="_RvI2x00_Eeybj420QgWBkA"
    previousVersion="_umpupQ1VEeqjM-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="002"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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