cain.018.001.02
The VerificationInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer). It conveys information to a receiver requiring verification or authentication.
Examples of usages are: authentication of certificates, assurance levels of tokens, certificate management, address verification, account verification and cheque verification. It is also used to inform the receiver of a verification that has been completed on its behalf.
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
%% VerificationInitiationV02 recursion level 0 with max 0
VerificationInitiationV02 *-- "1..1" Header60 : Header
VerificationInitiationV02 *-- "1..1" VerificationInitiation2 : Body
VerificationInitiationV02 *-- "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 management of the protocol. Set of characteristics related to the protocol.
For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Header60 recursion level 0 with max 1
class Header60{
MessageFunction MessageFunction17Code
ProtocolVersion IsoMax2048Text
ExchangeIdentification IsoMax35Text
ReTransmissionCounter IsoMax3NumericText
CreationDateTime IsoISODateTime
}
Header60 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation
Header60 *-- "1..1" GenericIdentification183 : InitiatingParty
Header60 *-- "0..1" GenericIdentification183 : RecipientParty
Header60 *-- "0..0" AdditionalData1 : TraceData
Header60 *-- "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
Header60 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | MessageFunction17Code - 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. | 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 verification initiation. Information related to the verification initiation message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% VerificationInitiation2 recursion level 0 with max 1
class VerificationInitiation2{
ICCRelatedData IsoMax10KHexBinaryText
}
VerificationInitiation2 *-- "1..1" Environment31 : Environment
VerificationInitiation2 *-- "1..1" Context11 : Context
VerificationInitiation2 *-- "1..1" Transaction146 : Transaction
VerificationInitiation2 *-- "0..1" AddendumData5 : AddendumData
VerificationInitiation2 *-- "0..1" ProcessingResult12 : ProcessingResult
VerificationInitiation2 *-- "0..0" ProtectedData1 : ProtectedData
VerificationInitiation2 *-- "0..0" SupplementaryData1 : SupplementaryData
%% Environment31 recursion level 1 with max 1
Environment31 *-- "1..1" PartyIdentification263 : Acquirer
Environment31 *-- "0..1" PartyIdentification263 : Originator
Environment31 *-- "0..1" PartyIdentification263 : Sender
Environment31 *-- "0..1" PartyIdentification263 : Receiver
Environment31 *-- "0..1" PartyIdentification255 : Acceptor
Environment31 *-- "0..1" PartyIdentification263 : Destination
Environment31 *-- "0..1" PartyIdentification257 : Payer
Environment31 *-- "0..1" PartyIdentification257 : Payee
Environment31 *-- "0..1" Terminal4 : Terminal
Environment31 *-- "0..1" PartyIdentification263 : Issuer
Environment31 *-- "0..1" CardData6 : Card
Environment31 *-- "0..1" CustomerDevice4 : CustomerDevice
Environment31 *-- "0..1" Wallet2 : Wallet
Environment31 *-- "0..1" Token3 : Token
Environment31 *-- "0..1" Cardholder19 : Cardholder
%% Context11 recursion level 1 with max 1
Context11 *-- "1..1" PointOfServiceContext3 : PointOfServiceContext
Context11 *-- "1..1" TransactionContext7 : TransactionContext
Context11 *-- "0..0" Verification5 : Verification
Context11 *-- "0..1" RiskContext2 : RiskContext
%% Transaction146 recursion level 1 with max 1
class Transaction146{
TransactionType ISO8583TransactionTypeCode
TransactionSubType IsoMax35Text
TransactionAttribute TransactionAttribute2Code
OtherTransactionAttribute IsoMax35Text
MessageReason ISO8583MessageReasonCode
AlternateMessageReason IsoMax256Text
TransactionCurrency ISO3NumericCurrencyCode
TransactionDescription IsoMax1000Text
}
Transaction146 *-- "0..0" AdditionalService2 : AdditionalService
Transaction146 *-- "0..0" SpecialProgrammeQualification1 : SpecialProgrammeQualification
Transaction146 *-- "1..1" TransactionIdentification18 : TransactionIdentification
Transaction146 *-- "0..0" DetailedAmount23 : DetailedAmount
Transaction146 *-- "0..1" Amount15 : ReconciliationAmount
Transaction146 *-- "0..0" AdditionalAmounts3 : AdditionalAmount
Transaction146 *-- "0..0" AdditionalFee2 : AdditionalFee
Transaction146 *-- "0..1" FundingService2 : FundsServices
Transaction146 *-- "0..1" AccountDetails3 : AccountFrom
Transaction146 *-- "0..1" AccountDetails3 : AccountTo
Transaction146 *-- "0..0" AdditionalData1 : AdditionalData
%% AddendumData5 recursion level 1 with max 1
AddendumData5 *-- "0..1" Instalment4 : Instalment
AddendumData5 *-- "0..0" AdditionalData1 : AdditionalData
%% ProcessingResult12 recursion level 1 with max 1
class ProcessingResult12{
ActionRequired IsoYesNoIndicator
}
ProcessingResult12 *-- "0..1" ApprovalData1 : ApprovalData
ProcessingResult12 *-- "0..1" ResultData11 : ResultData
ProcessingResult12 *-- "0..1" ResultData7 : OriginalResultData
ProcessingResult12 *-- "0..0" Action13 : Action
ProcessingResult12 *-- "0..0" AdditionalAction1 : AdditionalAction
ProcessingResult12 *-- "0..0" AdditionalInformation29 : AdditionalInformation
%% 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
VerificationInitiation2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | Environment31 - Required 1..1 |
| Context | Context in which the card transaction is performed. | Context11 - Required 1..1 |
| Transaction | Card transaction for which an authorisation is requested. | Transaction146 - Required 1..1 |
| AddendumData | Component contains data structures applicable to certain industries that require specific data within transaction messages | AddendumData5 - Optional 0..1 |
| ProcessingResult | Outcome of the processing of the verification. | ProcessingResult12 - Optional 0..1 |
| ICCRelatedData | Data related to an integrated circuit card application embedded in the payment card of the cardholder. ISO 8583 bit 55 | IsoMax10KHexBinaryText - 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 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 VerificationInitiationV02 implementation follows a specific implementaiton pattern. First of all, VerificationInitiationV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, VerificationInitiationV02Document implements IOuterDocument. Because VerificationInitiationV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type VerificationInitiationV02.
classDiagram
class IOuterRecord
VerificationInitiationV02 --|> IOuterRecord : Implements
VerificationInitiationV02Document --|> IOuterDocument~VerificationInitiationV02~ : Implements
class IOuterDocument~VerificationInitiationV02~ {
VerificationInitiationV02 Message
}
Document wrapper for serialization
The only real purpose VerificationInitiationV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:cain.018.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using VerificationInitiationV02.ToDocument() method. The returned VerificationInitiationV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
VerificationInitiationV02Document *-- VerificationInitiationV02 : 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:cain.018.001.02">
<VrfctnInitn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<Body>
<!-- Body inner content -->
</Body>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</VrfctnInitn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_3L3tMYELEeu6D49Gi-ZPwQ"
previousVersion="_acX4lVf3EeedJb6VxsnkPg"
name="VerificationInitiationV02"
definition="The VerificationInitiation message can be initiated by any party and received by any party (acquirer, agent or issuer). It conveys information to a receiver requiring verification or authentication. 



Examples of usages are: authentication of certificates, assurance levels of tokens, certificate management, address verification, account verification and cheque verification. It is also used to inform the receiver of a verification that has been completed on its behalf."
registrationStatus="Registered"
messageSet="_kT2-dARsEeWTJNHF-ohSqw"
xmlTag="VrfctnInitn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_3L3tM4ELEeu6D49Gi-ZPwQ"
previousVersion="_acX4mFf3EeedJb6VxsnkPg"
name="Header"
definition="Information related to the management of the protocol."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_x3IU4RvREey2RdTw-AkXzg" />
<messageBuildingBlock
xmi:id="_3L3tNYELEeu6D49Gi-ZPwQ"
previousVersion="_acX4l1f3EeedJb6VxsnkPg"
name="Body"
definition="Information related to the verification initiation."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Body"
complexType="_9_sxcYELEeu6D49Gi-ZPwQ" />
<messageBuildingBlock
xmi:id="_3L3tN4ELEeu6D49Gi-ZPwQ"
previousVersion="_acX4mVf3EeedJb6VxsnkPg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC"
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
<messageDefinitionIdentifier
businessArea="cain"
messageFunctionality="018"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.