ExtendOrPayResponseV01

tsrv.015.001.01

The ExtendOrPayResponse message is sent by the party that requested issuance of the undertaking (applicant or obligor) to the party that issued the undertaking, in response to the issuer’s request for the applicant’s response to the beneficiary’s request to extend or pay.

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
%% ExtendOrPayResponseV01 recursion level 0 with max 0
ExtendOrPayResponseV01 *-- "1..1" ExtendOrPayQuery2 : ExtendOrPayResponseDetails
ExtendOrPayResponseV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

Now, we will zero-in one-by-one on each of these building blocks.

ExtendOrPayResponseDetails building block

Details of the extend or pay response. Undertaking extend or pay query details. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ExtendOrPayQuery2 recursion level 0 with max 1
class ExtendOrPayQuery2{
    Status DemandStatus1Code
}
ExtendOrPayQuery2 *-- "1..1" Undertaking9 : UndertakingIdentification
ExtendOrPayQuery2 *-- "1..1" Demand4 : DemandDetails
%% Undertaking9 recursion level 1 with max 1
class Undertaking9{
    Identification IsoMax35Text
    ApplicantReferenceNumber IsoMax35Text
}
Undertaking9 *-- "1..1" PartyIdentification43 : Issuer
%% Demand4 recursion level 1 with max 1
class Demand4{
    Identification IsoMax35Text
    Amount IsoActiveCurrencyAndAmount
}
  

ExtendOrPayQuery2 members

DigitalSignature building block

Digital signature of the response. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyAndSignature2 recursion level 0 with max 1
PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party
PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ExtendOrPayResponseV01 --|> IOuterRecord : Implements
    ExtendOrPayResponseV01Document --|> IOuterDocument~ExtendOrPayResponseV01~ : Implements
    class IOuterDocument~ExtendOrPayResponseV01~ {
        ExtendOrPayResponseV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ExtendOrPayResponseV01Document *-- ExtendOrPayResponseV01 : 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:tsrv.015.001.01">
    <XtndOrPayRspn>
        <XtndOrPayRspnDtls>
            <!-- ExtendOrPayResponseDetails inner content -->
        </XtndOrPayRspnDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </XtndOrPayRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9iZZEnltEeG7BsjMvd1mEw_519258789"
  name="ExtendOrPayResponseV01"
  definition="The ExtendOrPayResponse message is sent by the party that requested issuance of the undertaking (applicant or obligor) to the party that issued the undertaking, in response to the issuer's request for the applicant's response to the beneficiary’s request to extend or pay."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="XtndOrPayRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9iZZE3ltEeG7BsjMvd1mEw_-29894697"
    name="ExtendOrPayResponseDetails"
    definition="Details of the extend or pay response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="XtndOrPayRspnDtls"
    complexType="_-Dxn0nltEeG7BsjMvd1mEw_1814093000" />
  <messageBuildingBlock
    xmi:id="_9iZZFHltEeG7BsjMvd1mEw_1281187011"
    name="DigitalSignature"
    definition="Digital signature of the response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="015"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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