acmt.023.001.03
Scope The IdentificationVerificationRequest message is sent by an assigner to an assignee. It is used to request the verification of party and/or account identification information. Usage The IdentificationVerificationRequest message is sent before the sending of one or several transactions messages. The IdentificationVerificationRequest message can contain one or more verification requests.
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
%% IdentificationVerificationRequestV03 recursion level 0 with max 0
IdentificationVerificationRequestV03 *-- "1..1" IdentificationAssignment3 : Assignment
IdentificationVerificationRequestV03 *-- "1..1" IdentificationVerification4 : Verification
IdentificationVerificationRequestV03 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
Assignment building block
Identifies the identification assignment. Provides the details of the identification assignment. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% IdentificationAssignment3 recursion level 0 with max 1
class IdentificationAssignment3{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
IdentificationAssignment3 *-- "0..1" IParty40Choice : Creator
IdentificationAssignment3 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : FirstAgent
IdentificationAssignment3 *-- "1..1" IParty40Choice : Assigner
IdentificationAssignment3 *-- "1..1" IParty40Choice : Assignee
%% IParty40Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% IParty40Choice recursion level 1 with max 1
%% IParty40Choice recursion level 1 with max 1
IdentificationAssignment3 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the assigner, and sent to the next party in the chain to unambiguously identify the message. Usage: The assigner has to make sure that MessageIdentification is unique per assignee for a pre-agreed period. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date and time at which the identification assignment was created. | IsoISODateTime - Required 1..1 |
| Creator | Party that created the identification assignment. | IParty40Choice - Optional 0..1 |
| FirstAgent | Identifies the first agent in the identification chain, following the payment initiating party. | BranchAndFinancialInstitutionIdentification6 - Optional 0..1 |
| Assigner | Party that assigns the identification assignment to another party. This is also the sender of the message. | IParty40Choice - Required 1..1 |
| Assignee | Party that the identification assignment is assigned to. This is also the receiver of the message. | IParty40Choice - Required 1..1 |
Verification building block
Information concerning the identification data that is requested to be verified. Provides the details of the identification data that is requested to be verified. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% IdentificationVerification4 recursion level 0 with max 1
class IdentificationVerification4{
Identification IsoMax35Text
}
IdentificationVerification4 *-- "1..1" IdentificationInformation4 : PartyAndAccountIdentification
%% IdentificationInformation4 recursion level 1 with max 1
IdentificationInformation4 *-- "0..1" PartyIdentification135 : Party
IdentificationInformation4 *-- "0..1" CashAccount40 : Account
IdentificationInformation4 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : Agent
IdentificationVerification4 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique identification, as assigned by a sending party, to unambiguously identify the party and account identification information group within the message. | IsoMax35Text - Required 1..1 |
| PartyAndAccountIdentification | Party and/or account identification information for which verification is requested. | IdentificationInformation4 - Required 1..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
| Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the IdentificationVerificationRequestV03 implementation follows a specific implementaiton pattern. First of all, IdentificationVerificationRequestV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IdentificationVerificationRequestV03Document implements IOuterDocument. Because IdentificationVerificationRequestV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IdentificationVerificationRequestV03.
classDiagram
class IOuterRecord
IdentificationVerificationRequestV03 --|> IOuterRecord : Implements
IdentificationVerificationRequestV03Document --|> IOuterDocument~IdentificationVerificationRequestV03~ : Implements
class IOuterDocument~IdentificationVerificationRequestV03~ {
IdentificationVerificationRequestV03 Message
}
Document wrapper for serialization
The only real purpose IdentificationVerificationRequestV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.023.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using IdentificationVerificationRequestV03.ToDocument() method. The returned IdentificationVerificationRequestV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram
IdentificationVerificationRequestV03Document *-- IdentificationVerificationRequestV03 : 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:acmt.023.001.03">
<IdVrfctnReq>
<Assgnmt>
<!-- Assignment inner content -->
</Assgnmt>
<Vrfctn>
<!-- Verification inner content -->
</Vrfctn>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</IdVrfctnReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_dgnUEwyYEeukGOovyT2RcQ"
previousVersion="_sZX_5FkyEeGeoaLUQk__nA_-973563434"
name="IdentificationVerificationRequestV03"
definition="Scope
The IdentificationVerificationRequest message is sent by an assigner to an assignee. It is used to request the verification of party and/or account identification information.
Usage
The IdentificationVerificationRequest message is sent before the sending of one or several transactions messages.
The IdentificationVerificationRequest message can contain one or more verification requests."
registrationStatus="Registered"
messageSet="_wRoFw02rEeG_I4xRYCA_7g"
xmlTag="IdVrfctnReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_dgnUFAyYEeukGOovyT2RcQ"
name="Assignment"
definition="Identifies the identification assignment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Assgnmt"
complexType="_QIQa4W49EeiU9cctagi5ow" />
<messageBuildingBlock
xmi:id="_dgnUFQyYEeukGOovyT2RcQ"
name="Verification"
definition="Information concerning the identification data that is requested to be verified."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="Vrfctn"
complexType="_fevvsdcZEeqRFcf2R4bPBw" />
<messageBuildingBlock
xmi:id="_dgnUFgyYEeukGOovyT2RcQ"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="acmt"
messageFunctionality="023"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.