caaa.002.001.09
The AcceptorAuthorisationResponse message is sent by the acquirer (or its agent) to an acceptor (or its agent), to return the result of the validation made by issuer about the payment transaction.
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 %% AcceptorAuthorisationResponseV09 recursion level 0 with max 0 AcceptorAuthorisationResponseV09 *-- "1..1" Header58 : Header AcceptorAuthorisationResponseV09 *-- "1..1" AcceptorAuthorisationResponse9 : AuthorisationResponse AcceptorAuthorisationResponseV09 *-- "0..1" ContentInformationType24 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Authorisation response message management information. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Header58 recursion level 0 with max 1 class Header58{ MessageFunction MessageFunction41Code ProtocolVersion IsoMax6Text ExchangeIdentification IsoNumber ReTransmissionCounter IsoMax3NumericText CreationDateTime IsoISODateTime } Header58 *-- "1..1" GenericIdentification176 : InitiatingParty Header58 *-- "0..1" GenericIdentification177 : RecipientParty Header58 *-- "0..0" Traceability8 : Traceability %% GenericIdentification176 recursion level 1 with max 1 class GenericIdentification176{ Identification IsoMax35Text Type PartyType33Code Issuer PartyType33Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } %% GenericIdentification177 recursion level 1 with max 1 class GenericIdentification177{ Identification IsoMax35Text Type PartyType33Code Issuer PartyType33Code Country IsoMin2Max3AlphaText ShortName IsoMax35Text } GenericIdentification177 *-- "0..1" NetworkParameters7 : RemoteAccess GenericIdentification177 *-- "0..1" Geolocation1 : Geolocation %% Traceability8 recursion level 1 with max 1 class Traceability8{ ProtocolName IsoMax35Text ProtocolVersion IsoMax6Text TraceDateTimeIn IsoISODateTime TraceDateTimeOut IsoISODateTime } Traceability8 *-- "1..1" GenericIdentification177 : RelayIdentification
Header58 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MessageFunction | Identifies the type of process related to the message. | MessageFunction41Code - 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 |
ReTransmissionCounter | Number of retransmissions of the message. | IsoMax3NumericText - 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. | GenericIdentification176 - Required 1..1 |
RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | GenericIdentification177 - Optional 0..1 |
Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability8 - Unknown 0..0 |
AuthorisationResponse building block
Information related to the response of the authorisation. Authorisation response from the acquirer. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AcceptorAuthorisationResponse9 recursion level 0 with max 1 AcceptorAuthorisationResponse9 *-- "1..1" CardPaymentEnvironment74 : Environment AcceptorAuthorisationResponse9 *-- "1..1" CardPaymentTransaction93 : Transaction AcceptorAuthorisationResponse9 *-- "1..1" CardPaymentTransaction94 : TransactionResponse AcceptorAuthorisationResponse9 *-- "0..0" SupplementaryData1 : SupplementaryData %% CardPaymentEnvironment74 recursion level 1 with max 1 CardPaymentEnvironment74 *-- "0..1" Acquirer10 : Acquirer CardPaymentEnvironment74 *-- "0..1" Organisation32 : Merchant CardPaymentEnvironment74 *-- "0..1" PointOfInteraction10 : POI CardPaymentEnvironment74 *-- "0..1" PaymentCard30 : Card CardPaymentEnvironment74 *-- "0..1" CustomerDevice1 : CustomerDevice CardPaymentEnvironment74 *-- "0..1" CustomerDevice1 : Wallet CardPaymentEnvironment74 *-- "0..1" CardPaymentToken5 : PaymentToken CardPaymentEnvironment74 *-- "0..1" Cardholder16 : Cardholder CardPaymentEnvironment74 *-- "0..1" ContentInformationType22 : ProtectedCardholderData %% CardPaymentTransaction93 recursion level 1 with max 1 class CardPaymentTransaction93{ SaleReferenceIdentification IsoMax35Text InitiatorTransactionIdentification IsoMax35Text RecipientTransactionIdentification IsoMax140Text ReconciliationIdentification IsoMax35Text InterchangeData IsoMax140Text MerchantReferenceData IsoMax70Text } CardPaymentTransaction93 *-- "1..1" TransactionIdentifier1 : TransactionIdentification CardPaymentTransaction93 *-- "1..1" CardPaymentTransactionDetails48 : TransactionDetails %% CardPaymentTransaction94 recursion level 1 with max 1 CardPaymentTransaction94 *-- "1..1" AuthorisationResult14 : AuthorisationResult CardPaymentTransaction94 *-- "0..0" TransactionVerificationResult4 : TransactionVerificationResult CardPaymentTransaction94 *-- "0..0" Product4 : AllowedProductCode CardPaymentTransaction94 *-- "0..0" Product4 : NotAllowedProductCode CardPaymentTransaction94 *-- "0..0" Product5 : AdditionalAvailableProduct CardPaymentTransaction94 *-- "0..1" AmountAndDirection93 : Balance CardPaymentTransaction94 *-- "0..1" ContentInformationType22 : ProtectedBalance CardPaymentTransaction94 *-- "0..0" Action10 : Action CardPaymentTransaction94 *-- "0..1" CurrencyConversion19 : CurrencyConversionEligibility %% SupplementaryData1 recursion level 1 with max 1 class SupplementaryData1{ PlaceAndName IsoMax350Text } SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
AcceptorAuthorisationResponse9 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Environment | Environment of the transaction. | CardPaymentEnvironment74 - Required 1..1 |
Transaction | Authorisation of a card payment transaction between an acceptor and an acquirer. | CardPaymentTransaction93 - Required 1..1 |
TransactionResponse | Authorisation response from the acquirer. Authorisation of a card payment transaction between an acceptor and an acquirer. | CardPaymentTransaction94 - Required 1..1 |
SupplementaryData | Additional information incorporated as an extension to the message. | SupplementaryData1 - Unknown 0..0 |
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 %% ContentInformationType24 recursion level 0 with max 1 class ContentInformationType24{ ContentType ContentType2Code } ContentInformationType24 *-- "1..1" AuthenticatedData6 : AuthenticatedData %% AuthenticatedData6 recursion level 1 with max 1 class AuthenticatedData6{ Version IsoNumber MAC IsoMax140Binary } AuthenticatedData6 *-- "1..0" IRecipient8Choice : Recipient AuthenticatedData6 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm AuthenticatedData6 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType24 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). | AuthenticatedData6 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorAuthorisationResponseV09 implementation follows a specific implementaiton pattern. First of all, AcceptorAuthorisationResponseV09 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorAuthorisationResponseV09Document implements IOuterDocument. Because AcceptorAuthorisationResponseV09 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorAuthorisationResponseV09.
classDiagram class IOuterRecord AcceptorAuthorisationResponseV09 --|> IOuterRecord : Implements AcceptorAuthorisationResponseV09Document --|> IOuterDocument~AcceptorAuthorisationResponseV09~ : Implements class IOuterDocument~AcceptorAuthorisationResponseV09~ { AcceptorAuthorisationResponseV09 Message }
Document wrapper for serialization
The only real purpose AcceptorAuthorisationResponseV09Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.002.001.09’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorAuthorisationResponseV09.ToDocument() method. The returned AcceptorAuthorisationResponseV09Document value will serialize correctly according to ISO 20022 standards.
classDiagram AcceptorAuthorisationResponseV09Document *-- AcceptorAuthorisationResponseV09 : 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.002.001.09">
<AccptrAuthstnRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<AuthstnRspn>
<!-- AuthorisationResponse inner content -->
</AuthstnRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</AccptrAuthstnRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_dmzocQuLEeqYM5yH99IYQw"
nextVersions="_ECB-IS5IEeunNvJlR_vCbg"
previousVersion="_Siuo4deeEeiJyp_aycJaTw"
name="AcceptorAuthorisationResponseV09"
definition="The AcceptorAuthorisationResponse message is sent by the acquirer (or its agent) to an acceptor (or its agent), to return the result of the validation made by issuer about the payment transaction."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AccptrAuthstnRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_dmzocwuLEeqYM5yH99IYQw"
type="purpose" />
<messageBuildingBlock
xmi:id="_dmzodQuLEeqYM5yH99IYQw"
nextVersions="_ECB-JS5IEeunNvJlR_vCbg"
previousVersion="_Siuo5deeEeiJyp_aycJaTw"
name="Header"
definition="Authorisation response message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_-_R68QuJEeqYM5yH99IYQw" />
<messageBuildingBlock
xmi:id="_dmzodwuLEeqYM5yH99IYQw"
nextVersions="_ECB-Jy5IEeunNvJlR_vCbg"
previousVersion="_SivP8deeEeiJyp_aycJaTw"
name="AuthorisationResponse"
definition="Information related to the response of the authorisation."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AuthstnRspn"
complexType="_B5SYgQuLEeqYM5yH99IYQw" />
<messageBuildingBlock
xmi:id="_dmzoeQuLEeqYM5yH99IYQw"
nextVersions="_ECB-KS5IEeunNvJlR_vCbg"
previousVersion="_SivP89eeEeiJyp_aycJaTw"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_GpvT8QuEEeqYM5yH99IYQw" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="002"
flavour="001"
version="09" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.