FinancialResponseV03

cain.004.001.03

The FinancialResponse message is sent by an issuer or an agent to an acquirer in response to a FinancialInitiation message.

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
%% FinancialResponseV03 recursion level 0 with max 0
FinancialResponseV03 *-- "1..1" Header62 : Header
FinancialResponseV03 *-- "1..1" FinancialResponse2 : Body
FinancialResponseV03 *-- "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
%% Header62 recursion level 0 with max 1
class Header62{
    MessageFunction MessageFunction16Code
    ProtocolVersion IsoMax2048Text
    ExchangeIdentification IsoMax35Text
    ReTransmissionCounter IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header62 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation
Header62 *-- "1..1" GenericIdentification183 : InitiatingParty
Header62 *-- "0..1" GenericIdentification183 : RecipientParty
Header62 *-- "0..0" AdditionalData1 : TraceData
Header62 *-- "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
  

Header62 members

Body building block

Information related to the financial response. Information related to the response of a financial initiation message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% FinancialResponse2 recursion level 0 with max 1
class FinancialResponse2{
    ICCRelatedData IsoMax10KHexBinaryText
}
FinancialResponse2 *-- "1..1" Environment26 : Environment
FinancialResponse2 *-- "1..1" Context13 : Context
FinancialResponse2 *-- "1..1" Transaction143 : Transaction
FinancialResponse2 *-- "0..1" AddendumData4 : AddendumData
FinancialResponse2 *-- "1..1" ProcessingResult10 : ProcessingResult
FinancialResponse2 *-- "0..0" ProtectedData1 : ProtectedData
FinancialResponse2 *-- "0..0" SupplementaryData1 : SupplementaryData
%% Environment26 recursion level 1 with max 1
Environment26 *-- "1..1" PartyIdentification263 : Acquirer
Environment26 *-- "0..1" PartyIdentification263 : Originator
Environment26 *-- "0..1" PartyIdentification263 : Sender
Environment26 *-- "0..1" PartyIdentification263 : Receiver
Environment26 *-- "0..1" PartyIdentification258 : Acceptor
Environment26 *-- "0..1" PartyIdentification263 : Destination
Environment26 *-- "0..1" Terminal6 : Terminal
Environment26 *-- "0..1" PartyIdentification263 : Issuer
Environment26 *-- "0..1" CardData9 : Card
Environment26 *-- "0..1" Wallet2 : Wallet
Environment26 *-- "0..1" Token2 : Token
Environment26 *-- "0..1" Cardholder19 : Cardholder
%% Context13 recursion level 1 with max 1
Context13 *-- "0..1" PointOfServiceContext4 : PointOfServiceContext
Context13 *-- "0..1" TransactionContext8 : TransactionContext
Context13 *-- "0..0" Verification4 : Verification
Context13 *-- "0..1" RiskContext2 : RiskContext
%% Transaction143 recursion level 1 with max 1
class Transaction143{
    TransactionType ISO8583TransactionTypeCode
    TransactionSubType IsoMax35Text
    TransactionAttribute TransactionAttribute2Code
    OtherTransactionAttribute IsoMax35Text
    MessageReason ISO8583MessageReasonCode
    AlternateMessageReason IsoMax256Text
    PreAuthorisationTimeLimit IsoMax6NumericText
    AssociatedDataDestination IsoMax35Text
    TransactionDescription IsoMax1000Text
}
Transaction143 *-- "0..0" AdditionalService2 : AdditionalService
Transaction143 *-- "0..0" SpecialProgrammeQualification1 : SpecialProgrammeQualification
Transaction143 *-- "1..1" TransactionIdentification51 : TransactionIdentification
Transaction143 *-- "1..1" DisputeData3 : DisputeData
Transaction143 *-- "1..1" TransactionAmounts2 : TransactionAmounts
Transaction143 *-- "0..0" AdditionalAmounts3 : AdditionalAmount
Transaction143 *-- "0..0" AdditionalFee2 : AdditionalFee
Transaction143 *-- "0..0" AdditionalFee2 : OriginalAdditionalFee
Transaction143 *-- "0..0" AccountBalance2 : AccountBalance
Transaction143 *-- "0..1" AccountDetails3 : AccountFrom
Transaction143 *-- "0..1" AccountDetails3 : AccountTo
Transaction143 *-- "0..0" AdditionalData1 : AdditionalData
Transaction143 *-- "0..1" AdditionalInformation20 : AdditionalInformation
%% AddendumData4 recursion level 1 with max 1
AddendumData4 *-- "0..1" FleetData5 : Fleet
AddendumData4 *-- "0..1" Instalment4 : Instalment
AddendumData4 *-- "0..0" AdditionalData1 : AdditionalData
%% ProcessingResult10 recursion level 1 with max 1
class ProcessingResult10{
    ApprovalCode IsoExact6AlphaNumericText
    ActionRequired IsoYesNoIndicator
}
ProcessingResult10 *-- "0..1" ApprovalEntity2 : ResponseSource
ProcessingResult10 *-- "1..1" ResultData7 : ResultData
ProcessingResult10 *-- "0..1" ErrorDetails2 : ErrorDetail
ProcessingResult10 *-- "0..1" ResultData7 : OriginalResultData
ProcessingResult10 *-- "0..0" Action13 : Action
ProcessingResult10 *-- "0..0" AdditionalAction1 : AdditionalAction
ProcessingResult10 *-- "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
  

FinancialResponse2 members

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

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the FinancialResponseV03 implementation follows a specific implementaiton pattern. First of all, FinancialResponseV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialResponseV03Document implements IOuterDocument. Because FinancialResponseV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialResponseV03.

classDiagram
    class IOuterRecord
    FinancialResponseV03 --|> IOuterRecord : Implements
    FinancialResponseV03Document --|> IOuterDocument~FinancialResponseV03~ : Implements
    class IOuterDocument~FinancialResponseV03~ {
        FinancialResponseV03 Message
     }
  

Document wrapper for serialization

The only real purpose FinancialResponseV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:cain.004.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FinancialResponseV03.ToDocument() method. The returned FinancialResponseV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    FinancialResponseV03Document *-- FinancialResponseV03 : 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.004.001.03">
    <FinRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Body>
            <!-- Body inner content -->
        </Body>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </FinRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_fpwfcYzMEeujJfnIQ4NlpQ"
  previousVersion="_aga5FVTsEeeeIYOiLZFQGg"
  name="FinancialResponseV03"
  definition="The FinancialResponse message is sent by an issuer or an agent to an acquirer in response to a FinancialInitiation message."
  registrationStatus="Registered"
  messageSet="_kT2-dARsEeWTJNHF-ohSqw"
  xmlTag="FinRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_fpwfc4zMEeujJfnIQ4NlpQ"
    previousVersion="_agkDAVTsEeeeIYOiLZFQGg"
    name="Header"
    definition="Information related to the management of the protocol."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_yws50RvUEey2RdTw-AkXzg" />
  <messageBuildingBlock
    xmi:id="_fpwfdYzMEeujJfnIQ4NlpQ"
    previousVersion="_agkDAFTsEeeeIYOiLZFQGg"
    name="Body"
    definition="Information related to the financial response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Body"
    complexType="_owpLcYzMEeujJfnIQ4NlpQ" />
  <messageBuildingBlock
    xmi:id="_fpwfd4zMEeujJfnIQ4NlpQ"
    previousVersion="_agkDA1TsEeeeIYOiLZFQGg"
    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="004"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.