AcceptorRejectionV04

caaa.015.001.04

The AcceptorRejection message is sent by the acquirer (or its agent) to reject a message request or advice sent by an acceptor (or its agent), to indicate that the received message could not be processed.

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
%% AcceptorRejectionV04 recursion level 0 with max 0
AcceptorRejectionV04 *-- "1..1" Header13 : Header
AcceptorRejectionV04 *-- "1..1" AcceptorRejection2 : Reject
  

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

Header building block

Rejection message management information. Set of characteristics related to the protocol after a rejection. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header13 recursion level 0 with max 1
class Header13{
    MessageFunction MessageFunction4Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header13 *-- "0..1" GenericIdentification53 : InitiatingParty
Header13 *-- "0..1" GenericIdentification53 : RecipientParty
Header13 *-- "0..0" Traceability2 : Traceability
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% Traceability2 recursion level 1 with max 1
class Traceability2{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability2 *-- "1..1" GenericIdentification76 : RelayIdentification
  

Header13 members

Reject building block

Information related to the reject. Reject of an exchange. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorRejection2 recursion level 0 with max 1
class AcceptorRejection2{
    RejectReason RejectReason1Code
    AdditionalInformation IsoMax500Text
    MessageInError IsoMax100KBinary
}
  

AcceptorRejection2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorRejectionV04 --|> IOuterRecord : Implements
    AcceptorRejectionV04Document --|> IOuterDocument~AcceptorRejectionV04~ : Implements
    class IOuterDocument~AcceptorRejectionV04~ {
        AcceptorRejectionV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AcceptorRejectionV04Document *-- AcceptorRejectionV04 : 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:caaa.015.001.04">
    <AccptrRjctn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Rjct>
            <!-- Reject inner content -->
        </Rjct>
    </AccptrRjctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_Bu3IsWpCEeS4VPLpYyQgxQ"
  nextVersions="_xrr9MY0OEeWRYffwL7E13A"
  previousVersion="_cMIJETTgEeO5e9wx3yvd8g"
  name="AcceptorRejectionV04"
  definition="The AcceptorRejection message is sent by the acquirer (or its agent) to reject a message request or advice sent by an acceptor (or its agent), to indicate that the received message could not be processed."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_Bu3Is2pCEeS4VPLpYyQgxQ"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_Bu3ItWpCEeS4VPLpYyQgxQ"
    nextVersions="_xrr9NY0OEeWRYffwL7E13A"
    previousVersion="_cMIJEzTgEeO5e9wx3yvd8g"
    name="Header"
    definition="Rejection message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_Hl7pwWpCEeS4VPLpYyQgxQ" />
  <messageBuildingBlock
    xmi:id="_Bu3It2pCEeS4VPLpYyQgxQ"
    nextVersions="_xrr9N40OEeWRYffwL7E13A"
    previousVersion="_cMIJFTTgEeO5e9wx3yvd8g"
    name="Reject"
    definition="Information related to the reject."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rjct"
    complexType="_8TjN8TTfEeO5e9wx3yvd8g" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="015"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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