catp.010.001.02
The ATMPINManagementRequest message is sent by an ATM to an ATM manager to request an operation on the cardholder PIN.
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
%% ATMPINManagementRequestV02 recursion level 0 with max 0
ATMPINManagementRequestV02 *-- "1..1" Header31 : Header
ATMPINManagementRequestV02 *-- "0..1" ContentInformationType10 : ProtectedATMPINManagementRequest
ATMPINManagementRequestV02 *-- "0..1" ATMPINManagementRequest2 : ATMPINManagementRequest
ATMPINManagementRequestV02 *-- "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
%% Header31 recursion level 0 with max 1
class Header31{
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoMax3NumericText
CreationDateTime IsoISODateTime
InitiatingParty IsoMax35Text
RecipientParty IsoMax35Text
ProcessState IsoMax35Text
}
Header31 *-- "1..1" ATMMessageFunction2 : MessageFunction
Header31 *-- "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
Header31 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 |
| 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 |
ProtectedATMPINManagementRequest 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 |
ATMPINManagementRequest building block
Information related to the request of a PIN management from an ATM. Information related to the request of a PIN management from an ATM. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ATMPINManagementRequest2 recursion level 0 with max 1
ATMPINManagementRequest2 *-- "1..1" ATMEnvironment11 : Environment
ATMPINManagementRequest2 *-- "1..1" ATMContext16 : Context
ATMPINManagementRequest2 *-- "1..1" ATMTransaction9 : Transaction
%% ATMEnvironment11 recursion level 1 with max 1
class ATMEnvironment11{
ATMManagerIdentification IsoMax35Text
}
ATMEnvironment11 *-- "0..1" Acquirer7 : Acquirer
ATMEnvironment11 *-- "0..1" TerminalHosting1 : HostingEntity
ATMEnvironment11 *-- "1..1" AutomatedTellerMachine9 : ATM
ATMEnvironment11 *-- "1..1" ATMCustomer4 : Customer
ATMEnvironment11 *-- "0..1" PaymentCard22 : Card
%% ATMContext16 recursion level 1 with max 1
class ATMContext16{
SessionReference IsoMax35Text
}
ATMContext16 *-- "1..1" ATMService20 : Service
%% ATMTransaction9 recursion level 1 with max 1
class ATMTransaction9{
ReconciliationIdentification IsoMax35Text
ICCRelatedData IsoMax10000Binary
}
ATMTransaction9 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
ATMTransaction9 *-- "0..1" OnLinePIN5 : CardholderNewPIN
ATMPINManagementRequest2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment in which the transaction is performed. | ATMEnvironment11 - Required 1..1 |
| Context | Context in which the transaction is performed. | ATMContext16 - Required 1..1 |
| Transaction | Transaction for which the service is requested. | ATMTransaction9 - 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 ATMPINManagementRequestV02 implementation follows a specific implementaiton pattern. First of all, ATMPINManagementRequestV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ATMPINManagementRequestV02Document implements IOuterDocument. Because ATMPINManagementRequestV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ATMPINManagementRequestV02.
classDiagram
class IOuterRecord
ATMPINManagementRequestV02 --|> IOuterRecord : Implements
ATMPINManagementRequestV02Document --|> IOuterDocument~ATMPINManagementRequestV02~ : Implements
class IOuterDocument~ATMPINManagementRequestV02~ {
ATMPINManagementRequestV02 Message
}
Document wrapper for serialization
The only real purpose ATMPINManagementRequestV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catp.010.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ATMPINManagementRequestV02.ToDocument() method. The returned ATMPINManagementRequestV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
ATMPINManagementRequestV02Document *-- ATMPINManagementRequestV02 : 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.010.001.02">
<ATMPINMgmtReq>
<Hdr>
<!-- Header inner content -->
</Hdr>
<PrtctdATMPINMgmtReq>
<!-- ProtectedATMPINManagementRequest inner content -->
</PrtctdATMPINMgmtReq>
<ATMPINMgmtReq>
<!-- ATMPINManagementRequest inner content -->
</ATMPINMgmtReq>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</ATMPINMgmtReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_YLWGQa4aEeW_TaP-ygI0SQ"
previousVersion="_SKd8QIq_EeSgLpgNvMAP2g"
name="ATMPINManagementRequestV02"
definition="The ATMPINManagementRequest message is sent by an ATM to an ATM manager to request an operation on the cardholder PIN."
registrationStatus="Registered"
messageSet="_wx2hAK1hEeWMg5rOByfExw"
xmlTag="ATMPINMgmtReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_YLWGQ64aEeW_TaP-ygI0SQ"
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="_eMl4Qa1wEeWMg5rOByfExw" />
<messageBuildingBlock
xmi:id="_YLWGRa4aEeW_TaP-ygI0SQ"
name="ProtectedATMPINManagementRequest"
definition="Encrypted body of the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrtctdATMPINMgmtReq"
complexType="_UfeMUWizEeS87LmvcA55sg" />
<messageBuildingBlock
xmi:id="_YLWGR64aEeW_TaP-ygI0SQ"
name="ATMPINManagementRequest"
definition="Information related to the request of a PIN management from an ATM."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="ATMPINMgmtReq"
complexType="_clVlUa4aEeW_TaP-ygI0SQ" />
<messageBuildingBlock
xmi:id="_YLWGSa4aEeW_TaP-ygI0SQ"
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="010"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.