caaa: Acceptor to Acquirer Card Transaction
caaa.013 Acceptor Diagnostic Request
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
caaa.013 is the ISO 20022 AcceptorDiagnosticRequest message in the Acceptor to Acquirer Card Transaction business area (caaa). The latest version is caaa.013.001.13, and 13 versions are in the repository.
- Message
- AcceptorDiagnosticRequest
- Latest version
- caaa.013.001.13
- Submitting organisation
- nexo
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What caaa.013 is for
The AcceptorDiagnosticRequest message is sent by an acceptor (or its agent) to the acquirer (or its agent), to check the end-to-end communication, to test the availability of this acquirer, or to validate the security environment.
caaa.013 versions
Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.
| Version | Registration status | Published in |
|---|---|---|
| caaa.013.001.13latest | Registered | Latest version set |
| caaa.013.001.12 | Registered | Previous version set |
| caaa.013.001.11 | Registered | Archive |
| caaa.013.001.10 | Registered | Archive |
| caaa.013.001.09 | Registered | Archive |
| caaa.013.001.08 | Registered | Archive |
| caaa.013.001.07 | Registered | Archive |
| caaa.013.001.06 | Registered | Archive |
| caaa.013.001.05 | Registered | Archive |
| caaa.013.001.04 | Registered | Archive |
| caaa.013.001.03 | Registered | Archive |
| caaa.013.001.02 | Registered | Archive |
| caaa.013.001.01 | Registered | Archive |
caaa.013 message structure
The building blocks of caaa.013.001.13 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.
Document[1..1]AccptrDgnstcReqAcceptorDiagnosticRequest [1..1]HdrHeader [1..1]Header70Diagnostic request message management information.
MsgFctnMessage Function [1..1]MessageFunction46CodeIdentifies the type of process related to the message.
PrtcolVrsnProtocol Version [1..1]Max6TextVersion of the acquirer protocol specifications.
XchgIdExchange Identification [1..1]NumberUnique identification of an exchange occurrence.
ReTrnsmssnCntrRe Transmission Counter [0..1]Max3NumericTextNumber of retransmissions of the message.
CreDtTmCreation Date Time [1..1]ISODateTimeDate and time at which the message was created.
InitgPtyInitiating Party [1..1]GenericIdentification176Unique identification of the partner that has initiated the exchange.
IdIdentification [1..1]Max35TextTpType [0..1]PartyType33CodeIssrIssuer [0..1]PartyType33CodeCtryCountry [0..1]Min2Max3AlphaTextShrtNmShort Name [0..1]Max35Text
RcptPtyRecipient Party [0..1]GenericIdentification177Unique identification of the partner that is the recipient of the message exchange.
IdIdentification [1..1]Max35TextTpType [0..1]PartyType33CodeIssrIssuer [0..1]PartyType33CodeCtryCountry [0..1]Min2Max3AlphaTextShrtNmShort Name [0..1]Max35TextRmotAccsRemote Access [0..1]NetworkParameters7GlctnGeolocation [0..1]Geolocation1
TracbltTraceability [0..*]Traceability8Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges.
RlayIdRelay Identification [1..1]GenericIdentification177PrtcolNmProtocol Name [0..1]Max35TextPrtcolVrsnProtocol Version [0..1]Max6TextTracDtTmInTrace Date Time In [1..1]ISODateTimeTracDtTmOutTrace Date Time Out [1..1]ISODateTime
DgnstcReqDiagnostic Request [1..1]AcceptorDiagnosticRequest13Information related to the diagnostic request.
EnvtEnvironment [1..1]CardPaymentEnvironment81Environment of the transaction.
AcqrrAcquirer [0..1]Acquirer10SvcPrvdrService Provider [0..1]Acquirer10MrchntMerchant [0..1]Organisation41POIPOI [0..1]PointOfInteraction15CardCard [0..1]PaymentCard35ChckCheck [0..1]Check1StordValAcctStored Value Account [0..*]StoredValueAccount2LltyAcctLoyalty Account [0..*]LoyaltyAccount3CstmrDvcCustomer Device [0..1]CustomerDevice3WlltWallet [0..1]CustomerDevice3PmtTknPayment Token [0..1]Token1MrchntTknMerchant Token [0..1]MerchantToken2CrdhldrCardholder [0..1]Cardholder21PrtctdCrdhldrDataProtected Cardholder Data [0..1]ContentInformationType40SaleEnvtSale Environment [0..1]RetailerSaleEnvironment2
AcqrrAvlbtyReqdAcquirer Availability Requested [0..1]TrueFalseIndicatorIndicates if the availability of the acquirer must be tested.
SctyTrlrSecurity Trailer [0..1]ContentInformationType37Trailer of the message containing a MAC.
CnttTpContent Type [1..1]ContentType2CodeType of data protection.
AuthntcdDataAuthenticated Data [1..1]AuthenticatedData10Data protection by a message authentication code (MAC).
VrsnVersion [0..1]NumberRcptRecipient [1..*]Recipient15Choice (choice)MACAlgoMAC Algorithm [1..1]AlgorithmIdentification31NcpsltdCnttEncapsulated Content [1..1]EncapsulatedContent3MACMAC [1..1]Max140Binary
Have a caaa.013 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
caaa.013 questions
- What is the latest version of caaa.013?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is caaa.013.001.13.
- What is the root element of caaa.013?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:caaa.013.001.13, and its message element is AccptrDgnstcReq (AcceptorDiagnosticRequest).
- Is there an MT equivalent of caaa.013?
- No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.
All ISO 20022 messages · ISO 20022 code sets · MT messages
The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.