caaa.016.001.04
The AcceptorCurrencyConversionRequest message is sent by the card acceptor to the currency conversion service provider to request if the cardholder is able to pay in the currency of its card.
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
%% AcceptorCurrencyConversionRequestV04 recursion level 0 with max 0
AcceptorCurrencyConversionRequestV04 *-- "1..1" Header30 : Header
AcceptorCurrencyConversionRequestV04 *-- "1..1" AcceptorCurrencyConversionRequest4 : CurrencyConversionRequest
AcceptorCurrencyConversionRequestV04 *-- "0..1" ContentInformationType15 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Currency Conversion 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 |
CurrencyConversionRequest building block
Information related to the currency conversion request. Information related to the currency conversion request. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AcceptorCurrencyConversionRequest4 recursion level 0 with max 1
AcceptorCurrencyConversionRequest4 *-- "1..1" CardPaymentEnvironment63 : Environment
AcceptorCurrencyConversionRequest4 *-- "1..1" CardPaymentTransaction72 : Transaction
%% CardPaymentEnvironment63 recursion level 1 with max 1
class CardPaymentEnvironment63{
CardholderLanguage LanguageCode
}
CardPaymentEnvironment63 *-- "0..1" GenericIdentification53 : AcquirerIdentification
CardPaymentEnvironment63 *-- "0..1" GenericIdentification53 : MerchantIdentification
CardPaymentEnvironment63 *-- "1..1" PointOfInteraction7 : POI
CardPaymentEnvironment63 *-- "1..1" PaymentCard21 : Card
%% CardPaymentTransaction72 recursion level 1 with max 1
class CardPaymentTransaction72{
TransactionCapture IsoTrueFalseIndicator
TransactionType CardPaymentServiceType5Code
AdditionalService CardPaymentServiceType9Code
ServiceAttribute CardPaymentServiceType3Code
MerchantCategoryCode IsoMin3Max4Text
SaleReferenceIdentification IsoMax35Text
AdditionalTransactionData IsoMax70Text
}
CardPaymentTransaction72 *-- "1..1" TransactionIdentifier1 : TransactionIdentification
CardPaymentTransaction72 *-- "0..1" CardPaymentTransaction73 : OriginalTransaction
CardPaymentTransaction72 *-- "1..1" CardPaymentTransactionDetails40 : TransactionDetails
AcceptorCurrencyConversionRequest4 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the transaction. | CardPaymentEnvironment63 - Required 1..1 |
| Transaction | Card payment transaction for which the currency conversion is requested. | CardPaymentTransaction72 - 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
%% 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 AcceptorCurrencyConversionRequestV04 implementation follows a specific implementaiton pattern. First of all, AcceptorCurrencyConversionRequestV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AcceptorCurrencyConversionRequestV04Document implements IOuterDocument. Because AcceptorCurrencyConversionRequestV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AcceptorCurrencyConversionRequestV04.
classDiagram
class IOuterRecord
AcceptorCurrencyConversionRequestV04 --|> IOuterRecord : Implements
AcceptorCurrencyConversionRequestV04Document --|> IOuterDocument~AcceptorCurrencyConversionRequestV04~ : Implements
class IOuterDocument~AcceptorCurrencyConversionRequestV04~ {
AcceptorCurrencyConversionRequestV04 Message
}
Document wrapper for serialization
The only real purpose AcceptorCurrencyConversionRequestV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caaa.016.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AcceptorCurrencyConversionRequestV04.ToDocument() method. The returned AcceptorCurrencyConversionRequestV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AcceptorCurrencyConversionRequestV04Document *-- AcceptorCurrencyConversionRequestV04 : 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.016.001.04">
<AccptrCcyConvsReq>
<Hdr>
<!-- Header inner content -->
</Hdr>
<CcyConvsReq>
<!-- CurrencyConversionRequest inner content -->
</CcyConvsReq>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</AccptrCcyConvsReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_MIALIaqMEeanIZ10Ka8PnA"
nextVersions="_GiBpQds5Eee9e6xduATmQg"
previousVersion="_Lx3NEY3ZEeW56qaqQ8B0kQ"
name="AcceptorCurrencyConversionRequestV04"
definition="The AcceptorCurrencyConversionRequest message is sent by the card acceptor to the currency conversion service provider to request if the cardholder is able to pay in the currency of its card.
"
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AccptrCcyConvsReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_MIALI6qMEeanIZ10Ka8PnA"
type="purpose" />
<messageBuildingBlock
xmi:id="_MIALJaqMEeanIZ10Ka8PnA"
nextVersions="_GiBpRds5Eee9e6xduATmQg"
previousVersion="_Lx3NFY3ZEeW56qaqQ8B0kQ"
name="Header"
definition="Currency Conversion request message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_IWFRgY0PEeWRYffwL7E13A" />
<messageBuildingBlock
xmi:id="_MIALJ6qMEeanIZ10Ka8PnA"
nextVersions="_GiBpR9s5Eee9e6xduATmQg"
previousVersion="_Lx3NF43ZEeW56qaqQ8B0kQ"
name="CurrencyConversionRequest"
definition="Information related to the currency conversion request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="CcyConvsReq"
complexType="_uPKTIaqLEeanIZ10Ka8PnA" />
<messageBuildingBlock
xmi:id="_MIALKaqMEeanIZ10Ka8PnA"
nextVersions="_GiBpSds5Eee9e6xduATmQg"
previousVersion="_Lx3NGY3ZEeW56qaqQ8B0kQ"
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="016"
flavour="001"
version="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.