acmt.023.001.01
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
%% IdentificationVerificationRequestV01 recursion level 0 with max 0
IdentificationVerificationRequestV01 *-- "1..1" IdentificationAssignment1 : Assignment
IdentificationVerificationRequestV01 *-- "1..1" IdentificationVerification1 : Verification
Now, we will zero-in one-by-one on each of these building blocks.
Assignment building block
Identifies the identification assignment. Set of elements that identify the identification assignment. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% IdentificationAssignment1 recursion level 0 with max 1
class IdentificationAssignment1{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
IdentificationAssignment1 *-- "0..1" IParty7Choice : Creator
IdentificationAssignment1 *-- "1..1" IParty7Choice : Assigner
IdentificationAssignment1 *-- "1..1" IParty7Choice : Assignee
%% IParty7Choice recursion level 1 with max 1
%% IParty7Choice recursion level 1 with max 1
%% IParty7Choice recursion level 1 with max 1
IdentificationAssignment1 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. | IParty7Choice - Optional 0..1 |
| Assigner | Party that assigns the identification assignment to another party. This is also the sender of the message. | IParty7Choice - Required 1..1 |
| Assignee | Party that the identification assignment is assigned to. This is also the receiver of the message. | IParty7Choice - Required 1..1 |
Verification building block
Information concerning the identification data that is requested to be verified. Set of elements used to provide information concerning the identification data that is requested to be verified. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% IdentificationVerification1 recursion level 0 with max 1
class IdentificationVerification1{
Identification IsoMax35Text
}
IdentificationVerification1 *-- "1..1" IdentificationInformation1 : PartyAndAccountIdentification
%% IdentificationInformation1 recursion level 1 with max 1
IdentificationInformation1 *-- "0..1" PartyIdentification32 : Party
IdentificationInformation1 *-- "0..1" IAccountIdentification4Choice : Account
IdentificationInformation1 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : Agent
IdentificationVerification1 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. | IdentificationInformation1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the IdentificationVerificationRequestV01 implementation follows a specific implementaiton pattern. First of all, IdentificationVerificationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IdentificationVerificationRequestV01Document implements IOuterDocument. Because IdentificationVerificationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IdentificationVerificationRequestV01.
classDiagram
class IOuterRecord
IdentificationVerificationRequestV01 --|> IOuterRecord : Implements
IdentificationVerificationRequestV01Document --|> IOuterDocument~IdentificationVerificationRequestV01~ : Implements
class IOuterDocument~IdentificationVerificationRequestV01~ {
IdentificationVerificationRequestV01 Message
}
Document wrapper for serialization
The only real purpose IdentificationVerificationRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.023.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using IdentificationVerificationRequestV01.ToDocument() method. The returned IdentificationVerificationRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
IdentificationVerificationRequestV01Document *-- IdentificationVerificationRequestV01 : 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.01">
<IdVrfctnReq>
<Assgnmt>
<!-- Assignment inner content -->
</Assgnmt>
<Vrfctn>
<!-- Verification inner content -->
</Vrfctn>
</IdVrfctnReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_sRylWGtdEeCY4-KZ9JEyUQ_-1959332273"
nextVersions="_sZX_5FkyEeGeoaLUQk__nA_-973563434"
name="IdentificationVerificationRequestV01"
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="_urpIICeJEeOCeO5e7islRQ"
xmlTag="IdVrfctnReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_sRylWWtdEeCY4-KZ9JEyUQ_-1079532632"
name="Assignment"
definition="Identifies the identification assignment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Assgnmt"
complexType="_QpUAxNp-Ed-ak6NoX_4Aeg_1072835479" />
<messageBuildingBlock
xmi:id="_sRylWmtdEeCY4-KZ9JEyUQ_731202779"
name="Verification"
definition="Information concerning the identification data that is requested to be verified."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="Vrfctn"
complexType="_QpUAwdp-Ed-ak6NoX_4Aeg_1074529982" />
<messageDefinitionIdentifier
businessArea="acmt"
messageFunctionality="023"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.