BatchManagementInitiationV01

caad.001.001.01

The BatchManagementInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer) connected to a network.

This message provides flow control information enabling a series of messages in batches and batches in collections to start, end or require checkpoints during the flow.

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
%% BatchManagementInitiationV01 recursion level 0 with max 0
BatchManagementInitiationV01 *-- "1..1" Header38 : Header
BatchManagementInitiationV01 *-- "1..1" BatchManagementInitiation1 : Body
BatchManagementInitiationV01 *-- "0..1" ContentInformationType20 : SecurityTrailer
  

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

Header building block

Information related to the management of the protocol. Set of characteristics related to the protocol.

For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header38 recursion level 0 with max 1
class Header38{
    MessageFunction MessageFunction18Code
    ProtocolVersion IsoMax2048Text
    ExchangeIdentification IsoMax35Text
    ReTransmissionCounter IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header38 *-- "1..1" GenericIdentification172 : InitiatingParty
Header38 *-- "0..1" GenericIdentification172 : RecipientParty
Header38 *-- "0..0" AdditionalData1 : TraceData
Header38 *-- "0..0" Traceability7 : Traceability
%% GenericIdentification172 recursion level 1 with max 1
class GenericIdentification172{
    Identification IsoMax35Text
    Type PartyType17Code
    OtherType IsoMax35Text
    Assigner PartyType18Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification172 recursion level 1 with max 1
class GenericIdentification172{
    Identification IsoMax35Text
    Type PartyType17Code
    OtherType IsoMax35Text
    Assigner PartyType18Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% AdditionalData1 recursion level 1 with max 1
class AdditionalData1{
    Type IsoMax35Text
    Value IsoMax2048Text
}
%% Traceability7 recursion level 1 with max 1
class Traceability7{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability7 *-- "1..1" GenericIdentification172 : RelayIdentification
  

Header38 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction18Code - Required 1..1
ProtocolVersion Version of the acquirer to issuer protocol specifications. IsoMax2048Text - Required 1..1
ExchangeIdentification Unique identification of an exchange of messages between two parties. IsoMax35Text - Optional 0..1
ReTransmissionCounter Number of retransmission of the message. Incremented by one for each retransmission. IsoMax3NumericText - Optional 0..1
CreationDateTime Date and time at which the message was sent. IsoISODateTime - Required 1..1
InitiatingParty Unique identification of the partner that has initiated the exchange. GenericIdentification172 - Required 1..1
RecipientParty Unique identification of the partner that is the recipient of the message exchange. GenericIdentification172 - Optional 0..1
TraceData Information sent in the request message to be returned in the response one, for instance to help in the retrieval of the context of the exchange. ISO 8583:93/2003 bit 59 AdditionalData1 - Unknown 0..0
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability7 - Unknown 0..0

Body building block

Information related to the batch management. Information related to the batch management. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BatchManagementInitiation1 recursion level 0 with max 1
BatchManagementInitiation1 *-- "1..1" Environment3 : Environment
BatchManagementInitiation1 *-- "0..1" Context8 : Context
BatchManagementInitiation1 *-- "1..1" Transaction95 : Transaction
BatchManagementInitiation1 *-- "0..0" ProtectedData1 : ProtectedData
BatchManagementInitiation1 *-- "0..0" SupplementaryData1 : SupplementaryData
%% Environment3 recursion level 1 with max 1
Environment3 *-- "0..1" PartyIdentification197 : Originator
Environment3 *-- "0..1" PartyIdentification197 : Sender
Environment3 *-- "0..1" PartyIdentification197 : Receiver
Environment3 *-- "0..1" PartyIdentification197 : Destination
%% Context8 recursion level 1 with max 1
Context8 *-- "0..1" TransactionContext5 : TransactionContext
%% Transaction95 recursion level 1 with max 1
class Transaction95{
    BatchManagementType BatchManagementType1Code
    OtherBatchManagementType IsoMax35Text
    CollectionIdentification IsoMax70Text
    BatchIdentification IsoMax70Text
    CollectionSize IsoNumber
    OriginalCollectionIdentification IsoMax70Text
    OriginalBatchIdentification IsoMax70Text
    NumberOfBatchesInCollection IsoNumber
    NumberOfMessages IsoNumber
    RemainingMessagesInCollection IsoNumber
    MessageSequenceNumber IsoMax15NumericText
    BatchIdentificationList IsoMax70Text
    CheckpointIdentification IsoMax70Text
    BatchChecksum IsoMax35Binary
    RequestAcknowledgement IsoTrueFalseIndicator
    MessagesBeforeAcknowledgement IsoNumber
    PositiveAcknowledgement IsoTrueFalseIndicator
}
Transaction95 *-- "0..1" TransactionIdentification10 : TransactionIdentification
Transaction95 *-- "0..0" AdditionalFee1 : AdditionalFees
Transaction95 *-- "0..0" AdditionalData1 : AdditionalData
%% ProtectedData1 recursion level 1 with max 1
class ProtectedData1{
    ContentType ContentType3Code
}
ProtectedData1 *-- "0..1" EnvelopedData6 : EnvelopedData
ProtectedData1 *-- "0..1" EncryptedData1 : EncryptedData
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

BatchManagementInitiation1 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. Environment3 - Required 1..1
Context Contains or describes conditions and characteristics of the transaction. Context8 - Optional 0..1
Transaction Batch management transaction. Transaction95 - Required 1..1
ProtectedData Contains protected data and the attributes used to protect the data. ProtectedData1 - Unknown 0..0
SupplementaryData Additional information that can not be captured in the structured fields and/or other specific block. SupplementaryData1 - Unknown 0..0

SecurityTrailer building block

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

classDiagram
   direction tb
%% ContentInformationType20 recursion level 0 with max 1
class ContentInformationType20{
    MAC IsoMax8HexBinaryText
}
ContentInformationType20 *-- "1..1" MACData1 : MACData
%% MACData1 recursion level 1 with max 1
class MACData1{
    Control IsoExact1HexBinaryText
    KeySetIdentifier IsoMax8NumericText
    DerivedInformation IsoMax32HexBinaryText
    Algorithm IsoMax2NumericText
    KeyLength IsoMax4NumericText
    KeyProtection IsoMax2NumericText
    KeyIndex IsoMax5NumericText
    PaddingMethod IsoMax2NumericText
    InitialisationVector IsoMax32HexBinaryText
}
  

ContentInformationType20 members

Member name Description Data Type / Multiplicity
MACData Type of data protection. ISO 8583:87 bit 53 or 110 ISO 8583:93 bit 53 or 111 ISO 8583:2003 bit 53 or 50 MACData1 - Required 1..1
MAC Message Authentication Code data. Binary, length of 8 ISO 8583 bit 64 or bit 128 IsoMax8HexBinaryText - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    BatchManagementInitiationV01 --|> IOuterRecord : Implements
    BatchManagementInitiationV01Document --|> IOuterDocument~BatchManagementInitiationV01~ : Implements
    class IOuterDocument~BatchManagementInitiationV01~ {
        BatchManagementInitiationV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    BatchManagementInitiationV01Document *-- BatchManagementInitiationV01 : 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:caad.001.001.01">
    <BtchMgmtInitn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Body>
            <!-- Body inner content -->
        </Body>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </BtchMgmtInitn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_CcEcRVW9EeeiG_nL4vgKnQ"
  nextVersions="_31KMYYdOEeuBS50MFjViNw"
  name="BatchManagementInitiationV01"
  definition="The BatchManagementInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer) connected to a network.&#xD;&#xA;&#xD;&#xA;This message provides flow control information enabling a series of messages in batches and batches in collections to start, end or require checkpoints during the flow."
  registrationStatus="Registered"
  messageSet="_oFVkcKmaEeqA4rV5xCgycA"
  xmlTag="BtchMgmtInitn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_CcEcR1W9EeeiG_nL4vgKnQ"
    nextVersions="_31KMY4dOEeuBS50MFjViNw"
    name="Header"
    definition="Information related to the management of the protocol."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_pn1tsVAWEeedyPuM0kK2EQ" />
  <messageBuildingBlock
    xmi:id="_CcEcSFW9EeeiG_nL4vgKnQ"
    nextVersions="_31KMZYdOEeuBS50MFjViNw"
    name="Body"
    definition="Information related to the batch management."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Body"
    complexType="_NYW1oFAVEeedyPuM0kK2EQ" />
  <messageBuildingBlock
    xmi:id="_CcEcRlW9EeeiG_nL4vgKnQ"
    nextVersions="_31KMZ4dOEeuBS50MFjViNw"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC"
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
  <messageDefinitionIdentifier
    businessArea="caad"
    messageFunctionality="001"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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