AcceptorRejectionV01

caaa.015.001.01

Scope The AcceptorRejection message is used by the acquirer to reject a message received from the card acceptor. The acquirer uses this message as a substitute to a response or an advice response message sent to the card acceptor. Usage The AcceptorRejection message is used to indicate that the received message could not be processed by the acquirer (for example, unable to read or process the message, security error, duplicate 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
%% AcceptorRejectionV01 recursion level 0 with max 0
AcceptorRejectionV01 *-- "1..1" Header1 : Header
AcceptorRejectionV01 *-- "1..1" AcceptorRejection1 : 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. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header1 recursion level 0 with max 1
class Header1{
    MessageFunction MessageFunction1Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header1 *-- "1..1" GenericIdentification32 : InitiatingParty
Header1 *-- "0..1" GenericIdentification32 : RecipientParty
Header1 *-- "0..0" Traceability1 : Traceability
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% Traceability1 recursion level 1 with max 1
class Traceability1{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability1 *-- "1..1" GenericIdentification31 : RelayIdentification
  

Header1 members

Reject building block

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

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

AcceptorRejection1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorRejectionV01 --|> IOuterRecord : Implements
    AcceptorRejectionV01Document --|> IOuterDocument~AcceptorRejectionV01~ : Implements
    class IOuterDocument~AcceptorRejectionV01~ {
        AcceptorRejectionV01 Message
     }
  

Document wrapper for serialization

The only real purpose AcceptorRejectionV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.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 AcceptorRejectionV01.ToDocument() method. The returned AcceptorRejectionV01Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    AcceptorRejectionV01Document *-- AcceptorRejectionV01 : 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.01">
    <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="_NR9PhaMVEeCJ6YNENx4h-w_449190071"
  nextVersions="_juj-cSnAEeKIjpr--01h3Q"
  name="AcceptorRejectionV01"
  definition="Scope&#xD;&#xA;The AcceptorRejection message is used by the acquirer to reject a message received from the card acceptor. The acquirer uses this message as a substitute to a response or an advice response message sent to the card acceptor.&#xD;&#xA;Usage&#xD;&#xA;The AcceptorRejection message is used to indicate that the received message could not be processed by the acquirer (for example, unable to read or process the message, security error, duplicate message)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_NR9PhqMVEeCJ6YNENx4h-w_-1188630353"
    name="Header"
    definition="Rejection message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_SvV__wEcEeCQm6a_G2yO_w_677025486" />
  <messageBuildingBlock
    xmi:id="_NR9Ph6MVEeCJ6YNENx4h-w_-377399680"
    name="Reject"
    definition="Information related to the reject."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rjct"
    complexType="_Svfw9wEcEeCQm6a_G2yO_w_1794621080" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="015"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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