Iso20022

AcceptorAuthorisationRequestV02

caaa.001.001.02

The AcceptorAuthorisationRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to check with the issuer (or its agent) that the account associated to the card has the resources to fund the payment. This checking will include validation of the card data and any additional transaction data provided.

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
%% AcceptorAuthorisationRequestV02 recursion level 0 with max 0
AcceptorAuthorisationRequestV02 *-- "1..1" Header1 : Header
AcceptorAuthorisationRequestV02 *-- "1..1" AcceptorAuthorisationRequest2 : AuthorisationRequest
AcceptorAuthorisationRequestV02 *-- "1..1" ContentInformationType6 : SecurityTrailer

Now, we will zero-in one-by-one on each of these building blocks.

Header building block

Authorisation request message management information. Set of characteristics related to the protocol. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header1 recursion level 0 with max 1
class Header1{
    MessageFunction MessageFunction1Code
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header1 *-- "1..1" GenericIdentification32 : InitiatingParty
Header1 *-- "0..1" GenericIdentification32 : RecipientParty
Header1 *-- "0..0" Traceability1 : Traceability
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% GenericIdentification32 recursion level 1 with max 1
class GenericIdentification32{
    Identification IsoMax35Text
    Type PartyType3Code
    Issuer PartyType4Code
    ShortName IsoMax35Text
}
%% Traceability1 recursion level 1 with max 1
class Traceability1{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability1 *-- "1..1" GenericIdentification31 : RelayIdentification

Header1 members

Member name Description Data Type / Multiplicity
MessageFunction Identifies the type of process related to the message. MessageFunction1Code - 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. GenericIdentification32 - Required 1..1
RecipientParty Unique identification of the partner that is the recipient of the message exchange. GenericIdentification32 - Optional 0..1
Traceability Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. Traceability1 - Unknown 0..0

AuthorisationRequest building block

Information related to the authorisation request. Authorisation request from an acceptor. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AcceptorAuthorisationRequest2 recursion level 0 with max 1
AcceptorAuthorisationRequest2 *-- "1..1" CardPaymentEnvironment9 : Environment
AcceptorAuthorisationRequest2 *-- "1..1" CardPaymentContext1 : Context
AcceptorAuthorisationRequest2 *-- "1..1" CardPaymentTransaction11 : Transaction
%% CardPaymentEnvironment9 recursion level 1 with max 1
CardPaymentEnvironment9 *-- "0..1" Acquirer2 : Acquirer
CardPaymentEnvironment9 *-- "0..1" Organisation8 : Merchant
CardPaymentEnvironment9 *-- "1..1" PointOfInteraction2 : POI
CardPaymentEnvironment9 *-- "1..1" PaymentCard5 : Card
CardPaymentEnvironment9 *-- "0..1" Cardholder3 : Cardholder
%% CardPaymentContext1 recursion level 1 with max 1
CardPaymentContext1 *-- "1..1" PaymentContext1 : PaymentContext
CardPaymentContext1 *-- "0..1" SaleContext1 : SaleContext
%% CardPaymentTransaction11 recursion level 1 with max 1
class CardPaymentTransaction11{
    TransactionCapture IsoTrueFalseIndicator
    TransactionType CardPaymentServiceType4Code
    AdditionalService CardPaymentServiceType2Code
    ServiceAttribute CardPaymentServiceType3Code
    MerchantCategoryCode IsoMin3Max4Text
    InitiatorTransactionIdentification IsoMax35Text
    ReconciliationIdentification IsoMax35Text
    AdditionalTransactionData IsoMax70Text
}
CardPaymentTransaction11 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction11 *-- "0..1" CardPaymentTransaction17 : OriginalTransaction
CardPaymentTransaction11 *-- "1..1" CardPaymentTransactionDetails1 : TransactionDetails

AcceptorAuthorisationRequest2 members

Member name Description Data Type / Multiplicity
Environment Environment of the transaction. CardPaymentEnvironment9 - Required 1..1
Context Context in which the transaction is performed (payment and sale). CardPaymentContext1 - Required 1..1
Transaction Card payment transaction for which the authorisation is requested. CardPaymentTransaction11 - 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
%% ContentInformationType6 recursion level 0 with max 1
class ContentInformationType6{
    ContentType ContentType1Code
}
ContentInformationType6 *-- "0..0" AuthenticatedData2 : AuthenticatedData
%% AuthenticatedData2 recursion level 1 with max 1
class AuthenticatedData2{
    Version IsoNumber
    MAC IsoMax35Binary
}
AuthenticatedData2 *-- "1..0" IRecipient2Choice : Recipient
AuthenticatedData2 *-- "1..1" AlgorithmIdentification3 : MACAlgorithm
AuthenticatedData2 *-- "1..1" EncapsulatedContent1 : EncapsulatedContent

ContentInformationType6 members

Member name Description Data Type / Multiplicity
ContentType Type of data protection. ContentType1Code - Required 1..1
AuthenticatedData Data protection by a message authentication code (MAC). AuthenticatedData2 - Unknown 0..0

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AcceptorAuthorisationRequestV02 --|> IOuterRecord : Implements
    AcceptorAuthorisationRequestV02Document --|> IOuterDocument~AcceptorAuthorisationRequestV02~ : Implements
    class IOuterDocument~AcceptorAuthorisationRequestV02~ {
        AcceptorAuthorisationRequestV02 Message
     }

Document wrapper for serialization

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

classDiagram
    AcceptorAuthorisationRequestV02Document *-- AcceptorAuthorisationRequestV02 : 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.001.001.02">
    <AccptrAuthstnReq>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <AuthstnReq>
            <!-- AuthorisationRequest inner content -->
        </AuthstnReq>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </AccptrAuthstnReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_kXA6QQvfEeK9Xewg3qiFQA"
  nextVersions="_2czxMS9GEeOlZIh7PImd0A"
  previousVersion="_ghrzxaMVEeCJ6YNENx4h-w_1039526828"
  name="AcceptorAuthorisationRequestV02"
  definition="The AcceptorAuthorisationRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to check with the issuer (or its agent) that the account associated to the card has the resources to fund the payment. This checking will include validation of the card data and any additional transaction data provided."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AccptrAuthstnReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_kXA6QwvfEeK9Xewg3qiFQA"
    nextVersions="_2czxMy9GEeOlZIh7PImd0A"
    name="Header"
    definition="Authorisation request message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_SvV__wEcEeCQm6a_G2yO_w_677025486" />
  <messageBuildingBlock
    xmi:id="_kXA6RwvfEeK9Xewg3qiFQA"
    nextVersions="_2czxNS9GEeOlZIh7PImd0A"
    name="AuthorisationRequest"
    definition="Information related to the authorisation request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AuthstnReq"
    complexType="_VXVacQvVEeKzJ69IWwzB9Q" />
  <messageBuildingBlock
    xmi:id="_kXA6SwvfEeK9Xewg3qiFQA"
    nextVersions="_2czxNy9GEeOlZIh7PImd0A"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_6DM4sQvFEeKzJ69IWwzB9Q" />
  <messageDefinitionIdentifier
    businessArea="caaa"
    messageFunctionality="001"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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