caaa.001.001.11
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 %% AcceptorAuthorisationRequestV11 recursion level 0 with max 0 AcceptorAuthorisationRequestV11 *-- "1..1" Header59 : Header AcceptorAuthorisationRequestV11 *-- "1..1" AcceptorAuthorisationRequest11 : AuthorisationRequest AcceptorAuthorisationRequestV11 *-- "0..1" ContentInformationType31 : 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 %% 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 |
AuthorisationRequest building block
Information related to the authorisation request. Authorisation request from an acceptor. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AcceptorAuthorisationRequest11 recursion level 0 with max 1 AcceptorAuthorisationRequest11 *-- "1..1" CardPaymentEnvironment78 : Environment AcceptorAuthorisationRequest11 *-- "1..1" CardPaymentContext29 : Context AcceptorAuthorisationRequest11 *-- "1..1" CardPaymentTransaction119 : Transaction AcceptorAuthorisationRequest11 *-- "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 %% CardPaymentContext29 recursion level 1 with max 1 CardPaymentContext29 *-- "0..1" PaymentContext28 : PaymentContext CardPaymentContext29 *-- "0..1" SaleContext4 : SaleContext CardPaymentContext29 *-- "0..1" CardDirectDebit2 : DirectDebitContext %% CardPaymentTransaction119 recursion level 1 with max 1 class CardPaymentTransaction119{ TransactionCapture IsoTrueFalseIndicator TransactionType CardPaymentServiceType12Code AdditionalService CardPaymentServiceType9Code ServiceAttribute CardPaymentServiceType14Code LastTransactionFlag IsoTrueFalseIndicator MerchantCategoryCode IsoMin3Max4Text CustomerConsent IsoTrueFalseIndicator CardProgrammeProposed IsoMax35Text CardProgrammeApplied IsoMax35Text SaleReferenceIdentification IsoMax35Text InitiatorTransactionIdentification IsoMax35Text ReconciliationIdentification IsoMax35Text IssuerCITIdentification IsoMax140Text MerchantCITIdentification IsoMax140Text MerchantReferenceData IsoMax70Text AdditionalTransactionData IsoMax70Text } CardPaymentTransaction119 *-- "1..1" TransactionIdentifier1 : TransactionIdentification CardPaymentTransaction119 *-- "0..1" CardPaymentTransaction122 : OriginalTransaction CardPaymentTransaction119 *-- "1..1" CardPaymentTransactionDetails51 : TransactionDetails CardPaymentTransaction119 *-- "0..1" CardAccount16 : AccountFrom CardPaymentTransaction119 *-- "0..1" CardAccount16 : AccountTo %% SupplementaryData1 recursion level 1 with max 1 class SupplementaryData1{ PlaceAndName IsoMax350Text } SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
AcceptorAuthorisationRequest11 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Environment | Environment of the transaction. | CardPaymentEnvironment78 - Required 1..1 |
Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext29 - Required 1..1 |
Transaction | Card payment transaction for which the authorisation is requested. | CardPaymentTransaction119 - 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 AcceptorAuthorisationRequestV11 implementation follows a specific implementaiton pattern. First of all, AcceptorAuthorisationRequestV11 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorAuthorisationRequestV11Document implements IOuterDocument. Because AcceptorAuthorisationRequestV11 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorAuthorisationRequestV11.
classDiagram class IOuterRecord AcceptorAuthorisationRequestV11 --|> IOuterRecord : Implements AcceptorAuthorisationRequestV11Document --|> IOuterDocument~AcceptorAuthorisationRequestV11~ : Implements class IOuterDocument~AcceptorAuthorisationRequestV11~ { AcceptorAuthorisationRequestV11 Message }
Document wrapper for serialization
The only real purpose AcceptorAuthorisationRequestV11Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.001.001.11’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorAuthorisationRequestV11.ToDocument() method. The returned AcceptorAuthorisationRequestV11Document value will serialize correctly according to ISO 20022 standards.
classDiagram AcceptorAuthorisationRequestV11Document *-- AcceptorAuthorisationRequestV11 : 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.11">
<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="_sxWGUU3jEey_VecAUE-C9Q"
nextVersions="_LuF5QHMGEe2vXY6MoVq19w"
previousVersion="_7tvJgS5DEeunNvJlR_vCbg"
name="AcceptorAuthorisationRequestV11"
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="_fMW_EL1vEeKoB-JG4saAMg_-385897474"
xmlTag="AccptrAuthstnReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_sxWGU03jEey_VecAUE-C9Q"
type="purpose" />
<messageBuildingBlock
xmi:id="_sxWGVU3jEey_VecAUE-C9Q"
nextVersions="_LuF5RHMGEe2vXY6MoVq19w"
previousVersion="_7tvJhS5DEeunNvJlR_vCbg"
name="Header"
definition="Authorisation request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_Rz5m4S_aEeugIJ3Gvoevmg" />
<messageBuildingBlock
xmi:id="_sxWGV03jEey_VecAUE-C9Q"
nextVersions="_LuJjoXMGEe2vXY6MoVq19w"
previousVersion="_7tvJhy5DEeunNvJlR_vCbg"
name="AuthorisationRequest"
definition="Information related to the authorisation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AuthstnReq"
complexType="_R-Cb4U3jEey_VecAUE-C9Q" />
<messageBuildingBlock
xmi:id="_sxWGWU3jEey_VecAUE-C9Q"
nextVersions="_LuJjo3MGEe2vXY6MoVq19w"
previousVersion="_7tvJiS5DEeunNvJlR_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="001"
flavour="001"
version="11" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.