cafm.001.001.02
The FileActionInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer).
This message is used to inquire, add, change, delete or replace a file or a record.
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 %% FileActionInitiationV02 recursion level 0 with max 0 FileActionInitiationV02 *-- "1..1" Header68 : Header FileActionInitiationV02 *-- "1..1" FileActionInitiation2 : Body FileActionInitiationV02 *-- "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 protocol management. Set of characteristics related to the protocol.
For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header68 recursion level 0 with max 1 class Header68{ MessageFunction MessageFunction44Code ProtocolVersion IsoMax2048Text ExchangeIdentification IsoMax35Text ReTransmissionCounter IsoMax3NumericText CreationDateTime IsoISODateTime } Header68 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation Header68 *-- "1..1" GenericIdentification183 : InitiatingParty Header68 *-- "0..1" GenericIdentification183 : RecipientParty Header68 *-- "0..0" AdditionalData1 : TraceData Header68 *-- "0..0" Traceability9 : Traceability %% BatchManagementInformation1 recursion level 1 with max 1 class BatchManagementInformation1{ CollectionIdentification IsoMax35Text BatchIdentification IsoMax35Text MessageSequenceNumber IsoMax15NumericText MessageChecksumInputValue IsoMax140Binary } %% GenericIdentification183 recursion level 1 with max 1 class GenericIdentification183{ Identification IsoMax35Text Type PartyType17Code OtherType IsoMax35Text Assigner PartyType18Code Country ISOMax3ACountryCode ShortName IsoMax35Text } %% GenericIdentification183 recursion level 1 with max 1 class GenericIdentification183{ Identification IsoMax35Text Type PartyType17Code OtherType IsoMax35Text Assigner PartyType18Code Country ISOMax3ACountryCode ShortName IsoMax35Text } %% AdditionalData1 recursion level 1 with max 1 class AdditionalData1{ Type IsoMax35Text Value IsoMax2048Text } %% Traceability9 recursion level 1 with max 1 class Traceability9{ TraceDateTimeIn IsoISODateTime TraceDateTimeOut IsoISODateTime } Traceability9 *-- "1..1" GenericIdentification183 : RelayIdentification
Header68 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | MessageFunction44Code - 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 |
BatchManagementInformation | Information related to the batch and the collection to which the message belongs if any. | BatchManagementInformation1 - Optional 0..1 |
InitiatingParty | Unique identification of the partner that has initiated the exchange. | GenericIdentification183 - Required 1..1 |
RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification183 - 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. | Traceability9 - Unknown 0..0 |
Body building block
Information related to the initiation of a file action. Information related to the file action. For comparison, see the ISO20022 official specification
classDiagram direction tb %% FileActionInitiation2 recursion level 0 with max 1 FileActionInitiation2 *-- "1..1" Environment22 : Environment FileActionInitiation2 *-- "0..1" Context17 : Context FileActionInitiation2 *-- "1..1" Transaction157 : Transaction FileActionInitiation2 *-- "0..1" ResultData9 : ProcessingResult FileActionInitiation2 *-- "0..0" ProtectedData1 : ProtectedData FileActionInitiation2 *-- "0..0" SupplementaryData1 : SupplementaryData %% Environment22 recursion level 1 with max 1 Environment22 *-- "0..1" PartyIdentification263 : Acquirer Environment22 *-- "0..1" PartyIdentification263 : Originator Environment22 *-- "0..1" PartyIdentification263 : Sender Environment22 *-- "0..1" PartyIdentification263 : Receiver Environment22 *-- "0..1" PartyIdentification254 : Acceptor Environment22 *-- "0..1" PartyIdentification257 : Payer Environment22 *-- "0..1" PartyIdentification257 : Payee Environment22 *-- "0..1" Terminal4 : Terminal Environment22 *-- "0..1" PartyIdentification263 : Issuer Environment22 *-- "0..1" CardData8 : Card Environment22 *-- "0..1" PartyIdentification263 : Destination Environment22 *-- "0..1" CustomerDevice4 : CustomerDevice Environment22 *-- "0..1" Wallet2 : Wallet Environment22 *-- "0..1" Token3 : Token Environment22 *-- "0..1" Cardholder19 : Cardholder %% Context17 recursion level 1 with max 1 Context17 *-- "0..1" TransactionContext10 : TransactionContext %% Transaction157 recursion level 1 with max 1 class Transaction157{ MessageReason ISO8583MessageReasonCode AlternateMessageReason IsoMax256Text FileActionScope FileActionScope1Code FileActionType FileActionType2Code OtherFileActionType IsoMax35Text ContinuationIndicator IsoTrueFalseIndicator } Transaction157 *-- "0..1" TransactionIdentification12 : TransactionIdentification Transaction157 *-- "1..1" FileActionDetails2 : FileActionDetails Transaction157 *-- "0..0" AdditionalFee2 : AdditionalFee Transaction157 *-- "0..0" AdditionalData1 : AdditionalData Transaction157 *-- "0..1" CorrectionIdentification1 : Correction %% ResultData9 recursion level 1 with max 1 class ResultData9{ Result FileActionResult1Code OtherResult IsoMax35Text ResultDetails ISO8583ResponseCode OtherResultDetails IsoMax35Text } %% 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
FileActionInitiation2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Environment | Environment of the file action transaction. | Environment22 - Required 1..1 |
Context | Contains or describes conditions and characteristics of the transaction. | Context17 - Optional 0..1 |
Transaction | File action transaction details. | Transaction157 - Required 1..1 |
ProcessingResult | Results of the file action processing. | ResultData9 - Optional 0..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. It corresponds partially to ISO 8583 field number 53, completed by the field number 64 or 128. 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 FileActionInitiationV02 implementation follows a specific implementaiton pattern. First of all, FileActionInitiationV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FileActionInitiationV02Document implements IOuterDocument. Because FileActionInitiationV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FileActionInitiationV02.
classDiagram class IOuterRecord FileActionInitiationV02 --|> IOuterRecord : Implements FileActionInitiationV02Document --|> IOuterDocument~FileActionInitiationV02~ : Implements class IOuterDocument~FileActionInitiationV02~ { FileActionInitiationV02 Message }
Document wrapper for serialization
The only real purpose FileActionInitiationV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:cafm.001.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FileActionInitiationV02.ToDocument() method. The returned FileActionInitiationV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram FileActionInitiationV02Document *-- FileActionInitiationV02 : 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:cafm.001.001.02">
<FileActnInitn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<Body>
<!-- Body inner content -->
</Body>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</FileActnInitn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_LQXFYIKwEeu4svNQ5N-l6w"
previousVersion="_OtjNBFZiEeen1vB4iz5SyA"
name="FileActionInitiationV02"
definition="The FileActionInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer).

This message is used to inquire, add, change, delete or replace a file or a record."
registrationStatus="Registered"
messageSet="_kT2-dARsEeWTJNHF-ohSqw"
xmlTag="FileActnInitn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_LQXFYoKwEeu4svNQ5N-l6w"
previousVersion="_OtjNB1ZiEeen1vB4iz5SyA"
name="Header"
definition="Information related to the protocol management."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_qtlCIUGKEeyZG7AU5fJYtQ" />
<messageBuildingBlock
xmi:id="_LQXFZIKwEeu4svNQ5N-l6w"
previousVersion="_OtjNBVZiEeen1vB4iz5SyA"
name="Body"
definition="Information related to the initiation of a file action."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Body"
complexType="_7nhvUYKvEeu4svNQ5N-l6w" />
<messageBuildingBlock
xmi:id="_LQXFZoKwEeu4svNQ5N-l6w"
previousVersion="_OtjNBlZiEeen1vB4iz5SyA"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC.
It corresponds partially to ISO 8583 field number 53, completed by the field number 64 or 128."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
<messageDefinitionIdentifier
businessArea="cafm"
messageFunctionality="001"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.