Iso20022

AcceptorAuthorisationResponseV04

caaa.002.001.04

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
%% AcceptorAuthorisationResponseV04 recursion level 0 with max 0
AcceptorAuthorisationResponseV04 *-- "1..1" Header10 : Header
AcceptorAuthorisationResponseV04 *-- "1..1" AcceptorAuthorisationResponse4 : AuthorisationResponse
AcceptorAuthorisationResponseV04 *-- "1..1" ContentInformationType11 : 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
%% Header10 recursion level 0 with max 1
class Header10{
    MessageFunction MessageFunction4Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header10 *-- "1..1" GenericIdentification53 : InitiatingParty
Header10 *-- "0..1" GenericIdentification53 : RecipientParty
Header10 *-- "0..0" Traceability2 : Traceability
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% Traceability2 recursion level 1 with max 1
class Traceability2{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability2 *-- "1..1" GenericIdentification76 : RelayIdentification

Header10 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction4Code - Required 1..1
ProtocolVersion Version of the acquirer protocol specifications. IsoMax6Text - Required 1..1
ExchangeIdentification Unique identification of an exchange occurrence. IsoMax3NumericText - 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. GenericIdentification53 - Optional 0..1
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability2 - 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
%% AcceptorAuthorisationResponse4 recursion level 0 with max 1
AcceptorAuthorisationResponse4 *-- "1..1" CardPaymentEnvironment33 : Environment
AcceptorAuthorisationResponse4 *-- "1..1" CardPaymentTransaction38 : Transaction
AcceptorAuthorisationResponse4 *-- "1..1" CardPaymentTransaction39 : TransactionResponse
AcceptorAuthorisationResponse4 *-- "0..0" SupplementaryData1 : SupplementaryData
%% CardPaymentEnvironment33 recursion level 1 with max 1
CardPaymentEnvironment33 *-- "0..1" GenericIdentification53 : AcquirerIdentification
CardPaymentEnvironment33 *-- "0..1" GenericIdentification32 : MerchantIdentification
CardPaymentEnvironment33 *-- "1..1" GenericIdentification32 : POIIdentification
CardPaymentEnvironment33 *-- "0..1" PaymentCard10 : Card
CardPaymentEnvironment33 *-- "0..1" CardPaymentToken2 : PaymentToken
%% CardPaymentTransaction38 recursion level 1 with max 1
class CardPaymentTransaction38{
    SaleReferenceIdentification IsoMax35Text
    RecipientTransactionIdentification IsoMax35Text
    ReconciliationIdentification IsoMax35Text
    InterchangeData IsoMax140Text
}
CardPaymentTransaction38 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction38 *-- "1..1" CardPaymentTransactionDetails20 : TransactionDetails
%% CardPaymentTransaction39 recursion level 1 with max 1
class CardPaymentTransaction39{
    DeclinedProductCode IsoMax70Text
}
CardPaymentTransaction39 *-- "1..1" AuthorisationResult4 : AuthorisationResult
CardPaymentTransaction39 *-- "0..0" TransactionVerificationResult3 : TransactionVerificationResult
CardPaymentTransaction39 *-- "0..1" AmountAndDirection41 : Balance
CardPaymentTransaction39 *-- "0..1" ContentInformationType10 : ProtectedBalance
CardPaymentTransaction39 *-- "0..0" Action3 : Action
CardPaymentTransaction39 *-- "0..1" CurrencyConversion3 : CurrencyConversion
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope

AcceptorAuthorisationResponse4 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment33 - Required 1..1
Transaction Authorisation of a card payment transaction between an acceptor and an acquirer. CardPaymentTransaction38 - Required 1..1
TransactionResponse Authorisation response from the acquirer. Authorisation of a card payment transaction between an acceptor and an acquirer. CardPaymentTransaction39 - 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
%% ContentInformationType11 recursion level 0 with max 1
class ContentInformationType11{
    ContentType ContentType2Code
}
ContentInformationType11 *-- "0..0" 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

ContentInformationType11 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 - Unknown 0..0

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorAuthorisationResponseV04 --|> IOuterRecord : Implements
    AcceptorAuthorisationResponseV04Document --|> IOuterDocument~AcceptorAuthorisationResponseV04~ : Implements
    class IOuterDocument~AcceptorAuthorisationResponseV04~ {
        AcceptorAuthorisationResponseV04 Message
     }

Document wrapper for serialization

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

classDiagram
    AcceptorAuthorisationResponseV04Document *-- AcceptorAuthorisationResponseV04 : 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.04">
    <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="_NVsYsWkgEeSTIuB9A-QJ6g"
  nextVersions="_oN7qgY0oEeWzoK7sd7oTyw"
  previousVersion="_gjkcwTGmEeO118ZQJgaQSQ"
  name="AcceptorAuthorisationResponseV04"
  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="_NVsYs2kgEeSTIuB9A-QJ6g"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_NVsYtWkgEeSTIuB9A-QJ6g"
    nextVersions="_oN7qhY0oEeWzoK7sd7oTyw"
    previousVersion="_gjkcwzGmEeO118ZQJgaQSQ"
    name="Header"
    definition="Authorisation response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_EXmNsWeeEeSh-d9-KfCEyA" />
  <messageBuildingBlock
    xmi:id="_NVsYt2kgEeSTIuB9A-QJ6g"
    nextVersions="_oN7qh40oEeWzoK7sd7oTyw"
    previousVersion="_gjkcxTGmEeO118ZQJgaQSQ"
    name="AuthorisationResponse"
    definition="Information related to the response of the authorisation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AuthstnRspn"
    complexType="_crk9kWkgEeSTIuB9A-QJ6g" />
  <messageBuildingBlock
    xmi:id="_NVsYuWkgEeSTIuB9A-QJ6g"
    nextVersions="_oN7qiY0oEeWzoK7sd7oTyw"
    previousVersion="_gjkcxzGmEeO118ZQJgaQSQ"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_cg4dYWkIEeS7zPBpvm732w" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="002"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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