AcceptorBatchTransferV08

caaa.011.001.08

The AcceptorBatchTransfer is sent by an acceptor (or its agent) to transfer the financial data of a collection of transactions to the acquirer (or its agent).

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
%% AcceptorBatchTransferV08 recursion level 0 with max 0
AcceptorBatchTransferV08 *-- "1..1" Header25 : Header
AcceptorBatchTransferV08 *-- "1..1" CardPaymentBatchTransfer7 : BatchTransfer
AcceptorBatchTransferV08 *-- "0..1" ContentInformationType16 : SecurityTrailer
  

Now, we will zero-in one-by-one on each of these building blocks.

Header building block

Batch capture message management information. Set of characteristics related to the transfer of transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header25 recursion level 0 with max 1
class Header25{
    DownloadTransfer IsoTrueFalseIndicator
    FormatVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    CreationDateTime IsoISODateTime
}
Header25 *-- "1..1" GenericIdentification53 : InitiatingParty
Header25 *-- "0..1" GenericIdentification94 : RecipientParty
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification94 recursion level 1 with max 1
class GenericIdentification94{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification94 *-- "0..1" NetworkParameters5 : RemoteAccess
  

Header25 members

BatchTransfer building block

Card payment transactions from one or several data set of transactions. Card payment transactions from one or several data set of transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CardPaymentBatchTransfer7 recursion level 0 with max 1
CardPaymentBatchTransfer7 *-- "0..0" TransactionTotals7 : TransactionTotals
CardPaymentBatchTransfer7 *-- "0..0" CardPaymentDataSet22 : DataSet
%% TransactionTotals7 recursion level 1 with max 1
class TransactionTotals7{
    POIGroupIdentification IsoMax35Text
    CardProductProfile IsoMax35Text
    Currency ActiveCurrencyCode
    Type TypeTransactionTotals2Code
    TotalNumber IsoNumber
    CumulativeAmount IsoImpliedCurrencyAndAmount
}
%% CardPaymentDataSet22 recursion level 1 with max 1
CardPaymentDataSet22 *-- "1..1" DataSetIdentification5 : DataSetIdentification
CardPaymentDataSet22 *-- "0..0" Traceability5 : Traceability
CardPaymentDataSet22 *-- "0..1" GenericIdentification53 : DataSetInitiator
CardPaymentDataSet22 *-- "1..0" TransactionTotals7 : TransactionTotals
CardPaymentDataSet22 *-- "0..1" CommonData8 : CommonData
CardPaymentDataSet22 *-- "1..0" ICardPaymentDataSetTransaction7Choice : Transaction
  

CardPaymentBatchTransfer7 members

SecurityTrailer building block

Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing authenticated data. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContentInformationType16 recursion level 0 with max 1
class ContentInformationType16{
    ContentType ContentType2Code
}
ContentInformationType16 *-- "1..1" AuthenticatedData5 : AuthenticatedData
%% AuthenticatedData5 recursion level 1 with max 1
class AuthenticatedData5{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData5 *-- "1..0" IRecipient6Choice : Recipient
AuthenticatedData5 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData5 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
  

ContentInformationType16 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorBatchTransferV08 --|> IOuterRecord : Implements
    AcceptorBatchTransferV08Document --|> IOuterDocument~AcceptorBatchTransferV08~ : Implements
    class IOuterDocument~AcceptorBatchTransferV08~ {
        AcceptorBatchTransferV08 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AcceptorBatchTransferV08Document *-- AcceptorBatchTransferV08 : 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:caaa.011.001.08">
    <AccptrBtchTrf>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <BtchTrf>
            <!-- BatchTransfer inner content -->
        </BtchTrf>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrBtchTrf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_hUUmMdekEeiJyp_aycJaTw"
  nextVersions="_lPTosQt8EeqYM5yH99IYQw"
  previousVersion="_Q6qukdppEeearpaEPXv9UA"
  name="AcceptorBatchTransferV08"
  definition="The AcceptorBatchTransfer is sent by an acceptor (or its agent) to transfer the financial data of a collection of transactions to the acquirer (or its agent)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrBtchTrf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_hUUmM9ekEeiJyp_aycJaTw"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_hUUmNdekEeiJyp_aycJaTw"
    nextVersions="_lPWE8Qt8EeqYM5yH99IYQw"
    previousVersion="_Q6quldppEeearpaEPXv9UA"
    name="Header"
    definition="Batch capture message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_SzGD4Y3IEeWjkqXgn_0Imw" />
  <messageBuildingBlock
    xmi:id="_hUUmN9ekEeiJyp_aycJaTw"
    nextVersions="_lPWsAQt8EeqYM5yH99IYQw"
    previousVersion="_Q6qul9ppEeearpaEPXv9UA"
    name="BatchTransfer"
    definition="Card payment transactions from one or several data set of transactions."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BtchTrf"
    complexType="_aU2SoNekEeiJyp_aycJaTw" />
  <messageBuildingBlock
    xmi:id="_hUUmOdekEeiJyp_aycJaTw"
    nextVersions="_lPWsAwt8EeqYM5yH99IYQw"
    previousVersion="_Q6qumdppEeearpaEPXv9UA"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_Wb7MEds3Eee9e6xduATmQg" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="011"
    flavour="001"
    version="08" />
</messageDefinition>

ISO Building Blocks

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