SaleToPOIServiceRequestV04

casp.001.001.04

This SaleToPOIServiceRequest message is sent by a sale system to trig a financial service on POI system.

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
%% SaleToPOIServiceRequestV04 recursion level 0 with max 0
SaleToPOIServiceRequestV04 *-- "1..1" Header41 : Header
SaleToPOIServiceRequestV04 *-- "1..1" ServiceRequest5 : ServiceRequest
SaleToPOIServiceRequestV04 *-- "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

ServiceRequest building block

Information related to a service request. This component defines the service to be called. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ServiceRequest5 recursion level 0 with max 1
class ServiceRequest5{
    ServiceContent RetailerService2Code
}
ServiceRequest5 *-- "1..1" CardPaymentEnvironment78 : Environment
ServiceRequest5 *-- "1..1" CardPaymentContext29 : Context
ServiceRequest5 *-- "0..1" PaymentRequest4 : PaymentRequest
ServiceRequest5 *-- "0..1" ReversalRequest4 : ReversalRequest
ServiceRequest5 *-- "0..1" BalanceInquiryRequest5 : BalanceInquiryRequest
ServiceRequest5 *-- "0..1" LoyaltyRequest4 : LoyaltyRequest
ServiceRequest5 *-- "0..1" StoredValueRequest5 : StoredValueRequest
ServiceRequest5 *-- "0..1" BatchRequest4 : BatchRequest
ServiceRequest5 *-- "0..1" EnableServiceRequest4 : EnableServiceRequest
ServiceRequest5 *-- "0..1" CardAcquisitionRequest3 : CardAcquisitionRequest
ServiceRequest5 *-- "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
%% PaymentRequest4 recursion level 1 with max 1
PaymentRequest4 *-- "0..1" CardPaymentTransaction120 : PaymentTransaction
PaymentRequest4 *-- "0..0" LoyaltyRequestData3 : LoyaltyData
%% ReversalRequest4 recursion level 1 with max 1
class ReversalRequest4{
    ReversalReason ReversalReason1Code
    ReversedAmount IsoImpliedCurrencyAndAmount
}
ReversalRequest4 *-- "0..1" CardPaymentTransaction120 : ReversalTransaction
ReversalRequest4 *-- "0..0" LoyaltyRequestData3 : LoyaltyData
ReversalRequest4 *-- "0..1" CustomerOrder1 : CustomerOrder
%% BalanceInquiryRequest5 recursion level 1 with max 1
BalanceInquiryRequest5 *-- "0..1" TransactionIdentifier1 : SaleTransactionIdentification
BalanceInquiryRequest5 *-- "0..1" PaymentAccountRequest1 : PaymentAccountRequest
BalanceInquiryRequest5 *-- "0..1" LoyaltyAccountRequest3 : LoyaltyAccountRequest
BalanceInquiryRequest5 *-- "0..1" StoredValueRequest5 : StoredValueAccountRequest
%% LoyaltyRequest4 recursion level 1 with max 1
LoyaltyRequest4 *-- "0..1" CustomerOrder1 : CustomerOrder
LoyaltyRequest4 *-- "1..1" LoyaltyTransaction4 : Transaction
LoyaltyRequest4 *-- "0..0" LoyaltyRequestData3 : Data
%% StoredValueRequest5 recursion level 1 with max 1
StoredValueRequest5 *-- "0..1" TransactionIdentifier1 : SaleTransactionIdentification
StoredValueRequest5 *-- "1..0" StoredValueData5 : Data
%% BatchRequest4 recursion level 1 with max 1
class BatchRequest4{
    RemoveAllFlag IsoTrueFalseIndicator
}
BatchRequest4 *-- "0..1" TransactionIdentifier1 : SaleBatchIdentification
BatchRequest4 *-- "0..0" ITransactionToPerform4Choice : TransactionToPerform
%% EnableServiceRequest4 recursion level 1 with max 1
class EnableServiceRequest4{
    TransactionAction TransactionAction1Code
    ServicesEnabled RetailerService2Code
}
EnableServiceRequest4 *-- "0..1" ActionMessage9 : DisplayOutput
%% CardAcquisitionRequest3 recursion level 1 with max 1
class CardAcquisitionRequest3{
    AllowedPaymentBrand IsoMax35Text
    AllowedLoyaltyBrand IsoMax35Text
    ForceCustomerSelectionFlag IsoTrueFalseIndicator
    TotalAmount IsoImpliedCurrencyAndAmount
    PaymentType CardPaymentServiceType13Code
    CashBackFlag IsoTrueFalseIndicator
    SaleToPOIData IsoMax70Text
    SaleToAcquirerData IsoMax70Text
    SaleToIssuerData IsoMax70Text
}
CardAcquisitionRequest3 *-- "0..1" TransactionIdentifier1 : SaleTransactionIdentification
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

ServiceRequest5 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
ServiceContent Define the type of service requested. RetailerService2Code - Required 1..1
PaymentRequest Content of the payment request. PaymentRequest4 - Optional 0..1
ReversalRequest Content of the reversal request. ReversalRequest4 - Optional 0..1
BalanceInquiryRequest Content of a Balance Inquiry Request. BalanceInquiryRequest5 - Optional 0..1
LoyaltyRequest Content of the Loyalty Request. LoyaltyRequest4 - Optional 0..1
StoredValueRequest Content of a Stored Value Request. StoredValueRequest5 - Optional 0..1
BatchRequest Content of the Batch Request. BatchRequest4 - Optional 0..1
EnableServiceRequest Content of the Enable Service Request. EnableServiceRequest4 - Optional 0..1
CardAcquisitionRequest Content of the Card Acquisition Request. CardAcquisitionRequest3 - Optional 0..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 SaleToPOIServiceRequestV04 implementation follows a specific implementaiton pattern. First of all, SaleToPOIServiceRequestV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SaleToPOIServiceRequestV04Document implements IOuterDocument. Because SaleToPOIServiceRequestV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SaleToPOIServiceRequestV04.

classDiagram
    class IOuterRecord
    SaleToPOIServiceRequestV04 --|> IOuterRecord : Implements
    SaleToPOIServiceRequestV04Document --|> IOuterDocument~SaleToPOIServiceRequestV04~ : Implements
    class IOuterDocument~SaleToPOIServiceRequestV04~ {
        SaleToPOIServiceRequestV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SaleToPOIServiceRequestV04Document *-- SaleToPOIServiceRequestV04 : 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.001.001.04">
    <SaleToPOISvcReq>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <SvcReq>
            <!-- ServiceRequest inner content -->
        </SvcReq>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </SaleToPOISvcReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_n5ruoU31Eey_VecAUE-C9Q"
  nextVersions="_Ids_YXMuEe2vXY6MoVq19w"
  previousVersion="_3x9W0S5LEeunNvJlR_vCbg"
  name="SaleToPOIServiceRequestV04"
  definition="This SaleToPOIServiceRequest message is sent by a sale system to trig a financial service on POI system."
  registrationStatus="Registered"
  messageSet="_IwdwsFSSEeqZkqCw0Z-zEQ"
  xmlTag="SaleToPOISvcReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_n5ruo031Eey_VecAUE-C9Q"
    nextVersions="_Ids_Y3MuEe2vXY6MoVq19w"
    previousVersion="_3x9W0y5LEeunNvJlR_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="_n5rupU31Eey_VecAUE-C9Q"
    nextVersions="_Ids_ZXMuEe2vXY6MoVq19w"
    previousVersion="_3x9W1S5LEeunNvJlR_vCbg"
    name="ServiceRequest"
    definition="Information related to a service request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SvcReq"
    complexType="_R3lwcU31Eey_VecAUE-C9Q" />
  <messageBuildingBlock
    xmi:id="_n5rup031Eey_VecAUE-C9Q"
    nextVersions="_Ids_Z3MuEe2vXY6MoVq19w"
    previousVersion="_3x9W1y5LEeunNvJlR_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="001"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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