Iso20022

AcceptorAuthorisationResponseV11

caaa.002.001.11

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
%% AcceptorAuthorisationResponseV11 recursion level 0 with max 0
AcceptorAuthorisationResponseV11 *-- "1..1" Header59 : Header
AcceptorAuthorisationResponseV11 *-- "1..1" AcceptorAuthorisationResponse11 : AuthorisationResponse
AcceptorAuthorisationResponseV11 *-- "0..1" ContentInformationType31 : 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
%% Header59 recursion level 0 with max 1
class Header59{
    MessageFunction MessageFunction42Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    ReTransmissionCounter IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header59 *-- "1..1" GenericIdentification176 : InitiatingParty
Header59 *-- "0..1" GenericIdentification177 : RecipientParty
Header59 *-- "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

Header59 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction42Code - 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
%% AcceptorAuthorisationResponse11 recursion level 0 with max 1
AcceptorAuthorisationResponse11 *-- "1..1" CardPaymentEnvironment78 : Environment
AcceptorAuthorisationResponse11 *-- "1..1" CardPaymentTransaction121 : Transaction
AcceptorAuthorisationResponse11 *-- "1..1" CardPaymentTransaction114 : TransactionResponse
AcceptorAuthorisationResponse11 *-- "0..0" SupplementaryData1 : SupplementaryData
%% CardPaymentEnvironment78 recursion level 1 with max 1
CardPaymentEnvironment78 *-- "0..1" Acquirer10 : Acquirer
CardPaymentEnvironment78 *-- "0..1" Organisation41 : Merchant
CardPaymentEnvironment78 *-- "0..1" PointOfInteraction12 : POI
CardPaymentEnvironment78 *-- "0..1" PaymentCard32 : Card
CardPaymentEnvironment78 *-- "0..1" Check1 : Check
CardPaymentEnvironment78 *-- "0..0" StoredValueAccount2 : StoredValueAccount
CardPaymentEnvironment78 *-- "0..0" LoyaltyAccount3 : LoyaltyAccount
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : CustomerDevice
CardPaymentEnvironment78 *-- "0..1" CustomerDevice3 : Wallet
CardPaymentEnvironment78 *-- "0..1" Token1 : PaymentToken
CardPaymentEnvironment78 *-- "0..1" MerchantToken2 : MerchantToken
CardPaymentEnvironment78 *-- "0..1" Cardholder18 : Cardholder
CardPaymentEnvironment78 *-- "0..1" ContentInformationType32 : ProtectedCardholderData
CardPaymentEnvironment78 *-- "0..1" RetailerSaleEnvironment2 : SaleEnvironment
%% CardPaymentTransaction121 recursion level 1 with max 1
class CardPaymentTransaction121{
    SaleReferenceIdentification IsoMax35Text
    InitiatorTransactionIdentification IsoMax35Text
    RecipientTransactionIdentification IsoMax140Text
    ReconciliationIdentification IsoMax35Text
    InterchangeData IsoMax140Text
    MerchantReferenceData IsoMax70Text
}
CardPaymentTransaction121 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction121 *-- "1..1" CardPaymentTransactionDetails51 : TransactionDetails
%% CardPaymentTransaction114 recursion level 1 with max 1
CardPaymentTransaction114 *-- "1..1" AuthorisationResult17 : AuthorisationResult
CardPaymentTransaction114 *-- "0..0" TransactionVerificationResult4 : TransactionVerificationResult
CardPaymentTransaction114 *-- "0..0" Product4 : AllowedProductCode
CardPaymentTransaction114 *-- "0..0" Product4 : NotAllowedProductCode
CardPaymentTransaction114 *-- "0..0" Product5 : AdditionalAvailableProduct
CardPaymentTransaction114 *-- "0..1" AmountAndDirection93 : Balance
CardPaymentTransaction114 *-- "0..1" ContentInformationType32 : ProtectedBalance
CardPaymentTransaction114 *-- "0..0" Action12 : Action
CardPaymentTransaction114 *-- "0..1" CurrencyConversion23 : CurrencyConversionEligibility
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope

AcceptorAuthorisationResponse11 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment78 - Required 1..1
Transaction Authorisation of a card payment transaction between an acceptor and an acquirer. CardPaymentTransaction121 - Required 1..1
TransactionResponse Authorisation response from the acquirer. Authorisation of a card payment transaction between an acceptor and an acquirer. CardPaymentTransaction114 - 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
%% ContentInformationType31 recursion level 0 with max 1
class ContentInformationType31{
    ContentType ContentType2Code
}
ContentInformationType31 *-- "1..1" AuthenticatedData8 : AuthenticatedData
%% AuthenticatedData8 recursion level 1 with max 1
class AuthenticatedData8{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData8 *-- "1..0" IRecipient11Choice : Recipient
AuthenticatedData8 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData8 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent

ContentInformationType31 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). AuthenticatedData8 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorAuthorisationResponseV11 --|> IOuterRecord : Implements
    AcceptorAuthorisationResponseV11Document --|> IOuterDocument~AcceptorAuthorisationResponseV11~ : Implements
    class IOuterDocument~AcceptorAuthorisationResponseV11~ {
        AcceptorAuthorisationResponseV11 Message
     }

Document wrapper for serialization

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

classDiagram
    AcceptorAuthorisationResponseV11Document *-- AcceptorAuthorisationResponseV11 : 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.11">
    <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="_spAG4U0YEeybj420QgWBkA"
  nextVersions="_3Gbm0XMHEe2vXY6MoVq19w"
  previousVersion="_ECB-IS5IEeunNvJlR_vCbg"
  name="AcceptorAuthorisationResponseV11"
  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="_fMW_EL1vEeKoB-JG4saAMg_-385897474"
  xmlTag="AccptrAuthstnRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_spAG400YEeybj420QgWBkA"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_spAG5U0YEeybj420QgWBkA"
    nextVersions="_3Gbm1XMHEe2vXY6MoVq19w"
    previousVersion="_ECB-JS5IEeunNvJlR_vCbg"
    name="Header"
    definition="Authorisation response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_Rz5m4S_aEeugIJ3Gvoevmg" />
  <messageBuildingBlock
    xmi:id="_spAG500YEeybj420QgWBkA"
    nextVersions="_3Gbm13MHEe2vXY6MoVq19w"
    previousVersion="_ECB-Jy5IEeunNvJlR_vCbg"
    name="AuthorisationResponse"
    definition="Information related to the response of the authorisation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AuthstnRspn"
    complexType="_VTRWkU0YEeybj420QgWBkA" />
  <messageBuildingBlock
    xmi:id="_spAG6U0YEeybj420QgWBkA"
    nextVersions="_3Gbm2XMHEe2vXY6MoVq19w"
    previousVersion="_ECB-KS5IEeunNvJlR_vCbg"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_dJxbAVFFEeyApZmLzm74zA" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="002"
    flavour="001"
    version="11" />
</messageDefinition>

ISO Building Blocks

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