caaa.001.001.03
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
%% AcceptorAuthorisationRequestV03 recursion level 0 with max 0
AcceptorAuthorisationRequestV03 *-- "1..1" Header7 : Header
AcceptorAuthorisationRequestV03 *-- "1..1" AcceptorAuthorisationRequest3 : AuthorisationRequest
AcceptorAuthorisationRequestV03 *-- "1..1" ContentInformationType8 : 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
%% Header7 recursion level 0 with max 1
class Header7{
MessageFunction MessageFunction4Code
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoMax3NumericText
CreationDateTime IsoISODateTime
}
Header7 *-- "1..1" GenericIdentification32 : InitiatingParty
Header7 *-- "0..1" GenericIdentification32 : RecipientParty
Header7 *-- "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
Header7 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. | 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
%% AcceptorAuthorisationRequest3 recursion level 0 with max 1
AcceptorAuthorisationRequest3 *-- "1..1" CardPaymentEnvironment20 : Environment
AcceptorAuthorisationRequest3 *-- "1..1" CardPaymentContext5 : Context
AcceptorAuthorisationRequest3 *-- "1..1" CardPaymentTransaction22 : Transaction
%% CardPaymentEnvironment20 recursion level 1 with max 1
CardPaymentEnvironment20 *-- "0..1" Acquirer2 : Acquirer
CardPaymentEnvironment20 *-- "0..1" Organisation8 : Merchant
CardPaymentEnvironment20 *-- "1..1" PointOfInteraction3 : POI
CardPaymentEnvironment20 *-- "1..1" PaymentCard7 : Card
CardPaymentEnvironment20 *-- "0..1" Cardholder5 : Cardholder
CardPaymentEnvironment20 *-- "0..1" ContentInformationType7 : ProtectedCardholderData
%% CardPaymentContext5 recursion level 1 with max 1
CardPaymentContext5 *-- "1..1" PaymentContext5 : PaymentContext
CardPaymentContext5 *-- "0..1" SaleContext1 : SaleContext
%% CardPaymentTransaction22 recursion level 1 with max 1
class CardPaymentTransaction22{
TransactionCapture IsoTrueFalseIndicator
TransactionType CardPaymentServiceType5Code
AdditionalService CardPaymentServiceType6Code
ServiceAttribute CardPaymentServiceType3Code
MerchantCategoryCode IsoMin3Max4Text
SaleReferenceIdentification IsoMax35Text
InitiatorTransactionIdentification IsoMax35Text
ReconciliationIdentification IsoMax35Text
AdditionalTransactionData IsoMax70Text
}
CardPaymentTransaction22 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction22 *-- "0..1" CardPaymentTransaction21 : OriginalTransaction
CardPaymentTransaction22 *-- "1..1" CardPaymentTransactionDetails12 : TransactionDetails
AcceptorAuthorisationRequest3 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment20 - Required 1..1 |
| Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext5 - Required 1..1 |
| Transaction | Card payment transaction for which the authorisation is requested. | CardPaymentTransaction22 - 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
%% ContentInformationType8 recursion level 0 with max 1
class ContentInformationType8{
ContentType ContentType1Code
}
ContentInformationType8 *-- "0..0" AuthenticatedData3 : AuthenticatedData
%% AuthenticatedData3 recursion level 1 with max 1
class AuthenticatedData3{
Version IsoNumber
MAC IsoMax35Binary
}
AuthenticatedData3 *-- "1..0" IRecipient3Choice : Recipient
AuthenticatedData3 *-- "1..1" AlgorithmIdentification10 : MACAlgorithm
AuthenticatedData3 *-- "1..1" EncapsulatedContent2 : EncapsulatedContent
ContentInformationType8 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). | AuthenticatedData3 - Unknown 0..0 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorAuthorisationRequestV03 implementation follows a specific implementaiton pattern. First of all, AcceptorAuthorisationRequestV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorAuthorisationRequestV03Document implements IOuterDocument. Because AcceptorAuthorisationRequestV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorAuthorisationRequestV03.
classDiagram
class IOuterRecord
AcceptorAuthorisationRequestV03 --|> IOuterRecord : Implements
AcceptorAuthorisationRequestV03Document --|> IOuterDocument~AcceptorAuthorisationRequestV03~ : Implements
class IOuterDocument~AcceptorAuthorisationRequestV03~ {
AcceptorAuthorisationRequestV03 Message
}
Document wrapper for serialization
The only real purpose AcceptorAuthorisationRequestV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.001.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorAuthorisationRequestV03.ToDocument() method. The returned AcceptorAuthorisationRequestV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorAuthorisationRequestV03Document *-- AcceptorAuthorisationRequestV03 : 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.03">
<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="_2czxMS9GEeOlZIh7PImd0A"
nextVersions="_51NNAWedEeSh-d9-KfCEyA"
previousVersion="_kXA6QQvfEeK9Xewg3qiFQA"
name="AcceptorAuthorisationRequestV03"
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">
<doclet
xmi:id="_2otfMC9GEeOlZIh7PImd0A"
type="purpose" />
<messageBuildingBlock
xmi:id="_2czxMy9GEeOlZIh7PImd0A"
nextVersions="_51NNBWedEeSh-d9-KfCEyA"
previousVersion="_kXA6QwvfEeK9Xewg3qiFQA"
name="Header"
definition="Authorisation request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_UNSh8S9IEeOlZIh7PImd0A" />
<messageBuildingBlock
xmi:id="_2czxNS9GEeOlZIh7PImd0A"
nextVersions="_51NNB2edEeSh-d9-KfCEyA"
previousVersion="_kXA6RwvfEeK9Xewg3qiFQA"
name="AuthorisationRequest"
definition="Information related to the authorisation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AuthstnReq"
complexType="_shuccTDYEeO9waS4ina8CA" />
<messageBuildingBlock
xmi:id="_2czxNy9GEeOlZIh7PImd0A"
nextVersions="_51NNCWedEeSh-d9-KfCEyA"
previousVersion="_kXA6SwvfEeK9Xewg3qiFQA"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SctyTrlr"
complexType="_KpedcTF5EeO118ZQJgaQSQ" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="001"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.