caaa.001.001.06
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
%% AcceptorAuthorisationRequestV06 recursion level 0 with max 0
AcceptorAuthorisationRequestV06 *-- "1..1" Header30 : Header
AcceptorAuthorisationRequestV06 *-- "1..1" AcceptorAuthorisationRequest6 : AuthorisationRequest
AcceptorAuthorisationRequestV06 *-- "0..1" ContentInformationType15 : 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
%% Header30 recursion level 0 with max 1
class Header30{
MessageFunction MessageFunction10Code
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoNumber
CreationDateTime IsoISODateTime
}
Header30 *-- "1..1" GenericIdentification53 : InitiatingParty
Header30 *-- "0..1" GenericIdentification94 : RecipientParty
Header30 *-- "0..0" Traceability5 : Traceability
%% GenericIdentification53 recursion level 1 with max 1
class GenericIdentification53{
Identification IsoMax35Text
Type PartyType3Code
Issuer PartyType4Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
%% GenericIdentification94 recursion level 1 with max 1
class GenericIdentification94{
Identification IsoMax35Text
Type PartyType3Code
Issuer PartyType4Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
GenericIdentification94 *-- "0..1" NetworkParameters5 : RemoteAccess
%% Traceability5 recursion level 1 with max 1
class Traceability5{
ProtocolName IsoMax35Text
ProtocolVersion IsoMax6Text
TraceDateTimeIn IsoISODateTime
TraceDateTimeOut IsoISODateTime
}
Traceability5 *-- "1..1" GenericIdentification76 : RelayIdentification
Header30 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | MessageFunction10Code - 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 |
| 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. | GenericIdentification94 - Optional 0..1 |
| Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability5 - 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
%% AcceptorAuthorisationRequest6 recursion level 0 with max 1
AcceptorAuthorisationRequest6 *-- "1..1" CardPaymentEnvironment57 : Environment
AcceptorAuthorisationRequest6 *-- "1..1" CardPaymentContext20 : Context
AcceptorAuthorisationRequest6 *-- "1..1" CardPaymentTransaction76 : Transaction
AcceptorAuthorisationRequest6 *-- "0..0" SupplementaryData1 : SupplementaryData
%% CardPaymentEnvironment57 recursion level 1 with max 1
CardPaymentEnvironment57 *-- "0..1" Acquirer4 : Acquirer
CardPaymentEnvironment57 *-- "0..1" Organisation25 : Merchant
CardPaymentEnvironment57 *-- "1..1" PointOfInteraction7 : POI
CardPaymentEnvironment57 *-- "1..1" PaymentCard21 : Card
CardPaymentEnvironment57 *-- "0..1" CustomerDevice1 : CustomerDevice
CardPaymentEnvironment57 *-- "0..1" CustomerDevice1 : Wallet
CardPaymentEnvironment57 *-- "0..1" CardPaymentToken1 : PaymentToken
CardPaymentEnvironment57 *-- "0..1" Cardholder12 : Cardholder
CardPaymentEnvironment57 *-- "0..1" ContentInformationType10 : ProtectedCardholderData
%% CardPaymentContext20 recursion level 1 with max 1
CardPaymentContext20 *-- "1..1" PaymentContext20 : PaymentContext
CardPaymentContext20 *-- "0..1" SaleContext2 : SaleContext
%% CardPaymentTransaction76 recursion level 1 with max 1
class CardPaymentTransaction76{
TransactionCapture IsoTrueFalseIndicator
TransactionType CardPaymentServiceType5Code
AdditionalService CardPaymentServiceType9Code
ServiceAttribute CardPaymentServiceType3Code
MerchantCategoryCode IsoMin3Max4Text
CustomerConsent IsoTrueFalseIndicator
CardProgrammeProposed IsoMax35Text
CardProgrammeApplied IsoMax35Text
SaleReferenceIdentification IsoMax35Text
InitiatorTransactionIdentification IsoMax35Text
ReconciliationIdentification IsoMax35Text
MerchantReferenceData IsoMax70Text
AdditionalTransactionData IsoMax70Text
}
CardPaymentTransaction76 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction76 *-- "0..1" CardPaymentTransaction52 : OriginalTransaction
CardPaymentTransaction76 *-- "1..1" CardPaymentTransactionDetails41 : TransactionDetails
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
AcceptorAuthorisationRequest6 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment57 - Required 1..1 |
| Context | Context in which the transaction is performed (payment and sale). | CardPaymentContext20 - Required 1..1 |
| Transaction | Card payment transaction for which the authorisation is requested. | CardPaymentTransaction76 - 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
%% ContentInformationType15 recursion level 0 with max 1
class ContentInformationType15{
ContentType ContentType2Code
}
ContentInformationType15 *-- "1..1" 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
ContentInformationType15 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 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AcceptorAuthorisationRequestV06 implementation follows a specific implementaiton pattern. First of all, AcceptorAuthorisationRequestV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorAuthorisationRequestV06Document implements IOuterDocument. Because AcceptorAuthorisationRequestV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorAuthorisationRequestV06.
classDiagram
class IOuterRecord
AcceptorAuthorisationRequestV06 --|> IOuterRecord : Implements
AcceptorAuthorisationRequestV06Document --|> IOuterDocument~AcceptorAuthorisationRequestV06~ : Implements
class IOuterDocument~AcceptorAuthorisationRequestV06~ {
AcceptorAuthorisationRequestV06 Message
}
Document wrapper for serialization
The only real purpose AcceptorAuthorisationRequestV06Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.001.001.06’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorAuthorisationRequestV06.ToDocument() method. The returned AcceptorAuthorisationRequestV06Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorAuthorisationRequestV06Document *-- AcceptorAuthorisationRequestV06 : 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.06">
<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="_ZqSqQapyEeanIZ10Ka8PnA"
nextVersions="_19mLwdnGEeeN3v2fup_Shw"
previousVersion="_saAdoY0NEeWRYffwL7E13A"
name="AcceptorAuthorisationRequestV06"
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="_ZqTRUapyEeanIZ10Ka8PnA"
type="purpose" />
<messageBuildingBlock
xmi:id="_ZqTRU6pyEeanIZ10Ka8PnA"
nextVersions="_19mLxdnGEeeN3v2fup_Shw"
previousVersion="_saAdpY0NEeWRYffwL7E13A"
name="Header"
definition="Authorisation request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_IWFRgY0PEeWRYffwL7E13A" />
<messageBuildingBlock
xmi:id="_ZqTRVapyEeanIZ10Ka8PnA"
nextVersions="_19mLx9nGEeeN3v2fup_Shw"
previousVersion="_saAdp40NEeWRYffwL7E13A"
name="AuthorisationRequest"
definition="Information related to the authorisation request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AuthstnReq"
complexType="_E2-MUapyEeanIZ10Ka8PnA" />
<messageBuildingBlock
xmi:id="_ZqTRV6pyEeanIZ10Ka8PnA"
nextVersions="_19mLydnGEeeN3v2fup_Shw"
previousVersion="_saAdqY0NEeWRYffwL7E13A"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_uSOuUCrHEeWRf8RNsvC5fQ" />
<messageDefinitionIdentifier
businessArea="caaa"
messageFunctionality="001"
flavour="001"
version="06" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.