caaa.005.001.05
The AcceptorCancellationRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to request the cancellation of a successfully completed transaction. Cancellation should only occur before the transaction has been cleared.
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
%% AcceptorCancellationRequestV05 recursion level 0 with max 0
AcceptorCancellationRequestV05 *-- "1..1" Header30 : Header
AcceptorCancellationRequestV05 *-- "1..1" AcceptorCancellationRequest5 : CancellationRequest
AcceptorCancellationRequestV05 *-- "0..1" ContentInformationType15 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Cancellation request message management information. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Header30 recursion level 0 with max 1
class Header30{
MessageFunction MessageFunction10Code
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoNumber
CreationDateTime IsoISODateTime
}
Header30 *-- "1..1" GenericIdentification53 : InitiatingParty
Header30 *-- "0..1" GenericIdentification94 : RecipientParty
Header30 *-- "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
Header30 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | MessageFunction10Code - Required 1..1 |
| ProtocolVersion | Version of the acquirer protocol specifications. | IsoMax6Text - Required 1..1 |
| ExchangeIdentification | Unique identification of an exchange occurrence. | IsoNumber - Required 1..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 - Required 1..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 |
CancellationRequest building block
Information related to the cancellation request. Cancellation request from an acceptor. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AcceptorCancellationRequest5 recursion level 0 with max 1
AcceptorCancellationRequest5 *-- "1..1" CardPaymentEnvironment48 : Environment
AcceptorCancellationRequest5 *-- "1..1" CardPaymentContext16 : Context
AcceptorCancellationRequest5 *-- "1..1" CardPaymentTransaction56 : Transaction
%% CardPaymentEnvironment48 recursion level 1 with max 1
CardPaymentEnvironment48 *-- "0..1" Acquirer4 : Acquirer
CardPaymentEnvironment48 *-- "0..1" Organisation25 : Merchant
CardPaymentEnvironment48 *-- "1..1" PointOfInteraction5 : POI
CardPaymentEnvironment48 *-- "1..1" PaymentCard20 : Card
CardPaymentEnvironment48 *-- "0..1" CustomerDevice1 : CustomerDevice
CardPaymentEnvironment48 *-- "0..1" CustomerDevice1 : Wallet
CardPaymentEnvironment48 *-- "0..1" CardPaymentToken3 : PaymentToken
%% CardPaymentContext16 recursion level 1 with max 1
CardPaymentContext16 *-- "1..1" PaymentContext16 : PaymentContext
CardPaymentContext16 *-- "0..1" SaleContext2 : SaleContext
%% CardPaymentTransaction56 recursion level 1 with max 1
class CardPaymentTransaction56{
TransactionCapture IsoTrueFalseIndicator
MerchantCategoryCode IsoMin3Max4Text
SaleReferenceIdentification IsoMax35Text
InitiatorTransactionIdentification IsoMax35Text
RecipientTransactionIdentification IsoMax35Text
ReconciliationIdentification IsoMax35Text
AdditionalTransactionData IsoMax70Text
}
CardPaymentTransaction56 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction56 *-- "1..1" CardPaymentTransaction52 : OriginalTransaction
CardPaymentTransaction56 *-- "1..1" CardPaymentTransactionDetails34 : TransactionDetails
AcceptorCancellationRequest5 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment48 - Required 1..1 |
| Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext16 - Required 1..1 |
| Transaction | Cancellation transaction between an acceptor and an acquirer. | CardPaymentTransaction56 - Required 1..1 |
SecurityTrailer building block
Trailer of the message containing a MAC. General cryptographic message syntax (CMS) containing authenticated data. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ContentInformationType15 recursion level 0 with max 1
class ContentInformationType15{
ContentType ContentType2Code
}
ContentInformationType15 *-- "1..1" AuthenticatedData4 : AuthenticatedData
%% AuthenticatedData4 recursion level 1 with max 1
class AuthenticatedData4{
Version IsoNumber
MAC IsoMax140Binary
}
AuthenticatedData4 *-- "1..0" IRecipient4Choice : Recipient
AuthenticatedData4 *-- "1..1" AlgorithmIdentification15 : MACAlgorithm
AuthenticatedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType15 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
| AuthenticatedData | Data protection by a message authentication code (MAC). | AuthenticatedData4 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorCancellationRequestV05 implementation follows a specific implementaiton pattern. First of all, AcceptorCancellationRequestV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorCancellationRequestV05Document implements IOuterDocument. Because AcceptorCancellationRequestV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorCancellationRequestV05.
classDiagram
class IOuterRecord
AcceptorCancellationRequestV05 --|> IOuterRecord : Implements
AcceptorCancellationRequestV05Document --|> IOuterDocument~AcceptorCancellationRequestV05~ : Implements
class IOuterDocument~AcceptorCancellationRequestV05~ {
AcceptorCancellationRequestV05 Message
}
Document wrapper for serialization
The only real purpose AcceptorCancellationRequestV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.005.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorCancellationRequestV05.ToDocument() method. The returned AcceptorCancellationRequestV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorCancellationRequestV05Document *-- AcceptorCancellationRequestV05 : 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.005.001.05">
<AccptrCxlReq>
<Hdr>
<!-- Header inner content -->
</Hdr>
<CxlReq>
<!-- CancellationRequest inner content -->
</CxlReq>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</AccptrCxlReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_bq6h8Y1AEeWsypzzYao74A"
nextVersions="_A39QsaqAEeanIZ10Ka8PnA"
previousVersion="_rI7scGl3EeSQMKir9owD5A"
name="AcceptorCancellationRequestV05"
definition="The AcceptorCancellationRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to request the cancellation of a successfully completed transaction. Cancellation should only occur before the transaction has been cleared.

"
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AccptrCxlReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_bq6h841AEeWsypzzYao74A"
type="purpose" />
<messageBuildingBlock
xmi:id="_bq6h9Y1AEeWsypzzYao74A"
nextVersions="_A39QtaqAEeanIZ10Ka8PnA"
previousVersion="_rI7sdGl3EeSQMKir9owD5A"
name="Header"
definition="Cancellation request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_IWFRgY0PEeWRYffwL7E13A" />
<messageBuildingBlock
xmi:id="_bq6h941AEeWsypzzYao74A"
nextVersions="_A39Qt6qAEeanIZ10Ka8PnA"
previousVersion="_rI7sdml3EeSQMKir9owD5A"
name="CancellationRequest"
definition="Information related to the cancellation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="CxlReq"
complexType="_7fP2QY1AEeWsypzzYao74A" />
<messageBuildingBlock
xmi:id="_bq6h-Y1AEeWsypzzYao74A"
nextVersions="_A39QuaqAEeanIZ10Ka8PnA"
previousVersion="_rI7seGl3EeSQMKir9owD5A"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_uSOuUCrHEeWRf8RNsvC5fQ" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="005"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.