AcceptorBatchTransferResponseV08

caaa.012.001.08

The AcceptorBatchTransferResponse is sent by the acquirer (or its agent) to inform the acceptor (or its agent) of the transfer in a previous AcceptorBatchTransfer of a collection of transactions.

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
%% AcceptorBatchTransferResponseV08 recursion level 0 with max 0
AcceptorBatchTransferResponseV08 *-- "1..1" Header56 : Header
AcceptorBatchTransferResponseV08 *-- "1..1" CardPaymentBatchTransferResponse7 : BatchTransferResponse
AcceptorBatchTransferResponseV08 *-- "0..1" ContentInformationType24 : SecurityTrailer
  

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

Header building block

Capture advice response message management information. Set of characteristics related to the transfer of transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header56 recursion level 0 with max 1
class Header56{
    DownloadTransfer IsoTrueFalseIndicator
    FormatVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    CreationDateTime IsoISODateTime
}
Header56 *-- "1..1" GenericIdentification176 : InitiatingParty
Header56 *-- "0..1" GenericIdentification177 : RecipientParty
%% GenericIdentification176 recursion level 1 with max 1
class GenericIdentification176{
    Identification IsoMax35Text
    Type PartyType33Code
    Issuer PartyType33Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% 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
  

Header56 members

BatchTransferResponse building block

Information related to the previously sent set of transaction. Status of the transactions sent in a previous batch of card payment transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CardPaymentBatchTransferResponse7 recursion level 0 with max 1
CardPaymentBatchTransferResponse7 *-- "0..0" TransactionTotals7 : TransactionTotals
CardPaymentBatchTransferResponse7 *-- "0..0" CardPaymentDataSet24 : DataSet
%% TransactionTotals7 recursion level 1 with max 1
class TransactionTotals7{
    POIGroupIdentification IsoMax35Text
    CardProductProfile IsoMax35Text
    Currency ActiveCurrencyCode
    Type TypeTransactionTotals2Code
    TotalNumber IsoNumber
    CumulativeAmount IsoImpliedCurrencyAndAmount
}
%% CardPaymentDataSet24 recursion level 1 with max 1
class CardPaymentDataSet24{
    RemoveDataSet IsoTrueFalseIndicator
}
CardPaymentDataSet24 *-- "1..1" DataSetIdentification5 : DataSetIdentification
CardPaymentDataSet24 *-- "1..1" ResponseType10 : DataSetResult
CardPaymentDataSet24 *-- "0..1" GenericIdentification176 : DataSetInitiator
CardPaymentDataSet24 *-- "1..0" TransactionTotals7 : TransactionTotals
CardPaymentDataSet24 *-- "0..0" CardPaymentDataSet25 : RejectedTransaction
CardPaymentDataSet24 *-- "0..0" CardPaymentDataSet25 : SuspendedTransaction
CardPaymentDataSet24 *-- "0..0" CardPaymentDataSet25 : ResumedApproval
CardPaymentDataSet24 *-- "0..0" CardPaymentDataSet25 : ResumedRejection
  

CardPaymentBatchTransferResponse7 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
%% ContentInformationType24 recursion level 0 with max 1
class ContentInformationType24{
    ContentType ContentType2Code
}
ContentInformationType24 *-- "1..1" AuthenticatedData6 : AuthenticatedData
%% 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
  

ContentInformationType24 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorBatchTransferResponseV08 --|> IOuterRecord : Implements
    AcceptorBatchTransferResponseV08Document --|> IOuterDocument~AcceptorBatchTransferResponseV08~ : Implements
    class IOuterDocument~AcceptorBatchTransferResponseV08~ {
        AcceptorBatchTransferResponseV08 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AcceptorBatchTransferResponseV08Document *-- AcceptorBatchTransferResponseV08 : 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.012.001.08">
    <AccptrBtchTrfRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <BtchTrfRspn>
            <!-- BatchTransferResponse inner content -->
        </BtchTrfRspn>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrBtchTrfRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_s260IQuZEeqYM5yH99IYQw"
  nextVersions="_CnF1sS4-EeunNvJlR_vCbg"
  previousVersion="_wMuQods3Eee9e6xduATmQg"
  name="AcceptorBatchTransferResponseV08"
  definition="The AcceptorBatchTransferResponse is sent by the acquirer (or its agent) to inform the acceptor (or its agent) of the transfer in a previous AcceptorBatchTransfer of a collection of transactions."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrBtchTrfRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_s260IwuZEeqYM5yH99IYQw"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_s260JQuZEeqYM5yH99IYQw"
    nextVersions="_CnF1tS4-EeunNvJlR_vCbg"
    previousVersion="_wMuQpds3Eee9e6xduATmQg"
    name="Header"
    definition="Capture advice response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_E0yzQQt-EeqYM5yH99IYQw" />
  <messageBuildingBlock
    xmi:id="_s260JwuZEeqYM5yH99IYQw"
    nextVersions="_CnF1ty4-EeunNvJlR_vCbg"
    previousVersion="_wMuQp9s3Eee9e6xduATmQg"
    name="BatchTransferResponse"
    definition="Information related to the previously sent set of transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="BtchTrfRspn"
    complexType="_7HR7YQuZEeqYM5yH99IYQw" />
  <messageBuildingBlock
    xmi:id="_s260KQuZEeqYM5yH99IYQw"
    nextVersions="_CnF1uS4-EeunNvJlR_vCbg"
    previousVersion="_wMuQqds3Eee9e6xduATmQg"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_GpvT8QuEEeqYM5yH99IYQw" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="012"
    flavour="001"
    version="08" />
</messageDefinition>

ISO Building Blocks

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