catp.009.001.02
The ATMCompletionAcknowledgement message is sent by an acquirer or its agent to an ATM to acknowledge the receipt of an ATMCompletionAdvice message.
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 %% ATMCompletionAcknowledgementV02 recursion level 0 with max 0 ATMCompletionAcknowledgementV02 *-- "1..1" Header32 : Header ATMCompletionAcknowledgementV02 *-- "0..1" ContentInformationType10 : ProtectedATMCompletionAcknowledgement ATMCompletionAcknowledgementV02 *-- "0..1" ATMCompletionAcknowledgement2 : ATMCompletionAcknowledgement ATMCompletionAcknowledgementV02 *-- "0..1" ContentInformationType15 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Information related to the protocol management on a segment of the path from the ATM to the acquirer. Information related to the protocol management on a segment of the path from the ATM to the acquirer. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header32 recursion level 0 with max 1 class Header32{ ProtocolVersion IsoMax6Text ExchangeIdentification IsoMax3NumericText ReTransmissionCounter IsoNumber CreationDateTime IsoISODateTime InitiatingParty IsoMax35Text RecipientParty IsoMax35Text ProcessState IsoMax35Text } Header32 *-- "1..1" ATMMessageFunction2 : MessageFunction Header32 *-- "0..0" Traceability4 : Traceability %% ATMMessageFunction2 recursion level 1 with max 1 class ATMMessageFunction2{ Function MessageFunction11Code ATMServiceCode IsoMax35Text HostServiceCode IsoMax35Text } %% Traceability4 recursion level 1 with max 1 class Traceability4{ SequenceNumber IsoMax35Text TraceDateTimeIn IsoISODateTime TraceDateTimeOut IsoISODateTime } Traceability4 *-- "1..1" GenericIdentification77 : RelayIdentification
Header32 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | ATMMessageFunction2 - Required 1..1 |
ProtocolVersion | Version of the ATM protocol specifications. | IsoMax6Text - Required 1..1 |
ExchangeIdentification | Unique identification of an exchange occurrence. | IsoMax3NumericText - Required 1..1 |
ReTransmissionCounter | Retransmission counter of this advice, 0 for the first transmission. | IsoNumber - Optional 0..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. | IsoMax35Text - Required 1..1 |
RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | IsoMax35Text - Optional 0..1 |
ProcessState | State of the sender of the message inside the process flow. | IsoMax35Text - Optional 0..1 |
Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability4 - Unknown 0..0 |
ProtectedATMCompletionAcknowledgement building block
Encrypted body of the message. General cryptographic message syntax (CMS) containing encrypted data. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ContentInformationType10 recursion level 0 with max 1 class ContentInformationType10{ ContentType ContentType2Code } ContentInformationType10 *-- "1..1" EnvelopedData4 : EnvelopedData %% EnvelopedData4 recursion level 1 with max 1 class EnvelopedData4{ Version IsoNumber } EnvelopedData4 *-- "1..0" IRecipient4Choice : Recipient EnvelopedData4 *-- "0..1" EncryptedContent3 : EncryptedContent
ContentInformationType10 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
EnvelopedData | Data protection by encryption or by a digital envelope, with an encryption key. | EnvelopedData4 - Required 1..1 |
ATMCompletionAcknowledgement building block
Information related to the acknowledgement of an ATM completion on the ATM. manager. Information related to the acknowledgement of an ATM completion from the ATM manager. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ATMCompletionAcknowledgement2 recursion level 0 with max 1 ATMCompletionAcknowledgement2 *-- "1..1" AutomatedTellerMachine3 : ATM ATMCompletionAcknowledgement2 *-- "1..1" ATMContext13 : Context ATMCompletionAcknowledgement2 *-- "1..1" ATMTransaction18 : Transaction %% AutomatedTellerMachine3 recursion level 1 with max 1 class AutomatedTellerMachine3{ Identification IsoMax35Text AdditionalIdentification IsoMax35Text SequenceNumber IsoMax35Text } AutomatedTellerMachine3 *-- "0..1" PostalAddress17 : Location %% ATMContext13 recursion level 1 with max 1 class ATMContext13{ SessionReference IsoMax35Text } ATMContext13 *-- "1..1" ATMService14 : Service %% ATMTransaction18 recursion level 1 with max 1 class ATMTransaction18{ Response Response4Code ResponseReason ResultDetail4Code ICCRelatedData IsoMax10000Binary } ATMTransaction18 *-- "1..1" TransactionIdentifier1 : TransactionIdentification ATMTransaction18 *-- "0..0" ATMCommand7 : Command
ATMCompletionAcknowledgement2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
ATM | ATM information. | AutomatedTellerMachine3 - Required 1..1 |
Context | Context in which the transaction is performed. | ATMContext13 - Required 1..1 |
Transaction | Acknowledgement of the completion advice. | ATMTransaction18 - Required 1..1 |
SecurityTrailer building block
Trailer of the message containing a MAC. General cryptographic message syntax (CMS) containing authenticated data. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ContentInformationType15 recursion level 0 with max 1 class ContentInformationType15{ ContentType ContentType2Code } ContentInformationType15 *-- "1..1" AuthenticatedData4 : AuthenticatedData %% AuthenticatedData4 recursion level 1 with max 1 class AuthenticatedData4{ Version IsoNumber MAC IsoMax140Binary } AuthenticatedData4 *-- "1..0" IRecipient4Choice : Recipient AuthenticatedData4 *-- "1..1" AlgorithmIdentification15 : MACAlgorithm AuthenticatedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType15 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). | AuthenticatedData4 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the ATMCompletionAcknowledgementV02 implementation follows a specific implementaiton pattern. First of all, ATMCompletionAcknowledgementV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ATMCompletionAcknowledgementV02Document implements IOuterDocument. Because ATMCompletionAcknowledgementV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ATMCompletionAcknowledgementV02.
classDiagram class IOuterRecord ATMCompletionAcknowledgementV02 --|> IOuterRecord : Implements ATMCompletionAcknowledgementV02Document --|> IOuterDocument~ATMCompletionAcknowledgementV02~ : Implements class IOuterDocument~ATMCompletionAcknowledgementV02~ { ATMCompletionAcknowledgementV02 Message }
Document wrapper for serialization
The only real purpose ATMCompletionAcknowledgementV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catp.009.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ATMCompletionAcknowledgementV02.ToDocument() method. The returned ATMCompletionAcknowledgementV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram ATMCompletionAcknowledgementV02Document *-- ATMCompletionAcknowledgementV02 : 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:catp.009.001.02">
<ATMCmpltnAck>
<Hdr>
<!-- Header inner content -->
</Hdr>
<PrtctdATMCmpltnAck>
<!-- ProtectedATMCompletionAcknowledgement inner content -->
</PrtctdATMCmpltnAck>
<ATMCmpltnAck>
<!-- ATMCompletionAcknowledgement inner content -->
</ATMCmpltnAck>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</ATMCmpltnAck>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_x3hNsa4TEeWZgJQOa6iKCQ"
previousVersion="_vVWZgIqoEeS4a4abTJTSSw"
name="ATMCompletionAcknowledgementV02"
definition="The ATMCompletionAcknowledgement message is sent by an acquirer or its agent to an ATM to acknowledge the receipt of an ATMCompletionAdvice message."
registrationStatus="Registered"
messageSet="_wx2hAK1hEeWMg5rOByfExw"
xmlTag="ATMCmpltnAck"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_x3hNs64TEeWZgJQOa6iKCQ"
name="Header"
definition="Information related to the protocol management on a segment of the path from the ATM to the acquirer."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_4Wfn0a4JEeWZgJQOa6iKCQ" />
<messageBuildingBlock
xmi:id="_x3hNta4TEeWZgJQOa6iKCQ"
name="ProtectedATMCompletionAcknowledgement"
definition="Encrypted body of the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrtctdATMCmpltnAck"
complexType="_UfeMUWizEeS87LmvcA55sg" />
<messageBuildingBlock
xmi:id="_x3hNt64TEeWZgJQOa6iKCQ"
name="ATMCompletionAcknowledgement"
definition="Information related to the acknowledgement of an ATM completion on the ATM. manager."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="ATMCmpltnAck"
complexType="_4MbhUa4TEeWZgJQOa6iKCQ" />
<messageBuildingBlock
xmi:id="_x3hNua4TEeWZgJQOa6iKCQ"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_uSOuUCrHEeWRf8RNsvC5fQ" />
<messageDefinitionIdentifier
businessArea="catp"
messageFunctionality="009"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.