catp.011.001.01
The ATMPINManagementResponse message is sent by an ATM manager or its agent to the ATM to provide the information and the outcome of the cardholder PIN operation requested in the ATMPINManagementRequest.
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
%% ATMPINManagementResponseV01 recursion level 0 with max 0
ATMPINManagementResponseV01 *-- "1..1" Header20 : Header
ATMPINManagementResponseV01 *-- "0..1" ContentInformationType10 : ProtectedATMPINManagementResponse
ATMPINManagementResponseV01 *-- "0..1" ATMPINManagementResponse1 : ATMPINManagementResponse
ATMPINManagementResponseV01 *-- "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
%% Header20 recursion level 0 with max 1
class Header20{
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoMax3NumericText
CreationDateTime IsoISODateTime
InitiatingParty IsoMax35Text
RecipientParty IsoMax35Text
ProcessState IsoMax35Text
}
Header20 *-- "1..1" ATMMessageFunction1 : MessageFunction
Header20 *-- "0..0" Traceability4 : Traceability
%% ATMMessageFunction1 recursion level 1 with max 1
class ATMMessageFunction1{
Function MessageFunction7Code
ATMServiceCode IsoMax35Text
HostServiceCode IsoMax35Text
}
%% Traceability4 recursion level 1 with max 1
class Traceability4{
SequenceNumber IsoMax35Text
TraceDateTimeIn IsoISODateTime
TraceDateTimeOut IsoISODateTime
}
Traceability4 *-- "1..1" GenericIdentification77 : RelayIdentification
Header20 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | ATMMessageFunction1 - 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 |
| 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 |
ProtectedATMPINManagementResponse 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 |
ATMPINManagementResponse building block
Information related to the response of an ATM PIN Management from an ATM manager. Information related to the response of an ATM PIN Management from an ATM manager. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ATMPINManagementResponse1 recursion level 0 with max 1
ATMPINManagementResponse1 *-- "1..1" ATMEnvironment2 : Environment
ATMPINManagementResponse1 *-- "1..1" ATMContext4 : Context
ATMPINManagementResponse1 *-- "1..1" ATMTransaction10 : Transaction
%% ATMEnvironment2 recursion level 1 with max 1
ATMEnvironment2 *-- "0..1" Acquirer7 : Acquirer
ATMEnvironment2 *-- "0..1" Acquirer8 : ATMManager
ATMEnvironment2 *-- "0..1" TerminalHosting1 : HostingEntity
ATMEnvironment2 *-- "1..1" AutomatedTellerMachine2 : ATM
ATMEnvironment2 *-- "1..1" ATMCustomer2 : Customer
ATMEnvironment2 *-- "0..1" ContentInformationType10 : ProtectedCardData
ATMEnvironment2 *-- "0..1" PlainCardData14 : PlainCardData
%% ATMContext4 recursion level 1 with max 1
class ATMContext4{
SessionReference IsoMax35Text
}
ATMContext4 *-- "1..1" ATMService4 : Service
%% ATMTransaction10 recursion level 1 with max 1
class ATMTransaction10{
ReconciliationIdentification IsoMax35Text
CompletionRequired IsoTrueFalseIndicator
ICCRelatedData IsoMax10000Binary
}
ATMTransaction10 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
ATMTransaction10 *-- "1..1" ResponseType3 : TransactionResponse
ATMTransaction10 *-- "0..0" Action5 : Action
ATMTransaction10 *-- "0..0" ATMCommand1 : Command
ATMPINManagementResponse1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the PIN management transaction. | ATMEnvironment2 - Required 1..1 |
| Context | Context in which the transaction is performed. | ATMContext4 - Required 1..1 |
| Transaction | Response to the PIN management transaction. | ATMTransaction10 - 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 ATMPINManagementResponseV01 implementation follows a specific implementaiton pattern. First of all, ATMPINManagementResponseV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ATMPINManagementResponseV01Document implements IOuterDocument. Because ATMPINManagementResponseV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ATMPINManagementResponseV01.
classDiagram
class IOuterRecord
ATMPINManagementResponseV01 --|> IOuterRecord : Implements
ATMPINManagementResponseV01Document --|> IOuterDocument~ATMPINManagementResponseV01~ : Implements
class IOuterDocument~ATMPINManagementResponseV01~ {
ATMPINManagementResponseV01 Message
}
Document wrapper for serialization
The only real purpose ATMPINManagementResponseV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catp.011.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ATMPINManagementResponseV01.ToDocument() method. The returned ATMPINManagementResponseV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
ATMPINManagementResponseV01Document *-- ATMPINManagementResponseV01 : 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.011.001.01">
<ATMPINMgmtRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<PrtctdATMPINMgmtRspn>
<!-- ProtectedATMPINManagementResponse inner content -->
</PrtctdATMPINMgmtRspn>
<ATMPINMgmtRspn>
<!-- ATMPINManagementResponse inner content -->
</ATMPINMgmtRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</ATMPINMgmtRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_qemjoIrBEeSgLpgNvMAP2g"
nextVersions="_52hnca4aEeW_TaP-ygI0SQ"
name="ATMPINManagementResponseV01"
definition="The ATMPINManagementResponse message is sent by an ATM manager or its agent to the ATM to provide the information and the outcome of the cardholder PIN operation requested in the ATMPINManagementRequest."
registrationStatus="Registered"
messageSet="_lVeMdARsEeWTJNHF-ohSqw"
xmlTag="ATMPINMgmtRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_yhjGYIrBEeSgLpgNvMAP2g"
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="_47_isYnvEeS9F4Qrq_eaVA" />
<messageBuildingBlock
xmi:id="_8O7xsIrBEeSgLpgNvMAP2g"
name="ProtectedATMPINManagementResponse"
definition="Encrypted body of the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrtctdATMPINMgmtRspn"
complexType="_UfeMUWizEeS87LmvcA55sg" />
<messageBuildingBlock
xmi:id="_F2W-8IrCEeSgLpgNvMAP2g"
name="ATMPINManagementResponse"
definition="Information related to the response of an ATM PIN Management from an ATM manager."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="ATMPINMgmtRspn"
complexType="_-b5YgIrBEeSgLpgNvMAP2g" />
<messageBuildingBlock
xmi:id="_JoPVIIrCEeSgLpgNvMAP2g"
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="011"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.