caaa.015.001.05
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 %% AcceptorRejectionV05 recursion level 0 with max 0 AcceptorRejectionV05 *-- "1..1" Header26 : Header AcceptorRejectionV05 *-- "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 %% Header26 recursion level 0 with max 1 class Header26{ MessageFunction MessageFunction9Code ProtocolVersion IsoMax6Text ExchangeIdentification IsoNumber CreationDateTime IsoISODateTime } Header26 *-- "0..1" GenericIdentification53 : InitiatingParty Header26 *-- "0..1" GenericIdentification94 : RecipientParty Header26 *-- "0..0" Traceability5 : Traceability %% GenericIdentification53 recursion level 1 with max 1 class GenericIdentification53{ Identification IsoMax35Text Type PartyType3Code Issuer PartyType4Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% GenericIdentification94 recursion level 1 with max 1 class GenericIdentification94{ Identification IsoMax35Text Type PartyType3Code Issuer PartyType4Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } GenericIdentification94 *-- "0..1" NetworkParameters5 : RemoteAccess %% Traceability5 recursion level 1 with max 1 class Traceability5{ ProtocolName IsoMax35Text ProtocolVersion IsoMax6Text TraceDateTimeIn IsoISODateTime TraceDateTimeOut IsoISODateTime } Traceability5 *-- "1..1" GenericIdentification76 : RelayIdentification
Header26 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | MessageFunction9Code - Required 1..1 |
ProtocolVersion | Version of the acquirer protocol specifications. | IsoMax6Text - Required 1..1 |
ExchangeIdentification | Unique identification of an exchange occurrence. | IsoNumber - Optional 0..1 |
CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Required 1..1 |
InitiatingParty | Unique identification of the partner that has initiated the exchange. | GenericIdentification53 - Optional 0..1 |
RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification94 - Optional 0..1 |
Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability5 - Unknown 0..0 |
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
Member name | Description | Data Type / Multiplicity |
---|---|---|
RejectReason | Reject reason of the request or the advice. | RejectReason1Code - Required 1..1 |
AdditionalInformation | Additional information related to the reject of the exchange. | IsoMax500Text - Optional 0..1 |
MessageInError | Original request that caused the recipient party to reject it. | IsoMax100KBinary - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorRejectionV05 implementation follows a specific implementaiton pattern. First of all, AcceptorRejectionV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorRejectionV05Document implements IOuterDocument. Because AcceptorRejectionV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorRejectionV05.
classDiagram class IOuterRecord AcceptorRejectionV05 --|> IOuterRecord : Implements AcceptorRejectionV05Document --|> IOuterDocument~AcceptorRejectionV05~ : Implements class IOuterDocument~AcceptorRejectionV05~ { AcceptorRejectionV05 Message }
Document wrapper for serialization
The only real purpose AcceptorRejectionV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.015.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorRejectionV05.ToDocument() method. The returned AcceptorRejectionV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram AcceptorRejectionV05Document *-- AcceptorRejectionV05 : 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.05">
<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="_xrr9MY0OEeWRYffwL7E13A"
nextVersions="_W3Pk4QumEeqw5uEXxQ9H4g"
previousVersion="_Bu3IsWpCEeS4VPLpYyQgxQ"
name="AcceptorRejectionV05"
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="_fMW_EL1vEeKoB-JG4saAMg_-385897474"
xmlTag="AccptrRjctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_xrr9M40OEeWRYffwL7E13A"
type="purpose" />
<messageBuildingBlock
xmi:id="_xrr9NY0OEeWRYffwL7E13A"
nextVersions="_W3Pk5QumEeqw5uEXxQ9H4g"
previousVersion="_Bu3ItWpCEeS4VPLpYyQgxQ"
name="Header"
definition="Rejection message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_k3RnwY3YEeW56qaqQ8B0kQ" />
<messageBuildingBlock
xmi:id="_xrr9N40OEeWRYffwL7E13A"
nextVersions="_W3Pk5wumEeqw5uEXxQ9H4g"
previousVersion="_Bu3It2pCEeS4VPLpYyQgxQ"
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="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.