DebitAuthorisationResponse

camt.036.001.01

Scope The Debit Authorisation Response message is sent by an account owner to its account servicing institution. This message is used to approve or reject a debit authorisation request. Usage The Debit Authorisation Response message is used to reply to a Debit Authorisation Request message. The Debit Authorisation Response message covers one and only one payment instruction at a time. If an account owner needs to reply to several Debit Authorisation Request messages, then multiple Debit Authorisation Response messages must be sent. The Debit Authorisation Response message indicates whether the account owner agrees with the request by means of a code. It also allows further details to be given about the debit authorisation, such as acceptable amount and value date for the debit. The Debit Authorisation Response message must be used exclusively between the account owner and the account servicing institution. It must not be used in place of a Resolution Of Investigation message between subsequent agents.

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
%% DebitAuthorisationResponse recursion level 0 with max 0
DebitAuthorisationResponse *-- "1..1" CaseAssignment : Assignment
DebitAuthorisationResponse *-- "1..1" Case : Case
DebitAuthorisationResponse *-- "1..1" DebitAuthorisationConfirmation : Confirmation
  

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

Assignment building block

Identifies an assignment. Represents the assignment of a case to a party. Assignment is a step in the overall process of managing a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment recursion level 0 with max 1
class CaseAssignment{
    Identification IsoMax35Text
    Assigner IsoAnyBICIdentifier
    Assignee IsoAnyBICIdentifier
    CreationDateTime IsoISODateTime
}
  

CaseAssignment members

Case building block

Identifies a case. Information identifying a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case recursion level 0 with max 1
class Case{
    Identification IsoMax35Text
    Creator IsoAnyBICIdentifier
    ReopenCaseIndication IsoYesNoIndicator
}
  

Case members

Confirmation building block

Indicates if the debit authorisation is granted or not. Indicates if the debit authorisation is granted or not. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DebitAuthorisationConfirmation recursion level 0 with max 1
class DebitAuthorisationConfirmation{
    DebitAuthorisation IsoYesNoIndicator
    AmountToDebit IsoCurrencyAndAmount
    ValueDateToDebit IsoISODate
    Reason IsoMax140Text
}
  

DebitAuthorisationConfirmation members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    DebitAuthorisationResponse --|> IOuterRecord : Implements
    DebitAuthorisationResponseDocument --|> IOuterDocument~DebitAuthorisationResponse~ : Implements
    class IOuterDocument~DebitAuthorisationResponse~ {
        DebitAuthorisationResponse Message
     }
  

Document wrapper for serialization

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

classDiagram
    DebitAuthorisationResponseDocument *-- DebitAuthorisationResponse : 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:camt.036.001.01">
    <camt.036.001.01>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Conf>
            <!-- Confirmation inner content -->
        </Conf>
    </camt.036.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_Tq8ZyNE-Ed-BzquC8wXy7w_1812295152"
  nextVersions="_UJ8C6NE-Ed-BzquC8wXy7w_1776892387"
  name="DebitAuthorisationResponse"
  definition="Scope&#xD;&#xA;The Debit Authorisation Response message is sent by an account owner to its account servicing institution. This message is used to approve or reject a debit authorisation request.&#xD;&#xA;Usage&#xD;&#xA;The Debit Authorisation Response message is used to reply to a Debit Authorisation Request message.&#xD;&#xA;The Debit Authorisation Response message covers one and only one payment instruction at a time. If an account owner needs to reply to several Debit Authorisation Request messages, then multiple Debit Authorisation Response messages must be sent.&#xD;&#xA;The Debit Authorisation Response message indicates whether the account owner agrees with the request by means of a code. It also allows further details to be given about the debit authorisation, such as acceptable amount and value date for the debit.&#xD;&#xA;The Debit Authorisation Response message must be used exclusively between the account owner and the account servicing institution. It must not be used in place of a Resolution Of Investigation message between subsequent agents."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="camt.036.001.01"
  xmlTag="camt.036.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_Tq8ZydE-Ed-BzquC8wXy7w_1252126016"
    name="Assignment"
    definition="Identifies an assignment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Dpetp-Ed-ak6NoX_4Aeg_588710247" />
  <messageBuildingBlock
    xmi:id="_Tq8ZytE-Ed-BzquC8wXy7w_1259517114"
    name="Case"
    definition="Identifies a case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnotp-Ed-ak6NoX_4Aeg_136183535" />
  <messageBuildingBlock
    xmi:id="_Tq8Zy9E-Ed-BzquC8wXy7w_-1737905108"
    name="Confirmation"
    definition="Indicates if the debit authorisation is granted or not."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Conf"
    complexType="_T9WkaNp-Ed-ak6NoX_4Aeg_2085142381" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="036"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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