Download as pdf or txt
Download as pdf or txt
You are on page 1of 470

CAPE

Card Payments
Message Usage Guide

Version 5.0
2 June 2017

© 2017 nexo-standards AISBL All rights reserved.


This information is protected by international intellectual property laws and its use is governed by the applicable End-User
license
Card Payments Message Usage Guide Version 5.0

TABLE OF CONTENTS

1 Introduction ......................................................................................................................... 12
1.1 Purpose and Use of this Guide.......................................................................................................12
1.2 Intended Audience ..........................................................................................................................12
1.3 Scope of the Document ..................................................................................................................12
1.4 Messages Covered in this Guide....................................................................................................12
1.5 How this Guide was created ...........................................................................................................13
1.6 nexo and ISO 20022 .......................................................................................................................13
1.7 ISO 20022 Intellectual Property Rights Policy ................................................................................14
1.8 Message Transport .........................................................................................................................14
1.9 Security ...........................................................................................................................................14
1.10 Coding ............................................................................................................................................14
1.11 Related Documents and Guides.....................................................................................................14
1.12 Conventions ....................................................................................................................................15
1.13 What’s new in the edition 5 .............................................................................................................15
2 Message Exchange and Processes ................................................................................... 16
2.1 Card Payment .................................................................................................................................16
2.1.1 Authorisation.................................................................................................................................... 16
2.1.2 Completion ...................................................................................................................................... 16
2.1.3 Financial capture ............................................................................................................................. 17
2.1.4 Batch ............................................................................................................................................... 17
2.1.5 Dynamic Currency Conversion ........................................................................................................ 17
2.2 Scope of Card Payments ................................................................................................................19
2.3 Types of environments ...................................................................................................................20
2.3.1 Online only....................................................................................................................................... 20
2.3.1.1 Financial capture made during the authorisation exchange...................................................................... 20
2.3.1.2 Financial capture made during the completion exchange ......................................................................... 22
2.3.2 Semi-online authorisations .............................................................................................................. 24
2.3.2.1 Capture of offline and online transactions during completion ................................................................... 24
2.3.2.2 Capture during authorisation for online transactions and during completion for offline authorisations ....... 25
2.3.3 Offline only....................................................................................................................................... 26
2.3.4 Capture by Batch ............................................................................................................................. 27
2.3.4.1 Authorisation through an authorisation exchange without completion with capture in batch ..................... 27
2.3.4.2 Authorisation through authorisation and completion exchanges with capture in batch .............................. 28
2.3.4.3 Offline authorisation with capture in batch................................................................................................ 29
Capture of unsuccessful transactions in batch ......................................................................................... 30
2.3.4.4 30
2.3.5 Batch of Authorisations .................................................................................................................... 31
2.4 Cancellation ....................................................................................................................................32
2.4.1 Cancellation through cancellation advice or batch .......................................................................... 33
2.4.2 Cancellation through cancellation request and advice exchanges .................................................. 37
2.4.3 Cancellation declined by the Acquirer ............................................................................................. 39
2.4.4 Error in Cancellation Message Exchanges ...................................................................................... 40
2.4.4.1 Cancellation declined after timeout of a cancellation request ................................................................... 40

-2-
Card Payments Message Usage Guide Version 5.0

2.4.4.2 Cancellation successful after timeout of a completion advice ................................................................... 41


2.4.4.3 Cancellation declined after timeout of a completion advice ...................................................................... 43
2.4.4.4 Cancellation declined after timeout .......................................................................................................... 45
2.4.4.5 Cancellation successful after completion errors ....................................................................................... 47
2.4.4.6 Cancellation in batch mode..................................................................................................................... 48
2.4.4.7 Declined cancellation in batch mode ........................................................................................................ 50
2.4.4.8 Declined cancellation after timeout in batch mode and cancellation request ............................................ 52
2.4.4.9 Declined cancellation in batch mode after timeout in cancellation request ............................................... 54
2.4.4.10 Cancellation in batch mode of a transaction captured but not yet cleared ............................................... 56
2.5 Batch ...............................................................................................................................................58
2.5.1 Introduction ...................................................................................................................................... 58
2.5.2 Data Organisation............................................................................................................................ 59
2.5.2.1 AcceptorBatchTransfer ............................................................................................................................ 59
2.5.2.2 AcceptorBatchTransferResponse ............................................................................................................ 59
2.5.2.3 Data Factorisation ................................................................................................................................... 60
2.5.2.4 Multiplicity ................................................................................................................................................ 61
2.5.3 Types of Batch Transfer .................................................................................................................. 62
2.5.3.1 Batch containing Completion and Cancellation Transactions ................................................................... 62
2.5.3.2 Batch containing Authorisation Transactions ........................................................................................... 63
2.6 Reconciliation Process ...................................................................................................................66
2.6.1 Introduction ...................................................................................................................................... 66
2.6.2 Reconciliation Period Identification .................................................................................................. 67
2.6.3 Transaction Totals ........................................................................................................................... 70
2.6.4 Reconciliation Exchange ................................................................................................................. 72
2.7 Diagnostic Messages .....................................................................................................................74
2.8 Reject Message ..............................................................................................................................78
3 Message Functionalities..................................................................................................... 81
3.1 Message Organisation ....................................................................................................................81
3.1.1 Management of the message .......................................................................................................... 81
3.1.1.1 Management information ......................................................................................................................... 82
3.1.1.2 Parties involved in the message .............................................................................................................. 83
3.1.1.3 Traceability information............................................................................................................................ 84
3.1.2 ApplicationData ............................................................................................................................... 85
3.1.2.1 Environment ............................................................................................................................................ 86
3.1.2.2 Context .................................................................................................................................................... 87
3.1.2.3 Transaction.............................................................................................................................................. 87
3.1.3 SecurityTrailer ................................................................................................................................. 88
3.2 Traceability .....................................................................................................................................89
3.2.1 Security level ................................................................................................................................... 89
3.2.2 Usage Condition .............................................................................................................................. 89
3.2.3 Traceability in an exchange ............................................................................................................. 89
3.3 Message Retransmission ...............................................................................................................91
3.3.1 Acceptor Behaviour ......................................................................................................................... 91
3.3.1.1 Late Responses to an Advice message ................................................................................................... 92
3.3.1.2 Unordered Responses to Retransmitted Advice messages ...................................................................... 93
3.3.2 Acquirer Behaviour .......................................................................................................................... 94
3.4 Error Handling.................................................................................................................................96
3.4.1 Error Cases ..................................................................................................................................... 96

-3-
Card Payments Message Usage Guide Version 5.0

3.4.1.1 Acceptor is Unable to Send a Message ................................................................................................... 96


3.4.1.2 Acquirer Receives an Unacceptable Message ......................................................................................... 97
3.4.1.3 Acquirer is Unable to Process the Message............................................................................................. 98
3.4.1.4 Acquirer is Unable to Send a Message .................................................................................................... 98
3.4.1.5 Acceptor has not Received a Response Message ................................................................................... 99
3.4.1.6 Acceptor Receives an Unacceptable Message ........................................................................................ 99
3.4.1.7 Acceptor is Unable to Process the Response Message ......................................................................... 100
3.4.1.8 Acquirer or Acceptor has received a Duplicate Message. ...................................................................... 101
3.4.2 Acceptor Error Handling ................................................................................................................ 101
3.4.2.1 Reverse the Transaction ........................................................................................................................ 102
3.4.2.2 Retransmission of the Advice ................................................................................................................ 102
3.4.2.3 Terminate the Exchange in Progress ..................................................................................................... 103
3.4.2.4 Ignore the Error ..................................................................................................................................... 103
3.4.3 Acquirer Error Handling ................................................................................................................. 104
3.4.3.1 Message Rejection ................................................................................................................................ 104
3.4.3.2 Retransmission of the Response ........................................................................................................... 104
3.4.3.3 Ignore the Error ..................................................................................................................................... 105

4 Messages and Usage ........................................................................................................ 106


4.1 Configuration Parameters/ Condition of Presence .......................................................................106
4.2 Authorisation Messages ...............................................................................................................107
4.2.1 AcceptorAuthorisationRequest (caaa.001.001.05) ........................................................................ 107
4.2.1.1 Constraints ............................................................................................................................................ 119
4.2.2 AcceptorAuthorisationResponse (caaa.002.001.05) ..................................................................... 121
4.2.2.1 Constraints ............................................................................................................................................ 126
4.3 Completion Messages ..................................................................................................................127
4.3.1 AcceptorCompletionAdvice (caaa.003.001.05).............................................................................. 127
4.3.1.1 Constraints ............................................................................................................................................ 137
4.3.2 AcceptorCompletionAdviceResponse (caaa.004.001.05) ............................................................. 139
4.3.2.1 Constraints ............................................................................................................................................ 141
4.4 Cancellation Messages ................................................................................................................142
4.4.1 AcceptorCancellationRequest (caaa.005.001.05) ......................................................................... 142
4.4.1.1 Constraints ............................................................................................................................................ 147
4.4.2 AcceptorCancellationResponse (caaa.006.001.05) ....................................................................... 149
4.4.2.1 Constraints ............................................................................................................................................ 151
4.4.3 AcceptorCancellationAdvice (caaa.007.001.05) ............................................................................ 152
4.4.3.1 Constraints ............................................................................................................................................ 157
4.4.4 AcceptorCancellationAdviceResponse (caaa.008.001.05) ............................................................ 158
4.5 Reconciliation Messages ..............................................................................................................161
4.5.1 AcceptorReconciliationRequest (caaa.009.001.05) ....................................................................... 161
4.5.1.1 Constraints ............................................................................................................................................ 163
4.5.2 AcceptorReconciliationResponse (caaa.010.001.05) .................................................................... 164
4.5.2.1 Constraints ............................................................................................................................................ 166
4.6 Batch .............................................................................................................................................167
4.6.1 AcceptorBatchTransfer (caaa.011.001.05) .................................................................................... 167
4.6.1.1 Constraints ............................................................................................................................................ 198
4.6.2 AcceptorBatchTransferResponse (caaa.012.001.05) .................................................................... 199
4.6.2.1 Constraints ............................................................................................................................................ 201
4.7 Diagnostic Messages ...................................................................................................................202

-4-
Card Payments Message Usage Guide Version 5.0

4.7.1 AcceptorDiagnosticRequest (caaa.013.001.05) ............................................................................ 202


4.7.1.1 Constraints ............................................................................................................................................ 204
4.7.2 AcceptorDiagnosticResponse (caaa.014.001.05).......................................................................... 205
4.8 Reject Message ............................................................................................................................207
4.8.1 AcceptorRejection (caaa.015.001.05) ........................................................................................... 207
4.8.1.1 Constraints ............................................................................................................................................ 208
4.9 Dynamic Currency Conversion Messages ...................................................................................209
4.9.1 AcceptorCurrencyConversionRequest (caaa.016.001.03) ............................................................ 209
4.9.2 AcceptorCurrencyConversionResponse (caaa.017.001.03) .......................................................... 213
5 Dynamic of the Payment Exchanges ............................................................................... 217
5.1 Introduction ...................................................................................................................................217
5.2 Determination of Payment Cases .................................................................................................217
5.2.1 Elements Impacting the Message Flow ......................................................................................... 217
5.2.1.1 Authorisation Type ................................................................................................................................. 217
5.2.1.2 Authorisation Result .............................................................................................................................. 218
5.2.1.3 Incident after Authorisation .................................................................................................................... 218
5.2.1.4 Merchant Forced Acceptance ................................................................................................................ 219
5.2.1.5 Capture Type......................................................................................................................................... 219
5.2.1.6 Completion Exchange............................................................................................................................ 220
5.2.2 List of Payment Cases ................................................................................................................... 221
5.3 Table of Payment Cases ..............................................................................................................225
5.4 Cancellation Exchange .................................................................................................................231
5.4.1 List of Cancellation Cases ............................................................................................................. 232
5.4.2 Table of Cancellation Cases .......................................................................................................... 234
6 Additional Payment Services ........................................................................................... 238
6.1 Voice Authorisation .......................................................................................................................238
6.2 Deferred Payments .......................................................................................................................242
6.2.1 Introduction .................................................................................................................................... 242
6.2.2 Constraints on the Protocol ........................................................................................................... 243
6.3 Cashback ......................................................................................................................................246
6.4 Cash Advance ..............................................................................................................................247
6.5 Gratuity .........................................................................................................................................248
6.6 Reservation...................................................................................................................................248
6.6.1 Introduction .................................................................................................................................... 248
6.6.2 Reservation steps .......................................................................................................................... 249
6.6.2.1 Initial Reservation .................................................................................................................................. 249
6.6.2.2 Update Reservation ............................................................................................................................... 249
6.6.2.3 Cancellation of the Reservation (before payment) ................................................................................. 249
6.6.2.4 Payment for the Reservation ................................................................................................................. 249
6.6.2.5 No show Payment for the Reservation ................................................................................................... 249
6.6.2.6 Additional Payment (after Payment for the Reservation) ........................................................................ 249
6.6.2.7 No-show payment without performing a prior reservation service .......................................................... 249
6.6.3 Message flows ............................................................................................................................... 249
6.6.4 Description of the steps ................................................................................................................. 250
6.6.4.1 Initial reservation ................................................................................................................................... 250
6.6.4.2 Update reservation ................................................................................................................................ 250
6.6.4.3 Cancellation of the reservation (before payment) ................................................................................... 251

-5-
Card Payments Message Usage Guide Version 5.0

6.6.4.4 Payment after reservation ...................................................................................................................... 251


6.6.5 Reservation transaction data ......................................................................................................... 251
6.6.5.1 Initial reservation ................................................................................................................................... 251
6.6.5.2 Update reservation ................................................................................................................................ 254
6.6.5.3 Cancellation of a Reservation before payment ....................................................................................... 256
6.6.5.4 Payment after reservation ...................................................................................................................... 257
6.6.5.5 Additional payment ................................................................................................................................ 259
6.6.5.6 No show payment without prior reservation ........................................................................................... 262
6.6.5.7 Batch ..................................................................................................................................................... 263
6.6.5.8 Reconciliation ........................................................................................................................................ 264

7 Messages Examples ......................................................................................................... 265


7.1 Authorisation, Completion, Cancellation and Reconciliation Exchanges .....................................265
7.1.1 Cryptographic Keys ....................................................................................................................... 266
7.1.2 Acquirer, Merchant and POI Data .................................................................................................. 267
7.1.3 Card Data ...................................................................................................................................... 270
7.1.3.1 Authorisation Request ........................................................................................................................... 270
7.1.3.2 Card Data for Other Messages .............................................................................................................. 274
7.1.3.3 AcceptorAuthorisationResponse ............................................................................................................ 275
7.1.3.4 AcceptorCompletionAdvice .................................................................................................................... 276
7.1.3.5 AcceptorCompletionAdviceResponse .................................................................................................... 277
7.1.3.6 AcceptorCancellationAdvice .................................................................................................................. 278
7.1.3.7 AcceptorCancellationAdviceResponse .................................................................................................. 279
7.1.4 Cardholder Data ............................................................................................................................ 280
7.1.5 Payment and Sale Contexts .......................................................................................................... 281
7.1.6 ICC Related Data .......................................................................................................................... 282
7.1.6.1 Authorisation Request ........................................................................................................................... 282
7.1.6.2 Authorisation Response......................................................................................................................... 283
7.1.6.3 Completion Advice................................................................................................................................. 283
7.2 Authorisation Messages ...............................................................................................................285
7.2.1 AcceptorAuthorisationRequest ...................................................................................................... 285
7.2.2 AcceptorAuthorisationResponse ................................................................................................... 299
7.3 Completion Messages ..................................................................................................................308
7.3.1 AcceptorCompletionAdvice............................................................................................................ 308
7.3.2 AcceptorCompletionAdviceResponse ........................................................................................... 324
7.4 Cancellation Messages ................................................................................................................332
7.4.1 AcceptorCancellationAdvice .......................................................................................................... 332
7.4.2 AcceptorCancellationAdviceResponse .......................................................................................... 347
7.5 Reconciliation Messages ..............................................................................................................356
7.5.1 AcceptorReconciliationRequest ..................................................................................................... 356
7.5.2 AcceptorReconciliationResponse .................................................................................................. 367
7.6 Batch Transfer messages .............................................................................................................377
7.6.1 AcceptorBatchTransfer .................................................................................................................. 377
7.7 Diagnostic Messages ...................................................................................................................430
7.7.1 AcceptorDiagnosticRequest .......................................................................................................... 430
7.7.2 AcceptorDiagnosticResponse........................................................................................................ 435
7.8 Rejection .......................................................................................................................................441
7.8.1 AcceptorDiagnosticRequest .......................................................................................................... 441
7.8.2 AcceptorRejection ......................................................................................................................... 444

-6-
Card Payments Message Usage Guide Version 5.0

8 Transport Protocols and Services ................................................................................... 449


8.1 Protocols Organisation .................................................................................................................449
8.2 TCP Protocol ................................................................................................................................451
8.2.1 Typical Use .................................................................................................................................... 451
8.2.2 Message Delimitation .................................................................................................................... 451
8.2.3 Addressing..................................................................................................................................... 451
8.3 Transport Services .......................................................................................................................452
8.3.1 Message Delimitation .................................................................................................................... 452
8.3.1.1 Definition ............................................................................................................................................... 452
8.3.1.2 Specifications ........................................................................................................................................ 452
8.3.1.3 Typical Example of Implementation ....................................................................................................... 452
8.3.1.4 Notes ..................................................................................................................................................... 452
8.3.2 Connection and Data Transfer Management ................................................................................. 454
8.3.2.1 Connection Services .............................................................................................................................. 454
8.3.2.2 Data Transfer ........................................................................................................................................ 455
8.3.3 Single Message Pair Exchange ..................................................................................................... 456
8.3.3.1 Definition ............................................................................................................................................... 456
8.3.3.2 Specifications ........................................................................................................................................ 456
8.3.3.3 Notes ..................................................................................................................................................... 457
8.3.4 Multiple Message Pair Exchange .................................................................................................. 458
8.3.4.1 Definition ............................................................................................................................................... 458
8.3.4.2 Specifications ........................................................................................................................................ 458
8.3.4.3 Notes ..................................................................................................................................................... 460
8.3.5 Addressing..................................................................................................................................... 461
8.3.5.1 Definition ............................................................................................................................................... 461
8.3.5.2 Specifications ........................................................................................................................................ 461
8.3.6 Flow Control .................................................................................................................................. 462
8.3.6.1 Definition ............................................................................................................................................... 462
8.3.6.2 Specifications ........................................................................................................................................ 462
8.3.7 Error Cases ................................................................................................................................... 463
8.3.7.1 Unable to Establish a Transport Connection (ERTR01) ......................................................................... 463
8.3.7.2 Transport Connection Broken (ERTR02) ............................................................................................... 463
8.3.7.3 Unable to Send a Message (ERTR03) ................................................................................................... 464
8.3.7.4 Message Too Big (ERTR04) .................................................................................................................. 464
8.3.7.5 Late Arrival (ERTR05) ........................................................................................................................... 465
8.3.7.6 Max Number of Connections (ERTR06) ................................................................................................. 465
8.3.7.7 Incomplete Application Message (ERTR07)........................................................................................... 466
8.3.7.8 Other Errors........................................................................................................................................... 466
8.3.8 Transport Service Parameters ....................................................................................................... 467
8.3.9 Connection and Data Management State Diagrams ..................................................................... 469
8.3.9.1 Recipient Party Diagram ........................................................................................................................ 469
8.3.9.2 Initiating Party Diagram ......................................................................................................................... 470

-7-
Card Payments Message Usage Guide Version 5.0

Figures

Figure 1: Authorisation with capture (successful transaction) ............................................................... 20


Figure 2: Authorisation with capture (failed transaction) ....................................................................... 21
Figure 3: Completion with capture (successful transaction) .................................................................. 22
Figure 4: Completion with capture (failed transaction) .......................................................................... 23
Figure 5: Capture of offline and online transactions during completion ................................................ 24
Figure 6: Capture during authorisation for online transactions ............................................................. 25
Figure 7: Capture through completion of previously offline-authorised transactions ............................ 26
Figure 8: Authorisation through an authorisation exchange without completion with capture in batch 27
Figure 9: Authorisation through authorisation and completion exchanges with capture in batch ......... 28
Figure 10: Off-line authorisation with capture in batch .......................................................................... 29
Figure 11: Capture of unsuccessful transactions in batch .................................................................... 30
Figure 12: Batch of Authorisations ........................................................................................................ 31
Figure 13: Cancellation through cancellation advice or batch ............................................................... 34
Figure 14: Cancellation through cancellation advice and batch exchanges ......................................... 36
Figure 15: Cancellation through cancellation request and advice exchanges ...................................... 38
Figure 16: Declined cancellation of a captured transaction .................................................................. 39
Figure 17: Cancellation declined after timeout of a cancellation request .............................................. 40
Figure 18: Cancellation successful after timeout of a completion advice ............................................. 42
Figure 19: Cancellation declined after timeout of a completion advice ................................................. 44
Figure 20: Cancellation declined after timeout ...................................................................................... 46
Figure 21: Cancellation successful after completion errors .................................................................. 47
Figure 22: Cancellation in batch mode .................................................................................................. 49
Figure 23: Declined cancellation in batch mode.................................................................................... 51
Figure 24: Declined cancellation after timeout in batch mode and cancellation request ...................... 53
Figure 25: Declined cancellation in batch mode after timeout cancellation request ............................. 55
Figure 26: Cancellation in batch mode of a transaction captured but not yet cleared .......................... 57
Figure 27: BatchTransfer structure ........................................................................................................ 59
Figure 28: BatchTransferResponse structure ....................................................................................... 60
Figure 29: Batch containing Financial Authorisations ........................................................................... 64
Figure 30: Batch containing Authorisations ........................................................................................... 65
Figure 31: Reconciliation Exchange ...................................................................................................... 66
Figure 32: Reconciliation Period Assigned by the Acceptor ................................................................. 67
Figure 33: Reconciliation Period Assigned by the Acquirer .................................................................. 68
Figure 34: Reconciliation between the Authorisation and the Completion ............................................ 68
Figure 35: Overlapping of Reconciliation Periods ................................................................................. 69
Figure 36: Diagnostic Exchange ........................................................................................................... 74
Figure 37: Diagnostic Reject ................................................................................................................. 75

-8-
Card Payments Message Usage Guide Version 5.0

Figure 38: Diagnostic Request from an Acceptor to an Agent .............................................................. 75


Figure 39: Diagnostic Request from an Intermediary Agent ................................................................. 77
Figure 40: Rejection of an Authorisation ............................................................................................... 78
Figure 41: Rejection of an Authorisation to an Agent ............................................................................ 79
Figure 42: Rejection of an Completion to an Agent .............................................................................. 80
Figure 43: Example of Traceability with an Intermediary Agent ............................................................ 90
Figure 44: Retransmission of an Advice by the Acceptor ..................................................................... 91
Figure 45: Late Responses to an Advice message ............................................................................... 92
Figure 46: Unordered Responses to Retransmitted Advice messages ................................................ 93
Figure 47: Retransmission of an AdviceResponse by the Acquirer ...................................................... 94
Figure 48: Non-Receipt of an Advice by the Acquirer ........................................................................... 94
Figure 49: Error Cases in Message Exchange...................................................................................... 96
Figure 50: Acceptor Error Handling in a Message Exchange ............................................................. 101
Figure 51: Acquirer Error Handling in a Message Exchange .............................................................. 104
Figure 52: Payment Cases Tree List ................................................................................................... 223
Figure 53: Payment Cases Tree List (Con't) ....................................................................................... 224
Figure 54 Cancellation Cases Tree List .............................................................................................. 233
Figure 55: Successful Voice Authorisation captured with Completion ................................................ 238
Figure 56: Unsuccessful Voice Authorisation captured with Completion. ........................................... 239
Figure 57: Successful Voice Authorisation Interleaved with another transaction ............................... 240
Figure 58: Successful Voice Authorisation Captured with Batch without Completion ........................ 241
Figure 59: Deferred Payment .............................................................................................................. 242
Figure 60: Interleaved Deferred Payment Transactions ..................................................................... 242
Figure 61: Approved Deferred Payment without Delivery ................................................................... 243
Figure 62: Declined Deferred Payment ............................................................................................... 243
Figure 63: Deferred Payment Captured by Completion ...................................................................... 244
Figure 64: Deferred Payment Captured by Batch ............................................................................... 244
Figure 65: Approved Deferred Payment without Delivery ................................................................... 245
Figure 66: Sequence of Message Exchanges..................................................................................... 265
Figure 67: Protocols Organisation ....................................................................................................... 449
Figure 68: Transport Adaptation Layer ................................................................................................ 449
Figure 69: Peer-to-peer TCP Transport Protocol ................................................................................ 451
Figure 70: Gateway TCP Transport Protocol ...................................................................................... 451
Figure 71: Header Length.................................................................................................................... 452
Figure 72: Connection Services .......................................................................................................... 454
Figure 73: Transport Connection Management Service Primitives ..................................................... 455
Figure 74: Application Protocol Message Flow ................................................................................... 455
Figure 75: Single Message Pair Exchange Sequence Flow ............................................................... 456
Figure 76: Single Message Pair Exchange Transport Primitives Sequence Flow .............................. 457
Figure 77: Multiple Message Pair Exchange Sequence Flow ............................................................. 458

-9-
Card Payments Message Usage Guide Version 5.0

Figure 78: Multiple Message Pair Exchange Transport Primitives Sequence Flow............................ 459
Figure 79: Transport Address .............................................................................................................. 461
Figure 80: Late Arrival Error Example ................................................................................................. 465
Figure 81: Recipient Party Connection Management State Diagram ................................................. 469
Figure 82: Initiating Party Connection Management State Diagram ................................................... 470

- 10 -
Card Payments Message Usage Guide Version 5.0

Tables
Table 1: MessageFunction Values ...................................................................................................... 222
Table 2: List of Payment Cases .......................................................................................................... 231
Table 3: Cancellation MessageFunction Values ................................................................................. 233
Table 4: List of Cancellation Cases ..................................................................................................... 237

- 11 -
Card Payments Message Usage Guide Version 5.0

1 Introduction
1.1 Purpose and Use of this Guide
This guide outlines how to use the CAPE Card Payments messages in the context of the acceptor-to-
1
acquirer transactions (caaa) ISO 20022 Business Area . It provides a comprehensive view on how
these messages fit within a card payment business process and the activities of the involved parties.
Also included are detailed explanations and examples of the use of the message components to
convey specific information related to these processes and activities. This guide acts as a
complement to the ISO 20022 CAPE Message Definition Report and the XML Schema for those
exchanges. It complies with ISO 20022 rules and specifications.

The guide provides information regarding the application of the included messages in a general
context. Additional documents, published by individual user communities, may be available that
discuss the application of this standard in a more specific context.

1.2 Intended Audience


The present guide is intended for both business people and message developers. It is also targeted
for manufacturers, software providers, banks and card payment services providers offering these
messages to their clients, technology firms seeking to embed support for these messaging standards
into their applications, and standards organisations that wish to use the payment kernel as part of the
messages they offer.

1.3 Scope of the Document


The present guide covers basic payments with a limited number of optional features such as cash-
back, gratuity, DCC, loyalty. It includes cancellation, refund and reconciliation associated with these
payments.

1.4 Messages Covered in this Guide


The present guide covers card payments in the acceptor-to-acquirer domain only and complies with
ISO 20022 message specifications published by ISO 20022 in "Message Definition Report Card
Payments Exchanges – Acceptor to Acquirer" on February 2016.

It addresses the following categories of exchanges of messages:

2
 Authorisation messages , cover the messages exchanged between an Acceptor and an
Acquirer to initiate and, in some implementations, to finalise the card-based payment
transactions initiated at a Point-of-Interaction.

3
 Completion messages , cover the messages exchanged between an Acceptor and an
Acquirer to finalise the card-based payment transactions initiated at a Point-of-Interaction.

1
http://www.iso20022.org/documents/general/ISO20022_BusinessAreas.pdf
2
AcceptorAuthorisationRequest (caaa.001.001.05) and AcceptorAuthorisationResponse (caaa.002.001.05)
3
AcceptorCompletionAdvice (caaa.003.001.05) and AcceptorCompletionAdviceResponse (caaa.004.001.05)

- 12 -
Card Payments Message Usage Guide Version 5.0

4
 Cancellation messages , cover the messages exchanged between an Acceptor and an
Acquirer to cancel successfully completed payment transactions or other types of transactions
(e.g. reservations) which have not yet been cleared. A cancellation is sometimes called a
manual reversal.

5
 Reconciliation messages , cover the messages exchanged between an Acceptor and an
Acquirer to perform checks and balances between the card acceptor and the acquirer for a
reconciliation period.

6
 Batch transfer messages cover the messages exchanged in batch between an Acceptor and
and Acquirer to finalise and/or capture card-based payment transactions initiated at a Point-
of-Interaction.

7
 Diagnostic messages cover the messages exchanged between an InitiatingParty and a
RecipientParty to prove that messages can be exchanged correctly between the parties.

8
 Rejection message cover the message send by a RecipientParty to an InitiatingParty to
indicate that the RecipientParty could not process the received message.

9
 Dynamic Currency conversion message cover the messages exchanged between and
Acceptor or an acquirer and a DCC service provider (Agent or Acquirer).

1.5 How this Guide was created


This guide was created through the combined efforts of the nexo Acquirer Protocol Working Group
involving representatives belonging to various industries (banks, card payments service providers,
manufacturers, software service providers, retailers, etc.). It follows ISO 20022 rules for the design of
Message Usage Guides.

1.6 nexo and ISO 20022


10
nexo is a major standardisation initiative in card-based payment transactions involving card-payment
experts belonging to various industries. Nexo has been created by merging various standardisation
initiative like EPAS Org, CIR and Oscar. Since its inception, EPASOrg has been following the ISO
20022 methodology in developing standards with the ultimate objective to become a full-fledged ISO
20022 standard. ISO 20022 is part of the International Organization for Standardization (ISO) under
Technical Committee 68 (TC68), which is the Financial Services Technical Committee of the
International Organization for Standardization. ISO 20022 message standards are submitted through
the ISO 20022 Registration Management Group (RMG) via a Business Justification. When this
Business Justification is approved, the RMG assigns the proposed message standards to a Standards
Evaluation Group (SEG).

4
AcceptorCancellationRequest (caaa.005.001.05), AcceptorCancellationResponse (caaa.006.001.05),
AcceptorCancellationAdvice (caaa.007.001.05) and AcceptorCancellationAdviceResponse (caaa.008.001.05)
5
AcceptorReconciliationRequest (caaa.009.001.05) and AcceptorReconciliationResponse (caaa.010.001.05)
6
AcceptorBatchTransfer (caaa.011.001.05) and AcceptorBatchTransferResponse (caaa.012.001.05)
7
AcceptorDiagnosticRequest (caaa.013.001.05) and AcceptorDiagnosticResponse (caaa.014.001.05)
8
AcceptorRejection (caaa.015.001.05)
9
AcceptorCurrencyConversionRequest (caaa.016.001.03) and AcceptorCurrencyConversionResponse (caaa.017.001.03)
10
http://www.nexo-standards.org

- 13 -
Card Payments Message Usage Guide Version 5.0

The Cards and Related Retail Financial Services SEG mandated by the RMG to address the card
payments business domain officially endorsed the nexo CAPE (Card Payment Exchanges) series of
messages in June 2010.

Complete information on the membership of the ISO 20022 SEGs, the ISO 20022 Financial
Repository, and the message maintenance and registration process can be found on www.iso20022.org.
For more information on ISO itself, please see www.iso.org.

For more information on nexo, the body in charge of the nexo and CAPE messages, please visit
www.nexo-satandards.org.

1.7 ISO 20022 Intellectual Property Rights Policy


EPASOrg acknowledges and abides by the ISO 20022 IPR policy outlined as follows: “Organizations
that contribute information to be incorporated into the ISO 20022 Repository shall keep any Intellectual
Property Rights (IPR) they have on this information. A contributing organization warrants that it has
sufficient rights on the contributed information to have it published in the ISO 20022 Repository
through the ISO 20022 Registration Authority in accordance with the rules set in ISO 20022. To
ascertain a widespread, public and uniform use of the ISO 20022 Repository information, the
contributing organization grants third parties a non-exclusive, royalty-free license to use the published
information”.

11
The EPAS End-User License Agreement can be downloaded from the ISO 20022 Web site.

1.8 Message Transport


CAPE messages are designed to be transport protocol independent. The CAPE standard does,
however, provide message transport conventions of its own (including header and trailer).

1.9 Security
CAPE messages embed their own security data components and structures to ensure an adequate
security in the transmission of the information.

1.10 Coding
CAPE messages are proposed in ISO 20022 XML derived from ISO 20022 Message Definitions.

1.11 Related Documents and Guides


The complete catalog of official ISO 20022 CAPE messages, including the Message Definition
Reports and XML Schemas, is available on the ISO 20022 official Web site ( http://www.iso20022.org ). All

11
http://www.iso20022.org/documents/general/EPASOrg_EPAS_End-user_License_Final.pdf

- 14 -
Card Payments Message Usage Guide Version 5.0

other CAPE or nexo related information can be found by visiting the nexo Web site (www.nexo-
standards.org).

Useful information about XML is available from the following sources:


 XML recommendations of W3C can be found at:
http://www.w3c.org/TR/2000/REC-xml-20081126
http://www.w3.org/TR/2006/REC-xml11-20060816/
 XML Schema recommendations of W3C can be found at:
http://www.w3c.org/TR/xmlschema-0/
http://www.w3c.org/TR/xmlschema-1/
http://www.w3c.org/TR/xmlschema-2/

The security element of these messages are described in the nexo document named Card Payment
Protocols Security v2.1.

1.12 Conventions
The words MUST, SHOULD and MAY will be used throughout this document with the meaning
defined by [RFC2119].
Items represented in grey in the table are not covered by the present MUG. Within the terms of the
protocol they may be used as agreed between the sender and receiver.

1.13 What’s new in the edition 5

This edition brings the following improvements:


 Dynamic Currency Conversion
 Support of value added services with Supplementary Data
 Support for purchasing card and
 Cancellation exchange use cases

- 15 -
Card Payments Message Usage Guide Version 5.0

2 Message Exchange and Processes

2.1 Card Payment

2.1.1 Authorisation
An authorisation is used in a card payment to request the approval of the transaction. It can be done
either remotely (on-line to the Acquirer through an authorisation exchange) or locally (off-line
authorisation) depending on the business context.

The possible outcomes of an authorisation are:


 a successful authorisation
 a declined authorisation
 a technical problem (eg. timeout, unable to go online, etc.)
 a voice referral, which in turn may result in a successful authorisation or a decline.

An online authorisation exchange is made up an AcceptorAuthorisationRequest message


(caaa.001.001.05) used to request the authorisation of the related transaction and an
AcceptorAuthorisationResponse message(caaa.002.001.05) used to provide the outcome of the
authorisation.

2.1.2 Completion
Completion is the process of finalising the interaction between the cardholder and the merchant at the
POI.
The outcome of a completion is the acceptance or decline of the transaction by the Acceptor.

A completion exchange may also be required by an Acquirer to finalise the transaction:


 when the Acceptor is configured to support completion,
 in the authorisation response (if required by the Acquirer),
 when an online approved authorisation did not complete successfully.

A completion exchange is made up an AcceptorCompletionAdvice message (caaa.003.001.05) sent


by an Acceptor to notify the Acquirer of the outcome of the transaction and an
AcceptorCompletionAdviceResponse message (caaa.004.001.05) used by the Acquirer to
acknowledge this notification.

A completion exchange can be performed in realtime at the end of the transaction or in a store-and-
forward mode of operation.

An AcceptorCompletionAdvice is used for three main purposes:


 to reverse an authorisation (also called a “reversal”)
 to inform the Acquirer of the outcome of a service

- 16 -
Card Payments Message Usage Guide Version 5.0

 to transfer the transaction data to the Acquirer for a further clearing and settlement (financial
capture).

The Acquirer must accept an AcceptorCompletionAdvice message. In case of an error, the message
is resent to the Acquirer (see section 3.3 Message Retransmission).

2.1.3 Financial capture


The ultimate financial settlement of a card payment transaction requires a prior financial capture of the
elements of this transaction by the Acquirer or by an agent acting on his behalf. The responsibility of
keeping the financial information is then transferred from the Acceptor to the Acquirer for a further
clearing and settlement of the transaction.

A financial capture can take place in realtime, after a short delay or at a later time as part of a batch
transfer.

A financial capture process can be done:


 within an authorisation exchange;
 within a completion exchange;
 through a batch transfer.

2.1.4 Batch
A batch is a collection of transactions sent to the Acquirer for a further processing.
A batch transfer is processed through an AcceptorBatchTransfer (caaa.011.001.05) and an
AcceptorBatchTransferResponse (caaa.012.001.05) which is used to acknowledge or to reject some
or all transactions contained in a batch.

2.1.5 Dynamic Currency Conversion


When the currency of the transaction is not the same as the currency of the card, it may be difficult for
a cardholder to estimate the actual amount he will have to pay in his own currency at the moment of
the payment.

Dynamic Currency Conversion (DCC) is a service offered by a merchant to allow the cardholder to
make the payment in the currency of his card instead of the currency of the merchant when different.

The cardholder can choose whether to accept the DCC service or not. When DCC is allowed by the
merchant, the currency conversion is managed through a DCC service provider proposing to the
cardholder the converted amount to be ultimately debited on his card.

If the DCC service is refused by the cardholder, the transaction then proceeds as a normal card
payment transaction in the currency of the merchant.

- 17 -
Card Payments Message Usage Guide Version 5.0

The DCC service may rely on an agent acting between the merchant and the DCC service provider.
The following use cases involve agents in the process, but direct exchanges between a merchant and
a DCC service provider or between a merchant and an acquirer follow the same logic.

The role of the DCC service provider can be played by any party (Agent, Acquirer, etc.).

DCC is supported by two types of exchanges:

- Authorisation exchanges where a pair of AcceptorAuthorisationRequest (caaa.001.001.05) and


AcceptorAuthorisationResponse (caaa.002.001.05) messages are used
- Dynamic Currency Conversion exchanges where a pair of AcceptorCurrencyConversionRequest
and AcceptorCurrencyConversionResponse messages are used to fulfil the same purpose.

Use cases outlining some typical DCC scenarios are described in Chapter NN.

- 18 -
Card Payments Message Usage Guide Version 5.0

2.2 Scope of Card Payments


Card payment exchanges can be domestic, cross-border and/or cross currency. They may be used by
an Acceptor to request to an Acquirer to initiate and/or complete a card transaction.

An Acceptor can directly exchange with an Acquirer a series of card payment messages. The
proposed messages may also go through the intermediation of one or more Intermediary Agents to
request similar services. The Intermediary Agent is then acting as an agent of the Acquirer, the
Acceptor or both.

In a normal card payment process, the Acquirer further forwards to the Issuer (e.g. a payment
institution or a similar entity issuing the payment card to the cardholder) the related authorisation
request to get an ultimate response from the entity entitled to issue the authorisation of payment for a
purchase which was initiated with the card issued by them. The protocol needs to transport all relevant
information to enable the Issuer to take the appropriate decision i.e. either to authorise or to decline
the card payment transaction submitted by the Acquirer.

In an alternative process and based on the information submitted by an Acceptor, the Acquirer may
take the responsibility to authorise or decline the transaction (below a certain amount, for instance) on
behalf of the Issuer. He may also decide to forward to the Issuer the information required by the Issuer
to take the ultimate authorisation decision. In this case, the information is exchanged through an
Acquirer-to-Issuer protocol. This exchange is out of scope of the present specification.

In some specific environments (e.g. petrol), some purchasing information, such as a list of products,
may accompany the authorisation since the final payment can occur if and only if the list of products
was approved by the issuer of the payment card.

In that case, either the Acceptor submits with an authorisation request the list of products for approval
to the Acquirer which further forwards this list to the Issuer for approval or, based on the information
contained in the authorisation request, the Issuer submits in the authorisation response the restricted
list of products (e.g. fuel dispensing products) authorised for the Cardholder. It is then the
responsibility of the Acceptor to deliver a product or a service which complies with the product(s)
contained in this list.

- 19 -
Card Payments Message Usage Guide Version 5.0

2.3 Types of environments

Depending on business constraints and the types of equipment used, typical implementations may be
classified in:

 Online-only
 Offline with online capability
 Offline-only with batch capture

2.3.1 Online only


In this mode all transactions are processed in a pure on-line mode of operation.The only required
exchanges are Authorisation and Completion:
Completion is required:
 In case of reversal
 For financial capture when not done during authorization.
 In case of request in the authorization response or by configuration.

2.3.1.1 Financial capture made during the authorisation exchange

Case of a successful transaction


An AcceptorAuthorisationRequest message is sent by an Acceptor to an Acquirer to request the
approval of a payment transaction. The transaction succeeds after the approval of the authorisation. In
some cases, the Acquirer may require a completion exchange for this transaction.

An AcceptorAuthorisationResponse message is returned by the Acquirer to inform the Acceptor of the


outcome of the request. The responsibility of the financial data (financial capture) is transferred from
the Acceptor to the Acquirer with the AcceptorAuthorisationRequest message. The Acquirer then
stores this information for the further clearing and settlement of the transaction.

Acceptor Acquirer

AcceptorAutho
risationReque
st
authorisation approval
and capture
ns e
risationRespo
AcceptorAutho
transaction
completed
successfully

Figure 1: Authorisation with capture (successful transaction)

- 20 -
Card Payments Message Usage Guide Version 5.0

Case of a failed transaction

An AcceptorAuthorisationRequest message is sent by an Acceptor to an Acquirer to request the


approval of a transaction. The transaction fails after the approval of the authorisation or if the Acceptor
has not received a response to the AcceptorAuthorisationRequest message. A completion exchange
is initiated by the Acceptor to reverse both the authorisation and the financial capture of the
transaction.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest

authorisation approval
and capture

orisa tionResponse
AcceptorAuth
transaction fails

negative completion to
reverse the transaction AcceptorCompl
etio nAdvice

Authorisation and
capture reversed
se
etio nAdviceRespon
AcceptorCompl

Figure 2: Authorisation with capture (failed transaction)

- 21 -
Card Payments Message Usage Guide Version 5.0

2.3.1.2 Financial capture made during the completion exchange

Case of a successful transaction

An AcceptorAuthorisationRequest message is sent by an Acceptor to an Acquirer to request the


approval of the transaction. The transaction succeeds after the approval of the authorisation.

An AcceptorCompletionAdvice message is sent by the Acceptor to the Acquirer to capture the


transaction. An AcceptorCompletionAdviceResponse message is sent back by the Acquirer to the
Acceptor to notify the Acceptor about the successful receipt of the advice.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest

Transaction
authorised

orisa tionResponse
AcceptorAuth
Transaction
authorised
AcceptorCompl
etio nAdvice
Transaction
authorised
and captured
Transaction completed etionAdv iceResponse
AcceptorCompl
successfully

Figure 3: Completion with capture (successful transaction)

- 22 -
Card Payments Message Usage Guide Version 5.0

Case of a failed transaction

An AcceptorAuthorisationRequest message is sent by an Acceptor to an Acquirer to request the


approval of the transaction. The transaction fails after the approval of the authorisation and/or the
Acceptor has not received a response to the AcceptorAuthorisationRequest message. A completion
exchange is then initiated by the Acceptor to reverse the authorisation of the transaction.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest

Transaction
authorised

orisa tionResponse
AcceptorAuth
transaction fails

Negative completion to
AcceptorCompl
reverse the etio nAdvice
authorisation
Authorisation
reversed
se
etio nAdviceRespon
AcceptorCompl

Figure 4: Completion with capture (failed transaction)

- 23 -
Card Payments Message Usage Guide Version 5.0

2.3.2 Semi-online authorisations

Authorisations are processed either online or offline depending on the context of the transaction. In
normal cases, the financial capture of the transaction is made during the completion exchange.

2.3.2.1 Capture of offline and online transactions during completion

In this scenario, financial capture of previously online and offline authorised transactions is carried out
during completion.

Acceptor Acquirer

AcceptorAuth
authorisation orisa tionRequest
online
authorisation approved
online Transaction
authorised

orisationR esponse
AcceptorAuth
Transaction
authorised
AcceptorCompl
etio nAdvice
Transaction
authorised
(online) and
se captured
etio nAdviceRespon
AcceptorCompl

offline
authorisation authorisation
approval
offline

AcceptorCompl
etio nAdvice
Transaction
authorised
(offline) and
captured
sponse
etionAdviceRe
AcceptorCompl

Figure 5: Capture of offline and online transactions during completion

- 24 -
Card Payments Message Usage Guide Version 5.0

2.3.2.2 Capture during authorisation for online transactions and during completion
for offline authorisations

In order to reduce the number of exchanges, the financial capture may be carried out during
authorisation exchanges for on-line authorisations and during completion exchanges for off-line
authorisations.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest
online
authorisation authorisation Transaction
approved authorised (online)
online and captured
orisa tionResponse
transaction AcceptorAuth
completed
successfully

offline authorisation
authorisation approved
offline
transaction
completes
successfully AcceptorCompl
etio nAdvice
Transaction
authorised
(offline) and
se captured
etio nAdviceRespon
AcceptorCompl

Figure 6: Capture during authorisation for online transactions


and during completion for offline transactions

- 25 -
Card Payments Message Usage Guide Version 5.0

2.3.3 Offline only

In this scenario, an AcceptorCompletionAdvice is used to inform the Acquirer about the outcome of a
previously offline-authorised transaction and to advise the Acquirer to capture the financial data for
clearing and settlement.

Acceptor Acquirer

authorisation approved
offline

AcceptorCompl
etio nAdvice
Transaction
authorised
(offline) and
se captured
etio nAdviceRespon
transaction completed AcceptorCompl
successfully

authorisation approved
offline

AcceptorCompl
etio nAdvice
Transaction
authorised
transaction completed (offline) and
successfully sponse captured
etionAdviceRe
AcceptorCompl

Figure 7: Capture through completion of previously offline-authorised transactions

- 26 -
Card Payments Message Usage Guide Version 5.0

2.3.4 Capture by Batch

The financial capture of transactions proceeds in batch.

The main relevant types of batch situations are:


 authorisation through an authorisation exchange without completion with capture in batch
 authorisation through authorisation and completion exchanges with capture in batch
 offline authorisation with capture in batch
 unsuccessful transactions communicated to the Acquirer in batch

2.3.4.1 Authorisation through an authorisation exchange without completion with


capture in batch

In this scenario, an AcceptorBatchTransfer message is used by an Acceptor to advise an Acquirer to


capture in batch mode transactions authorised through previous online or offline authorisation
exchanges. The Acquirer captures the financial data of the transactions for clearing and settlement.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest
online Authorisation
authorisation Transaction
initiated
authorised
online esponse
orisationR
AcceptorAuth

offline Authorisation
authorisation initiated
offline

AcceptorBatchT
Capture through batch rans fer
Transaction
authorised
Transaction e and captured
ransferRespons
completed AcceptorBatchT
successfully

Figure 8: Authorisation through an authorisation exchange without completion with capture in


batch

- 27 -
Card Payments Message Usage Guide Version 5.0

2.3.4.2 Authorisation through authorisation and completion exchanges with capture in


batch

In this scenario, an AcceptorBatchTransfer message is used by the Acceptor to advise the Acquirer to
capture in batch mode transactions authorised through previous authorisation and completion
exchanges. The Acquirer captures the financial data of the transactions for clearing and settlement.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest
Authorisation initiated Transaction
online authorised
orisa tionResponse
AcceptorAuth

Advise of authorised AcceptorCompl


etio nAdvice Transaction
transaction
authorised and
completed waiting
se
etio nAdviceRespon capture
AcceptorCompl

AcceptorBatchT
Capture through batch rans fer
Transaction
authorised
ferResponse and captured
rans
AcceptorBatchT

Figure 9: Authorisation through authorisation and completion exchanges with capture in batch

- 28 -
Card Payments Message Usage Guide Version 5.0

2.3.4.3 Offline authorisation with capture in batch

In this scenario, an AcceptorBatchTransfer message is used by the Acceptor to advise the Acquirer to
capture in batch mode transactions that were previously authorised offline and stored. The Acquirer
captures the financial data of the transactions for clearing and settlement.

Acceptor Acquirer

offline Transaction
authorisation authorised
offline

offline Transaction
authorisation authorised
offline

Capture
through batch AcceptorBatchT
rans fer
Transactions
authorised
e and captured
ransferRespons
AcceptorBatchT

Figure 10: Off-line authorisation with capture in batch

- 29 -
Card Payments Message Usage Guide Version 5.0

2.3.4.4 Capture of unsuccessful transactions in batch

In this scenario, an AcceptorBatchTransfer message is used by the Acceptor to send to the Acquirer
for capture in batch modeunsuccessfully completed and reversed transactions.

Acceptor Acquirer

AcceptorAuth
orisa tionRequest
Transaction
authorised
authorisation response orisa tionResponse
timeout AcceptorAuth

Authorisation reversed AcceptorCompl


through a negative etio nAdvice
completion Authorisation reversed

se
etio nAdviceRespon
AcceptorCompl

Capture
through batch AcceptorBatchT
rans fer
of authorised
Transactions
or
captured
unauthorised ferResponse
rans
authorised AcceptorBatchT
transactions

Figure 11: Capture of unsuccessful transactions in batch

- 30 -
Card Payments Message Usage Guide Version 5.0

2.3.5 Batch of Authorisations

An AcceptorBatchTransfer exchange is used by the Acceptor to send a collection of Authorisation


Requests to the Acquirer to authorise transactions.
The Acquirer is sending back to the Acceptor in an AcceptorBatchTransferResponse the
corresponding Authorisation Responses with the outcome of the authorisation process.

Acceptor Acquirer

offline authorisation
authorisation approved
online
transaction
completes
successfully

offline authorisation
authorisation approved
offline
transaction
completes
successfully

AcceptorBatchT
rans fer
Transactions
authorised
rans ferResponse
AcceptorBatchT

Figure 12: Batch of Authorisations

- 31 -
Card Payments Message Usage Guide Version 5.0

2.4 Cancellation

Cancellation is initiated by Acceptor to cancel a payment which was successfully completed. . A


cancellation is a user requested reversal. A cancellation cannot be revoked.

An AcceptorCancellationRequest (caaa.005.001.05) is used by an Acceptor to ask the Acquirer


whether a cancellation can be performed, before sending an AcceptorCancellationAdvice.

An AcceptorCancellationAdvice (caaa.007.001.05)- with or without a prior


AcceptorCancellationRequest is used by an Acceptor to inform the Acquirer that a cancellation has
been completed. It is also used to indicate that no response to an AcceptorCancellationRequest was
received and that the cancellation was declined.

An AcceptorCancellationAdvice (caaa.007.001.05) can only be used without an


AcceptorCancellationRequest (caaa.005.001.05) if the Acceptor is aware that the transaction was not
yet cleared.

An Acquirer can never decline an AcceptorCancellationAdvice (caaa.007.001.05). If the Acceptor does


not receive an AcceptorCancellationAdviceResponse (caaa.008.001.05), the Acceptor has to resend a
AcceptorCancellationAdvice until the Acceptor receives the corresponding response from the Acquirer
(see 3.3 Message Retransmission section).

Should an Acquirer decline an AcceptorCancellationRequest, an Acceptor always has the possibility to


refund the cardholder in cash or with a refund transaction.

The cancellation process may be affected by POI configuration parameters defined outside of the
present protocol.

- 32 -
Card Payments Message Usage Guide Version 5.0

2.4.1 Cancellation through cancellation advice or batch

A cancellation is carried out through an AcceptorCancellationAdvice exchange without a prior


AcceptorCancellationRequest.

This type of cancellation is used when:


 no financial capture of the original transaction occured (by message or by batch), or
 a financial capture of the original transaction occurred, and
 the Acceptor is aware that the original transaction has not been cleared by the Acquirer
(see note below)
 the Acceptor has all the data of the original transaction required for building up the
AcceptorCancellationAdvice.

Note: The Acceptor is able to know that the Acquirer did not clear the transaction because:
 the clearing of the transactions is only allowed after closing the corresponding reconciliation
period by a reconciliation exchange, and
 a reconciliation message to close the reconciliation period has not been sent for the
reconciliation period that includes the transaction.

A typical scenario is the following one:


 an Acceptor performs an authorisation without financial capture. The transaction is authorised
offline or online by the Acquirer. The transaction is successfully completed and stored by the
Acceptor.
 since no financial capture occurred, the Acceptor cancels the stored transaction and sends an
AcceptorCancellationAdvice to advise the Acquirer to reverse the authorisation.
 the Acquirer sends back an AcceptorCancellationAdviceResponse to inform the Acceptor that
the advice was acknowledged by the Acquirer and the authorisation reversed.

- 33 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or
AcceptorAuth
Authorised online orisa tionRequest
Transaction
authorised
orisa tionResponse
AcceptorAuth

Transaction
authorised

AcceptorCompl
etio nAdvice Transaction
Transaction completed authorised and
without capture completed without
se
etio nAdviceRespon capture
AcceptorCompl

Cancellation performed
locally

Option 1: Cancellation
advice used to reverse AcceptorCanc
ellatio nAdvice
authorisation Authorisation
reversed
Response
ellationAdvice
AcceptorCanc

Option 2: Batch used


to reverse AcceptorBatchT
rans fer
authorisation
Authorisation
reversed
e
ransferRespons
AcceptorBatchT

Figure 13: Cancellation through cancellation advice or batch

The message flow is the same as if the Acceptor had sent previously an AcceptorCompletionAdvice
without financial capture for the authorised transaction before the cancellation was processed.

For offline transactions, it is:

 optional to send an AcceptorCancellationAdvice if no AcceptorCompletionAdvice for the


transaction was previously sent
 mandatory to send an AcceptorCancellationAdvice if an AcceptorCompletionAdvice was
previously sent.

When the Acceptor uses batch transfer for financial capture, the Acceptor sends a batch transfer
depending on the configuration, with either:
 Include both the original debit (or credit) and cancellation transaction
 Remove the original debit (or credit) from the batch

- 34 -
Card Payments Message Usage Guide Version 5.0

An alternative scenario (with financial capture) is the following one:

 an Acceptor initiated several authorisations with financial capture (by individual messages or
batch).
 the transactions are authorised and captured by the Acquirer.
 the Acceptor is aware that the Acquirer has not yet cleared the transactions and he completes
the cancellation offline.
 the Acceptor sends an AcceptorCancellationAdvice to notify the Acquirer of the cancellation of
the authorisation and financial capture on his side.
 the Acquirer sends back an AcceptorCancellationAdviceResponse to inform the Acceptor that
the advice was received by the Acquirer. The Acquirer reverses the authorised and captured
transactions.
 should batch transfer be used by the Acceptor for financial capture, the Acceptor sends a
batch transfer depending on the configuration, with either:
Include both the original debit (or credit) and cancellation transaction
Remove the original debit (or credit) from the batch

- 35 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

Autorisation requested
online AcceptorAuth
orisa tionRequest Transaction
authorised

orisa tionResponse
AcceptorAuth

Transaction
authorised

AcceptorCompl
etio nAdvice
Option 1: Completion Transaction
Advice used for authorised
financial capture se and captured
etio nAdviceRespon
AcceptorCompl

AcceptorBatchT
rans fer
Option 2: Batch Transaction
transfer used for authorised
financial capture and captured
rans ferResponse
AcceptorBatchT

Option 1 : Cancellation
AcceptorCanc
carried out through a ellatio nAdvice
Cancellation Advice
Financial capture and
authorisation reversed
Response
ellationAdvice
AcceptorCanc

Option 2 : Cancellation
carried out through
batch with cancellation AcceptorBatchT
rans fer
flag set on
Financial capture and
e authorisation reversed
ransferRespons
AcceptorBatchT

Figure 14: Cancellation through cancellation advice and batch exchanges

- 36 -
Card Payments Message Usage Guide Version 5.0

2.4.2 Cancellation through cancellation request and advice exchanges

A cancellation is carried out through an AcceptorCancellationRequest followed by an


AcceptorCancellationAdvice.

This type of cancellation is used when all the following conditions are satisfied:
 financial capture of the transaction has already occured (by message or by batch), and
 the Acceptor is unaware whether the Acquirer cleared the transaction or not , and
 the Acceptor has all the data of the original transaction required for building up the
AcceptorCancellationRequest and AcceptorCancellationAdvice messages.

A typical scenario is the following one:


 an Acceptor performs an authorisation with financial capture. The transaction is authorised
offline or online by the Acquirer. The transaction is successfully completed and captured by
the Acquirer.
 the Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether the
transaction can be cancelled or not.
 should the cancellation be possible:
- the Acquirer sends a positive AcceptorCancellationResponse.
- the Acceptor sends back an AcceptorCancellationAdvice to complete the
cancellation by the Acquirer.
- the Acquirer responds with an AcceptorCancellationAdviceResponse to inform
the Acceptor that the advice was received by the Acquirer.
 should the cancellation not be possible:
- the Acquirer declines the request with a negative AcceptorCancellationResponse.
- the Acceptor does not send an AcceptorCancellationAdvice except if the
AcceptorCancellationResponse was not received.

- 37 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

Autorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisationR esponse
AcceptorAuth

Transaction
authorised

AcceptorCompl
etio nAdvice Transaction
Option 1: Completion
used for financial authorised and
capture captured
se
etio nAdviceRespon
AcceptorCompl

AcceptorBatchT
rans fer
Option 2 :Batch Transaction
transfer used for authorised and
capture captured
rans ferResponse
AcceptorBatchT

Cancellation initiated
through a cancellation AcceptorCanc
request ellatio nRequest

Capture reversed
e
ellationRespons
Capture reversed AcceptorCanc

Option 1: Cancellation AcceptorCanc


ellatio
advice used to nAdvice
complete cancellation Capture and
se Authorisation reversed
ellatio nAdviceRespon
AcceptorCanc

Option 2: Batch used


to complete
cancellation (flag to
cancel transactions) AcceptorBatchT
rans fer
Capture and
Authorisation reversed
e
ransferRespons
AcceptorBatchT

Figure 15: Cancellation through cancellation request and advice exchanges

- 38 -
Card Payments Message Usage Guide Version 5.0

2.4.3 Cancellation declined by the Acquirer

Should an AcceptorCancellationRequest be declined by the Acquirer, no further


AcceptorCancellationAdvice is sent by the Acceptor.
When the Acceptor used batch transfer for financial capture, the Acceptor may add the cancellation in
the batch according to the batch configuration.
Acceptor Acquirer
Transaction
authorised offline

or

Authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
ns e
orisationRespo
AcceptorAuth

Transaction
authorised

AcceptorCompl
etio nAdvice
Option 1 : Completion Transaction
Advice used for authorised and
capture captured
etionAdv iceResponse
AcceptorCompl

AcceptorBatchT
rans fer
Option 2 : Batch used Transaction
for capture authorised and
e captured
ransferRespons
AcceptorBatchT

Option 1 : Cancellation
AcceptorCanc
initiated ellatio nRequest
Cancellation declined
(transaction still
e captured)
ellationRespons
Cancellation declined AcceptorCanc

Declined Cancellation
can be sent in next
Batch transfer, if Batch
transfer is used

Option 2: Flag
transactions as AcceptorBatchT
cancelled or remove rans fer Cancellation declined
from batch (transactions still
captured)
rans ferResponse
Cancellation declined AcceptorBatchT

Figure 16: Declined cancellation of a captured transaction

- 39 -
Card Payments Message Usage Guide Version 5.0

2.4.4 Error in Cancellation Message Exchanges


In this chapter several scenarios are described where the Acceptor did not receive a response from
the Acquirer to AcceptorCancellationRequest messages.

2.4.4.1 Cancellation declined after timeout of a cancellation request

In this scenario:
 the Acceptor received an AcceptorCompletionAdviceResponse from the Acquirer
 the transaction was captured by the Acquirer
 the Acceptor did not receive a response to an AcceptorCancellationRequest.

In this case the Acceptor must decline the cancellation to the cardholder. An
AcceptorCancellationAdvice is sent to the Acquirer:
 to inform the Acquirer that the cancellation was declined to the cardholder

Acceptor Acquirer
Transaction
authorised offline

or

authorisation Initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised

orisationR esponse
AcceptorAuth

Completion Advice for AcceptorCom


pletio nAdvice
capture Transaction
authorised and
etionAd viceResponse captured
AcceptorCompl
Transaction authorised
and captured

Cancellation initiated AcceptorCanc


ellatio nRequest
If request received,
Cancellation
Cancellation is ellation processed
AcceptorCanc
declined as no reply Response
Cardholder informed
that the cancellation
was declined
AcceptorCanc
Advises Acquirer about ellatio nAdvice
declined cancellation Transaction
authorised and re-
se captured (if relevant)
ellatio nAdviceRespon
AcceptorCanc

Figure 17: Cancellation declined after timeout of a cancellation request

- 40 -
Card Payments Message Usage Guide Version 5.0

2.4.4.2 Cancellation successful after timeout of a completion advice

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice to capture the transaction and
 the Acceptor did not receive an AcceptorCompletionAdviceResponse and
 the Acceptor wants to cancel the transaction

Without having received an AcceptorCompletionAdviceResponse, the Acceptor is unaware whether


the transaction was captured or not.

Furthermore, the Acceptor is unaware whether the transaction was cleared or not (if the transaction
was actually captured).

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

Should the cancellation be possible:


 the Acquirer sends a AcceptorCancellationResponse to inform the Acceptor that the
transaction can be cancelled.
 the Acceptor informs the cardholder about the success of the cancellation and sends an
AcceptorCancellationAdvice to inform the Acquirer about the successful completion of the
cancellation.
 the Acquirer responds with an AcceptorCancellationAdviceResponse to inform the Acceptor
that the advice was received by the Acquirer.

Should clearing occur between the receipt of the AcceptorCancellationRequest and the
AcceptorCancellationAdvice, the Acquirer will refund the cardholder through an Acquirer to Issuer
exchange.

- 41 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

Authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisa tionResponse
AcceptorAuth

Completion Advice for AcceptorCom


capture pletio nAdvice Transaction
authorised and
possibly captured
etio n
AcceptorCompl
Acceptor unaware se
AdviceRespon
whether the transaction
was captured or not

Cancellation initiated AcceptorCanc


ellatio nRequest

Cancellation approved
e
ellationRespons
AcceptorCanc

Capture reversed (but


authorisation still active)

Complete cancellation AcceptorCanc


ellatio nAdvice
and reverse
Authorisation and
authorisation
capture (if relevant)
Response reversed
ellationAdvice
Transaction AcceptorCanc
successfully cancelled

Figure 18: Cancellation successful after timeout of a completion advice

- 42 -
Card Payments Message Usage Guide Version 5.0

2.4.4.3 Cancellation declined after timeout of a completion advice

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice to capture the transaction and
 the Acceptor did not receive an AcceptorCompletionAdviceResponse and
 the Acceptor wants to cancel the transaction.

Without having received an AcceptorCompletionAdviceResponse, the Acceptor is unaware whether


the transaction was captured or not.

Furthermore, the Acceptor is unaware whether the transaction was cleared or not (if the transaction
was actually captured).

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

Option 1

The cancellation is declined by the Acquirer because the transaction has already been captured and
cleared:
 the Acquirer sends an AcceptorCancellationResponse to inform the Acceptor that the
cancellation was declined.
 the Acceptor informs the cardholder that the cancellation was declined by the Acquirer
 the Acceptor needs to send an AcceptorCompletionAdvice with the financial data for capture
by the Acquirer because he does not know that the transaction is already captured. The
Acquirer discards the message since the transaction has already been captured.

Option 2

The cancellation is declined by the Acquirer because he did not receive the
AcceptorCompletionAdvice message:
 the Acquirer sends an AcceptorCancellationResponse to inform the Acceptor that the
cancellation was declined.
 the Acceptor informs the cardholder that the cancellation was declined by the Acquirer
 the Acceptor needs to send an AcceptorCompletionAdvice with the financial data for capture
by the Acquirer. The Acquirer captures the financial data for a further clearing.

The cardholder needs to get a refund for both options.

- 43 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

Autorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisa tionResponse
Transaction AcceptorAuth
successfully
completed

AcceptorCompletion
Option 1 Ad vice
Transaction captured
etion and cleared
AcceptorCompl
se
AdviceRespon
Option 2 AcceptorCom
pletionAdvice

Message not received

Cancellation requested AcceptorCanc


ellatio nRequest
Cancellation declined
e
ellationRespons
AcceptorCanc

Completion advice
for capture AcceptorCompl
etio nAdvice
Transaction captured
(option 2)
sponse
etionAdviceRe
AcceptorCompl

Figure 19: Cancellation declined after timeout of a completion advice

- 44 -
Card Payments Message Usage Guide Version 5.0

2.4.4.4 Cancellation declined after timeout

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice to capture the transaction and
 the Acceptor did not receive an AcceptorCompletionAdviceResponse.

The Acceptor wants to cancel the transaction but is unaware whether the Acquirer has already cleared
the transaction or not.
The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is
possible or not.

The Acceptor does not receive a response for the AcceptorCancellationRequest (timeout):
 the Acceptor informs the cardholder that the cancellation was declined
 the Acceptor sends back an AcceptorCompletionAdvice with the financial data for capture by
the Acquirer
 After receiving an AcceptorCompletionAdviceResponse from the Acquirer, the Acceptor sends
an AcceptorCancellationAdvice to inform the Acquirer that the cancellation was declined.
 The Acquirer acknowledges this advice with an AcceptorCancellationAdviceResponse.

- 45 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisationR esponse
AcceptorAuth
Transaction
successfully
completed

Completion advice for AcceptorCom


pletio nAdvice
capture
Transaction possibly
etion captured
AcceptorCompl
Acceptor unaware se
AdviceRespon
whether the transaction
was captured or not

Request cancellation AcceptorCanc


ellatio nRequest If request received:
Approve or decline
cancellation;
ellation If approved reverse
AcceptorCanc
Response capture (if relevant)
Cancellation declined to
cardholder

Repeat Completion AcceptorCompl


advice for capture etio nAdvice
Transaction
authorised and
se
etio nAdviceRespon captured
AcceptorCompl

Advise about declined AcceptorCanc


ellatio nAdvice
cancellation Transaction still
authorised and
Response captured
ellationAdvice
AcceptorCanc

Figure 20: Cancellation declined after timeout

- 46 -
Card Payments Message Usage Guide Version 5.0

2.4.4.5 Cancellation successful after completion errors

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice to capture the transaction and
 the Acceptor didn’t receive an AcceptorCompletionAdviceResponse.

The Acceptor wants to cancel the transaction and knows that the Acquirer did not clear the transaction
yet.
The Acceptor sends an AcceptorCancellationAdvice (without sending a prior
AcceptorCancellationRequest) to advise the Acquirer about the cancellation of the transaction.

The Acquirer accepts the cancellation:


 the Acquirer voids both the authorisation and financial capture associated to the transaction, if
required
 the Acquirer sends an AcceptorCancellationAdviceResponse to inform the Acceptor that the
cancellation succeeded.

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisa tionResponse
Transaction AcceptorAuth
successfully
completed

Completion Advice AcceptorCompl


etio nAdvice
with capture
Transaction possibly
captured
etion
AcceptorCompl
ceResp on se
Advi

Acceptor is aware that


the transaction has not
been cleared by the
Acquirer

Cancellation completed
offline

AcceptorCanc
ellatio nAdvice
Void capture and
authorisation
Response
ellationAdvice
AcceptorCanc

Figure 21: Cancellation successful after completion errors

- 47 -
Card Payments Message Usage Guide Version 5.0

2.4.4.6 Cancellation in batch mode

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice without capture and
 the Acceptor received an AcceptorCompletionAdviceResponse.

The Acceptor sends an AcceptorBatchTransfer to capture the transaction, but did not receive an
AcceptorBatchTransferResponse.

The Acceptor wants to cancel the transaction but is unaware whether the Acquirer has already cleared
the transaction or not.

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

The Acquirer accepts the cancellation:


 if needed, the Acquirer voids the financial capture associated with the transaction
 the Acquirer sends an AcceptorCancellationResponse to inform the Acceptor that the
cancellation was possible.
 the Acceptor informs the cardholder that the cancellation was accepted
 the Acceptor sends back an AcceptorCancellationAdvice to the Acquirer about the successful
cancellation of the transaction.
 the Acquirer voids the authorisation associated with the transaction
 the Acquirer sends an AcceptorCancellationAdviceResponse to inform the Acceptor that the
cancellation has been received.

The Acceptor sends a batch transfer depending on the configuration, with either:
 Include both the original debit (or credit) and cancellation transaction
 Remove the original debit (or credit) from the batch

- 48 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised

orisa tionResponse
Transaction AcceptorAuth
successfully
completed

Completion advice (no


capture) AcceptorCom
pletio nAdvice
Transaction
authorised and
se
ionAdviceRespon completed
AcceptorComplet

Batch transfer with AcceptorBatchT


capture rans fer
Transaction possibly
captured
rans fer
Acceptor unaware AcceptorBatchT
Response
whether the transaction
was captured or not

Cancellation initiated AcceptorCanc


ellatio nRequest
Cancellation approved
and capture reversed
ellatio nResponse (if relevant)
AcceptorCanc
Cancellation completed
but transaction still
authorised

Advise cancellation AcceptorCanc


through cancellation ellatio nAdvice
advice Authorisation and
se capture reversed
ellatio nAdviceRespon
AcceptorCanc

Advise cancellation AcceptorBatchT


rans fer
through batch
(transactions flagged as Authorisation and
cancelled or remove capture reversed
from batch) chTransfer
AcceptorBat e
Respons

Figure 22: Cancellation in batch mode

- 49 -
Card Payments Message Usage Guide Version 5.0

2.4.4.7 Declined cancellation in batch mode

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice without capture and
 the Acceptor received an AcceptorCompletionAdviceResponse.

The Acceptor sends an AcceptorBatchTransfer to capture the transaction, but does not receive an
AcceptorBatchTransferResponse.

The Acceptor wants to cancel the transaction but is unaware whether the Acquirer has already cleared
the transaction or not.

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

The Acquirer declines the cancellation:


 the Acquirer sends an AcceptorCancellationResponse to inform the Acceptor that the
cancellation was not possible.
 the Acceptor informs the cardholder that the cancellation was declined

The Acceptor has to resend the AcceptorBatchTransfer that failed. No AcceptorCancellationAdvice is


sent by the Acceptor.

- 50 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised

orisa tionResponse
Transaction AcceptorAuth
successfully
completed

Completion advice (no


capture) AcceptorCom
pletio nAdvice
Transaction
se authorised
ionAdviceRespon
AcceptorComplet

Batch transfer with AcceptorBatchT


capture rans fer
Transaction possibly
captured
ransfer
Acceptor unaware AcceptorBatchT
whether the transaction Response
was captured or not

Cancellation initiated AcceptorCanc


ellatio nRequest

Cancellation declined
e
ellationRespons
AcceptorCanc

Repeat batch transfer AcceptorBatchT


with capture rans fer
Transaction
authorised and
capture
chTransfer
AcceptorBat e
Respons

Figure 23: Declined cancellation in batch mode

- 51 -
Card Payments Message Usage Guide Version 5.0

2.4.4.8 Declined cancellation after timeout in batch mode and cancellation request

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice without capture and
 the Acceptor received an AcceptorCompletionAdviceResponse.

The Acceptor sends an AcceptorBatchTransfer to capture the transaction, but does not receive an
AcceptorBatchTransferResponse.

The Acceptor wants to cancel the transaction but is unaware whether the Acquirer already has cleared
the transaction or not.

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

The Acceptor does not received the response to the AcceptorCancellationRequest message
 the Acceptor has to decline the cancellation to the cardholder
 the Acceptor sends an AcceptorCancellationAdvice to inform the Acquirer about the declined
cancellation of the transaction.
 the Acquirer sends an AcceptorCancellationAdviceResponse to inform the Acceptor that the
cancellation was declined.

Once the Acceptor has sent the AcceptorCancellationAdvice, it has to resend the
AcceptorBatchTransfer for the financial capture by the Acquirer since the transaction was not
cancelled.

- 52 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest

Transaction
esponse authorised
orisationR
AcceptorAuth
Transaction
successfully
completed
AcceptorCom
pletio nAdvice
Completion advice
Transaction
(no capture)
se authorised
ionAdviceRespon
AcceptorComplet

Capture through batch AcceptorBatchT


rans fer
Transaction possibly
captured
ransfer
Acceptor unaware AcceptorBatchT
whether the transaction Response
was captured or not

Initiated cancellation for a


AcceptorCanc
transaction in previous ellatio nRequest If request received:
batch Approve or decline
cancellation;
ellatio n If approved void
AcceptorCanc
Response capture
Cancellation declined to
cardholder

Cancellation advice to
advise about declined AcceptorCanc
ellatio nAdvice
cancellation Transaction
authorised and
se capture reversed
Confirmation about ellatio nAdviceRespon
declined cancellation AcceptorCanc

Use batch to capture


the « un-captured » AcceptorBatchT
rans fer
authorised transaction Transactions
authorised and
captured
chTransfer
AcceptorBat e
Respons

Figure 24: Declined cancellation after timeout in batch mode and cancellation request

- 53 -
Card Payments Message Usage Guide Version 5.0

2.4.4.9 Declined cancellation in batch mode after timeout in cancellation request

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice without capture and
 the Acceptor received an AcceptorCompletionAdviceResponse.

The Acceptor sends an AcceptorBatchTransfer to capture the transaction and he receives an


AcceptorBatchTransferResponse to confirm the financial capture.

The Acceptor wants to cancel the transaction but is unaware whether the Acquirer has already cleared
the transaction or not.

The Acceptor sends an AcceptorCancellationRequest to ask the Acquirer whether a cancellation is


possible or not.

The Acceptor did not received a response to the AcceptorCancellationRequest:


 the Acceptor has to decline the cancellation to the cardholder
 the Acceptor sends an AcceptorCancellationAdvice to inform the Acquirer about the declined
cancellation of the transaction.
 the Acquirer sends an AcceptorCancellationAdviceResponse to inform the Acceptor that the
cancellation was reversed.

Once the Acquirer has declined the cancellation, no AcceptorBatchTransfer needs to be exchanged
since the Acquirer has already made the financial capture and the transaction was not cancelled.

- 54 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

authorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisa tionResponse
AcceptorAuth
Transaction
successfully
completed
AcceptorCom
pletio nAdvice
Completion advice
Transaction
without capture
se authorised
ionAdviceRespon
AcceptorComplet

Batch transfer with AcceptorBatchT


capture rans fer
Transaction
authorised and
captured
Transfer
Acceptor receives AcceptorBatch
R es po ns e
response

Request cancellation AcceptorCanc


ellatio nRequest If request received:
Acceptor unaware Approve or decline
whether the transaction cancellation;
ellatio n If approved void
was captured or not AcceptorCanc
Response capture
Cancellation declined

Inform Acquirer about


AcceptorCanc
declined cancellation ellatio nAdvice
Transaction remains
captured or is
se captured again
ellatio nAdviceRespon
AcceptorCanc

Figure 25: Declined cancellation in batch mode after timeout cancellation request

- 55 -
Card Payments Message Usage Guide Version 5.0

2.4.4.10 Cancellation in batch mode of a transaction captured but not yet cleared

In this scenario:
 the Acceptor sent an AcceptorCompletionAdvice without capture and
 the Acceptor received an AcceptorCompletionAdviceResponse.

The Acceptor sends an AcceptorBatchTransfer to capture the transaction, but does not receive an
AcceptorBatchTransferResponse.

The Acceptor wants to cancel the transaction and is aware that the Acquirer has not cleared the
transaction yet.

In that scenario:
 The Acceptor sends an AcceptorCancellationAdvice to inform the Acquirer about the
cancellation of the transaction.
 The Acquirer voids the authorisation and financial capture of the transaction
 The Acquirer sends an AcceptorCancellationAdviceResponse to inform the Acceptor that the
cancellation of the transaction suceeded.

The Acceptor sends a batch transfer depending on the configuration, with either:
 Include both the original debit (or credit) and cancellation transaction
 Remove the original debit (or credit) from the batch
.

- 56 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer
Transaction
authorised offline

or

autorisation initiated
online AcceptorAuth
orisa tionRequest
Transaction
authorised
orisa tionResponse
AcceptorAuth
Transaction
successfully
completed
AcceptorCom
pletio nAdvice
Completion advice
Transaction
without capture might
authorised and
be used se
ionAdviceRespon completed
AcceptorComplet

Batch transfer with AcceptorBatchT


capture rans fer
Transaction
authorised and
possibly captured
ransfer
Acceptor unaware AcceptorBatchT
whether the transaction Resp on se
was captured or not

Acceptor aware that the


transaction was not
cleared yet

Cancellation completed
offline
AcceptorCanc
ellatio nAdvice
Authorisation and
capture reversed
se
ellatio nAdviceRespon
AcceptorCanc
Batch transfer with
transaction flagged as AcceptorBatchT
cancelled rans fer

chTransfer
AcceptorBat e
Res ns
po

Figure 26: Cancellation in batch mode of a transaction captured but not yet cleared

- 57 -
Card Payments Message Usage Guide Version 5.0

2.5 Batch

2.5.1 Introduction

Batch allows an Acceptor to send groups of transactions in a single message or a file to the Acquirer
for financial capture.

A batch transfer exchange is composed of an AcceptorBatchTransfer (caaa.011.001.05) and an


AcceptorBatchTransferResponse (caaa.012.001.05) used to acknowledge or to reject some or all
transactions contained in a batch.

Towards the Acquirer

The AcceptorBatchTransfer to be uploaded contains locally stored offline and online transactions.

In addition to financial transactions (payments, refunds, etc.) non-financial transactions (incomplete,


declined, etc.) may be added to an AcceptorBatchTransfer.
TransactionTotals are part of the file to enable reconciliation.
Message or File integrity is ensured through a security trailer.

Towards the Acceptor

The Acquirer informs the acceptor about the validation of AcceptorBatchTransfer content by sending
an AcceptorBatchTransferResponse message.
The Acceptor retains the stored transactions which were previously sent to the Acquirer until receiving
an AcceptorBatchTransferResponse message from the Acquirer.
The AcceptorBatchTransferResponse provides status information about the data received.

The Acquirer informs the Acceptor about the transfer of data.

Once the Acceptor has received this notification, from a protocol perspective, the Acceptor is freed of
any technical responsibility to keep the data .

- 58 -
Card Payments Message Usage Guide Version 5.0

2.5.2 Data Organisation

2.5.2.1 AcceptorBatchTransfer

The upload of the data to be captured is initiated by an Acceptor using either a file transfer exchange
or exchanges of messages.

Data to be sent is organised into sets. An AcceptorBatchTransfer contains one or more sets.

A DataSet contains one or more financial and/or non-financial transactions. However it is possible that
a data set contains no transactions.

Data common to all transactions of a set may be factorised and sent prior to the transactions (e.g.
Acquirer data, POI data…)

The content of the set and its organisation depend on the POI configuration.

Its structure is represented as follows:

Header DataSet Trailer

0..n

DataSet Traceability DataSet Transaction Common Transaction


Identification Initiator Totals Data

Figure 27: BatchTransfer structure

2.5.2.2 AcceptorBatchTransferResponse
The Acquirer validates an AcceptorBatchTransfer with an AcceptorBatchTransferResponse according
to the following process:
 The Acquirer sends back an AcceptorBatchTransferResponse to the Acceptor in case of a
message exchange, or
 The Acceptor downloads an AcceptorBatchTransferResponse file.
The AcceptorBatchTransferResponse contains the response from the Acquirer for each DataSet that
has been processed. Any individual transactions that have been rejected by the Acquirer will be

- 59 -
Card Payments Message Usage Guide Version 5.0

contained within the appropriate DataSet response. An Acquirer can only send a DataSet in a
AcceptorBatchTransferResponse when all transactions in that DataSet have been processed.

If a set is partially approved, the element “DataSet” is present. It contains the details of rejected
transactions.

The content of the DataSet and its organisation depend on POI configuration.
File structure may be represented as follows:

Header DataSet Trailer

0 .. n

DataSetIdentification DataSetResult RemoveDataSet DataSetInitiator TransactionTotals RejectedTransaction

0 .. n

Figure 28: BatchTransferResponse structure

2.5.2.3 Data Factorisation

To prevent file size problems, some data of an AcceptorBatchTransfer may be factorised to reduce the
occurrences of repetitive data.

The Acquirer must support factorisation. The Acceptor may choose whether to perform factorisation or
not.

Factorisation is limited to the following data:


 Acquirer
 Merchant
 POI
 PaymentContext
 SaleContext
 TransactionType
 AdditionalService
 ServiceAttribute
 MerchantCategoryCode
 Currency

- 60 -
Card Payments Message Usage Guide Version 5.0

All transaction components within a DataSet will inherit data from the values held in CommonData
unless different data is held in the transaction component itself.

The Acquirer sends an AcceptorBatchTransferResponse with the same DataSet factorisation as in the
related AcceptorBatchTransfer.

2.5.2.4 Multiplicity
Data elements which are mandatory in an AcceptorCompletionAdvice message are de facto
mandatory in an AcceptorBatchTransfer. Some of the elements may be factorised in CommonData
and in that case need not appear in the Transaction components but they must all be present in one
place or the other.

- 61 -
Card Payments Message Usage Guide Version 5.0

2.5.3 Types of Batch Transfer

A batch is generally used as a collection of transactions to be sent to an Acquirer for processing.

2.5.3.1 Batch containing Completion and Cancellation Transactions

An AcceptorBatchTransfer is sent by an Acceptor to an Acquirer. It contains a collection of


completion and cancellation transactions.

Completion transactions which may be sent as:


 Successful debit transactions:
 “TransactionType” with the value “CardPayment”; “CashBack” or
“DeferredPayment” and
 “TransactionSuccess” with the value “True”
 Successful credit transactions:
 “TransactionType” with the value “Refund” and
 “TransactionSuccess” with the value “True”
 Failed or declined transactions:
 “TransactionSuccess” with the value “False”;

Cancelled transactions are sent with “TransactionSuccess” having the value “True”

Depending on a TMS configuration, the following types of transactions can be present or not :
 Debit and Credit transaction
 Failed transactions
 Declined transactions
 Cancelled transactions

An AcceptorBatchTransferResponse message is sent by the Acquirer to the Acceptor to confirm the


proper acknowledgement of the card payment transactions by the Acquirer.

The AcceptorBatchTransferResponse file contains the response from the Acquirer for each DataSet
that has been processed. Any individual transactions that have been rejected by the Acquirer must be
contained within the appropriate DataSet response.

An Acquirer can only send a DataSet in a BatchTransferResponse when all transactions in that
DataSet have been processed.

Responses to one AcceptorBatchTransfer can be sent in several AcceptorBatchTransferResponse.

Responses for several AcceptorBatchTransfer can be sent in one AcceptorBatchTransferResponse.


(See section 4.6 Batch.)

- 62 -
Card Payments Message Usage Guide Version 5.0

The acquirer has to give a response in one DataSet for all the transactions contained in a DataSet
received and only for these transactions.

2.5.3.2 Batch containing Authorisation Transactions

An AcceptorBatchTransfer is sent
 by an Acceptor to an Acquirer containing a collection of authorisation requests
 by an Acquirer to an Acceptor containing a collection of authorisation responses only.

The use of authorisations in BatchTransfer is not configurable but depends on a bilateral agreement
between an Acceptor and Acquirers involved.

In the case of batch transferred authorisations:


 A DataSet in the batch sent from an Acceptor to an Acquirer contains only
AuthorisationRequests,
 The batch sent from an Acquirer to an Acceptor contains only AuthorisationResponses.

A batch of authorisations may contain:


 Debit transactions : AuthorisationRequest occurrences with “transactionType” data element
value equal to “CardPayment”;
 Credit transactions : AuthorisationRequest occurrences with “transactionType” data element
value equal to “ “Refund”;
 Debit transactions : AuthorisationResponse occurrences;
 Credit transactions :AuthorisationResponse occurrences .

The rejected AuthorisationRequests are sent in a related AuthorisationResponse with Response set to
"TechnicalError". The BatchTransferResponse is not used for acknowledging AuthorisationRequests.
In this case, a completion can be sent to nullify the effect of the authorisation request.

A dataset containing AuthorisationRequest messages can be answered with more than one dataset.
In this case, all the rejected transactions must be present in the first dataset containing responses.
Responses contained in a dataset must refer to requests contained in only one dataset

The acquirer can require to receive completions in the batch for previously authorised online
transactions and / or authorised offline transactions.
 transactions authorised online are configured to be captured in batch (e.g. the TMS parameter
AcquirerProtocolParameters.OnlineTransaction.FinancialCapture is equal to Batch)
 transactions authorised offline are configured to be captured in batch (e.g. the TMS parameter
AcquirerProtocolParameters.OfflineTransaction.FinancialCapture is equal to Batch)

- 63 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer

Transaction initiated
offline
AcceptorBatchT
ra
Authorisations initiated (AuthorisationRe nsfer
by batch with capture quest)

Transactions
authorised and
captured
chTransfer
AcceptorBat esponse)
risatio nR
(Autho
Transaction
successfully
completed (approved/
declined) or rejected

AcceptorBatchT
ransfer
(completion)
Batch transfer with
capture to void rejected
transactions
Rejected transaction
voided

ns e
TransferRespo
AcceptorBatch

Figure 29: Batch containing Financial Authorisations

- 64 -
Card Payments Message Usage Guide Version 5.0

Acceptor Acquirer

Transaction initiated
offline
AcceptorBatchT
ra
Authorisations initiated (AuthorisationRe nsfer
quest)
by batch

Transactions
authorised

chTransfer
AcceptorBat esponse)
nR
(Authorisatio
Transaction
successfully
completed (approved/
declined) or rejected

AcceptorBatchT
Capture initiated by ransfer
(completion)
batch
Transactions
captured
ns e
TransferRespo
AcceptorBatch

Figure 30: Batch containing Authorisations

- 65 -
Card Payments Message Usage Guide Version 5.0

2.6 Reconciliation Process

2.6.1 Introduction

Reconciliation is the process of performing checks and balances of transactions previously captured.
This process is carried out between an Acceptor and an Acquirer for a given reconciliation period.

An Acceptor initiates a reconciliation exchange to ensure that the debits and credits match the
computed balances by the Acquirer and performed during the same reconciliation period.

An AcceptorReconciliationRequest message (caaa.009.001.05) is sent by the Acceptor to inform the


Acquirer about the totals accumulated during the reconciliation period.

An AcceptorReconciliationResponse message (caaa.010.001.05) is returned by the Acquirer to inform


the Acceptor about the totals accumulated during the reconciliation period.

Acceptor Acquirer

AcceptorReconciliationR
equ est

ponse
AcceptorReconciliationRes

Figure 31: Reconciliation Exchange

Should the Acceptor or the Acquirer detect a difference in totals, the discrepancy must then be
resolved by other means and is outside the scope of this protocol.

Reconciliation is not mandatory and reconciliation messages are never exchanged when the
configuration parameter AcquirerProtocolParameters.ReconciliationExchange.ExchangePolicy defined
in the AcceptorConfigurationUpdate TMS message has the value None or is absent.

- 66 -
Card Payments Message Usage Guide Version 5.0

2.6.2 Reconciliation Period Identification

If reconciliation between an Acceptor and an Acquirer is required, each transaction belongs to one and
only one reconciliation period identified by the message element
Transaction.ReconciliationIdentification.

Assignment of transactions to a reconciliation period can be made by either the Acceptor or the
Acquirer depending on the TMS configuration parameter flag ReconciliationByAcquirer.

If the reconciliation period assignment is under the control of the Acceptor (ReconciliationByAcquirer
parameter is False), the reconciliation period is identified by the message element
Transaction.ReconciliationIdentification in the AcceptorAuthorisationRequest,
AcceptorCompletionAdvice, AcceptorCancellationRequest and AcceptorCancellationAdvice
messages.

Acceptor Acquirer

ReconciliationIdentification:112 AcceptorAuthorisationReq
ues t

pon se
AcceptorAuthorisationRes

ReconciliationIdentification:112 AcceptorReconciliationReq
ues t

ReconciliationIdentification:112
ponse
AcceptorReconciliationRes

Figure 32: Reconciliation Period Assigned by the Acceptor

- 67 -
Card Payments Message Usage Guide Version 5.0

During the reconciliation exchange, the reconciliation period is identified in the message element
Transaction.ReconciliationIdentification of AcceptorReconciliationRequest and
AcceptorReconciliationResponse.

Acceptor Acquirer

AcceptorAuthorisationReq
ues t

ReconciliationIdentification:113
ponse
AcceptorAuthorisationRes

ReconciliationIdentification:113 AcceptorReconciliationReq
ues t

ReconciliationIdentification:113
ponse
AcceptorReconciliationRes

Figure 33: Reconciliation Period Assigned by the Acquirer

The reconciliation period of the transaction is identified by the ReconciliationIdentification at the time of
the transaction capture. If the capture is performed during the completion, the
AcceptorCompletionAdvice may have a ReconciliationIdentification value different from the
Authorisation.
Acceptor Acquirer

ReconciliationIdentification:112 AcceptorAuthorisationRequ
est
transaction 1
authorisation approval
nse without capture
AcceptorAuthorisationRespo
transaction 1

ReconciliationIdentification:112 AcceptorReconciliationRequest

transaction 1 not in the totals


se
AcceptorReconciliationRespon

ReconciliationIdentification:113 AcceptorCompletionAdvice
transaction 1
capture of transaction 1
ponse
AcceptorCompletionAdviceRes
transaction 1

ReconciliationIdentification:113 AcceptorReconciliationRequest

transaction 1 in the totals


se
AcceptorReconciliationRespon

Figure 34: Reconciliation between the Authorisation and the Completion

- 68 -
Card Payments Message Usage Guide Version 5.0

When the flow of transaction cannot be stopped for closing the reconciliation at the acceptor, before
sending the AcceptorReconciliationRequest message, the Acceptor must:
 Assigne the new transactions to the next reconciliation period, and
 Wait for the completion of the transactions of the reconciliation period to close before sending
the AcceptorReconciliationRequest message.
Successive reconciliation periods are then interleaved.
Acceptor Acquirer
AcceptorCompletionAdvice
ReconciliationIdentification:112
transaction 1
open reconciliation period 113
reconciliation
AcceptorCompletionAdvice period 112
ReconciliationIdentification:113
transaction 2

ponse
AcceptorCompletionAdviceRes
transaction 1
close reconciliation period 112
AcceptorReconc
ReconciliationIdentification:112 iliat ionRequest

ponse
AcceptorCompletionAdviceRes
transaction 2

AcceptorCompletionAdvice reconciliation
ReconciliationIdentification:113 period 113
transaction 3

nse
AcceptorReconciliationRespo

ponse
AcceptorCompletionAdviceRes
transaction 2

Figure 35: Overlapping of Reconciliation Periods

- 69 -
Card Payments Message Usage Guide Version 5.0

2.6.3 Transaction Totals

Transaction totals are calculated from transactions completed and captured during the reconciliation
period.

Before initiating a reconciliation exchange, the Acceptor must:


1) Perform the capture of all the transactions integrated in the totals of the reconciliation period,
2) Inform the Acquirer about all the online cancelled transactions of the reconciliation period
3) Inform the Acquirer about all the offline cancelled transactions, if these are integrated in the
totals of the reconciliation period, and
4) Inform the Acquirer about all the reversed online transactions of the reconciliation period.

Transaction totals may be split in a sequence of repeated Transaction.TransactionTotals message


elements, according to the following criteria:
 TransactionTotals.Type: the type of transaction, which is mandatory,
 TransactionTotals.POIGroupIdentification: the grouping of transactions made by the Acceptor,
when the two following conditions are fulfilled:
 the acceptor is configured to split totals (TMS configuration parameter
AcquirerProtocolParameters.SplitTotals is True), and
 the message element POI.GroupIdentification is present in AcceptorAuthorisationRequest,
AcceptorCompletionAdvice, AcceptorCancellationRequest or AcceptorCancellationAdvice
messages.
The transactions where POI.GroupIdentification is absent have to be combined in instances of
TransactionTotals without POIGroupIdentification.
 TransactionTotals.CardProductProfile: the card profile, when the two following conditions are
fulfilled:
 the acceptor is configured to split totals (TMS configuration parameter
AcquirerProtocolParameters.SplitTotals is True), and
 the message element Card.CardProductProfile is present in the
AcceptorAuthorisationRequest, AcceptorCompletionAdvice, AcceptorCancellationRequest
or AcceptorCancellationAdvice messages.
The transactions where CardProductProfile is absent have to be combined in instances of
TransactionTotals without CardProductProfile.
 TransactionTotals.Currency: the currency of the transaction, when the acceptor is configured
to split totals per currency (TMS configuration parameter
AcquirerProtocolParameters.TotalsPerCurrency is True). When TotalsPerCurrency is False,
totals are computed whatever the currency and the TransactionTotals.Currency message
element is absent.

The Totals of declined and failed transactions are included in the ReconciliationRequest. A
Reconciliation is never rejected because of differences with declined and failed transaction totals.

If a cancellation is allowed after the reconciliation of the original transaction, the original transaction is
considered as a Debit or Credit for the first reconciliation period, and the cancelled transaction
considered as a DebitReverse or a CreditReverse respectively for the second reconciliation period.

If a transaction can be cancelled on a different POI terminal from the POI terminal where the original
transaction has been performed, and the totals are accumulated per POIGroupIdentification, the

- 70 -
Card Payments Message Usage Guide Version 5.0

cancellation (DebitReverse or CreditReverse) is counted in the totals of the POIGroupIdentification


related to the original transaction, even if the Cancellation transaction belongs to another reconciliation
period.

A difference in totals between the Acceptor and the Acquirer may occur after reaching the maximum
number of retransmissions of an AcceptorCompletionAdvice (or AcceptorCancellationAdvice) without
a positive AcceptorCompletionAdviceResponse (or AcceptorCancellationAdviceResponse). In this
case, it is not possible for the Acceptor to determine the knowledge of the Acquirer about the outcome
of the transaction because:
 The Acquirer may have not received or understood the repeated AcceptorCompletionAdvice
(or AcceptorCancellationAdvice) messages,
 The Acquirer may have received and understood an AcceptorCompletionAdvice (or
AcceptorCancellationAdvice) message, but the Acceptor has not received or has not
understood the AcceptorCompletionAdviceResponse (or
AcceptorCancellationAdviceResponse).

- 71 -
Card Payments Message Usage Guide Version 5.0

2.6.4 Reconciliation Exchange

The configuration parameter AcquirerProtocolParameters.ReconciliationExchange.ExchangePolicy


defined in the AcceptorConfigurationUpdate TMS message determines whether an
AcceptorReconciliationRequest message may be used or not.

The Policy component of this configuration parameter can contain the following values:
 Cyclic: an AcceptorReconciliationRequest message is sent periodically according to the timing
conditions defined in the AcquirerProtocolParameters.ReconciliationExchange.TimeCondition
component.
 NumberLimit: an AcceptorReconciliationRequest message is sent as soon as the sum of all
TransactionTotals.TotalNumber of the current reconciliation period reaches the value
configured in the AcquirerProtocolParameters.ReconciliationExchange.MaximumNumber
component.
 TotalLimit: an AcceptorReconciliationRequest message is sent as soon as the sum of all
TransactionTotals.CumulativeAmount of the current reconciliation period reaches or exceeds
the value configured in the
AcquirerProtocolParameters.ReconciliationExchange.MaximumAmount component.
 OnDemand: an AcceptorReconciliationRequest message is sent when requested by the
Acceptor.
 None: the Acceptor never sends AcceptorReconciliationRequest messages.

The component Transaction.ClosePeriod may request the closure of a reconciliation period. This
request is useful when the Acquirer assigns a reconciliation period identification to transactions.

The response to an AcceptorReconciliationRequest message is either an AcceptorRejection message,


or an AcceptorReconciliationResponse message with Response = "Approved" or "Declined".

If there is no transactions in the reconciliation period, the AcceptorReconciliationResponse message


must be sent with Response = "Approved".

It is possible that the verification of the totals cannot be performed in real-time before sending the
response to the reconciliation. In this case, the AcceptorReconciliationResponse message must
contain:
 Response = "Approved".
 ResponseReason = "Totals Unavailable".
 TransactionTotals must be absent.

If the totals are performed in real-time by the Acquirer, and some totals are different from the totals
send by the Acceptor, the AcceptorReconciliationResponse message must contain:
 Response = "Declined".
 ResponseReason = "Difference in Totals".
 TransactionTotals must be present, as computed by the Acquirer.

Whatever the result of the reconciliation (Response = "Approved" or "Declined"), a new reconciliation
period has to be started to perform new transactions. Any difference or discrepancy has to be resolved
outside the protocol.

- 72 -
Card Payments Message Usage Guide Version 5.0

If the Acceptor did not receive an acceptable response to an AcceptorReconciliationRequest, it may


send a new AcceptorReconciliationRequest message, with a copy of the body ReconciliationRequest,
and a new value of ExchangeIdentification and CreationDateTime in the header.

It is recommended to stop exchanging transactions during a reconciliation exchange.


If it is not possible:
 the Acceptor assigns a new reconciliation period for the transactions that may follow,
 the Acceptor waits until the end of the transaction of the current reconciliation period,
 the Acceptor sends the required AcceptorCompletionAdvice (or AcceptorCancellationAdvice)
messages (see section 2.6.3)
 the Acceptor starts the reconciliation exchange.

- 73 -
Card Payments Message Usage Guide Version 5.0

2.7 Diagnostic Messages

A diagnostic exchange is composed of an AcceptorDiagnosticRequest (caaa.013.001.05) message


and an AcceptorDiagnosticResponse (caaa.014.001.05) message.

An AcceptorDiagnosticRequest is a message sent by an InitiatingParty to a RecipientParty to check


the availability, the security or the configuration of the dialogue with the RecipientParty.

The Diagnostic message has been designed to perform specific administrative tasks without relying on
“dummy” messages.

An AcceptorDiagnosticResponse message is sent back by the RecipientParty to the InitiatingParty to


confirm the availability of the RecipientParty.

Initiating Party Recipient Party

AcceptorDiagnosticRequ
est

ons e
AcceptorDiagnosticResp

Figure 36: Diagnostic Exchange

An AcceptorDiagnosticRequest message is used to:


 Confirm the identification of the partners of the exchanges,
 Ensure that security on both sides of the dialogue is synchronised,
 Test the communication with a RecipientParty ,
 Endorse the version of the configuration parameters.

If the AcceptorDiagnosticRequest message is received without errors by the RecipientParty, an


AcceptorDiagnosticResponse message is sent back by the RecipientParty to the InitiatingParty.

The RecipientParty uses an AcceptorDiagnosticResponse message to request the InitiatingParty to


notify the RecipientParty about any maintenance operations that may be required.

- 74 -
Card Payments Message Usage Guide Version 5.0

If the RecipientParty receives an AcceptorDiagnosticRequest message with errors or cannot process


the message, an AcceptorRejection message is returned to the InitiatingParty with the appropriate
RejectReason:
 UnableToProcess: the RecipientParty cannot process messages during a temporary period.
 InvalidMessage: Invalid envelope of the message
 ParsingError: Problem of format, absence of element, content of an element, etc.
 Security: Security error such as an invalid key or MAC
 InitiatingParty, RecipientParty: identification of the InitiatingParty or the RecipientParty is
invalid.
 DuplicateMessage: The message is a duplicate message for a given InitiatingParty and a
given RecipientParty when the following fields have the same value:
 Header.ExchangeIdentification,
 CreationDateTime and
 HeaderRetransmissionCounter if present.
 ProtocolVersion: The RecipientParty cannot support the version of the protocol contained in
ProtocolVersion.

Initiating Party Recipient Party

AcceptorDiagnosticRequ
est

invalid message

AcceptorRejection

Figure 37: Diagnostic Reject

Should an InitiatingParty send an AcceptorDiagnosticRequest to an Agent, the Agent returns an


AcceptorDiagnosticResponse to the InitiatingParty.

An AcceptorDiagnosticRequest message does not contain any information that may allow an Agent to
further route the message to another Agent or RecipientParty.

Acceptor Agent Acquirer

AcceptorDiagnosticRequ
est

ons e
AcceptorDiagnosticResp

Figure 38: Diagnostic Request from an Acceptor to an Agent

An Agent must never forward an AcceptorDiagnosticRequest message.

- 75 -
Card Payments Message Usage Guide Version 5.0

An Acceptor must only use an AcceptorDiagnosticRequest message under exceptional situations to


avoid any potential risk of message congestion (e.g. after the installation of a payment application or
during an update of electronic keys).

- 76 -
Card Payments Message Usage Guide Version 5.0

An Intermediary Agent uses a diagnostic exchange to check the availability of the communication with
an Acquirer or another Intermediary Agent.

Acceptor Agent Acquirer

AcceptorDiagnosticRequ
est

ons e
AcceptorDiagnosticResp

Figure 39: Diagnostic Request from an Intermediary Agent

- 77 -
Card Payments Message Usage Guide Version 5.0

2.8 Reject Message

A RecipientParty sends an AcceptorRejection message (caaa.015.001.05) to an InitiatingParty to


indicate that the RecipientParty could not process the received message.

For instance, if an InitiatingParty sends an AcceptorAuthorisationRequest message and that message


is not recognised by the RecipientParty, the RecipientParty sends back an AcceptorRejection in
response to that message.

InitiatingParty RecipientParty

AcceptorAuthorisationR
equ est
message couldn’t
be processed
AcceptorRejection

Figure 40: Rejection of an Authorisation

The AcceptorRejection message contains the reason of the rejection (RejectReason), some additional
information on the rejection (AdditionalInformation) for further analysis as well as the rejected
message itself (MessageInError) (to make it possible to compare with the message sent).

The AcceptorRejection message must be sent in the following cases:

1. The envelope of the received message is incorrect (see section 3.4.1.2 a) ).


RejectReason contains the value InvalidMessage. It is recommended to include the optional fields
AdditionalInformation to provide the details of the error. MessageInError contains the received
message with the error.

2. The rejected message cannot be decoded properly (see section 3.4.1.2 b) ).


RejectReason contains the value ParsingError. It is recommended to include the optional fields
AdditionalInformation to provide the details of the coding error. MessageInError contains the
received message with the coding error.

3. The identification of the rejected message is invalid (see section 3.4.1.2 e) ).


RejectReason contains the value InitiatingParty or RecipientParty. No other field is required.
AdditionalInformation may contain the invalid identifier.

4. The verification of the security of the rejected message fails (see section 3.4.1.2 d) ).
RejectReason contains the value Security. It is recommended to include the optional fields
AdditionalInformation to provide the details of the security error. MessageInError contains the
received message with the security error.

- 78 -
Card Payments Message Usage Guide Version 5.0

5. The version of the protocol used for the message (Header.ProtocolVersion) is not supported by
the RecipientParty which is not able to send a message response of this version to the
InitiatingParty (see section 3.4.1.2 c) ).
RejectReason contains the value ProtocolVersion and AdditionalInformation the invalid protocol
version.

6. The rejected message has already been sent by the InitiatingParty to the RecipientParty. The
message could not be processed a second time, and then a response could not be sent (see
section 3.4.1.2 f) ).
RejectReason contains the value DuplicateMessage. No other field is required.
AdditionalInformation may contain the invalid ExchangeIdentifier value.

7. The RecipientParty is not able to process the message for lack of resources. For that reason, a
message response could not be built and the message is not processed (see section 3.4.1.3 b) ).
RejectReason has the value UnableToProcess. AdditionalInformation contains the reason why
the message could not be processed.

The reaction of the InitiatingParty to an AcceptorRejection message depends on the RejectReason


and the type of rejected message.

As an AcceptorRejection message is related to a specific request or an advice message between two


entities, an Agent never forwards an AcceptorRejection message.
In the example illustrated below, an Agent forwards an AcceptorAuthorisationRequest message
issued by an Acceptor to the relevant Acquirer. The Acquirer cannot process the message and issues
an AcceptorRejection message instead of an AcceptorAuthorisationResponse. The Agent receives the
rejection message and sends to the card acceptor the appropriate AcceptorAuthorisationResponse
message with TransactionResponse.ResponseToAuthorisation.Response containing the value
TechnicalError.

Acceptor Agent Acquirer

AcceptorAuthorisationRe
quest

authorisation
AcceptorAuthorisationRe
quest
message couldn’t
be processed
AcceptorRejection
TechnicalError
nse
AcceptorAuthorisationRespo

Figure 41: Rejection of an Authorisation to an Agent

However, when the acquirer returns an AcceptorRejection message with RejectReason set to
UnableToProcess, in case of congestion of the acquirer host, the agent must return an
AcceptorRejection message with the same RejectReason.

- 79 -
Card Payments Message Usage Guide Version 5.0

In the example below, an Agent receives an AcceptorCompletionAdvice message issued by an


Acceptor:
 The Agent performs the completion of the transaction, including the sending of:
 an AcceptorCompletionAdvice to the relevant Acquirer,
 a positive AcceptorCompletionAdviceResponse to the Acceptor without waiting for the
response of the Acquirer.
 The Acquirer cannot process the message and sends an AcceptorRejection message instead
of an AcceptorCompletionAdviceResponse message.
 The Agent receives the rejection message and initiates the message retransmission process
(see section 3.3).
Acceptor Agent Acquirer

AcceptorCompletionAdvice

completion
process

AcceptorCompletionAdvice
esponse
AcceptorCompletionAdviceR message couldn’t
be processed
AcceptorRejection

Figure 42: Rejection of an Completion to an Agent

- 80 -
Card Payments Message Usage Guide Version 5.0

3 Message Functionalities

3.1 Message Organisation

A CAPE message is usually composed of three major functional blocks:


 a Message Header containing information related to the management of the message (routing
and processing)
 a Message Body containing information related to the application processing of the message
 a Security Trailer containing information related to the security aspects of the message
(optional).

3.1.1 Management of the message

Message item Multiplicity


A. Header [1..1]
MessageFunction [1..1]
ProtocolVersion [1..1]
ExchangeIdentification [1..1]
ReTransmissionCounter [0..1]
CreationDateTime [1..1]
+ InitiatingParty [1..1]
+ RecipientParty [0..1]
+ TraceabilityInfo [0..1]

The Header contains primary information required to either route the message to a specific destination
(e.g. an intermediary agent) or to process the message in a specific way (e.g. retransmission, financial
capture, etc.).

The Header is composed of three major categories of information:


 Management information
 Parties involved in the transmission of the message
 Traceability information

- 81 -
Card Payments Message Usage Guide Version 5.0

3.1.1.1 Management information


The Management information regroups data components associated with the routing and/or
processing of the message.

Message Item Mult. Usage


MessageFunction [1..1] Definition: This component identifies the type of process
related to the message.

Usage: Used mainly for routing purposes, namely in cases


where the message relies on some kind of processing (e.g.
message process with financial capture or without financial
capture).
ProtocolVersion [1..1] Definition: This component identifies the version of the
protocol used in the exchange.

Usage: The management of the protocol version is


described in sections 4.2.1 and 4.2.2 of the present
specifications.
ExchangeIdentification Definition: This component provides a unique identification
of the exchange of messages (request/response) for a
specific service.

Usage: This information is structured and used according


to guidelines provided by the Acquirer.
RetransmissionCounter Definition: This component identifies the number of
retransmissions for this message.

Usage: Retransmission is used for


AcceptorCompletionAdvice (caaa.003.001.05) and
AcceptorCancellationAdvice (caaa.007.001.05) messages.
Retransmission of other messages is not allowed.
CreationDateTime Definition: This component identifies the date and time of
the creation of the message. This information is mandatory
and needs to be present in the related message.

- 82 -
Card Payments Message Usage Guide Version 5.0

3.1.1.2 Parties involved in the message

The parties mentioned in the Header are provided with the purpose of facilitating the routing of the
message. The Header is not included when applying security to the message.

MessageItem Mult. Usage


InitiatingParty Definition: Party initiating the exchange. This can either be
the Acceptor or the party that initiates the exchange on
behalf of the Acceptor. This information is not part of the
secured section of the message.

Usage: Validate the origin of the exchange. The role of


InitiatingParty stays unchanged during the whole exchange
of the message (e.g. AcceptorCompletion Advice and
AcceptorCompletion AdviceResponse). The InitiatingParty
must always be present.
RecipientParty Definition: Party recipient of the exchange. This can either
be the Acquirer, or the party that received the exchange on
behalf of the Acquirer. This information is not part of the
secured section of the message.

Usage: Validate the destination of the exchange. The role


of RecipientParty stays unchanged during the whole
exchange of the message (e.g. AcceptorCompletionAdvice
and AcceptorCompletionAdviceResponse). The presence
of RecipientParty is configurable.

- 83 -
Card Payments Message Usage Guide Version 5.0

3.1.1.3 Traceability information

The Traceability information allows a RecipientParty to monitor the upstream transport and process of
a message throughout its lifetime.

In order to ensure an efficient traceability process end-to-end, each intermediary entity is invited to
add its own Traceability information to the incoming message before sending the resulting message to
the next party in the chain.

The value and interest of this process depends on the actual use of this option by all intermediaries in
the message exchange chain.

Traceability provides useful information as regards the processing and transport time for the exchange
of messages. This information can be used to carry out a global analysis of the performance of the
exchanges of messages end-to-end. In case of delays in processing card payment transactions, it can
also be used to identify the possible bottlenecks or problems encountered in the routing or processing
of the message.

This information is conditional and is not part of the secure section of the message.

MessageItem Mult. Usage


RelayIdentification Definition: Party relaying a message. This can be the
Acceptor, the Acquirer or any Intermediary Agent relaying a
message on behalf of the Acceptor or the Acquirer.

Usage: Used essentially to inform parties about the routing


process of the exchange (actual parties involved in the
exchange chain, time spent between agents in the chain,
problems encountered whilst processing or forwarding
messages, etc.). Whilst the use of this message is
conditional - once the relevant party has completed
RelayIdentification - it must further be enriched by all
following parties in the card payment chain.
TraceDateTimeIn Date and time of incoming messages for relaying or
processing
TraceDateTimeOut Date and time of outgoing messages for relaying or
processing

- 84 -
Card Payments Message Usage Guide Version 5.0

3.1.2 ApplicationData

Message item Multiplicity


A. Body [1..1]
+ Environment [1..1]
+ Context [1..1]
+ Transaction [1..1]

The Body of the message contains information related to the processing of the message by an
application.

The data is grouped by functional components such as:


 the environment of the card payment transaction in terms of actors involved (Acquirer,
Merchant, POI, Card, Cardholder),
 the context of the transaction (payment and sale contexts)
 the information related to the card payment transaction itself.

- 85 -
Card Payments Message Usage Guide Version 5.0

3.1.2.1 Environment
The environment functional component contains information related to the main actors involved in or
impacted by a payment transaction.

Actors need to be understood in the present context as either organisations and individuals (Acquirer,
Merchant, Cardholder) or objects (POI, Card).

The InitiatingParty (part of the Header) and Merchant (part of the Body) may be distinct entities.

The InitiatingParty may be an entity (e.g. a Processor) acting on behalf of the Merchant (or the
Acquirer) to ensure the routing and processing of the message, whilst the Merchant and the Acquirer
are entities involved in a commercial relationship associated with the actual provisioning of a card
payment transaction to a Cardholder.

Message Item Mult. Usage


Acquirer [1..1] Definition: A party in a contractual relation with Merchants
and Card schemes accepting payments. The Acquirer makes
payments to the Merchant based on data received from the
Acceptor.

Usage: An Acquirer acquires card payment data from an


Acceptor and forwards the data to the relevant Card Issuer.
Merchant [1..1] Definition: A party providing goods and/or services at a sales
location (physical or virtual). The Merchant signs an acquiring
agreement with an Acquirer. The Merchant can perform the
role of Acceptor or delegate it to another party.
POI Definition: A Point of Interaction defines the entry point of a
card into a payment system to accept payment and loyalty
cards at a sales location. It is a general term used to include
all situations where payment details may be entered (e.g.
petrol pump, merchant checkout, internet, mail order,
telephone order, etc.).

Usage: The identification of the POI is usually allocated by a


Merchant, an Acceptor, an Intermediary Agent or an Acquirer.
Card Definition: A physical or virtual device to enable a payment
and to identify a Cardholder account.

Usage: The card is usually identified by its PAN and may be


additionally qualified by a card sequence number.
Cardholder Definition: A person presenting a Card or card information to
a Merchant for the purchase of goods and services.

Usage: This item contains data elements used to identify and


authenticate the cardholder.

- 86 -
Card Payments Message Usage Guide Version 5.0

3.1.2.2 Context

Context describes the two main types of contexts associated to a card payment transaction: a sale
context (SaleContext) that identifies elements related to the commercial aspects of the transaction
exclusively and a payment context (PaymentContext) which provides the elements of information for
the payment associated with the sale transaction.

Message Item Mult. Usage


PaymentContext [1..1] Definition: This component identifies the elements of the
sales environment for payment.
SaleContext [0..1] Definition: This component contains elements that identify
the sale within the sales environment.

3.1.2.3 Transaction

This functional block contains all the information related to a card payment for which an authorisation
or another type of operation is required.

Message Item Mult. Usage


Transaction [1..1] Definition: This component contains the transaction specific
application data.
Product Definition: This component identifies the class of goods
and/or services.

- 87 -
Card Payments Message Usage Guide Version 5.0

3.1.3 SecurityTrailer

Message item Multiplicity


A. SecurityTrailer [0..1]
ContentType [1..1]
+ AuthenticatedData [0..*]

The SecurityTrailer building block is conditional. It contains a message authentication code computed
on the body of the message with a cryptographic key. It allows the authentication of the Initiator and
protects the content of the body against any unauthorised alteration of the message.

Message Item Mult. Usage


ContentType [1..1] Definition: This component identifies the type of security
used for the message (authentication).
AuthenticatedData [0..*] Definition: This component contains the Message
Authentication Code (MAC) for the message body with the
required information to check it.

- 88 -
Card Payments Message Usage Guide Version 5.0

3.2 Traceability
3.2.1 Security level
No security is required for traceability data. Traceability is not included in data elements taken into
account for the computation of the MAC.

3.2.2 Usage Condition


The presence of Traceability is configurable. When Traceability is configured as required, traces must
be present on the following messages: AcceptorAuthorisationRequest, AcceptorCompletionAdvice,
AcceptorCancellationRequest and AcceptorCancellationAdvice.

3.2.3 Traceability in an exchange


The path of traceability goes from the Acceptor back to the Acceptor and includes all intermediate
steps. In other terms, it means that when the Acceptor receives the response, the whole traceability of
the Acceptor to Acquirer domain is in the header.
For the entity which initiates the transaction, the value of “TraceDateTimeIn” and the value of
“TraceDateTimeOut” are the same.

An intermediary agent and the acquirer must populate Traceability if a previous entity has populated it;
The recipient must update Traceability when a message is received containing trace information by
adding a new trace entry with TraceTimeIn set to the time the recipient received the new message and
TraceDateTimeOut set to the time the recipient sent the message to the next party.

- 89 -
Card Payments Message Usage Guide Version 5.0

Acceptor Agent Acquirer

AcceptorAuthorisationRequest
AcceptorAuthorisationRequest
InitiatingParty RecipientParty
Identification: poi1 Identification: ia1 InitiatingParty RecipientParty
RelayIdentification Identification: ia2 Identification: acq1
Identification: poi1 RelayIdentification
TraceDateTimeIn: 2011:07:05T11:21:17.45+0200 Identification: poi1
TraceDateTimeOut: 2011:07:05T11:21:17.45+0200 TraceDateTimeIn: 2011:07:05T11:21:17.45+0200
TraceDateTimeOut: 2011:07:05T11:21:17.45+0200
RelayIdentification
Identification: ia2
TraceDateTimeIn: 2011:07:05T11:21:16.89+0200
TraceDateTimeOut: 2011:07:05T11:21:16.91+0200

AcceptorAuthorisationResponse
InitiatingParty RecipientParty
Identification: ia2 Identification: acq1
RelayIdentification
Identification: poi1
TraceDateTimeIn: 2011:07:05T11:21:17.45+0200
TraceDateTimeOut: 2011:07:05T11:21:17.45+0200
RelayIdentification
Identification: ia2
TraceDateTimeIn: 2011:07:05T11:21:16.89+0200
TraceDateTimeOut: 2011:07:05T11:21:16.91+0200
RelayIdentification
Identification: acq1
TraceDateTimeIn: 2011:07:05T11:21:18.25+0200
TraceDateTimeOut: 2011:07:05T11:21:19.53+0200
AcceptorAuthorisationResponse
InitiatingParty RecipientParty
Identification: poi1 Identification: ia1
RelayIdentification
Identification: poi1
TraceDateTimeIn: 2011:07:05T11:21:17.45+0200
TraceDateTimeOut: 2011:07:05T11:21:17.45+0200
RelayIdentification
Identification: ia2
TraceDateTimeIn: 2011:07:05T11:21:16.89+0200
TraceDateTimeOut: 2011:07:05T11:21:16.91+0200
RelayIdentification
Identification: acq1
TraceDateTimeIn: 2011:07:05T11:21:18.25+0200
TraceDateTimeOut: 2011:07:05T11:21:19.53+0200
RelayIdentification
Identification: ia1
TraceDateTimeIn: 2011:07:05T11:21:18.57+0200
TraceDateTimeOut: 2011:07:05T11:21:18.64+0200

Figure 43: Example of Traceability with an Intermediary Agent

- 90 -
Card Payments Message Usage Guide Version 5.0

3.3 Message Retransmission

An Acceptor retransmits a message when no response was received to an advice message sent to an
Acquirer.

Retransmission is used for AcceptorCompletionAdvice (caaa.003.001.05) and


AcceptorCancellationAdvice (caaa.007.001.05) messages only. Retransmission of other messages is
not allowed.

The purpose of retransmission is to ensure that an Acquirer has received and processed such
messages. The Acceptor initiates a retransmission process if the response to an advice is not
received.

A repeated advice message holds an unchanged copy of the message body which was originally sent.
RetransmissionCounter and CreationDateTime are the only data element which are modified in the
Header for each retransmission. In particular, the ExchangeIdentification has the same value for all
retransmissions of the same message. For DUKPT key management, because of the key evolution,
the Acceptor may have to recompute the MAC to be able to verify the MAC of the response.

3.3.1 Acceptor Behaviour


The RetransmissionCounter is absent from the first transmission of the advice message, or has a
value of 0. This component is present in every repeated advice message, with a value of 1 for the first
repetition, and incremented by 1 for each new repetition.

The number of message retransmissions must be limited, according to the configuration of the POI.
The protocol does not address potential errors that may arise when the limit of retransmissions is
reached.
Acceptor Acquirer

RetransmissionCounter:0 Advice

RetransmissionCounter:0
AdviceResponse

AdviceResponse not received


Advice is repeated
RetransmissionCounter:1 Advice

RetransmissionCounter:1
AdviceResponse
AdviceResponse received
End of retransmissions

Figure 44: Retransmission of an Advice by the Acceptor

The Acceptor stops the retransmission process upon receipt of a correct AdviceResponse message.
The value of RetransmissionCounter has no impact on the acceptance of the Advice Response
message.

- 91 -
Card Payments Message Usage Guide Version 5.0

3.3.1.1 Late Responses to an Advice message


In the example below, a response to an advice message seems to be lost, since received late.

The Acceptor retransmits the advice message to the Acquirer (RetransmissionCounter set to 1).

The Acceptor initiates a second retransmission of the advice message (RetransmissionCounter value
of 2) before a response to the first retransmitted advice message was received from the Acquirer.

The receipt of the first advice response (RetransmissionCounter value of 1) by the Acceptor stops any
further retransmission of the message.

The receipt of the second advice response (RetransmissionCounter value of 2) by the Acceptor is
simply ignored by the same party.
Acceptor Acquirer

Advice

AdviceResponse

AdviceResponse not received


Advice is repeated
RetransmissionCounter:1 Advice

RetransmissionCounter:1
AdviceResponse not received, o nse
esp
new repetition eR
vic
RetransmissionCounter:2 Advice Ad

1st repetition of AdviceResponse RetransmissionCounter:2


nse
received, end of retransmissions spo
Re
v ice
Ad

2nd repetition of
AdviceResponse is ignored

Figure 45: Late Responses to an Advice message

- 92 -
Card Payments Message Usage Guide Version 5.0

3.3.1.2 Unordered Responses to Retransmitted Advice messages


In some circumstances, AdviceResponse messages may be received in a different order from that in
which they were sent. In the example below, the response to a second retransmission is received by
the Acceptor before receiving a response to the first retransmission.

The response to the second retransmission (RetransmissionCounter value of 2) terminates the


retransmission process and the Acceptor ignores the response to the first repetition
(RetransmissionCounter value of 1).
Acceptor Acquirer

Advice

AdviceResponse

AdviceResponse not received


Advice is repeated
RetransmissionCounter:1 Advice

RetransmissionCounter:1
AdviceResponse not received,
se
new repetition
pon
es
eR

RetransmissionCounter:2 Advice
ic
dv
A

RetransmissionCounter:2
2nd repetition of AdviceResponse
received, end of retransmissions AdviceResponse

1st repetition of
AdviceResponse is ignored

Figure 46: Unordered Responses to Retransmitted Advice messages

- 93 -
Card Payments Message Usage Guide Version 5.0

3.3.2 Acquirer Behaviour

An advice message with RetransmissionCounter set to 0 or absent means that the received message
was an original one (e.g. not retransmitted).

For each advice message received, the Acquirer sends back a response message to the Acceptor
containing a copy of the RetransmissionCounter value.
It is required for the Acquirer to send an advice response to every retransmissions of an advice.
Acceptor Acquirer

RetransmissionCounter:0 Advice
Process Advice,
send the AdviceResponse
RetransmissionCounter:0
AdviceResponse

RetransmissionCounter:1 Advice
Send the same AdviceResponse with
a copy of RetransmissionCounter
RetransmissionCounter:1
AdviceResponse

Figure 47: Retransmission of an AdviceResponse by the Acquirer

Since the original advice might never reach the Acquirer (due to a problem of communication, for
instance), the retransmitted message received by the Acquirer (RetransmissionCounter set to 1) has
to be considered as the original one and processed as such.
Acceptor Acquirer

Advice

RetransmissionCounter:1 Advice
Process Advice,
send the AdviceResponse
RetransmissionCounter:1
AdviceResponse

RetransmissionCounter:2 Advice
Send the same AdviceResponse with
a copy of RetransmissionCounter
RetransmissionCounter:2
AdviceResponse

Figure 48: Non-Receipt of an Advice by the Acquirer

- 94 -
Card Payments Message Usage Guide Version 5.0

Similarly, advice retransmissions are not necessarily received by the Acquirer in the order adopted by
the Acceptor.

- 95 -
Card Payments Message Usage Guide Version 5.0

3.4 Error Handling


This section presents the errors related to an exchange of messages which occurs at a protocol level
as:
 The format of the message, including the security,
 The identification of the parties involved,
 The management of messages, including version management, linking a request with its
response, and message duplication,
 The communication between the sender and the receiver of a message, including the absence
of a response.

3.4.1 Error Cases


Error cases, summarised in the figure below, are presented in the order the messages are processed
by the parties during the exchange.
Acceptor Acquirer

Unable to send the message (3.4.4.1)


send the message Request or Unacceptable message (3.4.1.2)
Advice Or DuplicateMessage (3.4.1.8)

Unable to process the message (3.4.1.3)


wait for the response

process the message

Unable to send the message (3.4.1.4)


Response not received (3.4.1.5)
receive the response Response or send the response
AdviceResponse
Unacceptable message (3.4.1.6)
Or DuplicateMessage (3.4.1.8)

Unable to process the response (3.4.1.7)


process the response

Figure 49: Error Cases in Message Exchange

3.4.1.1 Acceptor is Unable to Send a Message


An Acceptor is unable to send a request or an advice, and is aware that the Acquirer did not receive
the complete message. This error occurs when:
a) No open transport connection is available, and no transport connection to the Acquirer host could
be opened, after reaching a maximum number of retries, or
b) The sending of the complete message has failed for some reason reported by the transport layer.

- 96 -
Card Payments Message Usage Guide Version 5.0

3.4.1.2 Acquirer Receives an Unacceptable Message


The message received by the Acquirer is not an acceptable message for one or several of the
following reasons:

a) The envelope of the received message is invalid:


 The tag of the XML root element is not Document,
 The root element contains more than one (child) element,
 The root element is empty and does not contain any element,
 The tag of the unique root child is not one of the following values: AccptrAuthstnReq,
AccptrCmpltnAdvc, AccptrCxlReq, AccptrCxlAdvc, AccptrRcncltnReq, AccptrBtchTrf,
AccptrDgnstcReq, or AccptrCcyConvsReq.

b) The message cannot be decoded properly:


 The size of the message exceeds the maximum size the Acquirer is able to handle.
 The XML parser generates a parsing error. For instance, the message is not a well formed
XML document, element that contains other elements has a non-empty content, elements
contain mixed content, or the message contains unexpected entities as DTD or Processing
Instructions.
 The XML version of the document is neither 1.0 nor 1.1,
 The character encoding is defined either in the XML prolog or in a byte order mark (BOM), but
not as UTF-8 or EF BB BF respectively (the usage of a BOM for the messages is not
recommended).
 The document contains invalid UTF-8 characters.
 The root element Document has no default XML Namespace declaration, or the name of the
Namespace is incorrect, or the name of the Namespace is inconsistent with the single child of
the root element (i.e. is different from urn:iso:std:iso:20022:tech:xsd:caaa.001.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.003.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.005.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.007.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.009.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.013.001.05, and for
urn:iso:std:iso:20022:tech:xsd:caaa.016.001.03, respectively AccptrAuthstnReq,
AccptrCmpltnAdvc, AccptrCxlReq, AccptrCxlAdvc, AccptrRcncltnReq,
AccptrDgnstcReq andAccptrCcyConvsReq).
 The sequence of elements defined in the schema for the message is not respected. The
sequence of optional elements in a data structure must respect the sequence of elements
defined in the XML/Schema (e.g. In the InitiatingParty, the data element Type cannot be after
Issuer).
 A mandatory data structure, a mandatory data element is absent or a data element configured
as "Mandatory" is absent (e.g. Header.ExchangeIdentification is absent).
 A data element has not a valid value for the type defined in the schema. For instance, a
numeric data containing non numeric characters.
 The value of a data element is not belonging to the set of enumerated values defined in the
schema or is not allowed (see section 4 Messages and Usage).
 The size of the value exceeds the maximum size defined in the schema.
 Inconsistency between data elements (e.g. Header.MessageFunction value inconsistent with
the body of the message).
 A rule or a condition of presence defined in the section 4 is not respected (e.g.
Response=Approved and an Action with ActionType=Referral in the
AcceptorAuthorisationResponse message).

- 97 -
Card Payments Message Usage Guide Version 5.0

If an optional data element that is not expected but present in the message itmust be ignored, and the
message is not rejected.

If a data element or a data structure is not known by the receiver of the message (i.e. not present in
the enclosing data structure definition), this data element is ignored (the schema validation of the XML
message is not required).

c) The version of the protocol used for the message (Header.ProtocolVersion) is not supported by the
RecipientParty.

d) The verification of the security of the message fails:


 A cryptographic key identification is invalid (including the Key Serial Number identification part
of a DUKPT key),
 The cryptographic key has expired,
 The computed MAC does not match the MAC value sent in the message,
 The decrypted data is inconsistent (e.g. wrong format or invalid content).

e) The identification of the sender (Header.InitiatingParty) or the receiver (Header.RecipientParty) of


the message is invalid.

f) The message is a duplicated message for a a given InitiatingParty and a given RecipientParty
when the following fields have the same value:

 Header.ExchangeIdentification
 CreationDateTime
 Header.RetransmissionCounter if present.

3.4.1.3 Acquirer is Unable to Process the Message


The message received by the RecipientParty cannot be performed for one of the following reasons:

a) The type of message (Header.MessageFunction) is not supported by the RecipientParty, which is


not able to process the message and send a response message to the InitiatingParty.

b) The RecipientParty is not able to process the message for lack of resources (e.g. congestion of
server, HSM unavailable). For that reason, a message response could not be built and the
message is not processed.

3.4.1.4 Acquirer is Unable to Send a Message


The Acquirer is unable to send a response to a request or an advice, and is sure that the complete
message has not been received by the Acceptor. The error occurs when the transport connection
previously open by the Acceptor to send the request or the advice, has been broken or released
before the sending of the complete response message.

- 98 -
Card Payments Message Usage Guide Version 5.0

3.4.1.5 Acceptor has not Received a Response Message


No response to a request or an advice message has been received by the Acceptor, resulting from
one of the following reasons:

a) The transport connection used to send the request or advice has been released or broken, and the
Acquirer is then unable to send the response messsage.

b) The timer monitoring the receipt of the response message has expired before the receipt of the
complete response message.

3.4.1.6 Acceptor Receives an Unacceptable Message


The message received by the Acceptor is not an acceptable message for one or several of the
following reasons:

a) The envelope of the received message is incorrect:


 The tag of the XML root element is not Document,
 The root element contains more than one (child) element,
 The root element does not contain any element,
 The tag of the unique root child is not one of the following values: AccptrAuthstnRspn,
AccptrCmpltnAdvcRspn, AccptrCxlRspn, AccptrCxlAdvcRspn, AccptrCcncltnRspn,
AccptrBtchTrfRspn, AccptrDgnstcRspn, or AccptrRjctn.

b) The message cannot be decoded properly:


 The size of the message exceeds the maximum size the Acceptor is able to handle.
 The XML parser generates a parsing error. For instance, the message is not a well formed
XML document, element that contains other elements has a non-empty content, elements
contain mixed content, or the message contains unexpected entities as DTD or Processing
Instructions.
 The XML version of the document is neither 1.0, 1.1 nor 2.0,
 The character encoding is defined either in the XML prolog or in a byte order mark (BOM), but
not as UTF-8 or EF BB BF respectively (the usage of a BOM for the messages is not
recommended).
 The document contains invalid UTF-8 charaters.
 The root element Document has no default XML Namespace declaration, or the name of the
Namespace is incorrect, or the name of the Namespace is inconsistent with the single child of
the root element (i.e. is different from urn:iso:std:iso:20022:tech:xsd:caaa.002.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.004.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.006.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.008.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.010.001.05,
urn:iso:std:iso:20022:tech:xsd:caaa.014.001.05, and
urn:iso:std:iso:20022:tech:xsd:caaa.015.001.05, for respectively
AccptrAuthstnRspn, AccptrCmpltnAdvcRspn, AccptrCxlRspn, AccptrCxlAdvcRspn,
AccptrCcncltnRspn, AccptrDgnstcRspn, and AccptrRjctn).
 The sequence of elements defined in the schema for the message is not respected (e.g.
Header.InitiatingParty appears before Header.MessageFunction).

- 99 -
Card Payments Message Usage Guide Version 5.0

 A mandatory data structure or a mandatory data element is absent (e.g.


Header.ExchangeIdentification is absent).
 A data element has not a valid value for the type defined in the schema. For instance, a
numeric data containing non numeric characters.
 The value of a data element is not belonging to the set of enumerated values defined in the
schema or is not allowed (see section 4 Messages and Usage).
 The size of the value exceeds the maximum size defined in the schema.
 Inconsistency between data elements (e.g. Header.MessageFunction value inconsistent with
the body of the message).
 A rule or a condition of presence defined in the section 4 is not respected (e.g.
ProtectedCardData and PlainCardData both present in the AcceptorAuthorisationResponse
message).
 A data element in a Response message (resp. AdviceResponse message) is specified as
"Copy", and has not the same value as in the related Request message (resp. Advice
message).

If a data element or data structure is not known by the receiver of the message, this data element is
ignored (the schema validation of the XML message is not required).

c) The verification of the security of the rejected message fails:


 A cryptographic key identification is invalid (including the Key Serial Number identification part
of a DUKPT key), or is not the same than in the request,
 The cryptographic key has expired,
 The computed MAC does not match the MAC value sent in the message,
 The decrypted data is inconsistent (e.g. wrong format or invalid content).

3.4.1.7 Acceptor is Unable to Process the Response Message


The response message received by the Acceptor cannot be processed for one of the following
reasons:

a) The message cannot be considered as a response to the request or the advice:


 Message identification (Header.ExchangeIdentification, Header.InitiatingParty,
Header.RecipientParty) does not have the same value as the request or the advice.
 If the response is not an AcceptorRejection, the message types (Header.MessageFunction or
the message body) is not related to the request or the advice (e.g.
MessageFunction=FinancialAuthorisationRequest in the request message and
MessageFunction=AuthorisationResponse in the response message, or the message body
AuthorisationRequest is in the request message and CancellationResponse in the response
message).
 A data element specified as to be copied from the request or the advice has not the same
value (e.g. Transaction.TransactionIdentification.TransactionDateTime or
Transaction.TransactionIdentification.TransactionReference)

b) The message received is an AcceptorRejection related to the request or the advice.

c) The response message is received too late, i.e. after the expiration of the time out, or just after the
transport connection release.

- 100 -
Card Payments Message Usage Guide Version 5.0

3.4.1.8 Acquirer or Acceptor has received a Duplicate Message.

Regardless of the root cause, the message received by the RecipientParty has already been received.
See duplicate message definition below.
In that case, the RejectReason is set to DuplicateMessage

3.4.2 Acceptor Error Handling

Errors handling of the Acceptor follow the process below:


1) Error case detection, as described in the previous section (see 3.4.1 Error Cases).
2) Error processing at a protocol level, depending on the type of exchange.
3) Continue to process the exchange or
4) Terminate the exchange and notify the error to the application.

Following sections describe each type of error handling of the Acceptor and the conditions under
which this handling has to be performed. The diagram below summarises for each error case defined
in the section 3.4.1, the error handling per message the Acquirer must perform.

Acceptor

Unable to process
No response
Unacceptable unmatched response Unable to send
Unacceptable matched response
Too late response
DuplicateMessage

AuthorisationRequest CompletionAdvice Reconciliation All messages All messages


CancellationRequest CancellationAdvice Diagnostic

1 2 3 4 3
Reverse the Terminate Terminate
Retransmission Ignore
Transaction Exchange Exchange

Send Retransmit Terminate No action Terminate


CompletionAdvice CompletionAdvice exchange in error exchange in error
CancellationAdvice CancellationAdvice
with Reversal flag

Terminate
exchange in error

Figure 50: Acceptor Error Handling in a Message Exchange

- 101 -
Card Payments Message Usage Guide Version 5.0

3.4.2.1 Reverse the Transaction

3.4.2.1.1 Conditions
This process is executed by the Acceptor after sending an AcceptorAuthorisationRequest or an
AcceptorCancellationRequest for the following error situations:
 The Acceptor has not received a response message (see section 3.4.1.5).
 The message is not an acceptable response (see section 3.4.1.6), and match a request in
progress.
 The Acceptor is unable to process the response message (see section 3.4.1.7 a) and b)), and
matches a request in progress.

3.4.2.1.2 Action
The Acceptor sends an AcceptorCompletionAdvice or an AcceptorCancellationAdvice to reverse the
respectively the AcceptorAuthorisationRequest and the AcceptorCancellationRequest (setting
Transaction.Revesal to the value True), and notifies the application of the failure of the exchange.

3.4.2.2 Retransmission of the Advice

3.4.2.2.1 Conditions
This process is executed by the Acceptor after sending an AcceptorCompletionAdvice message or an
AcceptorCancellationAdvice message for the following error situations:
 The Acceptor has not received a response message (see section 3.4.1.5).
 The message is not an acceptable response (see section 3.4.1.6), and matches an advice in
progress.
 The Acceptor is unable to process the response message (see section 3.4.1.7 a) and b)), and
matches an advice in progress.

3.4.2.2.2 Action
The Acceptor retransmits the AcceptorCompletionAdvice or the AcceptorCancellationAdvice message
in accordance to the section 3.3.1 Message Retransmission.

- 102 -
Card Payments Message Usage Guide Version 5.0

3.4.2.3 Terminate the Exchange in Progress

3.4.2.3.1 Conditions
Whatever the type of exchange, this process is executed for the following error situations:
 The Acceptor is unable to send a request or an advice message (see section 3.4.1.1).

This process is also executed after sending an AcceptorReconciliationRequest or an


AcceptorDiagnosticRequest message for the following error cases:
 The Acceptor has not received a response message (see section 3.4.1.5).
 The message is not an acceptable response (see section 3.4.1.6), and matches a request in
progress.
 The Acceptor is unable to process the response message (see section 3.4.1.7 a) and b)), and
matches an advice in progress.

3.4.2.3.2 Action
The Acceptor terminates the exchange in progress, and notifies the application of the failure of the
exchange (e.g. unable to go online).

3.4.2.4 Ignore the Error

3.4.2.4.1 Conditions
Whatever the type of exchange, this process is executed for the following circumstances:
 The message is not an acceptable response (see section 3.4.1.6), and could not be linked to
the request or the advice in progress (unmatched response).
 The Acceptor is unable to process the response message (see section 3.4.1.7 a) and b)), and
could not be linked to the request or the advice in progress (unmatched response).
 The response message arrives too late (see section 3.4.1.7 c) ).

3.4.2.4.2 Action
The Acceptor does not take any action, including any termination of exchange in progress.

- 103 -
Card Payments Message Usage Guide Version 5.0

3.4.3 Acquirer Error Handling

Errors handling of the Acquirer follow the process below:


1) Error case detection, as described in the section 3.4.1 Error Cases.
2) Error processing at a protocol level, depending on the type of exchange.
3) Complete the exchange sending the appropriate response or
4) Terminate the exchange and notify the error to the application.

Following sections describe each type of error handling of the Acquirer and the conditions under which
this process has to be performed.
Acquirer

Unacceptable message Retransmission of an Advice Unable to send


Unable to process the message
Message duplicated

All messages CompletionAdvice All messages


CancellationAdvice

1 2 3
Message
Retransmission Ignore
Rejection

Send an Retransmit No action,


AcceptorRejection AdviceResponse exchange completed

Figure 51: Acquirer Error Handling in a Message Exchange

3.4.3.1 Message Rejection

3.4.3.1.1 Conditions
Whatever the type of request or advice message, this error handling process is executed for the
following error cases:
 The Acquirer receives an unacceptable message (see section 3.4.1.2),
 The Acquirer is unable to process the message (see section 3.4.1.3),
 The Acquirer receives a duplicated message (see section 3.4.1.8).

3.4.3.1.2 Action
The Acquirer sends an AcceptorRejection message with the appropriate content, including the
RejectReason value related to the type of error (see section 2.8 Reject Message).

3.4.3.2 Retransmission of the Response

3.4.3.2.1 Conditions

- 104 -
Card Payments Message Usage Guide Version 5.0

This process is executed when the Acceptor retransmits an AcceptorCompletionAdvice message or


an AcceptorCancellationAdvice message (see section 3.3).

3.4.3.2.2 Action
The Acquirer sends an advice response in accordance to the section 3.3.2 Message Retransmission.

3.4.3.3 Ignore the Error

3.4.3.3.1 Conditions
Whatever the type of request or advice message, this process is executed for the following error case:
 The Acquirer is Unable to Send a Message (see section 3.4.1.4),

3.4.3.3.2 Action
The Acquirer does not take any action.

- 105 -
Card Payments Message Usage Guide Version 5.0

4 Messages and Usage


This chapter explains the usage, rules and conditions of presence for all data elements involved in
normal payment transactions, and complements the Message Definition Report on the usage of
message elements.

4.1 Configuration Parameters/ Condition of Presence


The "Rule" column contains the condition of presence for optional data elements, or some values for
mandatory data elements. Those rules have been grouped in following classes:
 Config: the condition of presence and possibly the value of a component in the message
depend on a configuration parameter of the Initiator of the message (e.g. the merchant
common name – CommonName). The value may depend on the Recipient and/or the
Acquirer of the transaction.
 Appli: the condition of presence of a component of the protocol depends on the payment
application exclusively (e.g. the PIN – CardholderOnlinePIN).
 Copy : the value of the mandatory component or element is copied from a related message
(e.g. the message exchange identification in the message response header –
ExchangeIdentification – contains a copy of that in the request header)
 CCopy: this condition is specific to Advice message. The condition of presence and the value
of a component of the Advice message complies to the following rules in that order:
 In the case of presence of this component in the Authorisation Response message, the
value of the component is copied from the Authorisation Response message ;
 Or in case of presence of this component in the Authorisation Request message, the
value of the component is copied from the Authorisation Request message ;
 Or when no authorisation exchange preceeded the completion one, the condition
associated with the component of the authorisation applies also to the Completion
Advice message.

The "Usage" column may contain some information about the condition of presence of an optional
element:
 Default: a default value is associated with the component of the message. The absence of the
component produces the same result as the presence of the component with the default value
(e.g. the message item Environment.Acquirer.Identification.Type has the comment "default
Acquirer" at the beginning of the Rule column, meaning that an absent Acquirer.Identification
is to having the value "Acquirer").
 Message-related: the condition of presence of a component of the protocol depends on the
presence or value of another component in a related message. This kind of condition is also
expressed at the beginning of the "Usage" column (e.g. the encrypted alternative of the
sensitive card data – ProtectedCardData – is present if the following condition is satisfied "if
Card.PlainCardData absent").

The “Constraint” (Cstr) column contains information about conditional presence or interdependency
between elements of the message:
 ‘*’: if a constraint exists directly on the presence or the value of an element (mark by a star ‘*’)
 ‘C<number>’: if a constraint exists due to interdependency of elements of the messages (e.g
data element A must be present if data element B equals X). In this latter case the constraint
is labelled as ‘C’ plus a number. These constraints may serve for semantic analysis.

- 106 -
Card Payments Message Usage Guide Version 5.0

4.2 Authorisation Messages

4.2.1 AcceptorAuthorisationRequest (caaa.001.001.05)

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


Header [1..1] It conveys information related to the protocol management on a
segment of the path from the Acceptor to the Acquirer:
MessageFunction [1..1] C1 The only valid codes to request an authorisation for a normal
C13 payment are:
AuthorisationRequest: Request without financial capture
(TransactionCapture="False")
FinancialAuthorisationRequest: Request with financial
capture TransactionCapture="True")
(if an invalid value is received, a Reject message is sent by the
Recipient with RejectReason equal to "ParsingError")
ProtocolVersion [1..1] * The current version is 5.0 (reference list of specification
documents).
ExchangeIdentification [1..1] Identifier per InitiatingParty/RecipientParty and per pair of
messages used to assign a response to a request and to
identify duplicate messages.
It may be used in combination with CreationDateTime to allow
the Recipient to identify retransmissions.
It may be a cyclic counter that increments by one with each new
message, starting at 0.
CreationDateTime [1..1] Date and time of the creation of the message Time accuracy
has to be at least tenth of a second.
InitiatingParty [1..1] Information used to identify the initiator of an exchange. The
content is bilaterally agreed between InitiatingParty and
RecipientParty.
Identification [1..1] Config The value of this identifier is bilaterally agreed between
InitiatingParty and RecipientParty. The Recipient of the
message must validate without ambiguity the Initiator of the
message.
Type [0..1] Config * Indicates the type of InitiatingParty, allowed values:
OriginatingPOI: from POI Terminal to an Intermediary Agent
or an Acquirer.
IntermediaryAgent: from an Intermediary Agent to another
Intermediary Agent or an Acquirer.
Acceptor: from a POI server performing functions of the
payment application.
Issuer [0..1] Config Indicates the assigner of the Identification value of the
InitiatingParty.
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Config Information used to identify the recipient of an exchange. The
structure and content is bilaterally agreed between
InitiatingParty and RecipientParty.
Identification [1..1] Config
Type [0..1] Config * Indicates the type of RecipientParty, allowed values:
IntermediaryAgent: from POI System or an Intermediary
Agent to an Intermediary Agent.
Acquirer: from POI System or an Intermediary Agent to an
Acquirer.
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]

- 107 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
[0..*]
ServerCertificateIdentifier
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Config see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
AuthorisationRequest [1..1] C1 The Header.MessageFunction must be "AuthorisationRequest"
or "FinancialAuthorisationRequest".
(In case of an invalid value, a Reject message is sent by the
Recipient with RejectReason equal to "ParsingError")
Environment [1..1]
Acquirer [0..1] Config Acquirer configuration parameter defines if this component
needs to be present.
Identification [0..1] Config
Identification [1..1] Appli Identification of the Acquirer or the Intermediary Agent
determined by the application from the card and other data
used in this transaction.
Type [0..1] Appli * default Acquirer
Allowed values: Acquirer, IntermediaryAgent
Issuer [0..1] * Allowed values: Acquirer and IntermediaryAgent
Country [0..1] Country of the Acquirer (must be ISO 3166-1 alpha-2 or alpha-
3)
ShortName [0..1] Name of the Acquirer or Intermediary Agent (e.g. name of the
bank or the processor)
ParametersVersion [1..1] This value can be used by the Acquirer or the Intermediary
Agent to:
- decline the request if the configuration parameters are
obsolete,
- checks if a request to the POI to initiate an update of its
configuration parameters (populating TMSTrigger in the
response) is necessary.
This element may be filled with a configuration parameter
(DataSet.Identification.Version of the TMS data set of the
AcceptorConfigurationUpdate message)
Merchant [0..1] C2 Present if it contains any data.
Identification [0..1] Config
Identification [1..1] Appli Identification of the Merchant determined by the application
profile.
Type [0..1] Appli * default Merchant
Allowed values: Merchant, Acceptor, IntermediaryAgent
Merchant may be used to mention the retailer headquarters
name and/or details
Acceptor is used to identify the actual POI entity processing the
transaction (e.g. a subsidiary of the Merchant)

- 108 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


Issuer [0..1] Config * The party assigning the identification.
Allowed values: Acquirer and IntermediaryAgent
ShortName [0..1] Config Name of the merchant assigned by the Acquirer or
IntermediaryAgent.
CommonName [0..1] Config Name of the merchant as appearing on the receipt.
LocationCategory [0..1] Config Code usually derived from the merchant contract. Indicates the
type of location where the transaction took place (e.g. train, in-
flight, nomadic, etc.).
LocationAndContact [0..1] Config
PostalAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
[0..2]
CountrySubDivision
Country [1..1]
Email [0..1]
URLAddress [0..1]
Phone [0..1]
CustomerService [0..1]
[0..1]
AdditionalContactInformation
SchemeData [0..1] Config
POI [1..1]
Identification [1..1] Identification of a POI terminal or system.
Identification [1..1] Appli Part of the Acquirer/IntermediaryAgent or Merchant
configuration.
Type [0..1] * default OriginatingPOI
Allowed values: OriginatingPOI, IntermediaryAgent
Issuer [0..1] Config * Allowed values: Merchant, Acquirer and IntermediaryAgent
ShortName [0..1] Config
SystemName [0..1] Config Allows a fast identification of the POI type by the Acquirer to
monitor the transaction.
GroupIdentification [0..1] Config This identifier can be used as a way for a merchant to group a
set of POI transactions for reconciliation.
Capabilities [0..1] C3 Present if it contains any data.
[0..*] Config Capabilities available to the payment application.
CardReadingCapabilities
[0..*] Config Capabilities available to the payment application.
CardholderVerific
ationCapabilities
[0..1]
PINLengthCapabil
ities
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1] Config Indicates whether the POI authorises transactions exclusively
offline (OffLine), exclusively online (OnLine) or only authorises
online if required by the payment application (Semi OffLine).
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]

- 109 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


NumberOfLines [0..1]
LineWidth [0..1]
[0..*]
AvailableLanguage
TimeZone [0..1] Time zone name as defined by IANA (Internet Assigned
Numbers Authority) in the time zone data base.
America/Chicago or Europe/Paris are examples of time zone
names.
TerminalIntegration [0..1] Indicates the type of integration of the POI terminal in the sale
environment.

INDR Indoor Indoor terminal.


IPMP Inside Pump Terminal incorporated in the
pump dispensing petrol.
MPOI Multiple POITerminal Multiple terminals linked
to a unique sale terminal.
MPMP MultiplePump Outdoor terminal serving several petrol
pumps.
MSLE MultipleSale Terminal Terminal serving multiple
sale terminals.
SSLE Single SaleTerminal Terminal linked to a
unique sale terminal.
VNDG VendingMachine Terminal integrated in a vending
machine
Component [0..*] Config / Information used by the Acquirer for :
Appli  The traceability of components used for the transaction.
 Identifying the version of the component (this information
may cause the TMSTrigger to be set in the response).
 The approval of POI components.
Type [1..1] * Components to be sent in the online authorisation are
configured locally or by TMS configuration.

Identification [1..1] Identification of the component.


ItemNumber [0..1]
[0..1] Identifies the provider of the component class (it replaces the
ProviderIdentification data element ManufacturerIdentification of version 1).
Identification [0..1] Identification of the component assigned by the provider (it
replaces the data element Model of version 1).
SerialNumber [0..1] Serial number of the component if available.
Status [0..1] Actual status of the component.
VersionNumber [0..1] Current version of component that may include the release
number.
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*] Identification of the standard for which the component complies
with.
Identification [1..1] Identification of the standard.
Version [1..1] Version of the standard.
Issuer [1..1] Entity assigning the identification
Characteristics [0..1] Only used in TMS protocol.
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]

- 110 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


[1..1]
Communicat
ionType
RemoteParty [1..*]
Active [1..1]
SecurityAccess- [0..1]
Modules
Subscriber- [0..1]
Identity-
Modules
KeyCheckValue [0..1]
Assessment [0..*] Only used in TMS protocol.
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1] Config The Acquirer configuration indicates if either ProtectedCardData
or PlainCardData is present (e.g. TMS parameter
AcquirerProtocolParameters.ProtectCardData).
ProtectedCardData [0..1] C4 Present if Card.PlainCardData absent.
Encryption of the PlainCardData component, including the
envelope, using CMS ContentType.EnvelopedData..
PlainCardData [0..1] C4 Present if ProtectedCardData absent.
PAN [1..1]
[0..1] Appli
CardSequenceNumber
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
ServiceCode [0..1] Appli
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
CardholderName [0..1]
[0..1] Unique reference to the card, used by both merchants and
PaymentAccountReference acquirers to link tokenised and non-tokenised transactions
associated to the same underlying card.
IssuerBIN [0..1] Bank identifier number of the issuer for routing purpose
CardCountryCode [0..1] Appli Alphabetic with 2 or 3 characters, or numeric code conforms to
ISO 3166 – 1. Indicates the country of the card issuer.
CardCurrencyCode [0..1] Currency code of the card issuer (ISO 4217 numeric code).
CardProductProfile [0..1] Config Defines the acceptance processing and rules performed by the
POI, after analysis of the application profile. Assigned by the
Acquirer.
CardBrand [0..1] Appli Brand name of the card or the scheme.
InternationalCard [0..1] “True” if the card may be used abroad. Else “False” for
domestic cards only.
AllowedProduct [0..*] Product that can be purchased with the card. The list of allowed
products contained in some specific cards (eg. Petrol cards)
ServiceOption [0..1] Options to the service provided by the card.
AdditionalCardData [0..1] Appli Additional data taken from specific card products.
CustomerDevice [0..1] Device used by the customer to perform the payment
transaction
Identification [0..1] Identification of the customer device used for payment
Type [0..1] Type of the device in free text

- 111 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


Provider [0..1] Provider of the device
Wallet [0..1] Container for tenders used by the customer to perform the
payment transaction.
Identification [0..1] Identification of the wallet used for payment
Type [0..1] Type of wallet in free text
Provider [0..1] Provider of the wallet
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
[1..1]
ProviderIdentification
[1..1]
RequestorIdentification
Cardholder [0..1] C5 Present if it contains any data.
Identification [0..1] Appli For verification of the Cardholder identity. A Cardholder may be
identified by more than one identification method.
[0..1]
DriverLicenseNumber
[0..1]
DriverLicenseLocation
DriverLicenseName [0..1]
DriverIdentification [0..1]
CustomerNumber [0..1]
[0..1]
SocialSecurityNumber
[0..1]
AlienRegistrationNumber
PassportNumber [0..1]
[0..1]
TaxIdentificationNumber
IdentityCardNumber [0..1]
[0..1]
EmplyerIdentificationNumber
[0..1]
EmployeeIdentificationNumbe
r
JobNumber [0..1]
Department [0..1]
EmailAddress [0..1]
DateAndPlaceOfbirth [0..1]
BirthDate [1..1]
ProvinceOfBirth [0..1]
CityOfBirth [1..1]
CountryOfBirth [1..1]
Other [0..*]
Identification [1..1]
IdentificationType [1..1]
Name [0..1] Appli For verification of the Cardholder identity.
Language [0..1] Appli Advise the Acquirer of the cardholder language so that
messages to the Cardholder can be customized to that
language.
BillingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]

- 112 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
ShippingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
TripNumber [0..1]
Vehicle [0..1]
VehicleNumber [0..1]
TrailerNumber [0..1]
VehicleTag [0..1]
[0..1]
VehicleTagEntryMode
UnitNumber [0..1]
ReplacementCar [0..1]
Odometer [0..1]
Hubometer [0..1]
TrailerHours [0..1]
ReferHours [0..1]
[0..1]
MaintenanceIdentification
DriverOrVehicleCard [0..1]
PAN [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
[0..*]
AdditionalCardData
EntryMode [0..1]
[0..*]
AdditionalVehicleData
Type [0..1]
EntryMode [0..1]
Data [1..1]
Authentication [0..*] Appli Method and data used or intended to be used for this
transaction to authenticate the owner of the card.
[1..1] C6 Method used to authenticate the cardholder:
AuthenticationMethod C7

AuthenticationValue [0..1] C6 Present if AuthenticationMethod="SecureCertificate" or


"SecureNoCertificate".
(e.g. Visa Cardholder Authentication Verification Value (CAVV)
or Mastercard Accountholder Authentication Value (AVV).
[0..1]
ProtectedAuthenticationValue

- 113 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


CardholderOnlinePIN [0..1] C7 Present if AuthenticationMethod="PINOnline"
PIN verification by the Issuer during an online authorisation.
[1..1] Transport the PIN in an encrypted form using the
EncryptedPINBlock EnvelopedData CMS data structure.
PINFormat [1..1] Appli
AdditionalInput [0..1] Appli Additional information required for the PIN verification, (e.g. the
driver number for some fleet cards).
[0..1]
CardholderIdentification
AddressVerification [0..1] C8 Present if it contains any data
For verifying the cardholder's billing address.
AddressDigits [0..1] Appli Numerics from the cardholder's address excluding the postal
code (i.e. house number).
PostalCodeDigits [0..1] Appli Numerics from the cardholder's postal code.
[0..*] Result of performed verifications for the transaction. Several
TransactionVerificationResult methods may have been used for verification
Method [1..1] Method of verification that has been performed.
VerificationEntity [0..1] Entity or device that has performed the verification
Result [0..1] Result of the verification.
AdditionalResult [0..1] Additional result of the verification
PersonalData [0..1] Appli Not to be used for cardholder identification or authentication.
ProtectedCardholderData [0..1]
Context [1..1]
PaymentContext [1..1]
CardPresent [0..1] C9 default True
Indicates whether the transaction has been initiated by a card
physically present or not:
Not present if CardDataEntryMode="AccountData",
Present or not if CardDataEntryMode="Physical",
Present for other values of CardDataEntryMode.
CardholderPresent [0..1] C10 default True
Indicates whether the transaction has been initiated in presence
of the cardholder or not (e.g. False for the 2nd and subsequent
payments on a recurring transaction).
AttendanceContext [0..1] Config C10 If CardholderPresent is "True":
Erreu Attended: an attendant is present and performs the financial
r! transaction (face to face).
Sour SemiAttended: one attendant monitors several POIs, to offer
ce du assistance if needed.
renv Unattended: an attendant is not present
oi Otherwise the element is absent
intro
uvabl
e.
[0..1] default Merchant
TransactionEnvironment Information required by some Acquirers or card schemes:
Merchant: POI is located at the premises of the merchant.
Private: remote payment, not at the premises of the merchant
Public: POI is located in a public area, not at the premises of
the merchant.
TransactionChannel [0..1] Config Information required by some Acquirers or card schemes for
specific environments.
MailOrder: services or good purchased by mail (written).
TelephoneOrder: services or good purchased by phone
(voice)
ElectronicCommerce: services or good purchased by
Internet (electronic)
TelevisionPayment: services or good purchased by TV
[0..1] C11 default True
AttendantMessageCapable Indicates to the Acquirer whether a message in the
authorisation response can be displayed to the Cashier or not.

- 114 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


AttendantLanguage [0..1] C11 Present If AttendantMessageCapable is True
Indicates to the Acquirer in the Authorisation Response
message the language of the message to be displayed to the
Cashier.
CardDataEntryMode [1..1] C9 The entry mode used to get the card data, and not the list of
entry modes in case of fall-back.
.
FallbackIndicator [0..1] Appli default False
Card data entry mode fallback..
SupportedOption [0..*] Payment options the card acceptor can support.
SaleContext [0..1] C12 Present if it contains any data.
Information provided by the sale system (e.g. EPAS Retailer
protocol).
SaleIdentification [0..1] Appli
SaleReferenceNumber [0..1] Appli
SaleReconciliation- [0..1] Appli
Identification
CashierIdentification [0..1] Appli
ShiftNumber [0..1] Appli
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
[1..1]
MerchantCategoryCode
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1] Appli
Transaction [1..1]
TransactionCapture [1..1] C13 If "True", this financial transaction must be captured for clearing
by the Acquirer.
MessageFunction value must be "AuthorisationRequest" if
TransactionCapture = "False", "FinancialAuthorisationRequest"
if TransactionCapture = "True".
TransactionType [1..1] C14 "CardPayment","CashAdvance", "DeferredPayment", "Refund"
AdditionalService [0..*] "Gratuity", "CashBack"
ServiceAttribute [0..1]
MerchantCategoryCode [1..1] Code assigned by the Acquirer, containing the ISO18245-4
MCC code associated with the category of services or goods
purchased in this transaction (the merchant can have several
MCCs associated to its business).
[0..1]
SaleReferenceIdentification
TransactionIdentification [1..1] Identification of the transaction assigned by the POI.
TransactionDateTime [1..1] Appli UTC date and time with offset or local date time.
TransactionReference [1..1] Appli Identification of the transaction that has to be unique in
combination with TransactionDateTime for the merchant and
the POI.
OriginalTransaction [0..1] Appli Not used if TransactionType="CardPayment",
"DeferredPayment" or "CashBack", optional if
TransactionType="Refund"
[0..1]
SaleReferenceIdentification

- 115 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


[1..1]
TransactionIdentification
TransactionDateTime [1..1]
[1..1]
TransactionReference
POIIdentification [0..1] Appli
Identification [1..1]
Type [0..1] default OriginatingPOI
Issuer [0..1] Config
ShortName [0..1] Config
InitiatorTransaction- [0..1] If present in the original transaction
Identification
RecipientTransaction- [0..1] If present in the original transaction
Identification
TransactionType [1..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
CardDataEntryMode [0..1]
TransactionResult [0..1] Appli
AuthorisationEntity [0..1]
Identification [0..1]
Type [1..1]
Issuer [0..1] Copy
Country [0..1]
ShortName [0..1] Copy
ResponseTo- [1..1]
Authorisation
Response [1..1]
ResponseReason [0..1] Appli
[0..1]
AdditionalResponseInformati
on
AuthorisationCode [0..1] Appli
InitiatorTransaction- [0..1] Appli A value provided by the card acceptor that is meaningful in the
Identification card acceptor’s system and that the acquirer can use in
referencing back to this transaction.
[0..1] Appli Identification of the reconciliation period assigned by the POI to
ReconciliationIdentification the transaction.
Conforming to the configuration parameters (by the EPAS TMS
configuration parameters ReconciliationByAcquirer and
ReconciliationExchange), absent if:
The acquirer assigns the reconciliation period, and provides
it in the response, or
There is no reconciliation exchange (e.g. capture in batch)
TransactionDetails [1..1]
Currency [1..1] Appli Currency of TotalAmount and DetailedAmount if present
TotalAmount [1..1] Requested amount to be authorised, including DetailedAmount
occurrences.
AmountQualifier [0..1] C14 default Actual
Allowed values depends on the TransactionType value:
"CardPayment": Actual
"DeferredPayment": Estimated or Maximum
DetailedAmount [0..1] Appli
[0..1]
AmountOfGoodAndServices
CashBack [0..1]

- 116 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
ValidityDate [0..1] Appli
OnlineReason [0..1] Appli Indicates to the Acquirer the primary reason why the transaction
has been sent online by the Card Acceptor.
[0..1] Appli Some card schemes may require for unattended POI terminals
UnattendedLevelCategory that the application determines the category level for the
transaction.
The value of this data is set by the application in compliance
with the rules of the card scheme.
AccountType [0..1] Appli defaut Default
Allows a cardholder to select the type of account used for the
transaction.
[0..1]
CurrencyConversionResult
[0..1]
AcceptedByCardholder
Conversion [0..1]
[0..1]
CurrencyConversionIdentifica
tion
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
[0..1]
InvertedExchangeRate
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]
[0..*]
CommissionDetails
Amount [1..1]
[0..1]
AdditionalInformation

- 117 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


MarkUpDetails [0..*]
Rate [1..1]
[0..1]
AdditionalInformation
DeclarationDetails [0..1]
Format [0..1]
[1..1]
MessageContent
Instalment [0..1]
InstalmentPlan [0..*]
PlanIdentification [0..1]
SequenceNumber [0..1]
PeriodUnit [0..1]
InstalmentPeriod [0..1]
[0..1]
TotalNumberOfPayments
FirstPaymentDate [0..1]
TotalAmount [0..1]
FirstAmount [0..1]
Charges [0..1]
AggregationTransaction [0..1]
[0..1]
FirstPaymentDateTime
[0..1]
LastPaymentDateTime
NumberOfPayments [0..1]
IndividualPayment [0..*]
Amount [1..1]
DateTime [1..1]
[0..1]
CardDataEntryMode
ICCRelatedData [0..1]
Label [0..1]
[0..1]
ProductCodeSetIdentification
SaleItem [0..*]
ItemIdentification [0..1]
ProductCode [1..1]
[0..1]
AdditionalProductCode
UnitOfMeasure [0..1]
ProductQuantity [0..1]
UnitPrice [0..1]
UnitPriceSign [0..1]
ProductAmount [1..1]
ProductAmountSign [0..1]
ValueAddedTax [0..1]
TaxType [0..1]
ProductDescription [0..1]
DeliveryLocation [0..1]
DeliveryService [0..1]
DeliveryLocation [0..1]

- 118 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Cstr Usage


CardPaymentInvoice [0..1]
InvoiceHeader [1..1]
Identification [1..1]
TypeCode [1..1]
Name [0..*]
IssueDateTime [1..1]
Issuer [0..1]
[1..1]
PartyIdentification
[0..1]
LegalOrganisation
[0..1]
Identification
[0..1]
Name
TaxParty [0..*]

LanguageCode [0..1]
CopyIndicator [0..1]
[0..1]
DocumentPurpose
IncludedNote [0..*]
[1..1]
InformationType
[1..1]
InformationValue
TradeAgrrement [1..1]
TradeDelivery [1..1]
LineItem [0..*]
ICCRelatedData [0..1] Appli A sequence of one or more TLV data elements in accordance
with ISO 7816-6, not in a specific order.
MerchantReferenceData [0..1]
AdditionalTransactionData [0..*] Appli
SupplmentaryData [0..*] Appli
PlaceAndName [0..1]
Envelope [1..1]
SecurityTrailer [0..1] The MAC of the message body AuthorisationRequest (including
the body envelope) held in the AuthenticatedData element of
the CMS data structure.

4.2.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When AuthorisationRequest is present the  Header.MessageFunction
Header.MessageFunction must be  AuthorisationRequest
AuthorisationRequest” or
“FinancialAuthorisationRequest”
C2 If AuthorisationRequest.Environment.Merchant is  AuthorisationRequest.Environment.Merchant
present it must have at least one child
C3 If AuthorisationRequest.Environment.POI.Capabilities  AuthorisationRequest.Environment.POI.Capabil
is present it must have at least one child ities

- 119 -
Card Payments Message Usage Guide Version 5.0

C4 Either  AuthorisationRequest.Environment.Card.Protec
AuthorisationRequest.Environment.Card.ProtectedCar tedCardData
dData or  AuthorisationRequest.Environment.Card.PlainC
AuthorisationRequest.Environment.Card.PlainCardDat ardData
a must be present.
C5 If AuthorisationRequest.Environment.Cardholder is  AuthorisationRequest.Environment.Cardholder
present it must have at least one child
C6 AuthenticationValue must be present if  AuthorisationRequest.Environment.Cardholder.
AuthenticationMethod is "SecureCertificate" or Authentication.AuthenticationMethod
"SecureNoCertificate".  AuthorisationRequest.Environment.Cardholder.
Authentication.AuthenticationValue
C7 CardholderOnlinePIN must be present if  AuthorisationRequest.Environment.Cardholder.
AuthenticationMethod is "PINOnline". Authentication.AuthenticationMethod
 AuthorisationRequest.Environment.Cardholder.
Authentication.CardholderOnlinePIN
C8 If AddressVerification is present it must have at least  AuthorisationRequest.Environment.Cardholder.
one child Authentication. AddressVerification
C9 CardPresent must be absent if  AuthorisationRequest.Context.PaymentContext
CardDataEntryMode="AccountData", .CardPresent
CardPresent must be present if CardDataEntryMode  AuthorisationRequest.Context.PaymentContext
has any other value than "AccountData" and "Physical" .CardDataEntryMode

C10 AttendanceContext must present only if  AuthorisationRequest.Context.AttendanceCont


CardholderPresent is "True" and has value “Attended”, ext
“SemiAttended” or “Unattended”  AuthorisationRequest.Context.CardholderPrese
nt
C11 AttendantLanguage must be present If  AuthorisationRequest.Context.
AttendantMessageCapable is “True” AttendantLanguage
 AuthorisationRequest.Context.
AttendantMessageCapable
C12 If SaleContext is present it must have at least one  AuthorisationRequest.Context.SaleContext
child
C13 MessageFunction value must be  Header.MessageFunction
"AuthorisationRequest" if TransactionCapture =  AuthorisationRequest.Transaction.Transaction
"False", "FinancialAuthorisationRequest" if Capture
TransactionCapture = "True".
C14 If TransactionType value is "CardPayment" then  AuthorisationRequest.Transaction.Transaction
AmountQualifier value must be “Actual”. If Type
TransactionType value is "DeferredPayment" then  AuthorisationRequest.Transaction.Transaction
AmountQualifier value must be either “Estimated” or Details.AmountQualifier
“Maximum”

- 120 -
Card Payments Message Usage Guide Version 5.0

4.2.2 AcceptorAuthorisationResponse (caaa.002.001.05)

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


Header [1..1] see AcceptorAuthorisationRequest
MessageFunction [1..1] C1 The only valid codes in a normal payment response are:
AuthorisationResponse: Response for
AuthorisationRequest
FinancialAuthorisationResponse: Response for
FinancialAuthorisationRequest
ProtocolVersion [1..1] Copy The Recipient Party has to adapt the
AcceptorAuthorisationResponse format to the version of the
Initiator sent in the AuthroisationRequest. If this version is
not supported the Recipient must reject the request.with
RejectReason = ProtocolVersion.
ExchangeIdentification [1..1] Copy
CreationDateTime [1..1] Date and time of the creation of the message response.
Time accuracy has to be at least tenth of a second.
InitiatingParty [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RecipientParty [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Present and completed if present in the request.
see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1]
ShortName [0..1] Copy
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
AuthorisationResponse [1..1] C1 The Header.MessageFunction must be

- 121 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


AuthorisationResponse or FinancialAuthorisationResponse.
(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)
Environment [1..1]
AcquirerIdentification [0..1] Appli If the identification is present in the request:
It must be present in the response, but it may be
different.
If the identification is absent in the request:
It may be absent in the response (if the POI does not
need it for capture, reconciliation, reporting, etc)
It may be present in the response (if the choice is not
made by the POI, and the POI needs it)
Identification [1..1]
Type [0..1] default Acquirer
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1] If the identification is present in the request:
It must be present in the response, but it may be
different from the request.
If the identification is absent in the request:
It may be absent in the response (if the POI don’t need it
for capture, reconciliation, report, etc)
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
ShortName [0..1]
POIIdentification [1..1] Appli May be different from the request.
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
Card
ProtectedCardData [0..1] Appli - - Encryption of the PlainCardData component,
including the envelope, using CMS
ContentType.EnvelopedData.
Present if:
- - the protection of sensitive card data is required
(TMS parameter ProtectedCardData equal to
True) and
- - the validation of card data by the acceptor is
required. These card data could be a subset of
those in the reques
PlainCardData [0..1] Appli Present if:
- sensitive card data does not require a protection (TMS parameter Prote
False) and
- the validation of card data by the acceptor is required.

PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1]

- 122 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Copy For verification.
TransactionDateTime [1..1]
TransactionReference [1..1]
[0..1]
InitiatorTransactionIdentification
RecipientTransaction- [0..1] Appli Used by the InitiatingParty when it refers back to the
Identification transaction of the RecipientParty (e.g. reconciliation
mismatch). If supplied, it is mandatory in the completion and
the batch.
ReconciliationIdentification [0..1] Copy or Conforming to the configuration parameters
Appli ReconciliationByAcquirer and ReconciliationExchange.
Present if:
The acquirer copies the value of the request assigned by
the acceptor.
The acquirer assigns the reconciliation period, and
provides it in the response.
InterchangeData [0..1] Appli Data received from a card scheme message and required
by the card scheme to be sent in the financial capture.
TransactionDetails [1..1]
Currency [1..1] Copy
TotalAmount [1..1] If the Response is PartialApproved, the TotalAmount (ie the
amount authorised) must be different from the amount
requested; otherwise it must be the same as in the request
message.
DetailedAmount [0..1] Appli
[0..1]
AmountOfGoodAndServices
CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
InvoiceAmount [0..1]
Amount [1..1]
Label [0..1]
ValidityDate [0..1] Appli
AccountType [0..1] Appli If present in the request this field must contain a copy of
the request value.
If not present in the request, it may inform the cardholder
about the account used for the transaction.

- 123 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


ICCRelatedData [0..1] A sequence of one or more TLV data elements in
accordance with ISO 7816-6, not in a specific order.
MerchantReferenceData [0..1]
TransactionResponse [1..1]
AuthorisationResult [1..1]
AuthorisationEntity [0..1] Identifies the entity which initially sets the Response value
(approves, declines, or generates a "technical error" ).
Identification [0..1]
Type [1..1] Intermediary Agent, Acquirer: conforming to the rules of the
card scheme, the Acquirer authorises the transaction (e.g.
because a stand-in process, or declined because of
technical problem).
CardIssuer: the standard case.
DelegateIssuer: for this transaction, the Issuer delegated
the authorising right to another entity, for some reason.
Issuer [0..1] Appli
Country [0..1]
ShortName [0..1] Appli
ResponseToAuthorisation [1..1]
Response [1..1] Declined: authorisation is declined or the requested capture
is not performed.
Approved: authorisation is approved for the full amount
requested, including capture if requested
PartialApproved: same as Approved, with TotalAmount
lower in the response than in the request.
TechnicalError: The message could not be processed for
technical reasons (e.g. timeout to the Issuer, HSM problem)
ResponseReason [0..1] Appli Additional information related to the response.
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli This code proves the approval delivered by the authorising
entity (e.g. ISO 8583 - Elem. 38 - approval code).
CompletionRequired [0..1] If the flag has the value "True", an
AcceptorCompletionAdvice has to be sent after the end of
the transaction (see Table 2 : List of Payment Cases
Erreur ! Source du renvoi introuvable. for the details)
TMSTrigger [0..1] Appli Present when the POI needs maintenance. The POI may
require maintenance prior to the execution of a specific
service.
TMSContactLevel [1..1] * Allowed values:
C3 Critical: TMS to be contacted before the next transaction
ASAP: TMS to be contacted as soon as possible (e.g. after
reconciliation)
DateTime: TMS to be contacted at the date and time
provided in TMSContactDateTime
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1] C3 Present if TMSContactLevel = DateTime
TransactionVerificationResult [0..*] Present if data structure is not empty
Method [1..1]
VerificationEntity [0..1]
Result [0..1]
AdditionalResult [0..1]
AllowedProductCode [0..*]
ProductCode [1..1]
AdditionalProductCode [0..1]
NotAllowedProductCode [0..*]
ProductCode [1..1]

- 124 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


AdditionalProductCode [0..1]
AdditionalAvailableProduct [0..*]
ProductCode [1..1]
AdditionalProductCode [0..1]
AmountLimit [0..1]
QuantityLimit [0..1]
UnitOfMeasure [0..1]
Balance [0..1] Appli
Amount [1..1]
Sign [0..1]
ProtectedBalance [0..1]
Action [0..*] Appli Several combinations of actions may be sent in the
response (e.g. CaptureCard plus a display message for the
merchant, or Referral plus separate display and print
messages for the cardholder and merchant)
ActionType [1..1] C5 Additional actions to complete the transaction:
DisplayMessage: Display a message.
PrintMessage: Print a message.
One of the following actions may be sent, if the Response is
“Declined”:
Busy: Server busy. Try later.
CaptureCard: Capture card.
ForbidOverride: Payment application cannot offer to the
merchant the possibility to override the transaction.
IDRequired: Additional identification required (passport,
ID card, etc.).
PINRetry: PIN verification retry.
PINLastTry: Last PIN try.
Referral: Referral with a voice authorisation has to be
performed.
RequestData: Request additional data through a
displayed text and request confirmation by attendant.

MessageToPresent [0..1] C5 if ActionType is DisplayMessage or PrintMessage


MessageDestination [1..1]
Format [0..1]
MessageContent [1..1]
[0..1] Appli
MessageContentSign
ature
CurrencyConversionEligibility [0..1]
[0..1]
CurrencyConversionI
dentification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
InvertedExchangeRate [0..1]
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]

- 125 -
Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationResponse Mult. Rule Cstr Usage


NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1.1*]
CommissionDetails [0..*]
Amount [1..1]
AdditionalInformation [0..1]
MarkUpDatails [0..*]
Rate [1..1]
AdditionalInformation [0..1]
DeclarationDetails [0..1]
Format [1..1]
MessageContent [1..1]
SupplementaryData [0..*]
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body AuthorisationResponse including the body
envelope (see chapter ).

4.2.2.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When AuthorisationResponse is present the  Header.MessageFunction
Header.MessageFunction must be  AuthorisationResponse
“AuthorisationResponse” or
“FinancialAuthorisationResponse”.
C3 TMSContactDateTime must be present if  AuthorisationResponse.TransactionResponse.
TMSContactLevel = “DateTime” TMSTrigger. TMSContactDateTime
 AuthorisationResponse.TransactionResponse.
TMSTrigger. TMSContactDateTime
C5 MessageToPresent must be present if ActionType is  AuthorisationResponse.TransactionResponse.
“DisplayMessage” or “PrintMessage” Action.ActionType
 AuthorisationResponse.TransactionResponse.
Action.MessageToPresent

- 126 -
Card Payments Message Usage Guide Version 5.0

4.3 Completion Messages

4.3.1 AcceptorCompletionAdvice (caaa.003.001.05)


AcceptorCompletionAdvice Mult. Rule Cstr Usage
Header [1..1]
MessageFunction [1..1] C1 The only valid codes to advice a normal payment are:
C5 CompletionAdvice: Completion without financial capture
(TransactionCapture=False, Reversal=False) or
(TransactionCapture=False, Reversal=True,
TransactionSuccess=True)
FinancialCompletionAdvice: Completion with financial
capture (TransactionCapture=True, Reversal=False)
or
(TransactionCapture=True, Reversal=True,
TransactionSuccess =True)
ReversalAdvice: Reversal of an authorisation without
financial capture (TransactionCapture=False,
Reversal=True, TransactionSuccess =False)
FinancialReversalAdvice: Reversal of a
FinancialAuthorisation (TransactionCapture=True,
Reversal=True, TransactionSuccess =False)
(in case of an invalid value, a Reject message is sent by
the Recipient with RejectReason equal to ParsingError)
ProtocolVersion [1..1] * see AcceptorAuthorisationRequest
ExchangeIdentification [1..1] see AcceptorAuthorisationRequest
RetransmissionCounter [0..1] default 0
see 3.3 Message Retransmission
CreationDateTime [1..1] see AcceptorAuthorisationRequest
InitiatingParty [1..1] see AcceptorAuthorisationRequest
Identification [1..1]
Type [0..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Config see AcceptorAuthorisationRequest
Identification [0..1]
Type [1..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Config
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]

- 127 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CompletionAdvice [1..1] C1 The Header.MessageFunction must be CompletionAdvice,
FinancialCompletionAdvice, ReversalAdvice or
FinancialReversalAdvice.
(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)
Environment [1..1]
Acquirer [0..1] Config If Acquirer identification has been sent in the Authorisation
response, this value has to be used in CompletionAdvice.
Identification [0..1]
Identification [1..1]
Type [0..1] * default Acquirer
see AcceptorAuthorisationRequest
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ParametersVersion [1..1] CCopy For online authorisation, the value has to be the same as
that in the Authorisation.
Merchant [0..1] CCopy Conditional copy for online transactions.
Configurable for offline transactions.
Identification [0..1]
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
ShortName [0..1]
CommonName [0..1]
LocationCategory [0..1]
LocationAndContact [0..1] Config
SchemeData [0..1]
POI [1..1] Copy from AcceptorAuthorisationRequest.
Identification [1..1] Copy from AcceptorAuthorisationResponse if any.
Identification [1..1] Identification of a POI terminal or system.
Type [0..1] default OriginatingPOI
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentification [0..1]
Capabilities [0..1]
CardReadingCapabilities [0..1]
CardholderVerification- [0..1]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1]

- 128 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*] see AcceptorAuthorisationRequest
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
Communication- [1..1]
Type
RemoteParty [1..*]
Active [1..1]
SecurityAccess- [0..1]
Modules
SubscriberIIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1]
ProtectedCardData [0..1] Only present if requested by the Acquirer configuration (e.g.
TMS parameter CardDataVerification is “True” and
ProtectCardData is “True”) or
AcceptorAuthorisationResponse was not received.
PlainCardData [0..1] Only present if requested by the Acquirer configuration (e.g.
TMS parameter CardDataVerification is “True” and

- 129 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


ProtectCardData is “False”) or
AcceptorAuthorisationResponse was not received.
PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
ServiceCode [0..1] Appli
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
CardholderName [0..1]
PaymentAccountReference [0..1)
IssuerBIN [0..1)
CardCountryCode [0..1] Appli see AcceptorAuthorisationRequest
CardCurrencyCode [0..1]
CardProductProfile [0..1] Config see AcceptorAuthorisationRequest
CardBrand [0..1] Appli see AcceptorAuthorisationRequest
InternationalCard [0..1]
AllowedProduct [0..*]
ServiceOption [0..1]
AdditionalCardData [0..1] Appli see AcceptorAuthorisationRequest
CustomerDevice [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
Cardholder [0..1] C2 Present if it contains any data.
Identification [0..1] Appli If required for capture of the transaction.
DriverLicenseNumber [0..1]
DriverLicenseLocation [0..1]
DriverLicenseName [0..1]
DriverIdentification [0..1]
CustomerNumber [0..1]
SocialSecurityNumber [0..1]
[0..1]
AlienRegistrationNumber
PassportNumber [0..1]
TaxIdentificationNumber [0..1]
IdentityCardNumber [0..1]
[0..1]
EmplyerIdentificationNumber
[0..1]
EmployeeIdentificationNumber

- 130 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


JobNumber [0..1]
Department [0..1]
EmailAddress [0..1]
DateAndPlaceOfbirth [0..1]
BirthDate [1..1]
ProvinceOfBirth [0..1]
CityOfBirth [1..1]
CountryOfBirth [1..1]
Other [0..*]
Identification [1..1]
IdentificationType [1..1]
Name [0..1]
Language [0..1]
BillingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
ShippingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
TripNumber [0..1]
Vehicle [0..1]
VehicleNumber [0..1]
TrailerNumber [0..1]
VehicleTag [0..1]
VehicleTagEntryMode [0..1]
UnitNumber [0..1]
ReplacementCar [0..1]
Odometer [0..1]
Hubometer [0..1]
TrailerHours [0..1]
ReferHours [0..1]
[0..1]
MaintenanceIdentification
DriverOrVehicleCard [0..1]
PAN [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
AdditionalCardData [0..*]
EntryMode [0..1]

- 131 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


AdditionalVehicleData [0..*]
Type [0..1]
EntryMode [0..1]
Data [1..1]
PersonalData [0..1]
ProtectedCardholderData [0..1]
Context [0..1] C3 Present if it contains any data
PaymentContext [1..1]
CardPresent [0..1] default True
see AcceptorAuthorisationRequest
CardholderPresent [0..1] default True
see AcceptorAuthorisationRequest
OnlineContext [0..1] default True
The flag is set to “False” if the authorisation was offline
without the need of sending an
AcceptorAuthorisationRequest during the transaction.
AttendanceContext [0..1] default Attended
see AcceptorAuthorisationRequest
TransactionEnvironment [0..1] default Merchant
see AcceptorAuthorisationRequest
TransactionChannel [0..1] Config see AcceptorAuthorisationRequest
CardDataEntryMode [1..1] see AcceptorAuthorisationRequest
FallbackIndicator [0..1] Appli default False
see AcceptorAuthorisationRequest
SupportedOption [0..*]
SaleContext [0..1] C4 Present if it contains any data.
see AcceptorAuthorisationRequest
SaleIdentification [0..1] Appli
SaleReferenceNumber [0..1] Appli
SaleReconciliation- [0..1] Appli
Identification
CashierIdentification [0..1] Appli
ShiftNumber [0..1] Appli
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1] Appli
Transaction [1..1] CCopy
TransactionCapture [0..1] Config C5 default False
If True, this financial transaction must be captured by the
Acquirer.
TransactionCapture is True if MessageFunction value is
FinancialCompletionAdvice or FinancialReversalAdvice and
False otherwise.
TransactionType [1..1]

- 132 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


AdditionalService [0..*] VoiceAuthorisation if transaction approved by phone after
Referral as ActionType in the declined authorisation
Gratuity, Cashback
ServiceAttribute [0..1]
MerchantCategoryCode [1..1] see AcceptorAuthorisationRequest
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] CCopy Identification of the transaction assigned by the POI
Same value as the AuthorisationRequest if any.
TransactionDateTime [1..1]
TransactionReference [1..1]
OriginalTransaction [0..1] Appli Not used for CardPayment, optional for Refund
TransactionType
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
InitiatorTransaction- [0..1]
Identification
RecipientTransaction- [0..1]
Identification
TransactionType [1..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
CardDataEntryMode [0..1]
TransactionResult [0..1]
AuthorisationEntity [1..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1]
Authorisation
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli
TransactionSuccess [1..1] C6 True if the outcome of the transaction is successful (see
section 5)
Reversal [0..1] default False
If True, a reversal of the online authorisation is requested
(see section 5).
MerchantOverride [0..1] Appli default False
True if the acceptor has forced the transaction to be
successful (see section 5).
FailureReason [0..*] Appli. C6 Mandatory if TransactionSuccess is False, or Reversal is
True or MerchantOverride is True (see section 5).
CardDeclined: Integrated circuit card declines the
transaction after the authorisation.
CustomerCancel: Customer cancellation, for example
removing the chip card after sending the
AcceptorAuthorisationRequest, but before the end of the
transaction.
Malfunction: Suspected malfunction (e.g. card reader
defect, printer out of order).

- 133 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


OfflineDeclined: Offline authorisation declined the
transaction.
OnLineDeclined: Online authorisation declined the
transaction.
SuspectedFraud: Card payment transaction failed because
the merchant suspected a fraud.
TimeOut: Timeout waiting for response from the acquirer,
or no response was received (for example connection
release before receiving the response).
TooLateResponse: Response to the authorisation received
too late.
UnableToComplete: Card acceptor device unable to
complete transaction after the authorisation response
(e.g. written signature invalid).
UnableToSend: Unable to deliver the
AcceptorAuthorisationRequest to the acquirer.
InitiatorTransaction- [0..1] Appli Copy from AuthorisationRequest if any.
Identification
RecipientTransaction- [0..1] Appli Copy from AuthorisationResponse if any.
Identification
ReconciliationIdentification [0..1] Appli For online transactions:
 If the transaction is captured during the authorisation
or by batch, copy from AuthorisationRequest.
 If the transaction is captured by the Completion,
identification of the reconciliation period. The value
may be different from the
AcceptorAuthorisationRequest.
see AcceptorAuthorisationRequest for offline transactions.
InterchangeData [0..1] Appli Copy from AuthorisationResponse if any.
TransactionDetails [1..1]
Currency [1..1]
TotalAmount [1..1] Final amount of the payment transaction when
TransactionSuccess is "True".
If TransactionSuccess is "False":
the amount of AuthorisationResponse for an online
approval,
the amount of AuthorisationRequest if unable to go
online or timeout,
the purchase amount for an offline authorisation
AmountQualifier [0..1] Appli
DetailedAmount [0..1] Appli
[0..1]
AmountOfGoodAndServices
CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
RequestAmount [0..1]

- 134 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


AuthorisedAmount [0..1]
InvoiceAmount [0..1]
ValidityDate [0..1]
UnattendedLevelCategory [0..1] Appli Present if AttendanceContext is Unattended
see AcceptorAuthorisationRequest
AccountType [0..1] Appli defaut Default
see AcceptorAuthorisationRequest
CurrencyConversionResult [0..1]
AcceptedByCardholder [0..1]
Conversion [0..1]
[0..1]
CurrencyConversionIdentification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
[0..1]
InvertedExchangeRate
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]
CommissionDetails [0..*]
Amount [1..1]
[0..1]
AdditionalInformation
MarkUpDetails [0..*]
Rate [1..1]
[0..1]
AdditionalInformation
DeclarationDetails [0..1]
Format [0..1]
MessageContent [1..1]
Instalment [0..1]
InstalmentPlan [0..*]
PlanIdentification [0..1]
SequenceNumber [0..1]
PeriodUnit [0..1]
InstalmentPeriod [0..1]
TotalNumberOfPayments [0..1]
FirstPaymentDate [0..1]
TotalAmount [0..1]
FirstAmount [0..1]
Charges [0..1]

- 135 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


AggregationTransaction [0..1]
FirstPaymentDateTime [0..1]
LastPaymentDateTime [0..1]
NumberOfPayments [0..1]
IndividualPayment [0..*]
Amount [1..1]
DateTime [1..1]
CardDataEntryMode [0..1]
ICCRelatedData [0..1]
Label [0..1]
[0..1]
ProductCodeSetIdentification
SaleItem [0..*]
ItemIdentification [0..1]
ProductCode [1..1]
AdditionalProductCode [0..1]
UnitOfMeasure [0..1]
ProductQuantity [0..1]
UnitPrice [0..1]
UnitPriceSign [0..1]
ProductAmount [1..1]
ProductAmountSign [0..1]
ValueAddedTax [0..1]
TaxType [0..1]
ProductDescription [0..1]
DeliveryLocation [0..1]
DeliveryService [0..1]
DeliveryLocation [0..1]
CardPaymentInvoice [0..1]
InvoiceHeader [1..1]
Identification [1..1]
TypeCode [1..1]
Name [0..*]
IssueDateTime [1..1]
Issuer [0..1]
[1..1]
PartyIdentification
[0..1]
LegalOrganisation
[0..1]
Identification
Name [0..1]
TaxParty [0..*]

LanguageCode [0..1]
CopyIndicator [0..1]
DocumentPurpose [0..1]
IncludedNote [0..*]
InformationType [1..1] see AcceptorAuthorisationRequest
InformationValue [1..1]
TradeAgrrement [1..1]

- 136 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Cstr Usage


TradeDelivery [1..1]
LineItem [0..*]
ICCRelatedData [0..1] Appli A sequence of one or more TLV data elements in
accordance with ISO 7816-6
AuthorisationResult [0..1] Appli Present for online authorisation if an
AcceptorAuthorisationResponse has been received.
AuthorisationEntity [0..1] CCopy see AcceptorAuthorisationResponse if received, otherwise
absent.
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseToAuthorisation [1..1] see AcceptorAuthorisationResponse
Response [1..1]
ResponseReason [0..1] Appli
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli Obtained from the corresponding
AcceptorAuthorisationResponse if any. For Voice
Authorisation the AuthorisationCode is obtained from the
Acquirer (see section 6.1).
TransactionVerificationResult [0..1] Appli
Method [1..1]
VerificationEntity [0..1]
Result [0..1]
AdditionalResult [0..1]
AdditionalTransactionData [0..*] Appli
SupplementaryData [0..*] Appli
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body CompletionAdvice including the body
envelope.

4.3.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When CompletionAdvice is present the  Header.MessageFunction
Header.MessageFunction must be  CompletionAdvice
“CompletionAdvice”, “FinancialCompletionAdvice”,
“ReversalAdvice” or “FinancialReversalAdvice”.
C2 If Cardholder is present it must have at least one child  CompletionAdvice.Environment.CardHolder
C3 If Context is present it must have at least one child  CompletionAdvice.Context
C4 If SaleContext is present it must have at least one  CompletionAdvice.Context.SaleContext
child
C5 If MessageFunction value is  Header.MessageFunction
“FinancialCompletionAdvice” or  CompletionAdvice.Transaction.TransactionCap
“FinancialReversalAdvice” then TransactionCapture ture
must be “True”. Otherwise it must be ”False”.
C6 FailureReason must be present if TransactionSuccess  CompletionAdvice.Transaction.TransactionSuc
is “False”. cess
 CompletionAdvice.Transaction.FailureReason

- 137 -
Card Payments Message Usage Guide Version 5.0

C7 If TransactionSuccess is "True" then TotalAmount  CompletionAdvice.Transaction.TransactionDet


must be Final amount of the payment transaction. ails.TotalAmount
Otherwhise, TotalAmount is:  CompletionAdvice.Transaction.TransactionSuc
the amount of AuthorisationResponse for an cess
online approval,
the amount of AuthorisationRequest if unable to
go online or timeout,
the purchase amount for an offline authorisation

- 138 -
Card Payments Message Usage Guide Version 5.0

4.3.2 AcceptorCompletionAdviceResponse (caaa.004.001.05)

AcceptorCompletionAdviceRespon Mult. Rule Cstr Usage


se
Header [1..1]
MessageFunction [1..1] C1 The only valid codes are:
CompletionAdviceResponse: response for
CompletionAdvice
FinancialCompletionAdviceResponse: response for
FinancialCompletionAdvice
ReversalAdviceResponse: response for
ReversalAdvice
FinancialReversalAdviceResponse: response for
FinancialReversalAdvice
(in case of an invalid value, a Reject message is sent by
the Recipient with RejectReason equal to ParsingError)
ProtocolVersion [1..1]
ExchangeIdentification [1..1] Copy
RetransmissionCounter [0..1] CCopy
CreationDateTime [1..1]
InitiatingParty [1..1] Copy
Identification [1..1]
Type [1..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RecipientParty [0..1] Copy
Identification [1..1]
Type [1..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Present if present in the completion advice.
see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
ProtocolName [0..1]
ProtocolVersion [0..1]

- 139 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdviceRespon Mult. Rule Cstr Usage


se
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CompletionAdviceResponse [1..1] C1
Environment [1..1]
AcquirerIdentification [0..1] Copy from AcceptorCompletionAdvice if present
Identification [1..1]
Type [0..1] default Acquirer
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1] Copy from AcceptorCompletionAdvice if present
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]

ShortName [0..1]
POIIdentification [1..1] Copy from AcceptorCompletionAdvice
Identification [1..1]
Type [0..1] default OriginatingPOI
Issuer [0..1] Config

ShortName [0..1] Config


Card
ProtectedCardData [0..1] Appli see AcceptorAuthorisationResponse
PlainCardData [0..1] Appli see AcceptorAuthorisationResponse
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1]
CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Copy from AcceptorCompletionAdvice if present
TransactionDateTime [1..1]
TransactionReference [1..1]
[0..1]
InitiatorTransactionIdentification
RecipientTransaction- [0..1] Appli Used by the InitiatingParty when it refers back to the
Identification transaction of the RecipientParty (e.g. reconciliation
mismatch). If supplied, it is mandatory in the completion and
the batch.
ReconciliationIdentification [0..1] see AcceptorAuthorisationResponse
Response [1..1] Approved: the CompletionAdvice is accepted.
For other responses, an error resolution process has to be
performed which is out of scope of the protocol.

- 140 -
Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdviceRespon Mult. Rule Cstr Usage


se
TMSTrigger [0..1] Appli see AcceptorAuthorisationResponse
TMSContactLevel [1..1] C2
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1] C2 Present if TMSContactLevel = DateTime
see AcceptorAuthorisationResponse
SupplementaryData [0..*]
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body CompletionAdviceResponse including the
body envelope, using the MAC key of the related
AcceptorCompletionAdvice message.

4.3.2.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When CompletionAdviceResponse is present the  Header.MessageFunction
Header.MessageFunction must be  CompletionAdviceResponse
“CompletionAdviceResponse”,
“FinancialCompletionAdviceResponse”,
“ReversalAdviceResponse”, “ReversalAdvice”,
“FinancialReversalAdviceResponse”
C2 TMSContactDateTime must be present if  CompletionAdviceResponse.TMSTrigger.
TMSContactLevel = “DateTime” TMSContactDateTime
 CompletionAdviceResponse.TMSTrigger.
TMSContactDateTime

- 141 -
Card Payments Message Usage Guide Version 5.0

4.4 Cancellation Messages

4.4.1 AcceptorCancellationRequest (caaa.005.001.05)

AcceptorCancellationRequest Mult. Rule Cstr Usage


Header [1..1]
MessageFunction [1..1] C1 The only valid code is CancellationRequest (CCAQ) to
request a cancellation for a previously completed
transaction, where the original transaction could not
retrieved at the POI.
(in case of an invalid value, a Reject message is sent by
the Recipient with RejectReason equal to ParsingError)
ProtocolVersion [1..1] see AcceptorAuthorisationRequest
ExchangeIdentification [1..1] see AcceptorAuthorisationRequest
CreationDateTime [1..1] see AcceptorAuthorisationRequest
InitiatingParty [1..1] see AcceptorAuthorisationRequest
Identification [1..1]
Type [0..1]
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
RecipientParty [0..1] Config see AcceptorAuthorisationRequest
Identification [1..1] Config
Type [0..1]
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Config see section 3.2 Traceability
RelayIdentification [1..1] Config
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1] Config
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1] Config
TraceDateTimeOut [1..1]
CancellationRequest [1..1] C1 The Header.MessageFunction must be
CancellationRequest.

- 142 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to “ParsingError”)
Environment [1..1] see AcceptorAuthorisationRequest
Acquirer [0..1] Config
Identification [0..1] Config
Identification [1..1] Appli
Type [0..1] default Acquirer
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
ParametersVersion [1..1] see AcceptorAuthorisationRequest
Merchant [0..1] C2 Present if it contains any data.
see AcceptorAuthorisationRequest
Identification [0..1] Config see AcceptorAuthorisationRequest
Identification [1..1] Appli
Type [0..1] default Merchant
Issuer [0..1] Config
ShortName [0..1] Config
LocationAndContact [0..1]
PostalAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
Email [0..1]
URLAddress [0..1]
Phone [0..1]
CustomerService [0..1]
[0..1]
AdditionalContactInformation
SchemeData [0..1] Config
POI [1..1] see AcceptorAuthorisationRequest
Identification [1..1]
Identification [1..1] Config
Type [0..1] default OriginatingPOI
Issuer [0..1] Config
ShortName [0..1] Config
SystemName [0..1] Config see AcceptorAuthorisationRequest
GroupIdentification [0..1] Config see AcceptorAuthorisationRequest
Capabilities [0..1] Present if it contains any data
see AcceptorAuthorisationRequest
CardReadingCapabilities [0..*] Config
CardholderVerification- [0..*] Config
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]

- 143 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


OnLineCapabilities [0..1] Config
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*] Config see AcceptorAuthorisationRequest
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
Communication- [1..1]
Type
RemoteParty [1..*]
Active [1..1]
SecurityAccess- [0..1]
Modules
SubscriberIdentify [0..1]
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1] Appli see AcceptorAuthorisationRequest
ProtectedCardData [0..1] see AcceptorAuthorisationRequest
PlainCardData [0..1] see AcceptorAuthorisationRequest
PAN [1..1]
CardSequenceNumber [0..1] Appli

- 144 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


EffectiveDate [0..1] Appli
ExpiryDate [1..1]
ServiceCode [0..1] Appli
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
[0..1]
PaymentAccountReference
MaskedPAN [0..1]
IssuerBIN [0..1]

CardCountryCode [0..1] Appli


CardCurrencyCode [0..1]
CardProductProfile [0..1] Config
CardBrand [0..1] Appli
CardProductType [0..1]
AdditionalCardData [0..1] Appli
CustomerDevice [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
TokenAssuranceLevel [0..1]
Context [1..1]
PaymentContext [1..1] Context of the cancellation transaction
CardPresent [0..1] default True
see AcceptorAuthorisationRequest
CardholderPresent [0..1] default True
see AcceptorAuthorisationRequest
AttendanceContext [0..1] Config see AcceptorAuthorisationRequest
TransactionEnvironment [0..1] default Merchant
see AcceptorAuthorisationRequest
TransactionChannel [0..1] Config see AcceptorAuthorisationRequest
AttendantMessageCapable [0..1] C4 default True
Indicates to the acquirer whether a message in the
cancellation response can be displayed to the attendant.
AttendantLanguage [0..1] C4 Present If AttendantMessageCapable is True
Indiciates the language of message in the cancellation
response to be displayed to the attendant
CardDataEntryMode [1..1] The entry mode used to get the card data for the
cancellation, the same values as in the
AcceptorAuthorisationRequest are allowed.
FallbackIndicator [0..1] Appli default False
Alternative for the card data entry mode of the cancellation
transaction.

- 145 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


SaleContext [0..1] Appli C5 Present if it contains any data.
see AcceptorAuthorisationRequest
SaleIdentification [0..1] Appli
SaleReferenceNumber [0..1] Appli
SaleReconciliation- [0..1] Appli
Identification
CashierIdentification [0..1] Appli
ShiftNumber [0..1] Appli
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1] Appli
Transaction [1..1]
TransactionCapture [0..1] Not used in this version
MerchantCategoryCode [1..1] see AcceptorAuthorisationRequest
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Identification of the cancellation transaction assigned by the
POI. This identification must be different from the original
transaction that is being cancelled.
TransactionDateTime [1..1]
TransactionReference [1..1]
OriginalTransaction [1..1] Appli Information about the transaction to be cancelled.
The OriginalTransaction components must have the value
of the related components of the transaction to cancel.
Only one transaction can be cancelled per message
exchange.
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Appli Identification of the transaction to cancel assigned by the
POI.
TransactionDateTime [1..1]
TransactionReference [1..1]
POIIdentification [0..1] Appli POI where the transaction to cancel was performed.
Identification [1..1]
Type [0..1]
ShortName [0..1]
InitiatorTransaction- [0..1] Appli Present if present in the transaction to cancel, with the
Identification same value.
RecipientTransaction- [0..1] Appli Present if present in the transaction to cancel, with the
Identification same value.
TransactionType [1..1] Copy TransactionType of the original transaction.
AdditionalService [0..*] Copy Cancellation of a transaction must cancel all associated
additional services; partial cancellation is not permitted.
ServiceAttribute [0..1] Copy Cancellation of the original transaction cancels the
transaction with its service attributes.
CardDataEntryMode [0..1]

- 146 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


TransactionResult [0..1] Appli TransactionResult of the transaction to cancel.
AuthorisationEntity [0..1] Appli AuthorisationEntity which has approved the transaction to
be cancelled.
see AcceptorAuthorisationResponse
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1] ResponseToAuthorisation of the transaction to be
Authorisation cancelled.
see AcceptorAuthorisationResponse
Response [1..1]
ResponseReason [0..1] Appli
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli AuthorisationCode of the transaction to be cancelled.
see AcceptorAuthorisationResponse
[0..1]
InitiatorTransactionIdentification
[0..1]
RecipientTransactionIdentificatio
n
ReconciliationIdentification [0..1] Appli Identification of the reconciliation period assigned by the
POI to the cancellation transaction.
see AcceptorAuthorisationRequest
TransactionDetails [1..1]
Currency [0..1] Copy Currency of TotalAmount of the transaction to cancel
TotalAmount [1..1] Copy Amount to cancel which is always the TotalAmount of the
approved transaction to cancel. Only the full amount of the
transaction can be cancelled.
ValidityDate [0..1] Appli
ICCRelatedData [0..1] Appli A sequence of one or more TLV data elements in
accordance with ISO 7816-6.
AdditionalTransactionData [0..*] Appli
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body CancellationRequest including the body
envelope.

4.4.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When CancellationRequest is present the  Header.MessageFunction
Header.MessageFunction must be  CancellationRequest
“CancellationRequest “
C2 If Merchant is present it must have at least one child  CancellationRequest.Environment.Merchant
C3 If Capabilities is present it must have at least one child  CancellationRequest.Environment.POI.Capabili
ties
C4 If AttendantMessageCapable is “True” then  CancellationRequest..Context.PaymentContext
AttendantLanguage must be present. AttendantMessageCapable
 CancellationRequest..Context.PaymentContext
AttendantLanguage

- 147 -
Card Payments Message Usage Guide Version 5.0

C5 If Salecontext is present it must have at least one child  CancellationRequest..Context.SaleContext

- 148 -
Card Payments Message Usage Guide Version 5.0

4.4.2 AcceptorCancellationResponse (caaa.006.001.05)

AcceptorCancellationResponse Mult. Rule Cstr Usage


Header [1..1]
MessageFunction [1..1] The only valid codes in a response to a cancellation request
is :
CancellationResponse
ProtocolVersion [1..1] Copy C1 The Recipient Party has to adapt the
AcceptorCacellationResponse format to the version of the
Initiator sent in the AcceptorCancellationRequest. If this
version is not supported the Recipient must reject the
request.
ExchangeIdentification [1..1] Copy
CreationDateTime [1..1] see AcceptorAuthorisationResponse
InitiatingParty [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1]
ShortName [0..1] Copy
RecipientParty [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1]
ShortName [0..1] Copy
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Present if present in the request.
see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1]
ShortName [0..1] Copy
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CancellationResponse [1..1] C1
Environment [1..1]
AcquirerIdentification [0..1] Appli see AcceptorAuthorisationResponse

- 149 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationResponse Mult. Rule Cstr Usage


Identification [1..1]
Type [0..1] default Acquirer
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1] see AcceptorAuthorisationResponse
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
ShortName [0..1]
POIIdentification [1..1] Appli see AcceptorAuthorisationResponse
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
Card [0..1]
ProtectedCardData [0..1] Appli see AcceptorAuthorisationResponse
PlainCardData [0..1] Appli see AcceptorAuthorisationResponse
PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1]
CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Copy see AcceptorAuthorisationResponse
TransactionDateTime [1..1]
TransactionReference [1..1]
[0..1]
InitiatorTransactionIdentification
RecipientTransaction- [0..1] Appli see AcceptorAuthorisationResponse
Identification
ReconciliationIdentification [0..1] Copy or see AcceptorAuthorisationResponse
Appli
InterchangeData [0..1] Appli see AcceptorAuthorisationResponse
TransactionDetails [1..1]
Currency [1..1] Copy
TotalAmount [1..1] Amount to cancel which is always the TotalAmount of the
transaction to cancel. Only the full amount of the transaction
can be cancelled.
ICCRelatedData [0..1]
TransactionResponse [1..1]
AuthorisationResult [1..1] Outcome of the CancellationRequest
AuthorisationEntity [0..1] Qualify and allows recognition the entity which has
authorises the cancellation offline or line:
see AcceptorAuthorisationResponse

- 150 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationResponse Mult. Rule Cstr Usage


Identification [0..1]
Type [1..1]
Issuer [0..1] Appli
Country [0..1]
ShortName [0..1] Appli
ResponseToAuthorisation [1..1]
Response [1..1] * Valid values are:
Approved: cancellation is approved, including capture if
requested.
Declined: cancellation is declined.

ResponseReason [0..1] Appli see AcceptorAuthorisationResponse


[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli
TMSTrigger [0..1] Appli see AcceptorAuthorisationResponse
TMSContactLevel [1..1] C2
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1] C2 Present if TMSContactLevel = DateTime
Action [0..*] Appli see AcceptorAuthorisationResponse
ActionType [1..1] * Allowed values: Busy, CaptureCard, DisplayMessage or
C3 PrintMessage
MessageToPresent [0..1] C3 if ActionType is DisplayMessage or PrintMessage
MessageDestination [1..1]
Format [0..1]
MessageContent [1..1]
MessageContent- [0..1] Appli
Signature
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body CancellationResponse including the body
envelope, using the MAC key of the related
AcceptorCancellationRequest message.

4.4.2.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When CancellationResponse is present the  Header.MessageFunction
Header.MessageFunction must be  CancellationResponse
“CancellationResponse”
C2 TMSContactDateTime must be present if  CancellationResponse.TMSTrigger.
TMSContactLevel = “DateTime” TMSContactDateTime
 CancellationResponse.TMSTrigger.
TMSContactDateTime
C3 MessageToPresent must be present if ActionType is  CancellationResponse.TransactionResponse.A
“DisplayMessage” or “PrintMessage” ction.ActionType
 CancellationResponse.TransactionResponse.A
ction.MessageToPresent

- 151 -
Card Payments Message Usage Guide Version 5.0

4.4.3 AcceptorCancellationAdvice (caaa.007.001.05)

AcceptorCancellationAdvice Mult. Rule Cstr Usage


Header [1..1]
MessageFunction [1..1] C1 The only valid code to advice a cancellation for a previously
completed transaction is :
CancellationAdvice (CCAV)
ProtocolVersion [1..1] see AcceptorAuthorisationRequest
ExchangeIdentification [1..1] see AcceptorAuthorisationRequest
RetransmissionCounter [0..1] default 0
see 3.3 Message Retransmission
CreationDateTime [1..1] see AcceptorAuthorisationRequest
InitiatingParty [1..1] see AcceptorAuthorisationRequest
Identification [1..1]
Type [0..1] Config
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Config see AcceptorAuthorisationRequest
Identification [1..1]
Type [0..1] Config
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Config see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CancellationAdvice [1..1] C1 The Header.MessageFunction must be CancellationAdvice.
(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)
Environment [1..1]
Acquirer [0..1] Config see AcceptorAuthorisationRequest
Identification [0..1] Config

- 152 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdvice Mult. Rule Cstr Usage


Identification [1..1] Appli
Type [0..1] default Acquirer
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
ParametersVersion [1..1] see AcceptorAuthorisationRequest and
AcceptorCompletionAdvice
Merchant [0..1] see AcceptorAuthorisationRequest
Identification [0..1] Config
Identification [1..1] Appli
Type [0..1] default Merchant
Issuer [0..1] Config
ShortName [0..1] Config
CommonName [0..1] Config
LocationCategory [0..1] Config
LocationAndContact [0..1] Config
SchemeData [0..1] Config
POI [1..1]
Identification [1..1] see AcceptorAuthorisationRequest
Identification [1..1] Config
Type [0..1] default OriginatingPOI
Issuer [0..1] Config
ShortName [0..1] Config
SystemName [0..1] Config
GroupIdentification [0..1] Config
Capabilities [0..1] C2 Present if it contains any data
see AcceptorAuthorisationRequest
CardReadingCapabilities [0..*] Config
CardholderVerification- [0..*] Config
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1] Config
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*] Config see AcceptorAuthorisationRequest
Type [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]

- 153 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdvice Mult. Rule Cstr Usage


VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
Communication- [1..1]
Type
RemoteParty [1..*]
Active [1..1]
SecurityAccess- [0..1]
Modules
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1] Appli Card components retrieved from the transaction to cancel
(e.g. log or receipt), or read from the card.
ProtectedCardData [0..1] see AcceptorAuthorisationRequest
PlainCardData [0..1] see AcceptorAuthorisationRequest
PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
ServiceCode [0..1] Appli
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
IssuerBIN [0..1]
CardCountryCode [0..1] Appli see AcceptorAuthorisationRequest
CardCurrencyCode [0..1]
CardProductProfile [0..1] Config see AcceptorAuthorisationRequest
CardBrand [0..1] Appli see AcceptorAuthorisationRequest
CardProductType [0..1]
AdditionalCardData [0..1] Appli see AcceptorAuthorisationRequest
CustomerDevice [0..1]

- 154 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdvice Mult. Rule Cstr Usage


Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
TokenAssuranceLevel [0..1]
Context [0..1] C3 Present if it contains any data
PaymentContext [1..1] Context of the cancellation transaction
CardPresent [0..1] default True
see AcceptorAuthorisationRequest
CardholderPresent [0..1] default True
see AcceptorAuthorisationRequest
OnlineContext [0..1] default True
True if a CancellationRequest has been sent previously.
AttendanceContext [0..1] Config default Attended
see AcceptorAuthorisationRequest
TransactionEnvironment [0..1] default Merchant
see AcceptorAuthorisationRequest
TransactionChannel [0..1] Config see AcceptorAuthorisationRequest
CardDataEntryMode [1..1] see AcceptorAuthorisationRequest
FallbackIndicator [0..1] default False
see AcceptorAuthorisationRequest
SaleContext [0..1] C4 Present if it contains any data.
Context of the cancellation transaction
see AcceptorAuthorisationRequest
SaleIdentification [0..1] Appli
SaleReferenceNumber [0..1] Appli
SaleReconciliation- [0..1] Appli
Identification
CashierIdentification [0..1] Appli
ShiftNumber [0..1] Appli
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1] Appli
Transaction [1..1]

- 155 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdvice Mult. Rule Cstr Usage


MerchantCategoryCode [1..1] see AcceptorAuthorisationRequest
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Identification of the cancellation transaction assigned by the
POI. This identification must be different from the original
transaction to cancel, but the same as in the
AcceptorCancellationRequest if any.
TransactionDateTime [1..1] see AcceptorAuthorisationRequest
TransactionReference [1..1] see AcceptorAuthorisationRequest
OriginalTransaction [0..1] see AcceptorCancellationRequest
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Appli see AcceptorCancellationRequest
TransactionDateTime [1..1]
TransactionReference [1..1]
POIIdentification [0..1] Appli see AcceptorCancellationRequest
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
InitiatorTransaction- [0..1] Appli see AcceptorCancellationRequest
Identification
RecipientTransaction- [0..1] Appli see AcceptorCancellationRequest
Identification
TransactionType [1..1] Copy see AcceptorCancellationRequest
AdditionalService [0..*] see AcceptorCancellationRequest
ServiceAttribute [0..1] see AcceptorCancellationRequest
CardDataEntryMode [0..1]
TransactionResult [0..1] Appli see AcceptorCancellationRequest
AuthorisationEntity [0..1] Appli AuthorisationEntity which has approved the transaction to
cancel.
see AcceptorAuthorisationResponse
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1] ResponseToAuthorisation of the transaction to cancel.
Authorisation see AcceptorAuthorisationResponse
Response [1..1]
ResponseReason [0..1] Appli
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli AuthorisationCode of the transaction to cancel.
see AcceptorAuthorisationResponse
TransactionSuccess [1..1]
Reversal [0..1] Default: False
True: no acceptable CancellationResponse message has
been received, or cancellation couldn't be completed
successfully after an approved cancellation request.
FailureReason [0..*] * No acceptable CancellationResponse message has been
received.
Allowed values: Malfunction or Timeout (see
AcceptorCompletionAdvice).
[0..1]
InitiatorTransactionIdentification

- 156 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdvice Mult. Rule Cstr Usage


RecipientTransaction- [0..1] Appli see AcceptorCancellationRequest
Identification
ReconciliationIdentification [0..1] Appli Identification of the reconciliation period assigned by the
POI to the cancellation transaction.
see AcceptorCompletionAdvice
InterchangeData [0..1] Appli see AcceptorCompletionAdvice
TransactionDetails [1..1]
Currency [1..1] copy Currency of TotalAmount of the transaction to cancel
TotalAmount [1..1] copy TotalAmount of the transaction to cancel
ValidityDate [0..1] Appli
ICCRelatedData [0..1] Appli A sequence of one or more TLV data elements in
accordance with ISO 7816-6.
AuthorisationResult [0..1] Result of the outcome of the
AcceptorCancellationResponse if any.
AuthorisationEntity [0..1] see AcceptorCancellationResponse
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseToAuthorisation [1..1] see AcceptorCancellationResponse
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
AdditionalTransactionData [0..*] Appli
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body CancellationAdvice including the body
envelope.

4.4.3.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When CancellationAdvice is present the  Header.MessageFunction
Header.MessageFunction must be  CancellationAdvice
“CancellationAdvice”
C2 If Capabilities is present it must have at least one child  CancellationAdvice.Environment.POI.Capabiliti
es
C3 If Context is present it must have at least one child  CancellationAdvice.Context
C4 If SaleContext is present it must have at least one  CancellationAdvice.Context.SaleContext
child

- 157 -
Card Payments Message Usage Guide Version 5.0

4.4.4 AcceptorCancellationAdviceResponse (caaa.008.001.05)

AcceptorCancellationAdviceRespon Mult. Rule Cstr Usage


se
Header [1..1]
MessageFunction [1..1] The only valid code in a response to a cancellation advice
is:
CancellationAdviceResponse
ProtocolVersion [1..1] Copy
ExchangeIdentification [1..1] Copy
ReTransmissionCounter [0..1] CCopy
CreationDateTime [1..1] see AcceptorCompletionAdviceResponse
InitiatingParty [1..1] Copy
Identification [1..1] Copy
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RecipientParty [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*] Present if present in the advice.
see section 3.2 Traceability
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
AcceptorCancellationAdvice- [1..1]
Response
Environment [1..1]
AcquirerIdentification [0..1] Appli Copy from AcceptorCancellationAdvice if present
Identification [1..1]

- 158 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationAdviceRespon Mult. Rule Cstr Usage


se
Type [0..1] default Acquirer
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1] see AcceptorCompletionAdviceResponse
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
ShortName [0..1]
POIIdentification [1..1] Copy
Identification [1..1]
Type [0..1] default OriginatingPOI
Issuer [0..1]
ShortName [0..1]
Card [0..1]
ProtectedCardData [0..1] Appli see AcceptorAuthorisationResponse
PlainCardData [0..1] Appli see AcceptorAuthorisationResponse
PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1]
CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] Copy For verification.
TransactionDateTime [1..1]
TransactionReference [1..1]
[0..1]
InitiatorTransactionIdentification
RecipientTransaction- [0..1] Appli Used by the InitiatingParty when it refers back to the
Identification transaction of the RecipientParty (e.g. reconciliation
mismatch). If supplied, it is mandatory in the completion and
the batch.
ReconciliationIdentification [0..1] see AcceptorAuthorisationResponse
Response [1..1] see AcceptorCompletionAdvice.
TMSTrigger [0..1] Appli see AcceptorAuthorisationResponse
TMSContactLevel [1..1]
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1] Present if TMSContactLevel = DateTime
see AcceptorAuthorisationResponse

SecurityTrailer [0..1] CMS data structure ContentInfoType with the


AuthenticatedData alternative, containing the MAC of the
message body CancellationAdviceResponse including the
body envelope, using the MAC key of the related
AcceptorCancellationAdvice message.

- 159 -
Card Payments Message Usage Guide Version 5.0

- 160 -
Card Payments Message Usage Guide Version 5.0

4.5 Reconciliation Messages

4.5.1 AcceptorReconciliationRequest (caaa.009.001.05)

AcceptorReconciliationRequest Mult. Rule Cstr Usage


Header [1..1] Unless stated otherwise, see AcceptorAuthorisationRequest
message header usage.
MessageFunction [1..1] C1 The only valid code to request the reconciliation is
ReconciliationRequest.
ProtocolVersion [1..1]
ExchangeIdentification [1..1]
CreationDateTime [1..1]
InitiatingParty [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RecipientParty [0..1] Config
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
ReconciliationRequest [1..1] C1 The Header.MessageFunction must be
ReconciliationRequest.
(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)

- 161 -
Card Payments Message Usage Guide Version 5.0

AcceptorReconciliationRequest Mult. Rule Cstr Usage


Environment [1..1]
Acquirer [1..1]
Identification [0..1] Appli
Identification [1..1]
Type [1..1]
Issuer [0..1] default Acquirer
Country
ShortName [0..1]
ParametersVersion [1..1]
MerchantIdentification [0..1] Appli Present if reconciliation groups transactions performed by
the same Merchant.
see AcceptorAuthorisationRequest
Identification [1..1]
Type [1..1]
Issuer [0..1] default Merchant
Country [0..1]
ShortName [0..1]
POIIdentification [0..1] Appli Absent if the reconciliation groups transactions from several
POI terminals.
This identification can also group all the POI terminals of a
POI system.
see AcceptorAuthorisationRequest
Identification [1..1]
Type [1..1]
Issuer [0..1] default OriginatingPOI
Country
ShortName [0..1]
Transaction [1..1]
ClosePeriod [0..1] default True
True: notifies that the reconciliation period must be
closed after the reconciliation exchange.
False: the current reconciliation period must stay open
after this exchange.
ReconciliationTransaction- [1..1] Identification of the reconciliation transaction.
Identification
TransactionDateTime [1..1]
TransactionReference [1..1]
ReconciliationIdentification [1..1] Identification of the reconciliation period.
If ClosePeriod is True, ReconciliationIdentification identifies
the current reconciliation period.
If ClosePeriod is False, ReconciliationIdentification
identifies the current or a closed reconciliation period.
TransactionTotals [0..*] TransactionTotals of the reconciliation period.
TransactionTotals is absent if the reconciliation period
contains no transactions.
POIGroupIdentification [0..1] Appli Collection of transactions containing this value sent in the
POI.GroupIdentification component of the message request
and advice.
CardProductProfile [0..1] Appli Collection of transactions containing this value sent in the
Card.CardProductProfile component of the message
request and advice.
Currency [0..1] Appli Currency is present when TransactionTotals are computed
per currency (TMS configuration parameter
AcquirerProtocolParameters.TotalsPerCurrency is True).
Type [1..1] * All the values are allowed:
Debit: Debit transactions (TransactionType is
CardPayment, CashBack, CashAdvance,

- 162 -
Card Payments Message Usage Guide Version 5.0

AcceptorReconciliationRequest Mult. Rule Cstr Usage


DeferredPayment) during the reconciliation period.
DebitReverse: Cancelled debit transactions.
Credit: Credit transactions (TransactionType is Refund)
during the reconciliation period.
CreditReverse: Cancelled credit transactions.
Declined: transactions declined online or offline.
Failed: failed transactions.
TotalNumber [1..1] * Total number of transactions for the related Type, Currency,
CardProductProfile and POIGroupIdentification, performed
by the InitiatingParty during the reconciliation period
ReconciliationIdentification.
CumulativeAmount [1..1] * Total amount of transactions for the related Type, Currency,
CardProductProfile and POIGroupIdentification, performed
by the InitiatingParty during the reconciliation period
ReconciliationIdentification.
AdditionalTransactionData [0..1] Appli
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body ReconciliationRequest including the body
envelope.

4.5.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When ReconciliationRequest is present the  Header.MessageFunction
Header.MessageFunction must be  ReconciliationRequest
“ReconciliationRequest”

- 163 -
Card Payments Message Usage Guide Version 5.0

4.5.2 AcceptorReconciliationResponse (caaa.010.001.05)

AcceptorReconciliationResponse Mult. Rule Cstr Usage


Header [1..1] Unless stated otherwise, see Authorisation Response
message header usage.
MessageFunction [1..1] C1 The only valid code to request the reconciliation is
ReconciliationResponse.
ProtocolVersion [1..1]
ExchangeIdentification [1..1] Copy
CreationDateTime [1..1]
InitiatingParty [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RecipientParty [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
ReconciliationResponse [1..1] C1 The Header.MessageFunction must be
ReconciliationResponse.
(if not the case, a Reject message is sent by the
RecipientParty with RejectReason equal to ParsingError)
Environment [1..1]
AcquirerIdentification [0..1] Copy
Identification [1..1]
Type [1..1] default Acquirer

- 164 -
Card Payments Message Usage Guide Version 5.0

AcceptorReconciliationResponse Mult. Rule Cstr Usage


Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1] CCopy see AcceptorCompletionAdviceResponse
Identification [1..1]
Type [1..1] default Merchant
Issuer [0..1]
ShortName [0..1]
POIIdentification [0..1] Copy
Identification [1..1]
Type [1..1] default OriginatingPOI
Issuer [0..1]
ShortName [0..1]
TransactionResponse [1..1]
Response [1..1] * The following codes are allowed:
Approved: The reconciliation is accepted, totals of
transactions performed by the Recipient are provided
in the response, or not computed in real-time.
Declined: Totals are different.
ResponseReason [0..1] One of the reasons defined in section 2.6.4 p. 72, if
Response is not Approved.
[0..1]
AdditionalResponseInformation
Transaction [1..1]
ClosePeriod [0..1] Copy
ReconciliationTransaction- [1..1] Copy
Identification
TransactionDateTime [1..1]
TransactionReference [1..1]
ReconciliationIdentification [1..1] Copy if the value of the request is not 0, otherwise put the
last used value of the ReconciliationIdentification.
TransactionTotals [0..*] TransactionTotals is absent if the reconciliation period
contains no transactions, or the totals computation is not
performed in real-time by the acquirer.
The sequence of TransactionTotals components, if present,
must be in the same order as the request, according to the
value of Type, Currency, CardProductProfile and
POIGroupIdentification.
In case of discrepancy, additional TransactionTotals must
be located at the end of the sequence.
POIGroupIdentification [0..1] Appli see AcceptorReconciliationRequest
CardProductProfile [0..1] Appli see AcceptorReconciliationRequest
Currency [0..1] Appli see AcceptorReconciliationRequest
Type [1..1]
TotalNumber [1..1] * Total number of transactions for the related Type, Currency,
CardProductProfile and POIGroupIdentification, performed
by the RecipientParty during the reconciliation period
ReconciliationIdentification. The value can be zero.
CumulativeAmount [1..1] * Sum of TotalAmount of transactions for the related Type,
Currency, CardProductProfile and POIGroupIdentification,
performed by the RecipientParty during the reconciliation
period ReconciliationIdentification. The value can be zero.
AdditionalTransactionData [0..1] Appli
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body ReconciliationResponse including the body
envelope, using the MAC key of the related
AcceptorReconciliationRequest message.

- 165 -
Card Payments Message Usage Guide Version 5.0

4.5.2.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When ReconciliationResponse is present the  Header.MessageFunction
Header.MessageFunction must be  ReconciliationResponse
“ReconciliationResponse”

- 166 -
Card Payments Message Usage Guide Version 5.0

4.6 Batch

4.6.1 AcceptorBatchTransfer (caaa.011.001.05)

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Header [1..1]
DownloadTransfer [1..1] True if BatchTransfer/Transaction occurrences
contain AuthorisationResponse.
False otherwise
FormatVersion [1..1] Same value as ProtocolVersion
see AcceptorAuthorisationRequest
ExchangeIdentification [1..1] Unique identifier for the InitiatingParty to detect
duplication of the transfer for a period of time.
It is a cyclic counter that increments by one with
each new transfer between the InitiatingParty
and the RecipientParty.
CreationDateTime [1..1] Date and time of the file creation. Time
accuracy has to be at least tenth of a second.
InitiatingParty [1..1] see AcceptorAuthorisationRequest
Identification [1..1] The value of this identifier is bilaterally agreed
between InitiatingParty and RecipientParty. The
Recipient of the message must identify without
ambiguity the Initiator of the message.
Type [0..1] Appli Indicates the type of InitiatingParty:
Acceptor, Merchant, OriginatingPOI,
IntermediaryAgent.
Issuer [0..1] Config Indicates the assigner for identifying the
InitiatingParty.
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Config Information used to identify the recipient of an
exchange. The structure and content is
bilaterally agreed between InitiatingParty and
RecipientParty.
Identification [1..1]
Type [0..1] Indicates the type of RecipientParty:
Acceptor, Merchant, IntermediaryAgent,
Acquirer, DelegateIssuer.
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
BatchTransfer [1..1]

- 167 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


TransactionTotals [0.*] Appli TransactionTotals of the whole BatchTransfer.
TransactionTotals is absent if the batch
contains no transactions.
POIGroupIdentification [0..1] Appli see AcceptorReconciliationRequest
CardProductProfile [0..1] Appli see AcceptorReconciliationRequest
Currency [0..1] see AcceptorReconciliationRequest
Type [1..1] see AcceptorReconciliationRequest
TotalNumber [1..1] see AcceptorReconciliationRequest
CumulativeAmount [1..1] see AcceptorReconciliationRequest
DataSet [0..*] A data set may include both financial
(completed transactions) and non financial
transactions (uncompleted transactions).
DataSetIdentification [1..1] Unique identifier for each of the DataSet for the
InitiatingParty
Name [1..1] Identifier of the DataSet for the InitiatingParty
Type [1..1] BatchCapture
Version [0..1] Not used in batch capture context
CreationDateTime [1..1] Date and time of the creation of the data set.
Time accuracy has to be at least tenth of a
second
Traceability [0..*] Config An intermediary Agent must include its own
traceability info, if traceability was present in the
data set received and if the data set is
forwarded with the same transactions.
RelayIdentification [1..1] Information used to identify the recipient of an
exchange. The structure and content is
bilaterally agreed between InitiatingParty and
RecipientParty.
Identification [1..1]
Type [1..1] Indicates the type of RecipientParty:
Acceptor, Merchant, IntermediaryAgent,
Acquirer, DelegateIssuer:
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
DataSetInitiator [0..1] Config The initiating party and the dataset initiator can
be the same entity. If not, it is possible for each
data set to identify the entity that creates it by
populating DataSetInitiator.
Identification [1..1] Information used to identify the initiator of a
dataset. The structure and content is bilaterally
agreed between InitiatingParty and
RecipientParty.
Type [0..1] Indicates the type of DataSetInitiator
Acceptor, Merchant, OriginatingPOI,
IntermediaryAgent:
default OriginatingPOI
Issuer [0..1] Indicates the assigner for identifying the
DatasetInitiator.
Acceptor, Merchant, , IntermediaryAgent,
acquirer:
Country [0..1]
ShortName [0..1]
TransactionTotals [1..*] TransactionTotals of the DataSet.

- 168 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


POIGroupIdentification [0..1] Appli see AcceptorReconciliationRequest
CardProductProfile [0..1] Config see AcceptorReconciliationRequest
Currency [0..1] Appli see AcceptorReconciliationRequest
Type [1..1] see AcceptorReconciliationRequest
TotalNumber [1..1] see AcceptorReconciliationRequest
CumulativeAmount [1..1] see AcceptorReconciliationRequest
CommonData [0..1] Data common to transactions of a DataSet may
be factorised in CommonData to reduce the
message length.
All transactions of the DataSet inherit the data
element value present in CommonData except
if this data element is present in the occurrence
of TransactionToCapture.
Environment [0..1]
Acquirer [0..1]
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ParametersVersion [0..1]
Merchant [0..1]
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
CommonName [0..1]
LocationCategory [0..1]
Address [0..1]
CountryCode [0..1]
SchemeData [0..1]
POI [0..1] C1
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentification [0..1]
Capabilities [0..1]
CardReadingCapabilities [0..*]
CardholderVerification- [0..*]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1]
MessageCapabilities [0..*]

- 169 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*]
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
CommunicationType [1..1]
RemoteParty [1..*]
Active [1..1]
SecurityAccessModules [0..1]
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Context [0..1] CardPaymentContext3 CardPaymentContext4
PaymentContext [0..1] PaymentContext1 PaymentContex4
CardPresent [0..1]
CardholderPresent [0..1]
OnlineContext [0..1]

- 170 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


AttendanceContext [0..1]
TransactionEnvironment [0..1]
TransactioChannel [0..1]
AttendantMessageCapable [0..1]
AttendantLanguage [0..1]
CardDataEntryMode [0..1]
FallbackIndicator [0..1]
SupportedOption [0..*]
SaleContext [0..1]
SaleIdentification [0..1]
SaleReferenceNumber [0..1]
SaleReconciliation- [0..1]
Identification
CashierIdentification [0..1]
ShiftNumber [0..1]
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1]
TransactionType [0..1] see AcceptorAuthorisationRequest.
AdditionalService [0..*]
ServiceAttribute [0..1]
MerchantCategoryCode [0..1] C3
ReconciliationIdentification [0..1]
Currency [0..1]
Transaction [1..*] Transaction of the data set.It must be a
completion, a cancellation advice, an
authorisation request or an authorisation
response.
{Or Completion [1..1]
TransactionSequenceCounter [1..1] Sequential number assigned for each
transaction of the DataSet to identify the
rejected transactions in the related
AcceptorBatchTransferResponse. The
TransactionSequenceCounter must be
increased for each transaction in the data set.
Traceability [0..*] Config An intermediary Agent must include its own
traceability info, if present in the previous
reorganisation of the batch file
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1] Config
Country [0..1]
ShortName [0..1] Config

- 171 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
Environment [1..1]
Acquirer [0..1] Config see AcceptorCompletionAdvice
Identification [0..1]
Identification [1..1]
Type [0..1] default Acquirer
see AcceptorAuthorisationRequest
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ParametersVersion [1..1] To be optional in future version.
see AcceptorCompletionAdvice
Merchant [0..1] CCopy see AcceptorCompletionAdvice
Identification [0..1]
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
ShortName [0..1]
CommonName [0..1]
LocationCategory [0..1]
LocationAndContact [0..1] Config
PostalAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
Email [0..1]
URLAddress [0..1]
Phone [0..1]
CustomerService [0..1]
[0..1]
AdditionalContactInformation
SchemeData [0..1]
POI [0..1] C1 Mandatory if absent from CommonData.
see AcceptorCompletionAdvice
Identification [1..1]
Identification [1..1]
Type [0..1] default OriginatingPOI
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentifier [0..1]
Capabilities [0..1]
CardReading- [0..*]
Capabilities

- 172 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


CardholderVerification- [0..*]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1]
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*] see AcceptorAuthorisationRequest
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
CommunicationType [1..1]
RemoteParty [1..*]
Active [1..1]
SecurityAccessModules [0..1]
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]

- 173 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


ExpirationDate [0..1]
Number [1..1]
Card [1..1] Appli
ProtectedCardData [0..1] see AcceptorAuthorisationRequest
ContentType [1..1]
EnvelopedData [1..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1] Appli
EffectiveDate [0..1] Appli
ExpiryDate [1..1]
ServiceCode [0..1] Appli
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
IssuerBIN
CardCountryCode [0..1] Appli see AcceptorAuthorisationRequest
CardCurrencyCode
CardProductProfile [0..1] Config see AcceptorAuthorisationRequest
CardBrand [0..1] Appli see AcceptorAuthorisationRequest
AdditionalCardData [0..1] Appli see AcceptorAuthorisationRequest
CustomerDevice [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
TokenAssuranceLevel [0..1]
Cardholder [0..1] see AcceptorCompletionAdvice
Identification [0..*]
DriverLicenseNumber [0..1]
DriverLicenseLocation [0..1]
DriverLicenseName [0..1]
DriverIdentification [0..1]
CustomerNumber [0..1]
SocialSecurityNumber [0..1]
[0..1]
AlienRegistrationNumber
PassportNumber [0..1]
[0..1]
TaxIdentificationNumber

- 174 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


IdentityCardNumber [0..1]
[0..1]
EmplyerIdentificationNumber
[0..1]
EmployeeIdentificationNumber
JobNumber [0..1]
Department [0..1]
EmailAddress [0..1]
DateAndPlaceOfbirth [0..1]
BirthDate [1..1]
ProvinceOfBirth [0..1]
CityOfBirth [1..1]
CountryOfBirth [1..1]
Other [0..*]
Identification [1..1]
IdentificationType [1..1]
Name [0..1]
Language [0..1]
BillingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
ShippingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
TripNumber [0..1]
Vehicle [0..1]
VehicleNumber [0..1]
TrailerNumber [0..1]
VehicleTag [0..1]
VehicleTagEntryMode [0..1]
UnitNumber [0..1]
ReplacementCar [0..1]
Odometer [0..1]
Hubometer [0..1]
TrailerHours [0..1]
ReferHours [0..1]
[0..1]
MaintenanceIdentification
DriverOrVehicleCard [0..1]
PAN [0..1]
Track1 [0..1]

- 175 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Track2 [0..1]
Track3 [0..1]
AdditionalVehicleData [0..*]
Type [0..1]
EntryMode [0..1]
Data [1..1]
PersonalData [0..1]
ProtectedCarholderData [0..1]
Context [0..1] C2 Present if it contains any data
PaymentContext [0..1] see AcceptorCompletionAdvice
CardPresent [0..1]
CardholderPresent [0..1]
OnlineContext [0..1] see AcceptorCompletionAdvice.
AttendanceContext [0..1]
TransactionEnvironment [0..1]
TransactionChannel [0..1]
AttendantMessageCapable [0..1]
AttendantLanguage [0..1]
CardDataEntryMode [0..1]
FallbackIndicator [0..1]
SupportedOption [0..*]
SaleContext [0..1] see AcceptorCompletionAdvice
SaleIdentification [0..1]
SaleReferenceNumber [0..1]
SaleReconciliation- [0..1]
Identification
CashierIdentification [0..1]
ShiftNumber [0..1]
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1]
Transaction [1..1]
TransactionType [0..1] CardPayment or Refund
AdditionalService [0..*] see AcceptorCompletionAdvice
ServiceAttribute [0..1] Not used for card payment
MerchantCategoryCode [0..1] C3 Mandatory If absent from CommonData
see AcceptorCompletionAdvice
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1] see AcceptorCompletionAdvice
TransactionDateTime [1..1]
TransactionReference [1..1]

- 176 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


OriginalTransaction [0..1] Appli see AcceptorCompletionAdvice
[0..1]
SaleReferenceIdentification
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
POIIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
InitiatorTransaction- [0..1]
Identification
RecipientTransaction- [0..1]
Identification
TransactionType [1..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
CardDataEntryMode [0..1]
TransactionResult [0..1]
AuthorisationEntity [0..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1]
Authorisation
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
TransactionSuccess [1..1] see AcceptorCompletionAdvice
Reversal [0..1] default False
see AcceptorCompletionAdvice
MerchantOverride [0..1] Appli default False
see AcceptorCompletionAdvice
FailureReason [0..*] Appli. see AcceptorCompletionAdvice

InitiatorTransaction- [0..1] Appli


Identification
RecipientTransaction- [0..1] Appli see AcceptorCompletionAdvice
Identification
ReconciliationIdentification [0..1] Appli Not used for batch
InterchangeData [0..1] Appli see AcceptorCompletionAdvice
TransactionDetails [1..1]
Currency [0..1] Mandatory if absent from CommonData
TotalAmount [1..1]
AmountQualifier [0..1] Appli
DetailedAmount [0..1] Appli
[0..1]
AmountOfGoodAndServices

- 177 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
RequestAmount [0..1]
AuthorisedAmount [0..1]
InvoiceAmount [0..1]
ValidityDate [0..1]
UnattendedLevelCategory [0..1] Appli see AcceptorCompletionAdvice
AccountType [0..1] Appli defaut Default
see AcceptorAuthorisationRequest
CurrencyConversionResult [0..1]
AcceptedByCardholder [0..1]
Conversion [0..1]
[0..1]
CurrencyConversionIdentification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
[0..1]
InvertedExchangeRate
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]
CommissionDetails [0..*]
Amount [1..1]
[0..1]
AdditionalInformation
MarkUpDetails [0..*]
Rate [1..1]
[0..1]
AdditionalInformation

- 178 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


DeclarationDetails [0..1]
Format [0..1]
MessageContent [1..1]
Instalment [0..1]
InstalmentPlan [0..*]
PlanIdentification [0..1]
SequenceNumber [0..1]
PeriodUnit [0..1]
InstalmentPeriod [0..1]
[0..1]
TotalNumberOfPayments
FirstPaymentDate [0..1]
TotalAmount [0..1]
FirstAmount [0..1]
Charges [0..1]
AggregationTransaction [0..1]
FirstPaymentDateTime [0..1]
LastPaymentDateTime [0..1]
NumberOfPayments [0..1]
IndividualPayment [0..*]
Amount [1..1]
DateTime [1..1]
CardDataEntryMode [0..1]
ICCRelatedData [0..1]
Label [0..1]
[0..1]
ProductCodeSetIdentification
SaleItem [0..*]
ItemIdentification [0..1]
ProductCode [1..1]
AdditionalProductCode [0..1]
UnitOfMeasure [0..1]
ProductQuantity [0..1]
UnitPrice [0..1]
UnitPriceSign [0..1]
ProductAmount [1..1]
ProductAmountSign [0..1]
ValueAddedTax [0..1]
TaxType [0..1]
ProductDescription [0..1]
DeliveryLocation [0..1]
DeliveryService [0..1]
DeliveryLocation [0..1]
CardPaymentInvoice [0..1]
InvoiceHeader [1..1]
Identification [1..1]
TypeCode [1..1]
Name [0..*]
IssueDateTime [1..1]
Issuer [0..1]

- 179 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


PartyIdentification [1..1]
LegalOrganisation [0..1]
Identification [0..1]
Name [0..1]
TaxParty [0..*]

LanguageCode [0..1]
CopyIndicator [0..1]
DocumentPurpose [0..1]
IncludedNote [0..*]
InformationType [1..1]
InformationValue [1..1]
TradeAgrrement [1..1]
TradeDelivery [1..1]
LineItem [0..*]
ICCRelatedData [0..1] Appli A sequence of one or more TLV data elements
in accordance with ISO 7816-6
AuthorisationResult [0..1] Appli
AuthorisationEntity [0..1] see AcceptorAuthorisationResponse
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseToAuthorisation [1..1] see AcceptorAuthorisationResponse
Response [1..1]
ResponseReason [0..1] Appli
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1] Appli see AcceptorAuthorisationResponse
CompletionRequired [0..1] Copy from AuthorisationResponse
TMSTrigger [0..1] Appli
TMSContactLevel [1..1]
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1]
TransactionVerification- [0..1] Appli
Result
Method [1..1]
VerificationEntity [0..1]
Result [0..1]
AdditionalResult [0..1]
AdditionalTransactionData [0..*] Appli
Or Cancellation [0..1] Cancelled card payment transaction.
TransactionSequenceCounter [1..1] see Completion/TransactionSequenceCounter
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]

- 180 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
Environment [1..1] see AcceptorCancellationAdvice
Acquirer [0..1]
Identification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ParametersVersion [1..1]
Merchant [0..1]
Identification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
CommonName [0..1]
LocationCategory [0..1]
LocationAndContact [0..1] Config
PostalAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
Email [0..1]
URLAddress [0..1]
Phone [0..1]
CustomerService [0..1]
[0..1]
AdditionalContactInformation
SchemeData [0..1]
POI [0..1]
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentifier [0..1]
Capabilities [0..1]
CardReading- [0..*]
Capabilities
CardholderVerification- [0..*]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]

- 181 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


CardCaptureCapable [0..1]
OnLineCapabilities [0..1]
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*]
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
CommunicationType [1..1]
RemoteParty [1..*]
Active [1..1]
SecurityAccessModules [0..1]
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1]
ProtectedCardData [0..1]

- 182 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


ContentType [1..1]
EnvelopedData [1..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
ServiceCode [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
IssuerBIN
CardCountryCode [0..1]
CardCurrencyCode
CardProductProfile [0..1]
CardBrand [0..1]
AdditionalCardData [0..1]
CustomerDevice [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
TokenAssuranceLevel [0..1]
Cardholder [0..1]
Identification [0..*]
DriverLicenseNumber [0..1]
DriverLicenseLocation [0..1]
DriverLicenseName [0..1]
DriverIdentification [0..1]
CustomerNumber [0..1]
SocialSecurityNumber [0..1]
[0..1]
AlienRegistrationNumber
PassportNumber [0..1]
[0..1]
TaxIdentificationNumber
IdentityCardNumber [0..1]
[0..1]
EmplyerIdentificationNumber
[0..1]
EmployeeIdentificationNumber

- 183 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


JobNumber [0..1]
Department [0..1]
EmailAddress [0..1]
DateAndPlaceOfbirth [0..1]
BirthDate [1..1]
ProvinceOfBirth [0..1]
CityOfBirth [1..1]
CountryOfBirth [1..1]
Other [0..*]
Identification [1..1]
IdentificationType [1..1]
Name [0..1]
Language [0..1]
BillingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
ShippingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
TripNumber [0..1]
Vehicle [0..1]
VehicleNumber [0..1]
TrailerNumber [0..1]
VehicleTag [0..1]
VehicleTagEntryMode [0..1]
UnitNumber [0..1]
ReplacementCar [0..1]
Odometer [0..1]
Hubometer [0..1]
TrailerHours [0..1]
ReferHours [0..1]
[0..1]
MaintenanceIdentification
DriverOrVehicleCard [0..1]
PAN [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
AdditionalVehicleData [0..*]
Type [0..1]

- 184 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


EntryMode [0..1]
Data [1..1]
PersonalData [0..1]
ProtectedCardholderData [0..1]
Context [0..1] see AcceptorCancellationAdvice
PaymentContext [0..1]
CardPresent [0..1]
CardholderPresent [0..1]
OnlineContext [0..1]
AttendanceContext [0..1]
TransactionEnvironment [0..1]
TransactionChannel [0..1]
AttendantMessageCapable [0..1]
AttendantLanguage [0..1]
CardDataEntryMode [1..1]
FallbackIndicator [0..1]
SupportedOption [0..*]
SaleContext [0..1]
SaleIdentification [0..1]
SaleReferenceNumber [0..1]
SaleReconciliation- [0..1]
Identification
CashierIdentification [0..1]
ShiftNumber [0..1]
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]
AdditionalSaleData [0..1]
Transaction [1..1] see AcceptorCancellationAdvice
MerchantCategoryCode [0..1] C3
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
OriginalTransaction [0..1]
[0..1]
SaleReferenceIdentification
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
POIIdentification [0..1]
Identification [1..1]

- 185 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Type [0..1]
Issuer [0..1]
ShortName [0..1]
InitiatorTransaction- [0..1]
Identification
RecipientTransaction- [0..1]
Identification
TransactionType [1..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
CardDataEntryMode [0..1]
TransactionResult [0..1]
AuthorisationEntity [0..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1]
Authorisation
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
TransactionSuccess [1..1]
Reversal [0..1]
FailureReason [0..*]
RecipientTransaction- [0..1]
Identification
ReconciliationIdentification [0..1]
InterchangeData [0..1]
TransactionDetails [1..1]
Currency [0..1]
TotalAmount [1..1]
ValidityDate [0..1]
ICCRelatedData [0..1]
AuthorisationResult [0..1]
AuthorisationEntity [0..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseToAuthorisation [1..1]
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
TMSTrigger [0..1]
TMSContactLevel [1..1]

- 186 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


TMSIdentification [0..1]
TMSContactDateTime [0..1]
AdditionalTransactionData [0..*]
Or AuthorisationRequest [0..1] Authorisation request of a card payment
transaction.
TransactionSequenceCounter [1..1] see Completion/TransactionSequenceCounter
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
Environment [1..1] see AcceptorAuthorisationRequest
Acquirer [0..1]
Identification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ParametersVersion [1..1]
Merchant [0..1]
Identification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
CommonName [0..1]
LocationCategory [0..1]
LocationAndContact [0..1] Config
PostalAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
Email [0..1]
URLAddress [0..1]
Phone [0..1]
CustomerService [0..1]
[0..1]
AdditionalContactInformation
SchemeData [0..1]

- 187 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


POI [0..1]
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentifier [0..1]
Capabilities [0..1]
CardReading- [0..*]
Capabilities
CardholderVerification- [0..*]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1]
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*]
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]

- 188 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


CommunicationType [1..1]
RemoteParty [1..*]
Active [1..1]
SecurityAccessModules [0..1]
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1]
ProtectedCardData [0..1]
ContentType [1..1]
EnvelopedData [1..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
ServiceCode [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
IssuerBIN
CardCountryCode [0..1]
CardCurrencyCode
CardProductProfile [0..1]
CardBrand [0..1]
AdditionalCardData [0..1]
CustomerDevice [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
Wallet [0..1]
Identification [0..1]
Type [0..1]
Provider [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenRequestor [0..1]
ProviderIdentification [1..1]
RequestorIdentification [1..1]
Cardholder [0..1]
Identification [0..*]

- 189 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


DriverLicenseNumber [0..1]
DriverLicenseLocation [0..1]
DriverLicenseName [0..1]
DriverIdentification [0..1]
CustomerNumber [0..1]
SocialSecurityNumber [0..1]
[0..1]
AlienRegistrationNumber
PassportNumber [0..1]
[0..1]
TaxIdentificationNumber
IdentityCardNumber [0..1]
[0..1]
EmplyerIdentificationNumber
[0..1]
EmployeeIdentificationNumber
JobNumber [0..1]
Department [0..1]
EmailAddress [0..1]
DateAndPlaceOfbirth [0..1]
BirthDate [1..1]
ProvinceOfBirth [0..1]
CityOfBirth [1..1]
CountryOfBirth [1..1]
Other [0..*]
Identification [1..1]
IdentificationType [1..1]
Name [0..1]
Language [0..1]
BillingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
ShippingAddress [0..1]
AddressLine [0..2]
StreetName [0..1]
BuildingNumber [0..1]
PostCode [0..1]
TownName [1..1]
CountrySubDivision [0..2]
Country [1..1]
TripNumber [0..1]
Vehicle [0..1]
VehicleNumber [0..1]
TrailerNumber [0..1]
VehicleTag [0..1]
VehicleTagEntryMode [0..1]

- 190 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


UnitNumber [0..1]
ReplacementCar [0..1]
Odometer [0..1]
Hubometer [0..1]
TrailerHours [0..1]
ReferHours [0..1]
[0..1]
MaintenanceIdentification
DriverOrVehicleCard [0..1]
PAN [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
AdditionalVehicleData [0..*]
Type [0..1]
EntryMode [0..1]
Data [1..1]
PersonalData [0..1]
ProtectedCardholderData [0..1]
Context [0..1] see AcceptorAuthorisationRequest
PaymentContext [0..1]
CardPresent [0..1]
CardholderPresent [0..1]
OnlineContext [0..1]
AttendanceContext [0..1]
TransactionEnvironment [0..1]
TransactionChannel [0..1]
AttendantMessageCapable [0..1]
AttendantLanguage [0..1]
CardDataEntryMode [0..1]
FallbackIndicator [0..1]
SupportedOption [0..*]
SaleContext [0..1]
SaleIdentification [0..1]
SaleReferenceNumber [0..1]
SaleReconciliation- [0..1]
Identification
CashierIdentification [0..1]
ShiftNumber [0..1]
PurchaseOrderNumber [0..1]
InvoiceNumber [0..1]
DeliveryNoteNumber [0..1]
SponsoredMerchant [0..*]
CommonName [1..1]
Address [0..1]
CountryCode [1..1]
MerchantCategoryCode [1..1]
RegisteredIdentifier [1..1]
SplitPayment [0..1]
RemainingAmount [0..1]

- 191 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


AdditionalSaleData [0..1]
Transaction [1..1] see AcceptorAuthorisationRequest
TransactionCapture [1..1]
TransactionType [0..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
MerchantCategoryCode [0..1] C3
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
OriginalTransaction [0..1]
[0..1]
SaleReferenceIdentification
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
POIIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
InitiatorTransaction- [0..1]
Identification
RecipientTransaction- [0..1]
Identification
TransactionType [1..1]
AdditionalService [0..*]
ServiceAttribute [0..1]
CardDataEntryMode [0..1]
TransactionResult [0..1]
AuthorisationEntity [0..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseTo- [1..1]
Authorisation
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
InitiatorTransaction- [0..1]
Identification
ReconciliationIdentification [0..1]
TransactionDetails [1..1]
Currency [0..1]
TotalAmount [1..1]
AmountQualifier [0..1]

- 192 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


DetailedAmount [0..1]
[0..1]
AmountOfGoodAndServices
CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
RequestAmount [0..1]
AuthorisedAmount [0..1]
InvoiceAmount [0..1]
ValidityDate [0..1]
OnlineReason [0..1]
UnattendedLevelCategory [0..1]
AccountType [0..1]
CurrencyConversionResult [0..1]
AcceptedByCardholder [0..1]
Conversion [0..1]
[0..1]
CurrencyConversionIdentification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
[0..1]
InvertedExchangeRate
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]
CommissionDetails [0..*]
Amount [1..1]
[0..1]
AdditionalInformation
MarkUpDetails [0..*]

- 193 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Rate [1..1]
[0..1]
AdditionalInformation
DeclarationDetails [0..1]
Format [0..1]
MessageContent [1..1]
Instalment [0..1]
InstalmentPlan [0..*]
PlanIdentification [0..1]
SequenceNumber [0..1]
PeriodUnit [0..1]
InstalmentPeriod [0..1]
[0..1]
TotalNumberOfPayments
FirstPaymentDate [0..1]
TotalAmount [0..1]
FirstAmount [0..1]
Charges [0..1]
AggregationTransaction [0..1]
FirstPaymentDateTime [0..1]
LastPaymentDateTime [0..1]
NumberOfPayments [0..1]
IndividualPayment [0..*]
Amount [1..1]
DateTime [1..1]
CardDataEntryMode [0..1]
ICCRelatedData [0..1]
Label [0..1]
[0..1]
ProductCodeSetIdentification
SaleItem [0..*]
ItemIdentification [0..1]
ProductCode [1..1]
AdditionalProductCode [0..1]
UnitOfMeasure [0..1]
ProductQuantity [0..1]
UnitPrice [0..1]
UnitPriceSign [0..1]
ProductAmount [1..1]
ProductAmountSign [0..1]
ValueAddedTax [0..1]
TaxType [0..1]
ProductDescription [0..1]
DeliveryLocation [0..1]
DeliveryService [0..1]
DeliveryLocation [0..1]
CardPaymentInvoice [0..1]
InvoiceHeader [1..1]
Identification [1..1]
TypeCode [1..1]
Name [0..*]

- 194 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


IssueDateTime [1..1]
Issuer [0..1]
PartyIdentification [1..1]
LegalOrganisation [0..1]
Identification [0..1]
Name [0..1]
TaxParty [0..*]

LanguageCode [0..1]
CopyIndicator [0..1]
DocumentPurpose [0..1]
IncludedNote [0..*]
InformationType [1..1]
InformationValue [1..1]
TradeAgrrement [1..1]
TradeDelivery [1..1]
LineItem [0..*]
ICCRelatedData [0..n]
AdditionalTransactionData [0..n]
Or} AuthorisationResponse [0..1] Authorisation response of a card payment
transaction.
TransactionSequenceCounter [1..1] see Completion/TransactionSequenceCounter
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
Environment [1..1] see AcceptorAuthorisationResponse
AcquirerIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
POIIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]

- 195 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


Card [0..1]
ProtectedCardData [0..1]
ContentType [1..1]
EnvelopedData [1..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1] Appli see AcceptorAuthorisationRequest
CardProductType [0..1] Config see AcceptorAuthorisationRequest
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1] see AcceptorAuthorisationResponse
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
[0..1]
InitiatorTransactionIdentification
RecipientTransaction- [0..1]
Identification
ReconciliationIdentification [0..1]
InterchangeData [0..1]
TransactionDetails [1..1]
Currency [0..1]
TotalAmount [1..1]
DetailedAmount [0..1]
[0..1]
AmountOfGoodAndServices
CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
InvoiceAmount [0..1]
Amount [1..1]
Label [0..1]
ValidityDate [0..1]

- 196 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


AccountType [0..1]
ICCRelatedData [0..1]
TransactionResponse [1..1]
AuthorisationResult [1..1]
AuthorisationEntity [1..1]
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ResponseToAuthorisation [1..1]
Response [1..1]
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
AuthorisationCode [0..1]
CompletionRequired [0..1]
TMSTrigger [0..1]
TMSContactLevel [1..1]
TMSIdentification [0..1]
TMSContactDateTime [0..1]
TransactionVerification- [0..1]
Result
Method [1..1]
VerificationEntity [0..1]
Result [0..1]
AdditionalResult [0..1]
AllowedProductCode [0..*]
ProductCode [1..1]
AdditionalProductCode [0..1]
NotAllowedProductCode [0..*]
ProductCode [1..1]
AdditionalProductCode [0..1]
AdditionalAvailableProduct [0..*]
ProductCode [1..1]
AdditionalProductCode [0..1]
AmountLimit [0..1]
QuantityLimit [0..1]
Balance [0..1]
ProtectedBalance
Currency [0..1]
Action [0..*]
ActionType [1..1]
MessageToPresent [0..1]
MessageDestination [1..1]
Format
MessageContent [1..1]
MessageContent- [0..1]
Signature
SecurityTrailer [0..1]
ContentType [1..1]

- 197 -
Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Cstr Type / Definition / Code List


EnvelopedData [0..1]
AuthenticatedData [0..1]
SignedData [0..1]
DigestedData [0..1]
NamedKeyEncryptedData [0..1]

4.6.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 POI must either be present in CommonData or in  BatchTransfer.DataSet.CommonData.Environm
Transaction ent.POI
 BatchTransfer.DataSet.Transaction.Completion
.Environment.POI
 BatchTransfer.DataSet.Transaction.Cancellatio
n.Environment.POI
 BatchTransfer.DataSet.Transaction.Authorisati
onRequest.Environment.POI
 BatchTransfer.DataSet.Transaction.Authorisati
onResponse.Environment.POI
C2 If Context is present it must have at least one child  BatchTransfer.DataSet.Transaction.Completion
.Context
 BatchTransfer.DataSet.Transaction.Cancellatio
n.Context
 BatchTransfer.DataSet.Transaction.Authorisati
onRequest. Context
 BatchTransfer.DataSet.Transaction.Authorisati
onResponse. Context
C3 MerchantCategoryCode must be present either in  BatchTransfer.DataSet.CommonData.
CommonData or in Transaction MerchantCategoryCode
 BatchTransfer.DataSet.Transaction.Completion
.Transaction. MerchantCategoryCode
 BatchTransfer.DataSet.Transaction.Cancellatio
n. Transaction. MerchantCategoryCode
 BatchTransfer.DataSet.Transaction.Authorisati
onRequest. Transaction.
MerchantCategoryCode
 BatchTransfer.DataSet.Transaction.Authorisati
onResponse. Transaction.
MerchantCategoryCode

- 198 -
Card Payments Message Usage Guide Version 5.0

4.6.2 AcceptorBatchTransferResponse (caaa.012.001.05)

AcceptorBatchTransferResponse Mult. Rule Cstr Usage


Header [1..1]
DownloadTransfer [1..1] True
FormatVersion [1..1] The Recipient Party has to adapt the batch transfer
response format to the version of the Initiator sent in the
batch transfer.
ExchangeIdentification [1..1] Copy Several AcceptorBatchTransferResponse related to the
same AcceptorBatchTransfer share the same
ExchangeIdentification value.
Duplication of a AcceptorBatchTransferResponse is
detected with a common value of CreationDateTime.
Mixing DataSet from different AcceptorBatchTransfer in the
same AcceptorBatchTransferResponse is forbidden.
CreationDateTime [1..1] see AcceptorBatchTransfer
InitiatingParty [1..1] Copy Initiator of the AcceptorBatchTransfer
see AcceptorBatchTransfer
Identification [1..1]
Type [0..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Copy
Identification [1..1]
Type [1..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
RemoteAccess [0..1]
BatchTransferResponse [1..1]
TransactionTotals [0.*] Appli
POIGroupIdentification [0..1] Appli
CardProductProfile [0..1] Appli
Currency [0..1]
Type [1..1]
TotalNumber [1..1]
CumulativeAmount [1..1]
DataSet [0..*] DataSet result concerns all the transactions present in the
original DataSet.
Each occurrence of DataSet present in the
AcceptorBatchTransferResponse must be present in the

- 199 -
Card Payments Message Usage Guide Version 5.0

AcceptorBatchTransferResponse Mult. Rule Cstr Usage


original AcceptorBatchTransfer.
Part of the DataSet could be missing and transferred in
another AcceptorBatchTransferResponse.
DataSetIdentification [1..1] Copy
Name [1..1]
Type [0..1] CaptureResponse
Version [0..1] Not used in Batch Capture context
CreationDateTime [1..1]
DataSetResult [1..1] Global result of the DataSet.
Response [1..1] C1 Approved: all transactions in DataSet are accepted.
Declined: all transactions in DataSet are rejected.
PartialApproved: only a subset of transactions is accepted
and the others are rejected.
ResponseReason [0..1]
[0..1]
AdditionalResponseInformation
RemoveDataSet [1..1] May be used to inform the Initiator to remove the
transactions from the memory.
DataSetInitiator [0..1] Copy
Identification [1..1] Copy
Type [0..1] Copy
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
TransactionTotals [1..*]
POIGroupIdentification [0..1] Copy
CardProductProfile [0..1] Copy
Currency [0..1] Copy
Type [1..1] Copy See AcceptorReconciliation Request
TotalNumber [1..1] This data element contains the total number of transactions
calculated by the recipient.
In case of a difference with the total calculated by the
InitatingParty, the InitiatingParty has to take care of the
error which has to be resolved by other mean.
CumulativeAmount [1..1] This data element contains the cumulative amount of
transactrions calculated by the recipient.
In case of a difference with the CumulativeAmount
calculated by the InitatingParty, the InitiatingParty has to
take care of the error which has to be resolved by other
mean.
RejectedTransaction [0..*] C1 Present if DataSetResult.Response is PartialApproved.
All transactions with TransactioResponse equal to Declined
or TechnicalError must be present.
TransactionSequence- [1..1] Copy
Counter
TransactionResponse [1..1]
Response [1..1] * Allowed values : Declined or TechnicalError.
ResponseReason [0..1]
Environment [1..1]
AcquirerIdentification [0..1] Copy
Identification [1..1]
Type [0..1] Copy
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]

- 200 -
Card Payments Message Usage Guide Version 5.0

AcceptorBatchTransferResponse Mult. Rule Cstr Usage


MerchantIdentification [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
POIIdentification [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
Card
ProtectedCardData [0..1] Copy see AcceptorBatchTransfer
PlainCardData [0..1] Copy see AcceptorBatchTransfer
PAN [1..1]
CardSequence- [0..1]
Number
EffectiveDate [0..1]
ExpiryDate [1..1]
[0..1]
PaymentAccountReference
MaskedPAN [0..1]
CardBrand [0..1]
CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
[0..1]
TokenAssuranceLevel
Transaction [1..1]
[0..1]
SaleReferenceIdentification
TransactionIdentification [1..1] Copy
TransactionDateTime [1..1]
TransactionReference [1..1]
Response [1..1] Same value as
RejectedTransaction.TransactionResponse.Response (not
to be verified by the RecipientParty)
SecurityTrailer [0..1]

4.6.2.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 If DataSetResult.Response is “PartialApproved” then  BatchTransferResponse.DataSet.DataSetResul
RejectedTransaction must be present. t.Response
 BatchTransferResponse.DataSet.RejectedTran
saction

- 201 -
Card Payments Message Usage Guide Version 5.0

4.7 Diagnostic Messages

4.7.1 AcceptorDiagnosticRequest (caaa.013.001.05)

AcceptorCancellationRequest Mult. Rule Cstr Usage


Header [1..1]
MessageFunction [1..1] C1 The only valid code is DiagnosticRequest to request a
diagnostic.
(in case of an invalid value, a Reject message is sent by
the Recipient with RejectReason equal to ParsingError)
ProtocolVersion [1..1] see AcceptorAuthorisationRequest
ExchangeIdentification [1..1] see AcceptorAuthorisationRequest
CreationDateTime [1..1] see AcceptorAuthorisationRequest
InitiatingParty [1..1] see AcceptorAuthorisationRequest
Identification [1..1]
Type [0..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RecipientParty [0..1] Config see AcceptorAuthorisationRequest
Identification [1..1] Config
Type [0..1]
Issuer [0..1] Config
Country [0..1] Config
ShortName [0..1] Config
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
DiagnosticRequest [1..1] C1 The Header.MessageFunction must be DiagnosticRequest.
(if not the case, a Reject message is sent by the Recipient
with RejectReason equal to “ParsingError”)

- 202 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


Environment [1..1] see AcceptorAuthorisationRequest
Acquirer [1..1]
Identification [1..1] Appli
Identification [1..1] Appli
Type [0..1] default OriginatingPOI
Issuer [0..1] Config
Country
ShortName [0..1] Config
AcquirerParametersVersion [1..1]
AcquirerAvailabilityRequested [0..1]
MerchantIdentification [0..1] Config see AcceptorAuthorisationRequest
Identification [1..1] Appli
Type [0..1] default Merchant
Issuer [0..1] Config
Country
ShortName [0..1] Config
POIIdentification [1..1]
Identification [1..1] Config
Type [0..1] default OriginatingPOI
Issuer [0..1] Config
ShortName [0..1] Config
POIComponent [0..*]
Type [1..1] Components to be sent in the online authorisation are
configured locally or by TMS configuration.:

Identification [1..1] Identification of the component.


ItemNumber [0..1]
ProviderIdentification [0..1] Identifies the provider of the component class (it replaces
the data element ManufacturerIdentification of version 1).
Identification [0..1] Identification of the component assigned by the provider (it
replaces the data element Model of version 1).
SerialNumber [0..1] Serial number of the component if available.
Status [0..1] Actual status of the component.
VersionNumber [0..1] Current version of component that may include the release
number.
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*] Identification of the standard for which the component
complies with.
Identification [1..1] Identification of the standard.
Version [1..1] Version of the standard.
Issuer [1..1] Entity assigning the identification
Characteristics [0..1] Only used in TMS protocol.
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
CommunicationType [1..1]
RemoteParty [1..*]

- 203 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationRequest Mult. Rule Cstr Usage


Active [1..1]
SecurityAccessModules [0..1]
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*] Only used in TMS protocol.
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body DiagnosticRequest including the body
envelope.

4.7.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When DiagnosticRequest is present the  Header.MessageFunction
Header.MessageFunction must be  DiagnosticRequest
DiagnosticRequest

- 204 -
Card Payments Message Usage Guide Version 5.0

4.7.2 AcceptorDiagnosticResponse (caaa.014.001.05)

AcceptorCancellationResponse Mult. Rule Cstr Usage


Header [1..1]
MessageFunction [1..1] The only valid code in a response to a diagnostic is :
DiagnosticResponse
ProtocolVersion [1..1] Copy see AcceptorAuthorisationResponse
ExchangeIdentification [1..1] Copy
CreationDateTime [1..1] see AcceptorAuthorisationResponse
InitiatingParty [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RecipientParty [0..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1] Copy
Country [0..1] Config
ShortName [0..1] Copy
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
DiagnosticResponse [1..1]
Environment [1..1]
Acquirer
Identification [1..1]
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
Country [0..1] Config

- 205 -
Card Payments Message Usage Guide Version 5.0

AcceptorCancellationResponse Mult. Rule Cstr Usage


ShortName [0..1]
AcquirerParametersVersion [1..1] Copy
AcquirerAvailable [0..1]
MerchantIdentification [0..1] see AcceptorAuthorisationResponse
Identification [1..1]
Type [0..1] default Merchant
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
POIIdentification [1..1] Copy
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
TMSTrigger [0..1] Appli see AcceptorAuthorisationResponse
TMSContactLevel [1..1]
TMSIdentification [0..1] Appli
TMSContactDateTime [0..1] Present if TMSContactLevel = DateTime
SecurityTrailer [0..1] CMS data structure ContentInfoType with the
AuthenticatedData alternative, containing the MAC of the
message body DiagnosticResponse including the body
envelope, using the MAC key of the related
AcceptorDiagnosticRequest message.

- 206 -
Card Payments Message Usage Guide Version 5.0

4.8 Reject Message

4.8.1 AcceptorRejection (caaa.015.001.05)


AcceptorRejection Mult. Rule Cstr Usage
Header [1..1] see AcceptorAuthorisationRequest
MessageFunction [1..1] C1 The only valid codes to be used in the case a reject message is
sent is:
Rejection: The receiving party could not handle the request or
the advice.
ProtocolVersion [1..1] see AcceptorAuthorisationResponse
ExchangeIdentification [0..1] Copy from the request if successfully extracted.
CreationDateTime [1..1] see AcceptorAuthorisationResponse
InitiatingParty [0..1] Copy from the request if successfully extracted .
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
RecipientParty [0..1] Copy from the request if successfully extracted, otherwise absent.
Identification [0..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
[0..*]
ServerCertificateIdentifier
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
Reject [1..1] C1 The Header.MessageFunction must be Rejection.
RejectReason [1..1] High level information allowing the sender of a request or an advice
to know the types of error, and handle them accordingly (see
section 3.4 p. 96).
UnableToProcess: Not possible to process the message (e.g.

- 207 -
Card Payments Message Usage Guide Version 5.0

AcceptorRejection Mult. Rule Cstr Usage


Host unavailable, Hardware Security Module unavailable,
problem of resource)
InvalidMessage: Invalid message envelope:
ParsingError: Invalid message, at least one of the data element
or data structure is not present, or the format or the content of
one data element or one data structure is not correct.
This addresses the formatting of the field and also high level
accuracy of its content (e.g MessageFunction).
Security: any security related error (e.g. invalid key, incorrect
MAC result...)
InitiatingParty: Invalid identification data for the sender
IniatingParty.
RecipientParty: Invalid identification data for the the receiver
RecipientParty.
DuplicateMessage: Duplicate message, i.e. same
ExchangeIdentification and CreationDateTime as for a previous
message from the initiator.
ProtocolVersion: The ProtocolVersion is not supported by the
recipient.

AdditionalInformation [0..1] Appli Additional information related to the sending of a reject message in
response to a request or an advice.
For logging purpose, in order to allow further analysis, statistics and
deferred processing on the success or the failure of the request
processing.
MessageInError [0..1] Appli Message received by the recipient which has been rejected and
produced this AcceptorRejection message.

4.8.1.1 Constraints
This section lists all business rules implying at least 2 different elements inside the message.

Constraint Definition Involved elements


Number
C1 When Reject is present the Header.MessageFunction  Header.MessageFunction
must be “Rejection”  Reject

- 208 -
Card Payments Message Usage Guide Version 5.0

4.9 Dynamic Currency Conversion Messages

4.9.1 AcceptorCurrencyConversionRequest (caaa.016.001.03)

AcceptorCurrencyConversionReques Mult. Rule Cstr Usage


t
Header [1..1]
MessageFunction [1..1]
ProtocolVersion [1..1]
ExchangeIdentification [1..1]
CreationDateTime [1..1]
InitiatingParty [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RecipientParty [0..1] Config
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1] Config
ShortName [0..1]
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]
RelayIdentification [1..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CurrencyConversionRequest [1..1]
Environment [1..1]
AcquirerIdentification [0..1]
Identification [1..1]

- 209 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionReques Mult. Rule Cstr Usage


t
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1]
Identification [1..1]
Type [1..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
POI [1..1]
Identification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
SystemName [0..1]
GroupIdentification [0..1]
Capabilities [0..1]
CardReadingCapabilities [0..*]
CardholderVerification- [0..*]
Capabilities
PINLengthCapabilities [0..1]
ApprovalCodeLength [0..1]
MaxScriptLength [0..1]
CardCaptureCapable [0..1]
OnLineCapabilities [0..1]
MessageCapabilities [0..*]
Destination [1..*]
AvailableFormat [0..*]
NumberOfLines [0..1]
LineWidth [0..1]
AvailableLanguage [0..*]
TimeZone [0..1]
TerminalIntegration [0..1]
Component [0..*]
Type [1..1]
Identification [1..1]
ItemNumber [0..1]
ProviderIdentification [0..1]
Identification [0..1]
SerialNumber [0..1]
Status [0..1]
VersionNumber [0..1]
Status [0..1]
ExpiryDate [0..1]
StandardCompliance [0..*]
Identification [1..1]
Version [1..1]

- 210 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionReques Mult. Rule Cstr Usage


t
Issuer [1..1]
Characteristics [0..1]
Memory [0..*]
Identification [1..1]
TotalSize [1..1]
FreeSize [1..1]
Unit [1..1]
Communication [0..*]
Communication- [1..1]
Type
RemoteParty [1..*]
Active [1..1]
SecurityAccess- [0..1]
Modules
SubscriberIdentity- [0..1]
Modules
KeyCheckValue [0..1]
Assessment [0..*]
Type [1..1]
Assigner [1..*]
DeliveryDate [0..1]
ExpirationDate [0..1]
Number [1..1]
Card [1..1]
ProtectedCardData [0..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
ServiceCode [0..1]
Track1 [0..1]
Track2 [0..1]
Track3 [0..1]
CardholderName [0..1]
PaymentAccountReference [0..1]
IssuerBIN [0..1]
CardCountryCode [0..1]
CardCurrencyCode [0..1]
CardProductProfile [0..1]
CardBrand [0..1]
InternationalCard [0..1]
AllowedProduct [0..*]
ServiceOption [0..1]
AdditionalCardData [0..1]
CardholderLanguage [0..1]
Transaction [1..1]
TransactionCapture [0..1]
TransactionType [1..1]
AdditionalService [0..*]

- 211 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionReques Mult. Rule Cstr Usage


t
ServiceAttribute [0..1]
MerchantCategoryCode [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
OriginalTransaction [0..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
POIIdentification [1..1]
CurrencyConversion [1..1]
Result [1..1]
ResultReason [0..1]
ConversionDetails [0..1]
[0..1]
CurrencyConversionIdentification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
InvertedExchangeRate [0..1]
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]
CommissionDetails [0..*]
Amount [1..1]
[0..1]
AdditionalInformation
MarkUpDetails [0..*]
Rate [1..1]
[0..1]
AdditionalInformation
DeclarationDetails [0..1]
Format [0..1]
MessageContent [1..1]
TransactionDetails [1..1]
Currency [1..1]
TotalAmount [1..1]
AmountQualifier [0..1]
DetailedAmount [0..1]
[0..1]
AmountOfGoodAndServices
CashBack [0..1]
Gratuity [0..1]

- 212 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionReques Mult. Rule Cstr Usage


t
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
ICCRelatedData [0..1]
AdditionalTransactionData [0..*]
SecurityTrailer [0..1]

4.9.2 AcceptorCurrencyConversionResponse (caaa.017.001.03)

AcceptorCurrencyConversionResponse Mult. Rule Cstr


Header [1..1]
MessageFunction [1..1]
ProtocolVersion [1..1]
ExchangeIdentification [1..1]
CreationDateTime [1..1]
InitiatingParty [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
RecipientParty [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
RemoteAccess [0..1]
Address [1..*]
NetworkType [1..1]
AddressValue [1..1]
UserName [0..1]
AccessCode [0..1]
ServerCertificate [0..*]
ServerCertificateIdentifier [0..*]
ClientCertificate [0..*]
SecurityProfile [0..1]
Traceability [0..*]

- 213 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionResponse Mult. Rule Cstr


RelayIdentification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
ProtocolName [0..1]
ProtocolVersion [0..1]
TraceDateTimeIn [1..1]
TraceDateTimeOut [1..1]
CurrencyConversionResponse [1..1]
Environment [1..1]
AcquirerIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
MerchantIdentification [0..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
Country [0..1]
ShortName [0..1]
POIIdentification [1..1]
Identification [1..1]
Type [0..1]
Issuer [0..1]
ShortName [0..1]
Card
ProtectedCardData [0..1]
PlainCardData [0..1]
PAN [1..1]
CardSequenceNumber [0..1]
EffectiveDate [0..1]
ExpiryDate [1..1]
PaymentAccountReference [0..1]
MaskedPAN [0..1]
CardBrand [0..1]
CardProductType [0..1]
PaymentToken [0..1]
TokenCharacteristic [0..*]
TokenAssuranceLevel [0..1]
Transaction [1..1]
SaleReferenceIdentification [0..1]
TransactionIdentification [1..1]
TransactionDateTime [1..1]
TransactionReference [1..1]
InitiatorTransactionIdentification [0..1]
RecipientTransactionIdentification [0..1]

- 214 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionResponse Mult. Rule Cstr


ReconciliationIdentification [0..1]
InterchangeData [0..1]
TransactionDetails [1..1]
Currency [1..1]
TotalAmount [1..1]
DetailedAmount [0..1]
AmountOfGoodAndServices [0..1]
CashBack [0..1]
Gratuity [0..1]
Fees [0..*]
Amount [1..1]
Label [0..1]
Rebate [0..*]
Amount [1..1]
Label [0..1]
ValueAddedTax [0..*]
Amount [1..1]
Label [0..1]
Surcharge [0..*]
Amount [1..1]
Label [0..1]
InvoiceAmount [0..1]
Amount [1..1]
Label [0..1]
ValidityDate [0..1]
AccountType [0..1]
ICCRelatedData [0..1]
MerchantReferenceData [0..1]
CurrencyConversionResult [1..1]
Result [1..1]
ResultReason [0..1]
ConversionDetails [0..1]
CurrencyConversion- [0..1]
Identification
TargetCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
ResultingAmount [1..1]
ExchangeRate [1..1]
InvertedExchangeRate [0..1]
QuotationDate [0..1]
ValidUntil [0..1]
SourceCurrency [1..1]
AlphaCode [1..1]
NumericCode [1..1]
Decimal [1..1]
Name [0..1]
OriginalAmount [1..1]

- 215 -
Card Payments Message Usage Guide Version 5.0

AcceptorCurrencyConversionResponse Mult. Rule Cstr


CommissionDetails [0..*]
Amount [1..1]
AdditionalInformation [0..1]
MarkUpDetails [0..*]
Rate [1..1]
AdditionalInformation [0..1]
DeclarationDetails [0..1]
Format [0..1]
MessageContent [1..1]
SecurityTrailer [0..1]

- 216 -
Card Payments Message Usage Guide Version 5.0

5 Dynamic of the Payment Exchanges

5.1 Introduction

This chapter presents an exhaustive catalogue of payment transactions cases by:


 Listing exhaustively the cases from the various process flows of the payment transaction,
 presenting the associated sequences of Authorisation, Completion and Batch exchanges
between an Acceptor and an Acquirer,
 determining the values of the message data components and configuration parameters
relevant for theses exchanges of messages, the financial capture and the outcome of the
transaction.

5.2 Determination of Payment Cases

5.2.1 Elements Impacting the Message Flow


The following sections addresse the message flows of the transactions by focusing on conditions
influencing the sequence of messages such as:
 authorisation type,
 authorisation result,
 incidents after the authorisation,
 transactions forced by the merchant,
 capture type, and
 use of completion messages,
 acquirer configuration parameters.

5.2.1.1 Authorisation Type


An authorisation can be made:
 online (exchange of authorisation messages between the Acceptor and the Acquirer)
 offline (no exchange of messages between the Acceptor and the Acquirer). In such a case,
the payment approval follows the rules of the POI payment application.

AcceptorCompletionAdvice or BatchTransfer messages contains the information indicating whether


the authorisation has been made online or offlline in the data element
Context.PaymentContext.OnLineContext.

- 217 -
Card Payments Message Usage Guide Version 5.0

5.2.1.2 Authorisation Result

The result of the authorisation can be:


 Approved online by the Acquirer or offline at the POI.
 Declined online by the Acquirer or offline at the POI.
 No Acceptable Response:
1/ When the Acceptor has tried to send an AcceptorAuthorisationRequest message to
the Acquirer without receiving a response in time (online authorisation only):
 Transaction.FailureReason contains one of the values UnableToSend, TimeOut or
TooLateResponse,
 Transaction.Reversal flag is set to True.
2/ When the AcceptorAuthorisationResponse contains
ResponseToAuthorisation/Response with the value “TechnicalError”:

5.2.1.3 Incident after Authorisation


After an online or offline authorisation, the transaction can terminate with incident.
Transaction.FailureReason has then one of the following values:
 CustomerCancel, transaction cancelled by the Cardholder
 CardDeclined, payment transaction finally declined by the card,
 Malfunction, malfunction of the card or of the card reader
 UnableToComplete, POI or Sale unable to complete transaction after the authorisation (e.g.
written signature invalid, risk too high for the Acceptor).

- 218 -
Card Payments Message Usage Guide Version 5.0

5.2.1.4 Merchant Forced Acceptance

The Merchant (Acceptor) may force the acceptance of a transaction (eg. in case of a trusted or loyal
customer).
A transaction can only be forced if it is allowed by the Acquirer and in accordance with the rules of the
card scheme.
The option to force a transaction may be presented to the Acceptor when a transaction does not
complete as approved, since:
 No response was received
 The transaction was declined
 Some incident occurred after authorisation at the POI.

If the Merchant forces the payment transaction , in the AcceptorCompletionAdvice message the
following values are used:
 Transaction.MerchantOverride flag is set to True,
 Transaction.FailureReason is present with one of the values: CardDeclined, Malfunction,
OfflineDeclined, OnlineDeclined, TimeOut, TooLateResponse, UnableToSend or
UnableToComplete value.

5.2.1.5 Capture Type

The capture of the transaction can occur in:


 the authorisation exchange, when the configuration parameter
OnlineTransaction.FinancialCapture has the value Authorisation.
 the completion exchange, when the configuration parameter
OnlineTransaction.FinancialCapture (if the authorisation was online) or
OfflineTransaction.FinancialCapture (if the authorisation was offline) has the value
Completion.
 a batch transfer, when the configuration parameter OnlineTransaction.FinancialCapture (if the
authorisation was online) or OfflineTransaction.FinancialCapture (if the authorisation was
offline) has the value Batch.

This configuration information is neither sent in the AcceptorAuthorisationRequest, nor in the


AcceptorCompletionAdvice messages.

- 219 -
Card Payments Message Usage Guide Version 5.0

5.2.1.6 Completion Exchange


A completion exchange for successful approved transactions is required depending on the value of the
TMS parameter CompletionExchange.ExchangePolicy:
 None: a Completion advice is never sent to the Acquirer (for offline authorisation only),
 Any other value defined in ExchangePolicy except OnDemand: a Completion advice is
always sent to the Acquirer. In addition, the value of the parameter determines the conditions
of the exchange (e.g. TotalLimit: exchange performed after reaching a cumulative amount of
transactions). The ExchangePolicy has the priority over a CompletionRequired flag set to
False.
On demand CompletionAdvice is sent after the Authorisation exchange if the CompletionRequired flag
of the AcceptorAuthorisationResponse message is set to True. The OnDemand value of the
CompletionExchange.ExchangePolicy has no effect on the completion behavior.

Regardless of the above values, a completion exchange is also required when:


 The transaction completes successfully and the capture is realised during the completion
exchange.
 An online authorisation needs to be reversed (e.g. no acceptable response to an
AcceptorAuthorisationRequest or incident after an approved authorisation).
 The merchant successfully forces the transaction (see 5.2.1.4) and the capture must be made
on-line (i.e. with an authorisation exchange or a completion exchange).
 a successful voice authorisation was performed and the capture must be made with the
completion exchange.
 The authorisation is declined or the payment transactions failed and the TMS parameter
BatchTransferContent is set to send declined or failed transactions.

In case of reversal (Transaction.Reversal has the value True), the AcceptorCompletionAdvice


message must be sent immediately after the transaction is completed, whatever the value of
CompletionExchange.ExchangePolicy.

- 220 -
Card Payments Message Usage Guide Version 5.0

5.2.2 List of Payment Cases


In the following figures, Figure 52: Payment Cases Tree List and Figure 53: Payment Cases Tree List
(Con't), payment cases are identified through the combination of the elements described in the
previous section.
Some combinations may be irrelevant and so do not produce cases, for instance:
Incident after Merchant Capture Sending
The completion exchange is Authorisation Forces Type Completion
qu.
always required if the payment no compl. re Case 1
uth
transaction completes u re a compl. requ
ired Case 2
c apt
completed without incident
successfully and is captured capture compl. Case 3
by the completion exchange ved
appro

(case 3).

Authorisation Incident after Merchant


Result Authorisation Forces

ent
incid
hout
d wit
plete The merchant cannot force the transaction if the
co m
payment transaction completes successfully after an
fail
ed

u re a approved authorisation.
ro v

fter e d
a forc
uth not
app

o ri s
atio
n
me r
ch a
nt fo
rce s

Authorisation Incident after Merchant


Result Authorisation Forces
Off
line

If an incident occurs for an offline authorisation,


aut
h.

the result of the offline authorisation (declined or ed


forc
approved) is not taken into consideration. not
failure
me
rch
ant
for
c es

On the right side of the tree, after the case number, the figure provides the sequence of exchange
related to the case:
 auth: Authorisation exchange (AcceptorAuthorisationRequest/Response),
 compl: Completion exchange (AcceptorCompletionAdvice/Response),
 reversal: Completion exchange with reversal(AcceptorCompletionAdvice/Response),
 batch: Batch exchange (AcceptorBatchTransfer/Response)
The exchange is in bold and underlined if the capture is realised during that exchange, in square
bracket if the exchange is optional, and define as reversal for a completion which is a reversal :
auth compl Capture is done with the Authorisation exchange, the Completion is required by the
Acquirer (without capture).
auth compl Capture is done with the Completion exchange.

auth batch Capture is done by Batch.

auth reversal Capture is done with the Authorisation exchange, no response is received by the
POI, a "financial reversal" is performed with the Completion.
auth [batch] The payment transaction fails, the transaction must be included in the batch if the

- 221 -
Card Payments Message Usage Guide Version 5.0

Acceptor is configured to do so.

The form of "auth" and "compl" gives the value of the Header.MessageFunction component of the
Authorisation and Completion messages, as summarized in the table below:

MessageFunction
auth "AuthorisationRequest" "AuthorisationResponse"
auth "FinancialAuthorisationRequest" "FinancialAuthorisationResponse"
compl "CompletionAdvice" "CompletionAdviceResponse"
compl "FinancialCompletionAdvice" "FinancialCompletionAdviceResponse"
reversal "ReversalAdvice" "ReversalAdviceResponse"
reversal "FinancialReversalAdvice" "FinancialReversalAdviceResponse"
Table 1: MessageFunction Values

- 222 -
Card Payments Message Usage Guide Version 5.0

Authorisation Authorisation Incident after Merchant Capture Sending


Type Result Authorisation Forces Type Completion
qu.
no compl. re Case 1 auth
uth
u re a compl. requ
ired Case 2 auth compl
c apt
capture compl. Case 3 auth compl
nt
in cide bat
ch
hout ca p no compl. re
qu.
Case 4 auth batch
d wit ture
plete
co m compl. requ
ired Case 5 auth compl batch

Case 6 auth reversal


fail
u re a capture auth
fter rce d
capture compl. Case 7 auth reversal
a uth ot fo batch captur
o ri s n e Case 8 auth reversal[batch]
atio
n
me r th Case 9 auth compl
ch a
nt fo capture au
rce s capture compl. Case 10 auth compl
batch captur
e Case 11 auth compl batch
qu.
no compl. re Case 12 auth
a uth compl. requ Case 13 auth compl
re ired
ve d

ptu
ca co m pl. re qu.
no Case 14 auth
a p p ro

capture compl
rce
d ba compl. requ
ired Case 15 auth compl
t fo tch
no ca
ptu m pl. re qu.
no co Case 16 auth [batch]
re
compl. requ
ired Case 17 auth compl [batch]
nt m
de er
n ci ch
an Case 18 auth compl
ti tf
ou or re auth
ith ce captu
w s capture compl. Case 19 auth compl
d
e te batc qu.
pl h ca no compl. re Case 20 auth batch
m ptur
co e
compl. requ Case 21 auth compl batch
ired
declined qu.
no compl. re Case 22 auth
fa th
i lu
re re
au compl. requ
ired Case 23 auth compl
af ptu
te ca qu.
r no compl. re Case 24 auth
au capture compl
th d compl. requ Case 25 auth compl
o ri s rce ba ired
at t fo tch
io no ca .
n ptu no compl. requ Case 26 auth [batch]
re
compl. requ
ired Case 27 auth compl [batch]
m
er
no ac

ch Case 28 auth compl


an
tf
or re auth
ce captu
cepta

s Case 29 auth compl


batc capture compl.
qu.
th.

ble re

h ca no compl. re Case 30 auth batch


ptur
au

e
compl. requ Case 31 auth compl batch
sp o n s
Online

ired

capture au
th Case 32 auth reversal
e

rce d
capture compl. Case 33 auth reversal
n ot fo batch captur
e Case 34 auth reversal[batch]
t
id en me r th Case 35 auth compl
inc
ch a
nt fo capture au
t rce s Case 36 auth compl
ou capture compl.
th
wi batch captur
e Case 37 auth compl batch
ed
let
mp Case 38 auth reversal
co capture au
th
failur
e after
autho rce d
capture compl. Case 39 auth reversal
risati
on n ot fo batch captur
e Case 40 auth reversal[batch]
me r th Case 41 auth compl
ca ch a capture au
rd nt fo
ap rce s capture compl. Case 42 auth compl
p ro batch captur
ve e Case 43 auth compl batch
s
Off
line

capture au
th Case 44 auth compl
aut

capture compl. Case 45 auth compl


h.

batch captur
e Case 46 auth compl batch

Figure 52: Payment Cases Tree List

- 223 -
Card Payments Message Usage Guide Version 5.0

Authorisation Authorisation Incident after Merchant Capture Sending


Type Result Authorisation Forces Type Completion
.
auth
ne
Onli

mp l Case 47 compl
capture co
qu.
batch c no compl. re Case 48 batch
apture
compl. requ
ired Case 49 compl batch
Off
line

ed qu.
ro v u re no compl. re Case 50
app ca p t l
aut

p
co m compl. requ Case 51 compl
h.

ired
e d qu.
o rc batc no compl. re
n ot f h ca
pture
Case 52 [batch]
compl. requ
ired Case 53 compl [batch]
declined me
rch pl Case 54 compl
ant
for ca pture com
c es qu.
batch c no compl. re Case 55 batch
apture
compl. requ
ired Case 56 compl batch
fa
il ur qu.
e u re
ca p t l no compl. re Case 57
p
co m compl. requ Case 58 compl
ired
ed qu.
o rc batc no compl. re
n ot f h ca
pture
Case 59 [batch]
compl. requ
ired Case 60 compl [batch]
me
rch pl Case 61 compl
ant
for ca pture com
c es qu.
batch c no compl. re Case 62 batch
apture
compl. requ
ired Case 63 compl batch

Figure 53: Payment Cases Tree List (Con't)

- 224 -
Card Payments Message Usage Guide Version 5.0

5.3 Table of Payment Cases

The table below provides for each case the value of the key data components inside the messages or
configuration parameters.

It reads as follows:

Authorisation Refers to both AcceptorAuthorisationRequest and


AcceptorAuthorisationResponse messages.
CompletionAdvice Refers to an AcceptorCompletionAdvice message.
Batch Refers to a BatchTransfer message.

Authorisation
Txn Capt. Refers to TransactionCapture flag to be used in an
AcceptorAuthorisationRequest message.
Response Refers to Response data component to be used in an
AcceptorAuthorisationResponse messages to give the outcome of the on-line
authorisation:
 Appr.: for the values Approved or PartialApproved.
 Decl.: for the values Declined.
Compl.Requ. An AcceptorCompletionAdvice message has to be sent in this instance. For
declined and failed transaction, this flag has the priority over the configuration
parameters ExchangeDeclined and ExchangeFailed.

CompletionAdvice
condition Express the condition for Completion exchange:
 mandatory: the Completion exchange always occurs,
 ExchPol = None (or ≠ None): the configuration parameter
OfflineTransaction.ExchangePolicy or OfflineTransaction.ExchangePolicy
has (or has not ) the value None.
 ExchDecl = True or False: the configuration parameter ExchangeDeclined
has the value True or False.
 ExchFail = True or False: the configuration parameter ExchangeFailed has
the value True or False.
 required : Completion is sent according to the ExchangePolicy.
Txn. Succ. Refers to TransactionSuccess flag to be used in an AcceptorCompletionAdvice
message to provide the success or the failure of the transaction.
In addition to the value of this flag, it contains the value of MessageFunction in
the Completion messages:
(c): "CompletionAdvice"
(fc): "FinancialCompletionAdvice"
(r): "ReversalAdvice"
(fr): "FinancialReversalAdvice"

- 225 -
Card Payments Message Usage Guide Version 5.0

Txn. Capt. Refers to TransactionCapture flag to be used in an AcceptorCompletionAdvice


message to indicate whether the transaction needs to be captured or not.
Reversal Refers to Reversal flag to be used in an AcceptorCompletionAdvice message to
indicate whether the message is to be considered as a reversal or not.
Failure Reason Refers to FailureReason data component to be used in an
AcceptorCompletionAdvice message which contains the reasons of the failure
causing the reversals, merchant override or failure of the transaction. A “+” mean
that an acceptor may send more than one failure reason.
Merch. Overr. Refers to MerchantOverride flag to be used in an AcceptorCompletionAdvice
message to indicate whether the merchant forced the acceptance of the
transaction or not.

Batch
condition Express the condition to include the payment transaction in a Batch transfer:
 Empty cell: the transaction is never included in a Batch transfer,
 BatchCont=DebitCredit: the transaction is included in the Batch transfer if
the configuration parameter BatchTransferContent has the value
DebitCredit,
 BatchCont=Declined: the transaction is included in the Batch transfer if the
configuration parameter BatchTransferContent has the value Declined,
 BatchCont= Failed: the transaction is included in the Batch transfer if the
configuration parameter BatchTransferContent has the value Failed.
The number below the condition refers to the line number containing the value of
the flags TransactionSuccess, Reversal, MerchantOverride, and the data
elements FailureReason and Response of the related transaction in the
BatchTransfer.

An empty cell means that the component is absent.

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.
Online approved
1 Capture Auth. True Appr. False
No Completion
Online approved True
True
2 Capture Auth. True Appr. False
absent required (c)
Completion
Online approved True
3 False Appr. absent mandatory True
Capture Compl. (fc)
Online approved BatchCont=
4 Batch Capture False Appr. False ExchPol=None DebitCredit
Compl. not requ. 3
Online approved True ExchPol=None BatchCont=
True
5 Batch Capture False Appr. False DebitCredit
absent required (c)
Compl. required 3

- 226 -
Card Payments Message Usage Guide Version 5.0

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.

mandatory CustCancel
Online approved
False Malfunction
6 Incident after Auth. True Appr. True True
(fr) CardDecline
Capture Auth.
Unab2Com

CustCancel
Online approved
False Malfunction
7 Incident after Auth. False Appr. absent mandatory False True
(r) CardDecline
Capture Compl.
Unab2Com

CustCancel
Online approved BatchCont=
mandatory False Malfunction
8 Incident after Auth. False Appr. False True Failed
(r) CardDecline
Batch Capture 8
Unab2Com

Online approved
Malfunction
Incident after Auth. mandatory True
9 True Appr. True True CardDecline True
Merchant forces (fc)
Unab2Com
Capture Auth.

Online approved
Malfunction
1 Incident after Auth. True
False Appr. absent mandatory True True CardDecline True
0 Merchant forces (fc)
Unab2Com
Capture Compl.
Online approved True
Malfunction BatchCont=
1 Incident after Auth. True
False Appr. False True CardDecline True DebitCredit
1 Merchant forces (c)
absent required Unab2Com 10
Batch Capture

Online declined False


1
Capture Auth. True Decl.
2 absent
Compl. not requ. ExchDecl=False

Online declined True


1 False
Capture Auth. True Decl. False OnlineDecl
3 absent (c)
Compl. required ExchDecl=True

Online declined False


1
Capture Compl. False Decl.
4 absent
Compl. not requ. ExchDecl=False

Online declined True


1 False
Capture Auth. False Decl. False OnlineDecl
5 absent (c)
Compl. required ExchDecl=True

Online declined False BatchCont=


1
Batch Capture False Decl. Declined
6 absent
Compl. not requ. ExchDecl=False 17

Online declined True BatchCont=


1 False
Batch Capture False Decl. False OnlineDecl Declined
7 absent (c)
Compl. required ExchDecl=True 17

Online declined absent


1 True
Merchant forces True Decl. or mandatory True OnlineDecl True
8 (fc)
Capture Auth. present
Online declined absent
1 True
Merchant forces False Decl. or mandatory True OnlineDecl True
9 (fc)
Capture Compl. present

- 227 -
Card Payments Message Usage Guide Version 5.0

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.
Online declined
BatchCont=
2 Merchant forces
False Decl. False DebitCredit
0 Batch Capture
19
Compl. not requ.
Online declined True
BatchCont=
2 Merchant forces True
False Decl. False OnlineDecl True DebitCredit
1 Batch Capture absent required (c)
19
Compl. required
Online declined False
2 Incident after Auth.
True Decl.
2 Capture Auth. absent
Compl. not requ. ExchFail=False

True OnlineDecl
Online declined +
2 Incident after Auth. False CustCancel
True Decl. False
3 Capture Auth. absent (c) Malfunction
Compl. required ExchFail=True
CardDecline
Unab2Com
Online declined False
2 Incident after Auth.
False Decl.
4 Capture Compl. absent
Compl. not requ. ExchFail=False

True OnlineDecl
Online declined +
2 Incident after Auth. False CustCancel
False Decl. False
5 Capture Compl. absent (c) Malfunction
Compl. required ExchFail=True
CardDecline
Unab2Com
Online declined False
BatchCont=
2 Incident after Auth.
False Decl. Failed
6 Batch Capture absent
ExchFail=False 27
Compl. not requ.
True OnlineDecl
Online declined +
BatchCont=
2 Incident after Auth. False CustCancel
False Decl. False Failed
7 Batch Capture absent (c) Malfunction
ExchFail=True 27
Compl. required CardDecline
Unab2Com
OnlineDecl
Online declined
+
2 Incident after Auth. True
True Decl. absent mandatory True Malfunction True
8 Merchant forces (fc)
CardDecline
Capture Auth.
Unab2Com
OnlineDecl
Online declined
+
2 Incident after Auth. True
False Decl. absent mandatory True Malfunction True
9 Merchant forces (fc)
CardDecline
Capture Compl.
Unab2Com
Online declined
Incident after Auth. BatchCont=
3
Merchant forces False Decl. False ExchPol=OnDem DebitCredit
0
Batch Capture 29
Compl. not requ.
3 Online declined False Decl. True True False OnlineDecl True BatchCont=

- 228 -
Card Payments Message Usage Guide Version 5.0

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.
1 Incident after Auth. (c) + DebitCredit
Merchant forces Malfunction 29
absent required
Batch Capture CardDecline
Compl. required Unab2Com

Appr. mandatory
3 Online no resp. False TimeOut
True or True True
2 Capture Auth. (fr) Unable2Send
Decl.

Appr.
3 Online no resp. required False TimeOut
False or absent False True
3 Capture Compl. (r) Unable2Send
Decl.

Appr. BatchCont=
3 Online no resp. mandatory False TimeOut
False or False True Failed
4 Batch Capture (r) Unable2Send
Decl. 34

Online no resp. Appr.


3 mandatory True TimeOut
Merchant forces True or True True True
5 (fc) Unable2Send
Capture Auth. Decl.

Online no resp. Appr.


3 required True TimeOut
Merchant forces False or True True True
6 (fc) Unable2Send
Capture Compl. Decl.

Online no resp. Appr. BatchCont=


3 required True TimeOut
Merchant forces False or False True True DebitCredit
7 (c) Unable2Send
Batch Capture Decl. 36

TimeOut
Unable2Send
Online no resp. Appr. +
3 mandatory False
Incident after Auth. True or True True CustCancel
8 (fr)
Capture Auth. Decl. Malfunction
CardDecline
Unab2Com

TimeOut
Unable2Send
Online no resp. Appr. +
3 required False
Incident after Auth. False or False True CustCancel
9 (r)
Capture Compl. Decl. Malfunction
CardDecline
Unab2Com

TimeOut
Unable2Send
Online no resp. Appr. + BatchCont=
4 required False
Incident after Auth. False or False True CustCancel Failed
0 (r)
Batch Capture Decl. Malfunction 40
CardDecline
Unab2Com

- 229 -
Card Payments Message Usage Guide Version 5.0

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.

TimeOut
Online no resp. Unable2Send
Appr.
4 Incident after Auth. mandatory True +
True or True True True
1 Merchant forces (fc) Malfunction
Decl.
Capture Auth. CardDecline
Unab2Com

TimeOut
Online no resp. Unable2Send
Appr.
4 Incident after Auth. mandatory True +
False or absent True True True
2 Merchant forces (fc) Malfunction
Decl.
Capture Compl. CardDecline
Unab2Com

TimeOut
Online no resp. Unable2Send
Appr. BatchCont=
4 Incident after Auth. required True +
False or False True True DebitCredit
3 Merchant forces (c) Malfunction
Decl. 42
Batch Capture CardDecline
Unab2Com

Online no resp. Appr.


4 mandatory True TimeOut
Card approves True or True True
4 (fc) Unable2Send
Capture Auth. Decl.

Online no resp. Appr.


4 mandatory True TimeOut
Card approves False or absent True True
5 (fc) Unable2Send
Capture Compl. Decl.

Online no resp. Appr. BatchCont=


4 required True TimeOut
Card approves False or False True DebitCredit
6 (c) Unable2Send
Batch Capture Decl. 45

4 Offline approved True


mandatory True
7 Capture Compl. (fc)
Offline approved BatchCont=
4
Batch Capture ExchPol=None DebitCredit
8
Compl. not requ. 47
Offline approved BatchCont=
4 required True
Batch Capture False DebitCredit
9 (c)
Compl. required 47
Offline declined
5
Capture Compl. ExchDecl=False
0
Compl. not requ.
Offline declined
5 False
Capture Compl. ExchDecl=True False OfflineDecl
1 (c)
Compl. required
Offline declined BatchCont=
5
Batch Capture ExchDecl=False Declined
2
Compl. not requ. 53
Offline declined BatchCont=
5 False
Batch Capture ExchDecl=True False OfflineDecl Declined
3 (c)
Compl. required 53
Offline declined
5 True
Merchant forces mandatory True OfflineDecl True
4 (fc)
Capture Compl.

- 230 -
Card Payments Message Usage Guide Version 5.0

Authorisation CompletionAdvice Batch


Txn Resp. Compl condition Txn Txn Rev- Failure Merch. Condition
Capt. Requ Succ. Capt. ersal Reason Overr.
Offline declined
BatchCont=
5 Merchant forces
ExchPol=None DebitCredit
5 Batch Capture
54
Compl. not requ.
Offline declined
BatchCont=
5 Merchant forces required True
False OfflineDecl True DebitCredit
6 Batch Capture (c)
54
Compl. required
Offline failure
5
Capture Compl. ExchFail=False
7
Compl. not requ.
CustCancel
Offline failure
5 False False Malfunction
Capture Compl. ExchFail=True
8 (c) CardDecline
Compl. required
Unab2Com
Offline failure BatchCont=
5
Batch Capture ExchFail=False Failed
9
Compl. not requ. 60
CustCancel
Offline failure BatchCont=
6 False Malfunction
Batch Capture ExchFail=True False Failed
0 (c) CardDecline
Compl. required 60
Unab2Com
Offline failure Malfunction
6 True
Merchant forces mandatory True CardDecline True
1 (fc)
Capture Compl. Unab2Com
Offline failure
BatchCont=
6 Merchant forces
ExchPol=None DebitCredit
2 Batch Capture
61
Compl. not requ.
Offline failure
Malfunction BatchCont=
6 Merchant forces required True
False CardDecline True DebitCredit
3 Batch Capture (c)
Unab2Com 61
Compl. required

Table 2: List of Payment Cases

5.4 Cancellation Exchange

A cancellation exchange should rely on a configuration with 3 possible options:


 The usage of both AcceptorCancellationRequest and AcceptorCancellationAdvice messages
to fulfil a cancellation
 The usage of solely AcceptorCancellationAdvice message to fulfil a cancellation
 Cancellation is not supported by the acquirer.

- 231 -
Card Payments Message Usage Guide Version 5.0

5.4.1 List of Cancellation Cases

In the Figure 54 Cancellation Cases Tree List cancellation cases are described, based on the type of
capture and the combination of Cancellation Request and Cancellation Advice requested. For batch
file, the tree also shows the case where cancelled transactions must (or must not) be included in the
batch transfer.

Case 5 to 14 are the same, the only difference being the authorisation type.This has no impact on
cancellation processing.
The tree also covers the case where the transaction is not available in the log file because of at least
one of the following:
 the cancellation is done in a new batch
 the cancellation and the original transaction are not in the same reconciliation period
 theoriginal transaction originates from another POI.
In this case cancellation request is mandatory and a cancellation advice must be sent if the request is
approved.

In the right hand side of the tree, after the case number, the figure provides the sequence of
exchanges related to the case:
 auth: Authorisation exchange (AcceptorAuthorisationRequest/Response),
 compl: Completion exchange (AcceptorCompletionAdvice/Response),
 batch: Batch exchange (AcceptorBatchTransfer/Response)
 canreq: Cancellation request exchange (AcceptorCancellationRequest/Response)
 canadv: Cancellation advice exchange (AcceptorCancellationAdvice/Response)

The exchange is in bold and underlined if the capture was done in the payment processing. As for the
payment case, the message is in bold and underlined if the financial capture was done. Cancellation
request or advice are in bold and italic if the capture is undone.

auth canadv
Capture was done on authorisation, no cancellation request and capture is
undone with a cancellation advice.
compl canreq canadv Capture was done with a completion, a cancellation request is accepted and
undo the capture, followed by a cancellation advice.
canreq canadv batch The capture hasn’t occured yet, transaction is cancelled by request and advice
and both original transaction and cancellation are included in batch.

For cancellation, “canreq” and “canadv” gives the value of the Header.MessageFunction component of
the Cancellation Request and CancellationAdvice messages, as summarized in the table below:

- 232 -
Card Payments Message Usage Guide Version 5.0

MessageFunction
canreq “CancellationRequest” “CancellationResponse”
canadv “CancellationAdvice” “CancellationAdviceResponse”
Table 3: Cancellation MessageFunction Values

Authorisation Capture Cancellation Cancellation Cancellation Batch Transfert


Type Type Request Result Advice content
u. canadv
no canreq req Case 1 auth canadv
Canreq
ca n r accepted canadv
e q re Case 2 auth canreq canadv
qu .
Canreq decl
th

ined
au

Ca
n Case 3 auth canreq
re s re q
re
ptu

po No canadv
ns
Case 4
ca

e auth canreq canadv


canadv
q u. Case 5 compl canadv
q r e
ca p anre Canreq
ture no c canadv
d
co m
pl. accepte Case 6 compl canreq canadv
th.

canreq requ.
au

Ca Canreq declined Case 7 compl canreq


ne

n
re s re q n
li

canadv
On

pon o
ba

se Case 8 compl canreq canadv


tch

tion
cancella Case 9 canadv batch
qu.
no canreq re canadv n o ca n c
canreq ellation Case 10 canadv
ca n re accepted
q req tion
cancella Case 11 canreq canadv batch
Off

u.
ca n a d
line

v
C

n o ca n c
an

Canr
eq de ellation Case 12 canreq canadv
re
aut

clined
q
no
h.

re

Case 13 canreq batch


sp
on

canadv
se

Case 14 canreq canadv batch

ca canadv
pt Case 5 compl canadv
ur u.
e q re q
co a n re C a n re q canadv
m no c
pl pted Case 6 compl canreq canadv
. a cce
canreq requ.
Canreq declined Case 7 compl canreq
bat

Ca
n
re s re q n o
ch

canadv
pon Case 8 compl canreq canadv
se

tion
cancella Case 9 canadv batch
qu.
no canreq re canadv
canreq n o ca n c Case 10 canadv
ellation
ca n re accepted
q req
u. ca n c ellation Case 11 canreq canadv batch
ca n a
dv
C
an

Canr n o ca n c Case 12 canreq canadv


ellation
re

eq de
q

cline
no

d
re

Case 13 canreq batch


sp
on

canadv batch
se

Canreq Case 14 canreq canadv

accepted canadv
Canreq decline
Case 15 canreq canadv [batch]
Transaction not in log canreq requ. d
Ca Case 16 canreq [batch]
n
re s re q
po no canadv [batch]
ns Case 17 canreq canadv
e

Figure 54 Cancellation Cases Tree List

- 233 -
Card Payments Message Usage Guide Version 5.0

5.4.2 Table of Cancellation Cases

The table below provides for each case the value of the key data components inside the messages or
configuration parameters.
It reads as follows:

Payment Case Refers to the possible payment that can be cancelled according to the
cancellation case.
Cancellation Refers to both AcceptorCancellationRequest and
Request AcceptorCancellationResponse messages.
Cancellation Refers to an AcceptorCancellationAdvice message.
Advice
Batch Refers to a BatchTransfer message.

Cancellation
Request
condition Express the condition for Cancellation exchange:
 CancExch = Advice: the configuration parameter OnlineTransaction.
CancellationExchange or OfflineTransaction. CancellationExchange has the
value Advice.
 CancExch = Request: the configuration parameter OnlineTransaction.
CancellationExchange or OfflineTransaction. CancellationExchange has the
value Request.

Response Refers to Response data component to be used in an


AcceptorCancellationResponse messages to give the outcome of the requested
cancellation:
 Appr.: for the values Approved.
 Decl.: for the values Declined.
Capture undone Give the final outcome of the cancellation.

- 234 -
Card Payments Message Usage Guide Version 5.0

Cancellation
Advice
Advice Sent Express the requirement to send or not an Advice.:
 True: A cancellation advice MUST be sent.
 False: A cancellation advice MUST NOT be sent.

Capture undone Give the final outcome of the cancellation.


Reverse Flag Refers to the Reversal component to be used in an AcceptorCancellationAdvice
to inform the acquirer that no response was received for a CancellationRequest:
 False: Default value.
 True: no acceptable CancellationResponse message has been received, or
cancellation couldn't be completed successfully after an approved
cancellation request.

Batch
Cancellation in Express the condition to include the cancellation transaction in a Batch transfer:
batch  Empty cell: the cancellation is never included in a Batch transfer,
 BatchCont=Cancellation: the cancellation transaction is included in the Batch
transfer because the configuration parameter BatchTransferContent has the
value Cancellation.,
 BatchCont≠Cancellation: the cancellation transaction is not included in the
Batch transfer because the configuration parameter BatchTransferContent
has not the value Cancellation.,

Cancellation Request Cancellation Advice Batch


Payment Case Capture Advice Capture Reverse Cancellation
Condition Resp
Undone sent undone flag in batch

Capture Auth.
CancExch=
1 No cancellation requ. 1,2 True True False
Advice
Cancellation advice
Capture Auth.
Cancellation requ. CancExch=
2 1,2 Appr. True True False False
Canc. approved Request
Cancellation advice
Capture Auth.
CancExch=
3 Cancellation requ. 1,2 Decl. False False
Request
Canc. declined
Capture Auth.
Cancellation requ. CancExch= No
4 1,2 False True False True
Canc. no response Request resp.
Cancellation advice

- 235 -
Card Payments Message Usage Guide Version 5.0

Capture Completion. 3,9,10,18,19,28,


CancExch=
5 No cancellation requ. 29,35,36,41,42, True True False
Advice
Cancellation advice 44,45,47,54,61

Capture Completion
Cancellation requ. 3,9,10,18,19,28,
CancExch=
6 29,35,36,41,42, Appr. True True False False
Canc. approved Request
44,45,47,54,61
Cancellation advice
Capture Completion 3,9,10,18,19,28,
CancExch=
7 Cancellation requ. 29,35,36,41,42, Decl. False False
Request
Canc. declined 44,45,47,54,61

Capture Completion
Cancellation requ. 3,9,10,18,19,28,
CancExch= No
8 29,35,36,41,42, False True False True
Canc. no response Request resp.
44,45,47,54,61
Cancellation advice
Batch Capture .
No cancellation requ. 4,5,11,20,21,30,
CancExch= BatchCont=
9 31,37,43,46,48, True False False
Cancellation advice Advice Cancellation
49,55,56,62,63
Cancellation in batch
Batch Capture
No cancellation requ. 4,5,11,20,21,30,
1 CancExch= BatchCont≠
Cancellation advice 31,37,43,46,48, True False False
0 Advice Cancellation
49,55,56,62,63
Cancellation not in
batch
Batch Capture
Cancellation requ. 4,5,11,20,21,30,
1 CancExch= BatchCont=
Canc. approved 31,37,43,46,48, Appr. True True False False
1 Request Cancellation
Cancellation advice 49,55,56,62,63

Cancellation in batch
Batch Capture
Cancellation requ.
1 4,5,11,20,21,30,
Canc. approved CancExch= BatchCont≠
31,37,43,46,48, Appr. True True False False
2 Cancellation advice Request Cancellation
49,55,56,62,63
Cancellation not in
batch
Batch Capture 4,5,11,20,21,30,
1 CancExch=
Cancellation requ. 31,37,43,46,48, Decl. False False
3 Request
Canc. declined 49,55,56,62,63

Batch Capture
1 Cancellation requ. 4,5,11,20,21,30,
CancExch= No
31,37,43,46,48, False True False True
4 Canc. no response Request resp.
49,55,56,62,63
Cancellation advice
Transaction not in 1,2,3,4,5,9,10,1
log 1,18,19,20,21,2
1 Cancellation requ. 8,29,30,31,35,3
BatchCont≠
6,37,41,42,,43,4 N/A Appr. True True False False
5 Canc. approved Cancellation
4,45,,46,47,48,4
Cancellation advice 9,54,55,56,61,6
2,63

- 236 -
Card Payments Message Usage Guide Version 5.0

Transaction not in 1,2,3,4,5,9,10,1


log 1,18,19,20,,21,2
1 Cancellation requ. 8,29,30,31,35,3
BatchCont≠
6,37,41,42,43,4 N/A Decl. False False
6 Canc. declined Cancellation
4,45,,46,47,48,4
9,54,55,56,61,6
2,63
Transaction not in 1,2,3,4,5,9,10,1
log 1,18,19,20,,21,2
1 Cancellation requ. 8,29,30,31,35,3
No BatchCont≠
6,37,41,42,43,4 N/A False True False True
7 Canc. no response resp. Cancellation
4,45,,46,47,48,4
Cancellation advice 9,54,55,56,61,6
2,63

Table 4: List of Cancellation Cases

- 237 -
Card Payments Message Usage Guide Version 5.0

6 Additional Payment Services


Unless stated otherwise, specifications presented in the previous sections refer to the standard
payment (i.e. Transaction.TransactionType = "CardPayment" with AdditionalService and
ServiceAttribute absents). This section contains specifications related to other values of
TransactionType, or AdditionalService and ServiceAttribute when these are presents.

6.1 Voice Authorisation


Voice Authorisation is an additional feature to approve a transaction over the phone when requested
in the AcceptorAuthorisationResponse.
1. The Acceptor performs an online authorisation, sending an AcceptorAuthorisationRequest for a
main service populated in the TransactionType component.
2. The Acquirer declined the authorisation (Response= "Declined"), and requests a voice
authorisation setting the action Referral in the message element Action.ActionType of the
AcceptorAuthorisationResponse message. The Acceptor is expected to provide information
included in the authorisation exchanged to the Voice Authorisation service verbally.
3. If the transaction is approved through the Voice Authorisation,
a. The Voice Authorisation service provides an authorisation code by phone to the Acceptor
and the transaction can be successfully completed.
b. The transaction must be captured by completion or batch with the following information:
 One occurrence of AdditionalService added and set to "VoiceAuthorisation",
 TransactionSuccess equal "True",
 AuthorisationResult.AuthorisationCode containing the authorisation code provided with
the Acquirer,
 ResponseToAuthorisation.Response set to "Declined",
c. In the Completion exchange TransactionCapture is present with the value "True" if the
Acceptor is configured to make the financial capture with the Authorisation or the
Completion.
Acceptor Acquirer

AcceptorAuth
online authorisation 1 orisa tionRequest

Response:Declined
2
ns e ActionType:Referral
orisationRespo
AcceptorAuth

Voice authorisation by phone:


approved authorisation with 3
a
authorisation code x...x

TransactionCapture:True
AdditionalService:VoiceAuthorisation
3 AcceptorCompl
TransactionSuccess:True b etio nAdvice
ResponseToAuthorisation:Declined
AuthorisationCode:x...x
e
etion AdviceRespons
AcceptorCompl

Figure 55: Successful Voice Authorisation captured with Completion

- 238 -
Card Payments Message Usage Guide Version 5.0

1. If the voice authorisation is declined, the transaction fails. The Acceptor must not send a capture,
and has to follow the the standard process flow of the declined transactions for the Completion
exchange (see section 5 Dynamic of the Payment Exchanges). If the transaction is sent in a
completion or a batch, it contains the following informations:
 TransactionCapture present with the value "False".
 An occurrence of AdditionalService must be added and set to "VoiceAuthorisation",
 TransactionSuccess equal "False".
 AuthorisationResult.AuthorisationCode is absent.
 ResponseToAuthorisation.Response set to "Declined"

Acceptor Acquirer

AcceptorAuth
online authorisation 1 orisa tionRequest

Response:Declined
2
tionResponse ActionType:Referral
orisa
AcceptorAuth

Voice authorisation by phone:


declined authorisation, no 4
authorisation code

TransactionCapture:False AcceptorCompl
etio nAdvice
AdditionalService:VoiceAuthorisation
TransactionSuccess:False
ResponseToAuthorisation:Declined e
etion AdviceRespons
AcceptorCompl

Figure 56: Unsuccessful Voice Authorisation captured with Completion.

- 239 -
Card Payments Message Usage Guide Version 5.0

The Acceptor is not necessary blocked between the declined/referral authorisation and the result of
the Voice Authorisation. Other transactions may be interleaved between the declined/referral
authorisation and the Completion containing the outcome of the Voice Authorisation. In the figure
below:
 An AcceptorAuthorisationRequest is declined with the ActionType "Referral" (transaction 1);
 Another payment transaction is performed on the terminal with an online authorisation and a
completion exchange (transaction 2);
 The Acceptor contact the voice authorisation center to get the authorsation code for
transaction 1;
 The Acceptor initiates a Completion after entering the authorisation code.
Acceptor Acquirer

AcceptorAuthorisationRequ
start transaction 1 est 1
Response:Declined
nse 1 ActionType:Referral
AcceptorAuthorisationRespo

AcceptorAuthorisationRequ
est 2
Response:Approved
nse 2
AcceptorAuthorisationRespo
transaction 2
AcceptorCompletionAdvice 2

pon se 2
AcceptorCompletionAdviceRes

Voice authorisation by phone:


approved authorisation with
authorisation code x...x

end transaction 1 AcceptorCompletionAdvice 1


AdditionalService:
VoiceAuthorisation pon se 1
AcceptorCompletionAdviceRes

Figure 57: Successful Voice Authorisation Interleaved with another transaction

- 240 -
Card Payments Message Usage Guide Version 5.0

An example of successful Voice Authorisation with Batch capture and no Completion is presented in
the figure below. The batch contains one occurrence of TransactionToCapture with:
 AdditionalService = "VoiceAuthorisation",
 TransactionSuccess = "True",
 ResponseToAuthorisation.Response = "Declined",
 AuthorisationCode containing the code provided by phone.

Acceptor Acquirer

AcceptorAuth
online authorisation orisa tionRequest

Response:Declined
nse ActionType:Referral
orisationRespo
AcceptorAuth

Voice authorisation by phone:


approved authorisation with
authorisation code x...x

other transactions [other transactions]

TransactionToCapture[n]
AdditionalService:VoiceAuthorisation
AcceptorBatchT
TransactionSuccess:True rans fer
ResponseToAuthorisation:Declined
AuthorisationCode:x...x
Tran sferResponse
AcceptorBatch

Figure 58: Successful Voice Authorisation Captured with Batch without Completion

- 241 -
Card Payments Message Usage Guide Version 5.0

6.2 Deferred Payments

6.2.1 Introduction
Deferred payment is a service which enable the Acceptor to:
 Request an authorisation to get a maximum amount to be able to pay,
 Complete the delivery of goods or use of service to be paid up to the maximum amount,
 Inform the Acquirer of the payment of these goods or services with the final amount.

The Authorisation and Completion exchanges are required to perform a deferred payment transaction.
Acceptor Acquirer

AcceptorAuthorisationRequ
est
maximum amount
maximum amount nse
AcceptorAuthorisationRespo

Delivery of goods
Use of service

AcceptorCompletionAdvice

final amount
ponse
AcceptorCompletionAdviceRes

Figure 59: Deferred Payment

During delivery of goods, other payment transactions can be performed, and the two steps of a
deferred payment transaction (Authorisation exchange and Completion exchange) may be interleaved.
Acceptor Acquirer

AcceptorAuthorisationRequ
est 1

nse 1
AcceptorAuthorisationRespo

AcceptorAuthorisationRequ
Delivery of goods est 2
transaction 1
nse 2
AcceptorAuthorisationRespo

AcceptorCompletionAdvice
1
Delivery of goods
ponse 1
AcceptorCompletionAdviceRes transaction 2

AcceptorCompletionAdvice
2

ponse 2
AcceptorCompletionAdviceRes

Figure 60: Interleaved Deferred Payment Transactions

A deferred payment transaction is characterised in the exchanged messages by the value


"DeferredPayment" of the data element TransactionType.

- 242 -
Card Payments Message Usage Guide Version 5.0

6.2.2 Constraints on the Protocol


The deferred payment transaction respects the following rules, particular to this service:

1. The Authorisation is performed online.

2. If an approved AcceptorAuthorisationResponse is received by the Acceptor, and goods or


services have been delivered, an AcceptorCompletionAdvice message must be sent with:
 MessageFunction = "CompletionAdvice" or "FinancialCompletionAdvice",
 TotalAmount with the final amount,
 Reversal = "False" or absent,
 TransactionSuccess = "True".
Acceptor Acquirer

AcceptorAuthorisationRequ
est
maximum amount
Response:Approved
nse
AcceptorAuthorisationRespo

delivery of goods/service

AcceptorCompletionAdvice
TotalAmount:final amount

ponse
AcceptorCompletionAdviceRes

Figure 61: Approved Deferred Payment without Delivery


3. The Completion exchange is mandatory, except when the two following conditions are
fullfilled:
 the AcceptorAuthorisationResponse has been received by the Acceptor, the authorisation
is declined and the payment transaction is not overridden by the Merchant, and
 the Acceptor is not configured to send a completion for declined online authorisations
(see section 5, Dynamic of the Payment Exchanges),
The AcceptorAuthorisationResponse of a declined deferred payment must have the final
amount TotalAmount with a copy of the value sent in the AcceptorAuthorisationRequest.
Acceptor Acquirer

AcceptorAuthorisationRequ
est
Response:Declined
maximum amount
nse
AcceptorAuthorisationRespo
No delivery of goods/service
(if configured to not send
declined)

Figure 62: Declined Deferred Payment

4. If the AuthorisationRequest contains AmountQualifier value:


 "Estimated", the AuthorisationResponse may contain TotalAmount higher, equal or
lower than in the request,
 "Maximum", the AuthorisationResponse may contain TotalAmount equal or lower than
in the request,
If the authorisation is approved, ResponseToAuthorisation.Response must be :

- 243 -
Card Payments Message Usage Guide Version 5.0

 "Approved" when TotalAmount of the AuthorisationResponse is higher than or equal to


the requested amount,
 "PartialApproved" when TotalAmount of the AuthorisationResponse is lower than in the
request.

5. If the authorisation is approved, the Completion exchange must be performed immediately


after the finalisation of the delivery of goods or service with:
 A value of TotalAmount lower or equal the value of TotalAmount sent in the
AcceptorAuthorisationResponse,
 AmountQualifier absent or equal to "Actual".
The configuration parameters of the Completion (TMS parameters
OnlineTransaction.CompletionExchange or OfflineTransaction.CompletionExchange) as well
as the CompletionRequired of the AuthorisationResponse are ignored.

6. The financial capture must be performed either within the Completion exchange, or through a
batch transfer. It cannot be performed as part of the Authorisation exchange.
Acceptor Acquirer

AcceptorAuthorisationRequ
est
maximum amount
Response:Approved
nse
AcceptorAuthorisationRespo

Delivery of goods/
Use of service

AcceptorCompletionAdvice
TransactionCapture:True

ponse
AcceptorCompletionAdviceRes

Figure 63: Deferred Payment Captured by Completion

Acceptor Acquirer

AcceptorAuthorisationRequ
est
maximum amount
Response:Approved
nse
AcceptorAuthorisationRespo
Delivery of goods/
Use of service
AcceptorCompletionAdvice
TransactionCapture:False

ponse
AcceptorCompletionAdviceRes

AcceptorBatchTransfer

se
AcceptorBatchTransferRespon

Figure 64: Deferred Payment Captured by Batch

- 244 -
Card Payments Message Usage Guide Version 5.0

7. After confirmation to the sale system that the goods can be delivered (e.g. after the payment
response to the sale system of the Retailer protocol), if the goods or services have not been
delivered because the customer did not continue or the delivery failed, an
AcceptorCompletionAdvice message must be sent with:
 MessageFunction = "CompletionAdvice" or "FinancialCompletionAdvice",
 TotalAmount with the value "0",
 Reversal = "False",
 TransactionSuccess = "True",
 FailureReason = "CustomerCancel", "Malfunction".
Acceptor Acquirer

AcceptorAuthorisationRequ
est
maximum amount
Response:Approved
nse
AcceptorAuthorisationRespo

No delivery of goods/service

AcceptorCompletionAdvice
TotalAmount:0

ponse
AcceptorCompletionAdviceRes

Figure 65: Approved Deferred Payment without Delivery

8. If there is an incident after receiving an approved AcceptorAuthorisationResponse, but before


confirming to the sale system that the goods can be delivered, an AcceptorCompletionAdvice
message must be sent with:
 MessageFunction = "ReversalAdvice",
 TotalAmount with the maximum authorised amount,
 Reversal = "True",
 TransactionSuccess = "False",
 FailureReason = "CardDeclined", "CustomerCancel", "Malfunction" or
"UnableToComplete".

9. The following scenarios from the Table 2 - List of Payment Cases page Erreur ! Signet non
défini. do not apply to the DeferredPayment type of transaction:
 All the offline authorisation cases are irrelevant (cases 47 to 63)
 All the cases where financial capture is performed during the authorisation (cases 1, 2,
6, 9,12, 13, 18, 22, 23, 28, 32, 35, 38, 41 and 44),
 The successful transaction cases where the completion is not required (cases 4, 20,
and 30).

- 245 -
Card Payments Message Usage Guide Version 5.0

6.3 Cashback
This feature allows the cardholder to obtain cash from the Card Acceptor in conjunction with a
payment. The cardholder receives the extra cash amount in notes or coins along with the
goods/services.
It is an additional feature on a payment and does not change message exchanges.
A cashback transaction must only permit the dispensing of cash on successful authorisation or
successful referral.

A cashback transaction must obey the following rules :


1. The cardholder must be present at the POI (PaymentContext.CardholderPresent = ”True”)
2. Cashback is requested in the AcceptorAuthorisationRequest (Transaction.TransactionType=
”CashBack”)
3. An instance of TransactionDetails.DetailedAmount must be included in AuthorisationRequest and
AuthorisationResponse messages:
 Type=”CashBack”
 Value=(cashback amount)
4. If Response = “Approved” or "PartialApproved", the authorised cashback amount (which may be
0) is returned in the AcceptorAuthorisationResponse message.
5. Any cashback given to the cardholder must be included in the AcceptorCompletionAdvice and
AcceptorBatchTransfer messages. If no cashback is delivered, a value of 0 is used.

- 246 -
Card Payments Message Usage Guide Version 5.0

6.4 Cash Advance


This is a service which allows the card acceptor to give cash to the cardholder without any other
goods or services.
It is a special case of a payment and does not change message exchanges.
A cash advance transaction must only permit the dispensing of cash on successful authorisation or
successful referral.
Normally a cash advance would be a face-to-face transaction between the card acceptor and
cardholder but with the rise of internet-based currency exchanges, this protocol does not limit the cash
advance service to this environment.

A cash advance transaction must obey the following rules :


1. Cash advance is requested in the AcceptorAuthorisationRequest with TransactionType=
”CashAdvance”.
2. The amount of cash advance transaction (TransactionDetails.TotalAmount) is the amount of
cash being distributed.
3. The Authorisation is always online ( PaymentContext.OnLineContext=”True”).

- 247 -
Card Payments Message Usage Guide Version 5.0

6.5 Gratuity
This feature allows adding a supplementary amount to the payment of goods/services.
It is an additional service on a payment and does not change message exchanges.
This protocol does not address any business rules regarding when in the payment process a gratuity
may be added to the transaction nor when a gratuity may need additional authorisations.

This protocol shows two different methods for implementing gratuity :


1. Gratuity is added before authorisation
2. Gratuity is added after authorisation
The cardholder must be present at the POI,PaymentContext.CardholderPresent=”True”.
Whenever a gratuity amount is included in a message exchange it must be clearly identified in an
instance of TransactionDetails.DetailedAmount as follows :
 Type=”Gratuity”
 Value=(gratuity amount)

Gratuity added before authorisation


1. A card payment is requested in the AcceptorAuthorisationRequest
 Transaction.AddtionalService=”Gratuity”
2. The total amount, TransactionDetails.TotalAmount, of a gratuity transaction
(TransactionDetails.TotalAmount) in the AcceptorAuthorisationRequest is the sum amount of
purchase amount and the gratuity amount.
3. If Response = “Approved” or "PartialApproved", the authorised gratuity amount (which may be
0) is returned in the AcceptorAuthorisationResponse message.

Gratuity added after authorisation


Gratuity must only be present in the AcceptorCompletionAdvice or AcceptorBatchTransfer.

Any gratuity must be included in the AcceptorCompletionAdvice and AcceptorBatchTransfer


messages related to the transaction and TotalAmount must contain the sum amount of purchase
amount and the gratuity amount.

6.6 Reservation

6.6.1 Introduction

A reservation service is mostly used in hotels and for rental business (car, video …). The reservation
service is implemented through one mandatory and four optional steps:

Mandatory step for standard case :


 Initial Reservation

Optional steps
 Update Reservation

- 248 -
Card Payments Message Usage Guide Version 5.0

 Cancellation of the Reservation (before payment)

 Payment after Reservation, it may be a No-show Payment

 Additional Payment after Reservation

A No Show payment can be performed without prior reservation.

6.6.2 Reservation steps

6.6.2.1 Initial Reservation


The “Initial Reservation” allows the card acceptor to reserve an amount for a specified period of time in
order to secure that sufficient fund is available to complete a subsequent payment.

6.6.2.2 Update Reservation


The “Update Reservation” allows the card acceptor to change the amount and/or the specified period
of a Reservation. An approved update reservation must cancel and replace the previous approved
initial or update reservation.

6.6.2.3 Cancellation of the Reservation (before payment)


If the Cancellation of the reservation occurs before the payment is performed; then it allows the card
acceptor to cancel a previously approved reservation.

6.6.2.4 Payment for the Reservation


The Payment for the Reservation allows the card acceptor to make a payment using a previously
approved initial or updated reservation.
The amount may be zero.

6.6.2.5 No show Payment for the Reservation


The “No show Payment for the Reservation” allows the card acceptor to charge the cardholder for an
agreed amount because the cardholder did not show up as expected.

6.6.2.6 Additional Payment (after Payment for the Reservation)


The “Additional Payment” allows the card acceptor to charge the cardholder for additional expenses
after the “Payment for the Reservation” has been done.
If the cardholder is absent during this phase, stored card data will be used which implies that the card
security code is not present. This transaction has to be identified as Additional Payment linked to the
reservation.

6.6.2.7 No-show payment without performing a prior reservation service


A no-show transaction can be performed although no prior reservation transaction was carried out.

6.6.3 Message flows


Message flows regarding the Authorisation Request, Authorisation Response, Completion Advice
and Completion Response are the same as for any other service and are therefore not specifically
documented here.

- 249 -
Card Payments Message Usage Guide Version 5.0

6.6.4 Description of the steps

6.6.4.1 Initial reservation


The initial reservation transaction always processes an online Authorisation to reserve an amount for a
specific period for a later payment of goods or services. Financial Capture with the authorisation is not
applicable.

If the authorisation request is approved by the card acceptor:


 Depending on the protocol configuration a successful completion can be sent

 The possible subsequent steps are:

o The reservation can be cancelled

o An update reservation can be done

o A payment after reservation or a No show payment after reservation can be done

If the authorisation request is declined:


 The reservation process is ended and, based on configuration, a completion may be sent.

A completion for an unsuccessful transaction must be sent under the following conditions:
 An approved authorisation is not correctly completed at card acceptor side
 There is no response to the authorization request
 The response of the authorization request is received too late:

Then the reservation process is ended

6.6.4.2 Update reservation


The update reservation transaction always processes an online Authorisation to change the previous
reservation amount and/or the specified period. Financial Capture with the authorisation is not
applicable

If the authorisation request is approved and correctly processed by the card acceptor:
 Depending on the configuration a successful completion can be sent

 The possible subsequent steps are:

o The reservation can be cancelled

o A new update reservation can be done

o A payment after reservation or a No show payment after reservation can be done

If the authorisation request is declined:


 The previous reservation remains unchanged.

6 Additional Payment Services - 250 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

If an approved update authorisation transaction is not correctly completed or if there is no response


or if the response is received too late :
 An unsuccessful completion must be sent.

 The previous reservation remains unchanged.

6.6.4.3 Cancellation of the reservation (before payment)


A reservation can be cancelled before the payment takes place. A reversal (completion) is sent on line
to reverse the reservation. The reservation process is ended.

6.6.4.4 Payment after reservation


A payment after reservation is carried out through a completion advice or batch transfer.
A Payment After Reservation can be a No Show payment
The reservation process is ended, nevertheless, the following subsequent steps are possible:
 An additional payment can be done.

 The payment for the reservation can be cancelled.

6.6.5 Reservation transaction data


Message structures regarding the Authorisation Request, Authorisation response, Completion Advice
and Completion Response are the same as for a normal payment and only the components with
specific reservation tags or values are represented in these tables.

6.6.5.1 Initial reservation

6.6.5.1.1 AcceptorAuthorisationRequest
AcceptorAuthorisationRequest Mult. Rule Usage
Header [1..1] It conveys information related to the protocol management on a segment of
the path from the Acceptor to the Acquirer:
MessageFunction [1..1] The only valid codes to request an authorisation for an initial reservation is:
AuthorisationRequest: Request without financial capture
(TransactionCapture="False")

(if an invalid value is received, a Reject message is sent by the Recipient


with RejectReason equal to "ParsingError")

AuthorisationRequest [1..1] The Header.MessageFunction must be "AuthorisationRequest".
(In case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to "ParsingError")

Transaction [1..1]
TransactionCapture [1..1] TransactionCapture = "False"
TransactionType [1..1] " Reservation "

ServiceAttribute [0..1] Mandatory. Equal to “InitialReservation”

SaleReferenceIdentification [0..1] Mandatory for reservation

OriginalTransaction [0..1] Appli Not used if TransactionType="Reservation” and
ServiceAttribute=”InitialReservation”

6 Additional Payment Services - 251 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Usage



TransactionDetails [1..1]

AmountQualifier [0..1] “Estimated”


ValidityDate [0..1] Config The date after which the reservation expires
...

6 Additional Payment Services - 252 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

6.6.5.1.2 AcceptorAuthorisationResponse
AcceptorAuthorisationResponse Mult. Rule Usage
Header [1..1] see AcceptorAuthorisationRequest
MessageFunction [1..1] The only valid codes to request an authorisation for an initial reservation is:
AuthorisationResponse:

AuthorisationResponse [1..1] The Header.MessageFunction must be AuthorisationResponse

Transaction [1..1]

TransactionDetails [1..1]

ValidityDate [0..1] Config Depending of the scheme rules, the value of validity date in the
authorisation response may differ from the value contained in the
authorisation request

6.6.5.1.3 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice an initial reservation are :
CompletionAdvice: Completion without financial capture
(TransactionCapture=False, Reversal=False) or
(TransactionCapture=False, Reversal=True, TransactionSuccess=True)
ReversalAdvice: Reversal of an authorisation without financial capture
(TransactionCapture=False, Reversal=True, TransactionSuccess =False)
in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError

CompletionAdvice [1..1] The Header.MessageFunction must be CompletionAdvice, or
ReversalAdvice
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy
TransactionCapture [0..1] Config False or is absent

TransactionType [1..1] “”Reservation”


ServiceAttribute [0..1] “InitialReservation”

SaleReferenceIdentification [0..1] Mandatory for reservation

OriginalTransaction [0..1] Appli Not used if TransactionType="Reservation and
ServiceAttribute=”InitialReservation”"

MerchantOverride [0..1] Appli False or is absent
FailureReason [0..*] Appli CardDeclined, CustomerCancel, UnableToComplete, TimeOut

TransactionDetails [1..1]

AmountQualifier [0..1] Appli ““Estimated”

6 Additional Payment Services - 253 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Usage



ValidityDate [0..1] Config

6.6.5.1.4 AcceptorCompletionAdviceResponse
AcceptorCompletionAdviceRespon Mult. Rule Usage
se
Header [1..1]
MessageFunction [1..1] The only valid codes are:
CompletionAdviceResponse: response for CompletionAdvice
ReversalAdviceResponse: response for ReversalAdvice
(in case of an invalid value, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)

6.6.5.2 Update reservation

6.6.5.2.1 AcceptorAuthorisationRequest
AcceptorAuthorisationRequest Mult. Rule Usage
Header [1..1] It conveys information related to the protocol management on a segment of
the path from the Acceptor to the Acquirer:
MessageFunction [1..1] The only valid codes to request an authorisation for an update reservation
is:
AuthorisationRequest: Request without financial capture
(TransactionCapture="False")

(if an invalid value is received, a Reject message is sent by the Recipient


with RejectReason equal to "ParsingError")

AuthorisationRequest [1..1] The Header.MessageFunction must be "AuthorisationRequest".


(In case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to "ParsingError")

Transaction [1..1]
TransactionCapture [1..1] TransactionCapture = "False"
TransactionType [1..1] " Reservation "

ServiceAttribute [0..1] “UpdateReservation”

SaleReferenceIdentification [0..1] Must be the same value as the initial value

OriginalTransaction [0..1] Appli Mandatory if available. Identify the previous transaction within the
reservation process

TransactionType [1..1] “Reservation"

ServiceAttribute [0..1] “InitialReservation” or “UpdateReservation”

TransactionDetails [1..1]

AmountQualifier [0..1] “Estimated”

6 Additional Payment Services - 254 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Usage


ValidityDate [0..1] Config
...

6.6.5.2.2 AcceptorAuthorisationResponse
AcceptorAuthorisationResponse Mult. Rule Usage
Header [1..1] see AcceptorAuthorisationRequest
MessageFunction [1..1] The only valid codes to request an authorisation for an update reservation
is:
AuthorisationResponse:

AuthorisationResponse [1..1] The Header.MessageFunction must be AuthorisationResponse

Transaction [1..1]

TransactionDetails [1..1]

ValidityDate [0..1] Config Depending of the scheme rules, the value of validity date in the
authorisation response may differ from the value contained in the
authorisation request

6.6.5.2.3 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice an update reservation are :
CompletionAdvice: Completion without financial capture
(TransactionCapture=False, Reversal=False) or
(TransactionCapture=False, Reversal=True, TransactionSuccess=True)
ReversalAdvice: Reversal of an authorisation without financial capture
(TransactionCapture=False, Reversal=True, TransactionSuccess =False)
in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError

CompletionAdvice [1..1] The Header.MessageFunction must be CompletionAdvice, or
ReversalAdvice
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy
TransactionCapture [0..1] Config False or is absent

TransactionType [1..1] “”Reservation”


ServiceAttribute [0..1] “UpdateReservation”

SaleReferenceIdentification [0..1] Mandatory for reservation

OriginalTransaction [0..1] Appli Mandatory, Identify the previous transaction within the reservation process

TransactionType [1..1] “”Reservation”

6 Additional Payment Services - 255 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Usage



ServiceAttribute [0..1] “InitialReservation” or “updateReservation”

MerchantOverride [0..1] Appli False or is absent
FailureReason [0..*] Appli “CardDeclined, ” CustomerCancel, UnableToComplete, TimeOut

TransactionDetails [1..1]

AmountQualifier [0..1] Appli ““Estimated”

ValidityDate [0..1] Config

6.6.5.2.4 AcceptorCompletionAdviceResponse
AcceptorCompletionAdviceRespon Mult. Rule Usage
se
Header [1..1]
MessageFunction [1..1] The only valid codes are:
CompletionAdviceResponse: response for CompletionAdvice
ReversalAdviceResponse: response for ReversalAdvice
(in case of an invalid value, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)

6.6.5.3 Cancellation of a Reservation before payment

6.6.5.3.1 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice an initial reservation is :
ReversalAdvice: Reversal of an authorisation without financial capture
(TransactionCapture=False, Reversal=True,
in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError

CompletionAdvice [1..1] The Header.MessageFunction must be CompletionAdvice, or
ReversalAdvice
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy
TransactionCapture [0..1] Config False or is absent

TransactionType [1..1] “”Reservation”


ServiceAttribute [0..1] “InitialReservation” or “UpdateReservation”

SaleReferenceIdentification [0..1] Must be the same value as the initial reservation

OriginalTransaction [0..1] Appli Must be present if available

6 Additional Payment Services - 256 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Usage



TransactionSuccess [1..1] True
Reversal [0..1] Appli True
MerchantOverride [0..1] Appli False or is absent
FailureReason [0..*] Appli CustomerCancel, Malfunction

TransactionDetails [1..1]

TotalAmount [1..1] Appli Must be equal to zero as specified for normal payment: “equal to Final
amount of the payment transaction when TransactionSuccess is "True””.
AmountQualifier [0..1] Appli Actual or is absent

AuthorisedAmount [0..1] Appli Must be present as specified for normal payment. “Amount authorised for
the payment transaction, , mandatory if the authorized amount
(TotalAmount of the AcceptorAuthorisationResponse) is different from the
requested amount (TotalAmount of the AcceptorAuthorisationRequest)”

ValidityDate [0..1] Mandatory for reservation

6.6.5.3.2 AcceptorCompletionAdviceResponse
AcceptorCompletionAdviceRespon Mult. Rule Usage
se
Header [1..1]
MessageFunction [1..1] The only valid codes is:
ReversalAdviceResponse: response for ReversalAdvice
(in case of an invalid value, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)

6.6.5.4 Payment after reservation

6.6.5.4.1 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice a payment after reservation is:
FinancialCompletionAdvice: Completion with financial capture
(TransactionCapture=True, Reversal=False)

(in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

CompletionAdvice [1..1] The Header.MessageFunction must be FinancialCompletionAdvice.
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy
TransactionCapture [0..1] Config True

TransactionType [1..1] “”Reservation”


AdditionalService [0..*] “NoShow” is possible for a payment after reservation

6 Additional Payment Services - 257 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Usage


ServiceAttribute [0..1] “PaymentReservation”

SaleReferenceIdentification [0..1] Must be the same value as the initial reservation

Reversal [0..1] False or is absent”

OriginalTransaction [0..1] Appli Mandatory, Identify the previous transaction within the reservation process

TransactionType [1..1] “”Reservation”
ServiceAttribute [0..1] “InitialReservation” or “updateReservation”

TransactionDetails [1..1]

AmountQualifier [0..1] Appli “Actual” or is absent

ValidityDate [0..1] Config

6.6.5.4.2 AcceptorCompletionAdviceResponse
AcceptorCompletionAdviceRespon Mult. Rule Usage
se
Header [1..1]
MessageFunction [1..1] The only valid codes are:
FinancialCompletionAdviceResponse: response for CompletionAdvice
(in case of an invalid value, a Reject message is sent by the Recipient
with RejectReason equal to ParsingError)

6.6.5.4.3 AcceptorCancellationRequest
AcceptorCancellationRequest Mult. Rule Usage

CancellationRequest [1..1] The Header.MessageFunction must be CancellationRequest.
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to “ParsingError”)

Transaction [1..1]

SaleReferenceIdentification [0..1] Mandatory for reservation

TransactionDetails [1..1]

ValidityDate [0..1] Config

6.6.5.4.4 AcceptorCancellationResponse

Refer to Normal Payment

6 Additional Payment Services - 258 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

6.6.5.4.5 AcceptorCancellationAdvice
AcceptorCancellationAdvice Mult. Rule Usage

CancellationAdvice [1..1] The Header.MessageFunction must be CancellationAdvice.


(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1]

SaleReferenceIdentification [0..1] Mandatory for reservation

TransactionDetails [1..1]

ValidityDate [0..1] Config


6.6.5.4.6 AcceptorCancellationAdviceResponse

Refer to Normal Payment

6.6.5.5 Additional payment

6.6.5.5.1 AcceptorAuthorisationRequest
AcceptorAuthorisationRequest Mult. Rule Usage
Header [1..1] It conveys information related to the protocol management on a segment of
the path from the Acceptor to the Acquirer:
MessageFunction [1..1] The only valid codes to request an authorisation for payment after
reservation are:
AuthorisationRequest: Request without financial capture
(TransactionCapture="False")
FinancialAuthorisationRequest: Request with financial capture
TransactionCapture="True")
(if an invalid value is received, a Reject message is sent by the Recipient
with RejectReason equal to "ParsingError")

AuthorisationRequest [1..1] The Header.MessageFunction must be "AuthorisationRequest" or
"FinancialAuthorisationRequest".
(In case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to "ParsingError")

Transaction [1..1]

TransactionType [1..1] "Reservation"

ServiceAttribute [0..1] “AdditionalPayment”

SaleReferenceIdentification [0..1] Must be the same value as the initial reservation

OriginalTransaction [0..1] Appli Not used if TransactionType="Reservation and
ServiceAttribute=”“AdditionalPayment”

6 Additional Payment Services - 259 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorAuthorisationRequest Mult. Rule Usage



TransactionDetails [1..1]

AmountQualifier [0..1] “Actual”


ValidityDate [0..1] Config
...

6.6.5.5.2 AcceptorauthorisationResponse

Refer to Normal Payment

6.6.5.5.3 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice a payment after reservation are:
CompletionAdvice: Completion without financial capture
(TransactionCapture=False, Reversal=False) or
(TransactionCapture=False, Reversal=True,
TransactionSuccess=True)
FinancialCompletionAdvice: Completion with financial capture
(TransactionCapture=True, Reversal=False) or
(TransactionCapture=True, Reversal=True, TransactionSuccess
=True)
ReversalAdvice: Reversal of an authorisation without financial capture
(TransactionCapture=False, Reversal=True, TransactionSuccess
=False)
FinancialReversalAdvice: Reversal of a FinancialAuthorisation
(TransactionCapture=True, Reversal=True, TransactionSuccess
=False)
(in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

CompletionAdvice [1..1] The Header.MessageFunction must be CompletionAdvice,
FinancialCompletionAdvice, ReversalAdvice or FinancialReversalAdvice.
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy

TransactionType [1..1] “”Reservation”

ServiceAttribute [0..1] “AdditionalPayment

SaleReferenceIdentification [0..1] Must be the same value as the inital reservation

OriginalTransaction [0..1] Appli Not used if TransactionType="Reservation and
ServiceAttribute=”AdditionalPayment”"

TransactionDetails [1..1]

6 Additional Payment Services - 260 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

AcceptorCompletionAdvice Mult. Rule Usage


ValidityDate [0..1] Config

6.6.5.5.4 AcceptorCompletionAdviceResponse

Refer to Normal Payment

6.6.5.5.5 AcceptorCancellationRequest
AcceptorCancellationRequest Mult. Rule Usage

CancellationRequest [1..1] The Header.MessageFunction must be CancellationRequest.
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to “ParsingError”)

Transaction [1..1]

SaleReferenceIdentification [0..1] Mandatory for reservation

TransactionDetails [1..1]

ValidityDate [0..1] Config

6.6.5.5.6 AcceptorCancellationResponse

Refer to Normal Payment

6.6.5.5.7 AcceptorCancellationAdvice
AcceptorCancellationAdvice Mult. Rule Usage

CancellationAdvice [1..1] The Header.MessageFunction must be CancellationAdvice.


(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1]

SaleReferenceIdentification [0..1] Mandatory for reservation

TransactionDetails [1..1]

ValidityDate [0..1] Config


6 Additional Payment Services - 261 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

6.6.5.5.8 AcceptorCancellationAdviceResponse

Refer to Normal Payment

6.6.5.6 No show payment without prior reservation

6.6.5.6.1 AcceptorCompletionAdvice
AcceptorCompletionAdvice Mult. Rule Usage
Header [1..1]
MessageFunction [1..1] The only valid codes to advice no show payment is ::
FinancialCompletionAdvice: Completion with financial capture
(TransactionCapture=True, Reversal=False)

(in case of an invalid value, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

CompletionAdvice [1..1] The Header.MessageFunction must be FinancialCompletionAdvice.
(if not the case, a Reject message is sent by the Recipient with
RejectReason equal to ParsingError)

Transaction [1..1] CCopy

TransactionType [1..1] “”CardPayment”
AdditionalService [1..1] “”NoShow”

6.6.5.6.2 AcceptorCompletionAdviceResponse

Refer to Normal Payment

6.6.5.6.3 AcceptorCancellationRequest

Refer to Normal Payment

6.6.5.6.4 AcceptorCancellationResponse

Refer to Normal Payment

6.6.5.6.5 AcceptorCancellationAdvice

Refer to Normal Payment

6.6.5.6.6 AcceptorCancellationAdviceResponse

Refer to Normal Payment

6 Additional Payment Services - 262 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

6.6.5.7 Batch

6.6.5.7.1 AcceptorBatchTransfer
Or AceptorBatchTransfer Mult. Rule Type / Definition / Code List
Header [1..1]

BatchTransfer [1..1]

DataSet [0..*] A data set may include both financial (completed transactions)
and non financial transactions (uncompleted transactions).
TransactionTotals [1..*] TransactionTotals of the DataSet.

Type [1..1] see AcceptorReconciliationRequest for Reservation

CommonData [0..1] Data common to transactions of a DataSet may be factorised in
CommonData to reduce the message length.
All transactions of the DataSet inherit the data element value
present in CommonData except if this data element is present
in the occurrence of Transaction.

TransactionType [0..1] “Reservation”
AdditionalService [0..*] “NoShow” is posiible
ServiceAttribute [0..1] “PaymentReservation”

Transaction [1..*] Transaction of the data set.It must be a completion, a
cancellation advice, an authorisation request or an authorisation
response.
{Or Completion [1..1]

Transaction [1..1]
TransactionType [0..1] “Reservation”
AdditionalService [0..*] “NoShow” is posiible
ServiceAttribute [0..1] “PaymentReservation”

SaleReferenceIdentification [0..1] Appli Mandatory for Reservation

TransactionIdentification [1..1] see AcceptorCompletionAdvice for Reservation after payment

OriginalTransaction [0..1] Appli see AcceptorCompletionAdvice for Reservation after payment

TransactionDetails [1..1] see AcceptorCompletionAdvice for Reservation after payment

Or Cancellation [1..1] Cancelled card payment transaction.

Transaction [1..1] see AcceptorCancellationAdvice for reservation after payment

Or AuthorisationRequest [1..1] Authorisation request of a card payment transaction.

Transaction [1..1] see AcceptorAuthorisationRequest for Initial and update
reservation

Or} AuthorisationResponse [1..1] Authorisation response of a card payment transaction.

6 Additional Payment Services - 263 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

Or AceptorBatchTransfer Mult. Rule Type / Definition / Code List



Transaction [1..1] see AcceptorAuthorisationResponse for Initial and update
reservation

6.6.5.8 Reconciliation

6.6.5.8.1 AcceptorReconciliationRequest
AcceptorReconciliationRequest Mult. Rule Usage

ReconciliationRequest [1..1] The Header.MessageFunction must be ReconciliationRequest.
(if not the case, a Reject message is sent by the Recipient with RejectReason
equal to ParsingError)

Transaction [1..1]

TransactionTotals [0..*] TransactionTotals of the reconciliation period.
TransactionTotals is absent if the reconciliation period contains no transactions.

Type [1..1] All the values are allowed:
Debit: Debit transactions (TransactionType is CardPayment, CashBack,
CashAdvance, DeferredPayment, Reservation) during the reconciliation
period.
DebitReverse: Cancelled debit transactions.
Credit: Credit transactions (TransactionType is Refund during the
reconciliation period.
CreditReverse: Cancelled credit transactions.
Declined: transactions declined online or offline.
Failed: failed transactions.

6.6.5.8.2 AcceptorReconciliationResponse

Refer to Normal Payment

6 Additional Payment Services - 264 - 6.6 Reservation


Card Payments Message Usage Guide Version 5.0

7 Messages Examples
7.1 Authorisation, Completion, Cancellation and Reconciliation
Exchanges

This section provides the data that are used in the examples of Authorisation, Completion,
Cancellation request and Cancellation advice.
These messages are taken from a sequence of exchanges including the following steps:
1) A transaction is performed through an online authorisation exchange, and with the data
capture of the transaction during a completion exchange,
2) Subsequently the Acceptor cancels the transaction, with the notification to the Acquirer
through a cancellation advice.
3) At the end of the day, a reconciliation exchange is initiated by the Acceptor.
The sequence of exchange is summarized in the figure below.
Acceptor Acquirer

1 AcceptorAuthor
isatio nRequest
authorisation approval
without capture
isationR esponse
AcceptorAuthor
transaction complete
successfully
AcceptorCompletionAdvice

transaction capture
ponse
etionAdviceRes
AcceptorCompl

cancellation of the 2
transaction AcceptorCancellationAdvice
void authorisation
and capture
ation AdviceResponse
AcceptorCancell

end of the day 3


AcceptorReconciliationRequest

esponse
iliationAdviceR
AcceptorReconc

Figure 66: Sequence of Message Exchanges

The InitiatingParty is a POI identified by 66000001, and the RecipientParty is an Acquirer identified by
epas-acquirer-1.

7 Messages Examples - 265 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.1 Cryptographic Keys

The Key Encryption Key is the DUKPT test key, named SpecV1TesKey, with the version 2010060715,
and the following input:
BDK (Base Derivation Key): 37233E89 0B0104E9 BC943D0E 45EAE5A7
KSN (Key Serial Number): 398725A501 E290200017
Providing the following initial key for the POI:
TIK (Terminal Initial Key): EE3AE644 1C2EEE18 3F3B4179 2DBCD318

The AcceptorAuthorisationRequest and AcceptorAuthorisationResponse use the following serial


number:
KSN: 398725A501 E290200017
Providing the following keys for the POI:
MAC Encryption Key Request: 5E64F1AB F25D3BA1 7F629EC2 B302F8EA
MAC Encryption Key Response: 5E64F1AB 0D5DC4A1 7F629EC2 4C0207EA
Data Encryption Key Request: A75D20F7 04517545 3E29259D 3B08A72A
Data Encryption Key Response: EC7F8A3D 76042AEA E69EE689 61613BE3

The AcceptorCompletionAdvice and AcceptorCompletionAdviceResponse use the following serial


number:
KSN: 398725A501 E290200018
Providing the following keys for the POI:
MAC Encryption Key Request: 1391756B 68DF9DFE 977F10BF AE4F250D
MAC Encryption Key Response: 1391756B 97DF62FE 977F10BF 514FDA0D
Data Encryption Key Request: 4326EA3B DA9101EA 3158F8D5 D91C4A54
Data Encryption Key Response: C4750DFB 2A798A2F D5DAD6A7 3EDC75CB

The AcceptorCancellationAdvice and AcceptorCancellationAdviceResponse use the following serial


number:
KSN: 398725A501 E290200019
Providing the following keys for the POI:
MAC Encryption Key Request: 23EC3237 B0FED957 38B9E0EF 54F7269D
MAC Encryption Key Response: 23EC3237 4FFE2657 38B9E0EF ABF7D99D
Data Encryption Key Request: 1304D91F 0B7634F8 15084F5B 0D195876
Data Encryption Key Response: 0ECB2C45 E5B08538 3D2FEF1C 5E0DCB67

The AcceptorReconciliationRequest and AcceptorReconciliationResponse use the following serial


number:
KSN: 398725A501 E290200022
Providing the following key for the POI:
MAC Encryption Key Request: 6D76756D CB46E907 E0C798AD 83256257
MAC Encryption Key Response: 6D76756D 34461607 E0C798AD 7C259D57

7 Messages Examples - 266 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.2 Acquirer, Merchant and POI Data


The Acquirer has the identification "9287351" and processes the payment transaction performed by
the POI 1 in a shop of the Merchant "EPASMER001" in France. The Merchant Category Code (MCC)
is 5411.

Message Item Value


Acquirer
Identification
Identification 9287351
Type Acquirer
AcquirerParametersVersion 2013-08-07 08:00:00

Merchant
Identification
Identification EPASMER001
CommonName EPASOrg Merchant 1
LocationCategory Fixed
LocationAndContact
PostalAddress
TownName Paris
Country FR

The resulting XML encoded structures are:


<Acqrr>
<Id>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>

and
<Mrchnt>
<Id>
<Id>EPASMER001</Id>
</Id>
<CmonNm>EPASOrg Merchant 1</CmonNm>
<LctnCtgy>FIXD</LctnCtgy>
<LctnAndCtct>
<PstlAdr>
<TwnNm>Paris</TwnNm>
<Ctry>FR</Ctry>
</PstlAdr>
</LctnAndCtct>
</Mrchnt>

7 Messages Examples - 267 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

The POI is a pin-pad "SmartPOI-8539", serial number "7825410759", from the manufacturer
“EPASVendor001", with ICC, and magstripe card readers.
The payment application "SEPAS-FAST" version "2.0".is able to perform plaintext and encrypted
offline PIN verification, online PIN and signature verification with the operator. Authorisation may be
executed online or offline.

Message Item Value


POI
Identification
Identification 1
Issuer Acquirer
SystemName POI01
Capabilities
CardReadingCapabilities ICC
CardReadingCapabilities MagneticStripe
CardReadingCapabilities Physical
CardholderVerificationCapabilities ManualSignature
CardholderVerificationCapabilities OfflinePINClear
CardholderVerificationCapabilities OfflinePINEncrypted
CardholderVerificationCapabilities OnLinePIN
OnLineCapabilities SemiOffLine
MessageCapabilities
Destination CardholderDisplay
NumberOfLines 2
LineWidth 20
MessageCapabilities
Destination MerchantDisplay
NumberOfLines 2
LineWidth 40
Component
Type Terminal
Identification
ItemNumber 1
ProviderIdentification EPASVendor001
Identification SmartPOI-8539
SerialNumber 7825410759
Component
Type PaymentApplication
Identification
ItemNumber 1
ProviderIdentification EPASVendor001
Status
VersionNumber 1.0
StandardCompliance
Identification SEPA-FAST
VersionNumber 3.0
Issuer CIR

7 Messages Examples - 268 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

The resulting XML encoded structure is:


<POI>
<Id>
<Id>1</Id>
<Issr>ACQR</Issr>
</Id>
<SysNm>POI01</SysNm>
<Cpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>CDSP</Dstn>
<NbOfLines>2</NbOfLines>
<LineWidth>20</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<NbOfLines>2</NbOfLines>
<LineWidth>40</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
<Id>SmartPOI-8539</Id>
<SrlNb>7825410759</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
</Id>
<Sts>
<VrsnNb>1.0</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.0</Vrsn>
<Issr>CIR</Issr>
</StdCmplc>
</Cmpnt>
</POI>

7 Messages Examples - 269 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3 Card Data


The cardholder uses a payment card containing the following data:
PAN: 9913330089010574
Sequence number: 00
Effective date: 06 01
Expiration date: 16 12
Service code: 201
Track 2: 9913330089010574D161220101064064
Country code: 056
Profile: 0003
Brand: TestCard

7.1.3.1 Authorisation Request


The sentitive card data must be protected, as required by the Acquirer. The plain card data structure is
presented below:

Message Item Value


PlainCardData
PAN 9913330089010574
CardSequenceNumber 00
EffectiveDate 2006-01
ExpiryDate 2016-12
ServiceCode 201
Track2 9913330089010574D161220101064064

The resulting XML encoded structure is:


<PlainCardData>
<PAN>9913330089010574</PAN>
<CardSeqNb>00</CardSeqNb>
<FctvDt>2006-01</FctvDt>
<XpryDt>2016-12</XpryDt>
<SvcCd>201</SvcCd>
<Trck2>9913330089010574D161220101064064</Trck2>
</PlainCardData>

7 Messages Examples - 270 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, this XML encoded structure with the
padding is:
0000 3C 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C |<PlainCardData><|
0010 50 41 4E 3E 39 39 31 33 33 33 30 30 38 39 30 31 |PAN>991333008901|
0020 30 35 37 34 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 |0574</PAN><CardS|
0030 65 71 4E 62 3E 30 30 3C 2F 43 61 72 64 53 65 71 |eqNb>00</CardSeq|
0040 4E 62 3E 3C 46 63 74 76 44 74 3E 32 30 30 36 2D |Nb><FctvDt>2006-|
0050 30 31 3C 2F 46 63 74 76 44 74 3E 3C 58 70 72 79 |01</FctvDt><Xpry|
0060 44 74 3E 32 30 31 36 2D 31 32 3C 2F 58 70 72 79 |Dt>2016-12</Xpry|
0070 44 74 3E 3C 53 76 63 43 64 3E 32 30 31 3C 2F 53 |Dt><SvcCd>201</S|
0080 76 63 43 64 3E 3C 54 72 63 6B 32 3E 39 39 31 33 |vcCd><Trck2>9913|
0090 33 33 30 30 38 39 30 31 30 35 37 34 44 31 36 31 |330089010574D161|
00A0 32 32 30 31 30 31 30 36 34 30 36 34 3C 2F 54 72 |220101064064</Tr|
00B0 63 6B 32 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 44 |ck2></PlainCardD|
00C0 61 74 61 3E 80 00 00 00 |ata>.... |

Using the Data Encryption Key derived from the TIK or the BDK, A75D20F7 04517545 3E29259D
3B08A72A (see section 7.1.1), and the Initialisation Vector value A27BB46D1C306E09, the encryption
of the padded card data provides the value below:
0000 CB 85 48 F2 F3 63 3C 4D E9 71 8E 0B F1 85 E8 74 |..H..c<M.q.....t|
0010 F9 5A D4 0B EE 69 BF CF EA FB 7C 57 C1 09 98 5F |.Z...i....|W..._|
0020 BE BA A7 60 45 D4 2F 0E 2E 8F 47 D2 64 31 B4 2D |...`E./...G.d1.-|
0030 7F DF 30 A3 F9 21 B6 5C 66 98 DE CE 08 C9 A4 44 |..0..!.\f......D|
0040 83 81 46 73 BF DE 05 D2 2B 78 33 24 79 66 5C 8C |..Fs....+x3$yf\.|
0050 99 BB 37 11 79 94 4C 24 63 16 27 DD BD 57 E8 DB |..7.y.L$c.'..W..|
0060 72 9E 18 0C 31 B0 D1 34 AD 9D F8 B6 53 4A 4A 31 |r...1..4....SJJ1|
0070 F5 D4 3A 40 74 66 33 FD E6 EA 9D C2 49 BA 5E 9B |..:@tf3.....I.^.|
0080 33 E7 C5 FE 46 E6 4A E3 D1 FB C5 12 E9 7A B4 79 |3...F.J......z.y|
0090 F9 AF 01 8C 21 5C 0D FB 56 A9 E2 77 C7 61 11 39 |....!\..V..w.a.9|
00A0 D7 3D 1E 69 27 58 7A AB 65 AF F8 12 1F 2F 04 14 |.=.i'Xz.e..../..|
00B0 E3 AC B1 34 49 C9 C2 5A 89 0D 92 7B 9B E0 DC 9D |...4I..Z...{....|
00C0 E2 8E 67 DA CA A9 A1 33 |..g....3 |

7 Messages Examples - 271 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

The ProtectedCardData data structure is presented in the table below.


Message Item Value
Card
ProtectedCardData
ContentType EnvelopedData
EnvelopedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
EncryptedContent
ContentType PlainData
ContentEncryptionAlgorithm
Algorithm DES112CBC
Parameter
InitialisationVector A27BB46D1C306E09
EncryptedData CB8548F2F3633C4DE9718E0BF185E874
F95AD40BEE69BFCFEAFB7C57C109985F
BEBAA76045D42F0E2E8F47D26431B42D
7FDF30A3F921B65C6698DECE08C9A444
83814673BFDE05D22B78332479665C8C
99BB371179944C24631627DDBD57E8DB
729E180C31B0D134AD9DF8B6534A4A31
F5D43A40746633FDE6EA9DC249BA5E9B
33E7C5FE46E64AE3D1FBC512E97AB479
F9AF018C215C0DFB56A9E277C7611139
D73D1E6927587AAB65AFF8121F2F0414
E3ACB13449C9C25A890D927B9BE0DC9D
E28E67DACAA9A133
CardCountryCode 056
CardProductProfile 0003
CardBrand TestCard

7 Messages Examples - 272 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

The resulting XML encoded structure is:


<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
y4VI8vNjPE3pcY4L8YXodPla1Avuab/P6vt8V8EJmF++uqdgRdQvDi6PR9Jk
MbQtf98wo/khtlxmmN7OCMmkRIOBRnO/3gXSK3gzJHlmXIyZuzcReZRMJGMW
J929V+jbcp4YDDGw0TStnfi2U0pKMfXUOkB0ZjP95uqdwkm6Xpsz58X+RuZK
49H7xRLperR5+a8BjCFcDftWqeJ3x2EROdc9HmknWHqrZa/4Eh8vBBTjrLE0
ScnCWokNknub4Nyd4o5n2sqpoTM=

</NcrptdData>
</NcrptdCntt>
</EnvlpdData>
</PrtctdCardData>
<CardCtryCd>056</CardCtryCd>
<CardPdctPrfl>0003</CardPdctPrfl>
<CardBrnd>TestCard</CardBrnd>
</Card>

7 Messages Examples - 273 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.2 Card Data for Other Messages


For the AcceptorCompletionAdvice after an online authorisation, the AcceptorCancellationAdvice and
all the response messages, card data are present for verification only:

Message Item Value


PlainCardData
PAN 9913330089010574
CardSequenceNumber 00
ExpiryDate 2016-12

The resulting XML encoded structure is:


<PlainCardData>
<PAN>9913330089010574</PAN>
<CardSeqNb>00</CardSeqNb>
<XpryDt>2016-12</XpryDt>
</PlainCardData>

Once unnecessary spaces and carriage returns are removed, the XML encoded structure with the
padding is:
0000 3C 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C |<PlainCardData><|
0010 50 41 4E 3E 39 39 31 33 33 33 30 30 38 39 30 31 |PAN>991333008901|
0020 30 35 37 34 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 |0574</PAN><CardS|
0030 65 71 4E 62 3E 30 30 3C 2F 43 61 72 64 53 65 71 |eqNb>00</CardSeq|
0040 4E 62 3E 3C 58 70 72 79 44 74 3E 32 30 31 36 2D |Nb><XpryDt>2016-|
0050 31 32 3C 2F 58 70 72 79 44 74 3E 3C 2F 50 6C 61 |12</XpryDt></Pla|
0060 69 6E 43 61 72 64 44 61 74 61 3E 80 00 00 00 00 |inCardData>.....|

In the following sections, all examples use the same Initialisation Vector value A27BB46D1C306E09.

7 Messages Examples - 274 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.3 AcceptorAuthorisationResponse
The AcceptorAuthorisationResponse uses the DUKPT encryption key EC7F8A3D 76042AEA
E69EE689 61613BE3, and the Initialisation Vector value A27BB46D1C306E09, provides the
encrypted value:
0000 08 06 A0 3A A0 C3 42 25 70 FC 9E 6E 33 7B D6 C5 |...:..B%p..n3{..|
0010 F4 72 D6 1C E8 C5 C7 23 7B 4C 6E 9A CE BE B3 F1 |.r.....#{Ln.....|
0020 26 A8 C2 B9 FB BC 5F C5 CC 77 CB E1 4D 4F 0D 7E |&....._..w..MO.~|
0030 E6 C5 3B 4E EF 7C C6 03 83 70 B0 DA 53 63 71 99 |..;N.|...p..Scq.|
0040 BE E3 C9 87 BD 98 39 4D FD 0D 7F 34 91 CF 4D BB |......9M...4..M.|
0050 4B 92 1F 7C D5 64 9E 5A 78 C5 A8 1D 98 19 79 A4 |K..|.d.Zx.....y.|
0060 34 A9 A7 BF 10 53 F8 B0 76 1F E9 FE D6 15 69 C0 |4....S..v.....i.|

The ProtectedCardData data structure contains the KEK and EncryptedData values presented in the
table below.
Message Item Value
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017

Message Item Value


EncryptedData 0806A03AA0C3422570FC9E6E337BD6C5
F472D61CE8C5C7237B4C6E9ACEBEB3F1
26A8C2B9FBBC5FC5CC77CBE14D4F0D7E
E6C53B4EEF7CC6038370B0DA53637199
BEE3C987BD98394DFD0D7F3491CF4DBB
4B921F7CD5649E5A78C5A81D981979A4
34A9A7BF1053F8B0761FE9FED61569C0

The resulting XML encoded structures of KEK and EncryptedData are:


<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>

<NcrptdData>
CAagOqDDQiVw/J5uM3vWxfRy1hzoxccje0xums6+s/EmqMK5+7xfxcx3y+FN
Tw1+5sU7Tu98xgODcLDaU2Nxmb7jyYe9mDlN/Q1/NJHPTbtLkh981WSeWnjF
qB2YGXmkNKmnvxBT+LB2H+n+1hVpwA==
</NcrptdData>

7 Messages Examples - 275 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.4 AcceptorCompletionAdvice
The AcceptorCompletionAdvice uses the DUKPT encryption key 4326EA3B DA9101EA 3158F8D5
D91C4A54, and the Initialisation Vector value A27BB46D1C306E09, provides the encrypted value:
0000 76 18 35 5C 40 B6 A2 5C D5 1E 58 5D 66 8E B7 DC |v.5\@..\..X]f...|
0010 14 F9 32 D9 CF 81 DC C2 63 61 D2 20 24 2F 52 E9 |..2.....ca. $/R.|
0020 C5 65 8D 7A 77 6F E2 77 78 26 7A 6C 7D FB 4C 47 |.e.zwo.wx&zl}.LG|
0030 3D 63 93 7E 3A 6A 6A C7 DF 81 3A 6B D7 FC B4 1D |=c.~:jj...:k....|
0040 61 FD E2 0D 3A BE 4F C1 A7 E9 98 8F 9A F3 BD 59 |a...:.O........Y|
0050 CE C6 F0 FA 45 77 78 4E 6F B0 D2 77 E6 2A 91 20 |....EwxNo..w.*. |
0060 71 EC 1E 19 A5 44 48 A8 AE BB A8 FA 5F B0 48 AF |q....DH....._.H.|

The ProtectedCardData data structure contains the KEK and EncryptedData values presented in the
table below.
Message Item Value
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200018

Message Item Value


EncryptedData 7618355C40B6A25CD51E585D668EB7DC
14F932D9CF81DCC26361D220242F52E9
C5658D7A776FE27778267A6C7DFB4C47
3D63937E3A6A6AC7DF813A6BD7FCB41D
61FDE20D3ABE4FC1A7E9988F9AF3BD59
CEC6F0FA4577784E6FB0D277E62A9120
71EC1E19A54448A8AEBBA8FA5FB048AF

The resulting XML encoded structures of KEK and EncryptedData are:


<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>

<NcrptdData>
dhg1XEC2olzVHlhdZo633BT5MtnPgdzCY2HSICQvUunFZY16d2/id3gmemx9
+0xHPWOTfjpqasffgTpr1/y0HWH94g06vk/Bp+mYj5rzvVnOxvD6RXd4Tm+w
0nfmKpEgceweGaVESKiuu6j6X7BIrw==
</NcrptdData>

7 Messages Examples - 276 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.5 AcceptorCompletionAdviceResponse
The AcceptorCompletionAdviceResponse uses the DUKPT encryption key C4750DFB 2A798A2F
D5DAD6A7 3EDC75CB, and the Initialisation Vector value A27BB46D1C306E09, provides the
encrypted value:
0000 A5 15 5C 98 2F 78 40 53 F2 51 59 CC 21 43 4C 04 |..\./x@S.QY.!CL.|
0010 39 D3 4C 2A C8 FF 88 28 28 3D 41 B7 F0 EC 4F B4 |9.L*...((=A...O.|
0020 82 FA FA 76 3E E1 CD 8E D1 7B 54 25 D5 B4 73 B0 |...v>....{T%..s.|
0030 7C B6 9F 1F 85 21 2B CE B2 E5 B2 A9 0F 78 74 3B ||....!+......xt;|
0040 4A B7 0C C1 AB 98 2D 93 A9 B9 6E CC D7 B0 C8 CB |J.....-...n.....|
0050 51 79 94 FE C6 C5 7F 67 60 C0 D5 92 AA 63 34 8B |Qy.....g`....c4.|
0060 82 99 E4 B5 68 F8 04 4C DA 5D 9C 39 1B CD 7D CB |....h..L.].9..}.|

The ProtectedCardData data structure contains the KEK and EncryptedData values presented in the
table below.
Message Item Value
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200018

Message Item Value


EncryptedData A5155C982F784053F25159CC21434C04
39D34C2AC8FF8828283D41B7F0EC4FB4
82FAFA763EE1CD8ED17B5425D5B473B0
7CB69F1F85212BCEB2E5B2A90F78743B
4AB70CC1AB982D93A9B96ECCD7B0C8CB
517994FEC6C57F6760C0D592AA63348B
8299E4B568F8044CDA5D9C391BCD7DCB
The resulting XML encoded structures of KEK and EncryptedData are:
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKPT9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>

<NcrptdData>
pRVcmC94QFPyUVnMIUNMBDnTTCrI/4goKD1Bt/DsT7SC+vp2PuHNjtF7VCXV
tHOwfLafH4UhK86y5bKpD3h0O0q3DMGrmC2TqbluzNewyMtReZT+xsV/Z2DA
1ZKqYzSLgpnktWj4BEzaXZw5G819yw==
</NcrptdData>

7 Messages Examples - 277 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.6 AcceptorCancellationAdvice
The AcceptorCancellationAdvice uses the DUKPT encryption key 1304D91F 0B7634F8
15084F5B 0D195876, and the Initialisation Vector value A27BB46D1C306E09, provides the
encrypted value:
0000 5C 63 C7 72 FC 67 30 6D 95 FF 9F 3A 61 C8 D7 EF |\c.r.g0m...:a...|
0010 7F E5 B2 24 AE 97 75 18 80 08 4B ED 8B 1E 79 F2 |...$..u...K...y.|
0020 23 64 F4 34 F3 74 F6 40 F1 71 6B 85 1C DD 57 E0 |#d.4.t.@.qk...W.|
0030 C3 54 6A AC E7 FC 0B AF BB FE BF D4 B9 3D C7 07 |.Tj..........=..|
0040 20 E8 21 E0 0D 74 D7 33 14 D3 92 78 6B 1E 73 54 | .!..t.3...xk.sT|
0050 69 4F A7 CB 0D C9 7C 27 16 23 BB 46 DF 0B C3 C5 |iO....|'.#.F....|
0060 2F 02 48 C0 5C A9 F1 A2 D9 5B DA 77 D5 8F 34 92 |/.H.\....[.w..4.|

The ProtectedCardData data structure contains the KEK and EncryptedData values presented in the
table below.
Message Item Value
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200019

Message Item Value


EncryptedData 5C63C772FC67306D95FF9F3A61C8D7EF
7FE5B224AE97751880084BED8B1E79F2
2364F434F374F640F1716B851CDD57E0
C3546AACE7FC0BAFBBFEBFD4B93DC707
20E821E00D74D73314D392786B1E7354
694FA7CB0DC97C271623BB46DF0BC3C5
2F0248C05CA9F1A2D95BDA77D58F3492

The resulting XML encoded structures of KEK and EncryptedData are:


<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>

<NcrptdData>
XGPHcvxnMG2V/586YcjX73/lsiSul3UYgAhL7YseefIjZPQ083T2QPFxa4Uc
3Vfgw1RqrOf8C6+7/r/UuT3HByDoIeANdNczFNOSeGsec1RpT6fLDcl8JxYj
u0bfC8PFLwJIwFyp8aLZW9p31Y80kg==
</NcrptdData>

7 Messages Examples - 278 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.3.7 AcceptorCancellationAdviceResponse
The AcceptorCancellationAdviceResponse uses the DUKPT encryption key 0ECB2C45 E5B08538
3D2FEF1C 5E0DCB67, and the Initialisation Vector value A27BB46D1C306E09, provides the
encrypted value:
0000 C2 FF 15 EC 22 BB 46 74 89 F4 EE AE 04 98 1E D8 |....".Ft........|
0010 4C E8 13 3B D5 B4 2A 6F 93 9D CD FD 7A 08 32 79 |L..;..*o....z.2y|
0020 BD 25 6B DE 24 20 7A 8A AA 5C 90 4F C7 6C C1 DE |.%k.$ z..\.O.l..|
0030 0D 76 1E B2 29 0E 70 29 77 1D 2B 4D 5D 7A 9F 57 |.v..).p)w.+M]z.W|
0040 F0 0B A9 13 48 DA 69 AC 7F 22 95 F7 85 AD E8 92 |....H.i.."......|
0050 E6 31 6A CE 55 A1 4F DA 77 B5 C7 D0 9F E7 E1 E9 |.1j.U.O.w.......|
0060 18 AC EA 59 CD A7 21 37 15 E0 FA 33 72 34 D2 11 |...Y..!7...3r4..|

The ProtectedCardData data structure contains the KEK and EncryptedData values presented in the
table below.
Message Item Value
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2010060715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200019

Message Item Value


EncryptedData C2FF15EC22BB467489F4EEAE04981ED8
4CE8133BD5B42A6F939DCDFD7A083279
BD256BDE24207A8AAA5C904FC76CC1DE
0D761EB2290E7029771D2B4D5D7A9F57
F00BA91348DA69AC7F2295F785ADE892
E6316ACE55A14FDA77B5C7D09FE7E1E9
18ACEA59CDA7213715E0FA337234D211
The resulting XML encoded structures of KEK and EncryptedData are:
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKPT9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>

<NcrptdData>
wv8V7CK7RnSJ9O6uBJge2EzoEzvVtCpvk53N/XoIMnm9JWveJCB6iqpckE/H
bMHeDXYesikOcCl3HStNXXqfV/ALqRNI2mmsfyKV94Wt6JLmMWrOVaFP2ne1
x9Cf5+HpGKzqWc2nITcV4PozcjTSEQ==
</NcrptdData>

7 Messages Examples - 279 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.4 Cardholder Data


The cardholder speaks French, and has been authenticated by offline PIN verification.
Message Item Value
Cardholder
Language fr
Authentication
TransactionVerificationResult
Method OfflinePIN
VerificationEntity ICC
Result Successful

The resulting XML encoded structure for the cardholder is:


<Crdhldr>
<Lang>fr</Lang>
<TxVrfctnRslt>
<Mtd>FPIN</Mtd>
<VrfctnNtty>ICCD</VrfctnNtty>
<Rslt>SUCC</Rslt>
</TxVrfctnRslt>
</Crdhldr>

7 Messages Examples - 280 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.5 Payment and Sale Contexts


The payment transaction is perfomed at an attended device where the attendant is to receive
messages in French.
The identification of the sale terminal, the sale transaction and the sale reconciliation are provided in
the transaction.

Message Item Value


Context
PaymentContext
AttendanceContext Attended
AttendantLanguage fr
CardEntryMode ICC
SaleContext
SaleIdentification ST06
SaleReferenceNumber S78-T06-0029
SaleReconciliationIdentification S78-8469

The resulting XML encoded structure is:


<Cntxt>
<PmtCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<AttndntLang>fr</AttndntLang>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleId>ST06</SaleId>
<SaleRefNb>S78-T06-0029</SaleRefNb>
<SaleRcncltnId>S78-8469</SaleRcncltnId>
</SaleCntxt>
</Cntxt>

7 Messages Examples - 281 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.6 ICC Related Data

7.1.6.1 Authorisation Request

The transaction uses an EMV payment card; the authorisation request will carry the following EMV
data:
Data Tag Length Value
Transaction Currency Code 5F2A 02 0978
Application PAN Sequence Number 5F34 01 00
Application Interchange Profile 82 02 7C00
Dedicated File (DF) Name 84 07 A0000000093510
Terminal Verification Results 95 05 0000008000
Transaction Date 9A 03 110411
Transaction Type 9C 01 00
Amount, Authorized (Numeric) 9F02 06 000000004314
Terminal Application Version Number 9F09 02 0002
Issuer Application Data 9F10 12 0210A780030400009F2100000000000000FF
Terminal Country Code 9F1A 02 0250
Application Cryptogram (AC) 9F26 08 2E3EAB17CEEC500C
Cryptogram Information Data (CID) 9F27 01 80
Terminal Capabilities 9F33 03 60A040
Cardholder Verification Method 9F34 03 440302
(CVM) Results
Terminal Type 9F35 01 22
Application Transaction Counter 9F36 02 0016
(ATC)
Unpredictable Number 9F37 04 BC75E9B3
Additional Terminal Capabilities 9F40 05 A00090F001
ICC Dynamic Number 9F4C 08 9F21B02E0EEAC454

Content of Transaction.TransactionDetails.ICCRelatedData in the AcceptorAuthorisationRequest


message will be:
ICCRelatedData 5F2A0209785F34010082027C008407A0000000093510950500
000080009A031104119C01009F02060000000043149F090200
029F10120210A780030400009F2100000000000000FF9F1A02
02509F26082E3EAB17CEEC500C9F2701809F330360A0409F34
034403029F3501229F360200169F3704BC75E9B39F4005A000
90F0019F4C089F21B02E0EEAC454

7 Messages Examples - 282 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.1.6.2 Authorisation Response

The authorisation response will carry the following EMV informations:


Data Tag Length Value
Issuer Authentication Data 91 0A 74E52FC59D6ADE2A0012
Authorisation Response Code 8A 02 3030

Content of Transaction.TransactionDetails.ICCRelatedData in the AcceptorAuthorisationResponse


message will be:
ICCRelatedData 910A74E52FC59D6ADE2A00128A023030

7.1.6.3 Completion Advice

The completion advice will carry the following EMV information:


Data Tag Length Value
Transaction Currency Code 5F2A 02 0978
Application PAN Sequence Number 5F34 01 00
Application Interchange Profile 82 02 7C00
Dedicated File (DF) Name 84 07 A0000000093510
Authorisation Response Code 8A 02 3030
Issuer Authentication Data 91 0A 74E52FC59D6ADE2A0012
Terminal Verification Results 95 05 0000008000
Transaction Date 9A 03 110411
Transaction Type 9C 01 00
Amount, Authorized (Numeric) 9F02 06 000000004314
Terminal Application Version Number 9F09 02 0002
Issuer Application Data 9F10 12 02106780030400009F2100000000000000FF
Terminal Country Code 9F1A 02 0250
Application Cryptogram (AC) 9F26 08 29A3BC20E461E80C
Cryptogram Information Data (CID) 9F27 01 40
Terminal Capabilities 9F33 03 60A040
Cardholder Verification Method 9F34 03 440302
(CVM) Results
Terminal Type 9F35 01 22
Application Transaction Counter 9F36 02 0016
(ATC)
Unpredictable Number 9F37 04 BC75E9B3
Additional Terminal Capabilities 9F40 05 A00090F001
ICC Dynamic Number 9F4C 08 9F21B02E0EEAC454

7 Messages Examples - 283 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

Content of Transaction.TransactionDetails.ICCRelatedData in the AcceptorCompletionAdvice


message will be:
ICCRelatedData 5F2A0209785F34010082027C008407A00000000935108A02303
0910A74E52FC59D6ADE2A0012950500000080009A031104119C
01009F02060000000043149F090200029F10120210678003040
0009F2100000000000000FF9F1A0202509F260829A3BC20E461
E80C9F2701409F330360A0409F34034403029F3501229F36020
0169F3704BC75E9B39F4005A00090F0019F4C089F21B02E0EEA
C454

7 Messages Examples - 284 - 7.1 Authorisation, Completion, Cancellation and


Reconciliation Exchanges
Card Payments Message Usage Guide Version 5.0

7.2 Authorisation Messages

7.2.1 AcceptorAuthorisationRequest

The transaction is a card payment of 43.14 euros and belongs to the reconciliation period 8469.

Message Item Value


Transaction
TransactionCapture False
TransactionType CardPayment
MerchantCategoryCode 5411
TransactionIdentification
TransactionDateTime 2013-08-11T17:22:04.51+01:00
TransactionReference 002949
ReconciliationIdentification 8469
TransactionDetails
Currency EUR
TotalAmount 43.14
OnlineReason ICCForced
ICCRelatedData 5F2A0209785F34010082027C008407A00000000935109505000
00080009A031104119C01009F02060000000043149F09020002
9F10120210A780030400009F2100000000000000FF9F1A02025
09F26082E3EAB17CEEC500C9F2701809F330360A0409F340344
03029F3501229F360200169F3704BC75E9B39F4005A00090F00
19F4C089F21B02E0EEAC454

The resulting XML encoded structure is:


<Tx>
<TxCaptr>false</TxCaptr>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<OnLineRsn>ICCF</OnLineRsn>
<ICCRltdData>
XyoCCXhfNAEAggJ8AIQHoAAAAAk1EJUFAAAAgACaAxEEEZwBAJ8CBgAAAABDFJ8JAgA
CnxASAhCngAMEAACfIQAAAAAAAAD/nxoCAlCfJgguPqsXzuxQDJ8nAYCfMwNgoECfNA
NEAwKfNQEinzYCABafNwS8demzn0AFoACQ8AGfTAifIbAuDurEVA==
</ICCRltdData>
</TxDtls>
</Tx>

7 Messages Examples - 285 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorAuthorisationRequest is shown below, omitting data structures described in


previous sections of this chapter.
Message Item Value
AcceptorAuthorisationRequest
Header
MessageFunction AuthorisationRequest
ProtocolVersion 5.0
ExchangeIdentifier 149
CreationDateTime 2013-08-11T17:22:54.13+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
AuthorisationRequest
Environment
Acquirer
---
Merchant
---
POI
---
Card
---
CardHolder
---
Context
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC DBA5136E491C41E

7 Messages Examples - 286 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

---

The AcceptorAuthorisationRequest XML message is presented below:


<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.001.001.05">
<AccptrAuthstnReq>
<Hdr>
<MsgFctn>AUTQ</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>149</XchgId>
<CreDtTm>2013-08-11T17:22:54.13+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<AuthstnReq>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>EPASMER001</Id>
</Id>
<CmonNm>EPASOrg Merchant 1</CmonNm>
<LctnCtgy>FIXD</LctnCtgy>
<LctnAndCtct>
<PstlAdr>
<TwnNm>Paris</TwnNm>
<Ctry>FR</Ctry>
</PstlAdr>
</LctnAndCtct>
</Mrchnt>
<POI>
<Id>
<Id>1</Id>
<Issr>ACQR</Issr>
</Id>
<SysNm>POI01</SysNm>
<Cpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>CDSP</Dstn>
<NbOfLines>2</NbOfLines>
<LineWidth>20</LineWidth>
</MsgCpblties>

7 Messages Examples - 287 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

<MsgCpblties>
<Dstn>MRCP</Dstn>
<NbOfLines>2</NbOfLines>
<LineWidth>40</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
<Id>SmartPOI-8539</Id>
<SrlNb>7825410759</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
</Id>
<Sts>
<VrsnNb>1.0</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.0</Vrsn>
<Issr>CIR</Issr>
</StdCmplc>
</Cmpnt>
</POI>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
y4VI8vNjPE3pcY4L8YXodPla1Avuab/P6vt8V8EJmF++uqdgRdQvD
i6PR9JkMbQtf98wo/khtlxmmN7OCMmkRIOBRnO/3gXSK3gzJHlmXI
yZuzcReZRMJGMWJ929V+jbcp4YDDGw0TStnfi2U0pKMfXUOkB0ZjP
95uqdwkm6Xpsz58X+RuZK49H7xRLperR5+a8BjCFcDftWqeJ3x2ER
Odc9HmknWHqrZa/4Eh8vBBTjrLE0ScnCWokNknub4Nyd4o5n2sqpo
TM=

</NcrptdData>
</NcrptdCntt>
</EnvlpdData>

7 Messages Examples - 288 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

</PrtctdCardData>
<CardCtryCd>056</CardCtryCd>
<CardPdctPrfl>0003</CardPdctPrfl>
<CardBrnd>TestCard</CardBrnd>
</Card>
<Crdhldr>
<Lang>fr</Lang>
<TxVrfctnRslt>
<Mtd>FPIN</Mtd>
<VrfctnNtty>ICCD</VrfctnNtty>
<Rslt>SUCC</Rslt>
</TxVrfctnRslt>
</Crdhldr>
</Envt>
<Cntxt>
<PmtCntxt>
<CardPres>true</CardPres>
<CrdhldrPres>true</CrdhldrPres>
<AttndncCntxt>ATTD</AttndncCntxt>
<AttndntMsgCpbl>true</AttndntMsgCpbl>
<AttndntLang>fr</AttndntLang>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleId>ST06</SaleId>
<SaleRefNb>S78-T06-0029</SaleRefNb>
<SaleRcncltnId>S78-8469</SaleRcncltnId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxCaptr>false</TxCaptr>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<OnLineRsn>ICCF</OnLineRsn>
<ICCRltdData>
XyoCCXhfNAEAggJ8AIQHoAAAAAk1EJUFAAAAgACaAxEEEZwBAJ8CBgAAAABDFJ
8JAgACnxASAhCngAMEAACfIQAAAAAAAAD/nxoCAlCfJgguPqsXzuxQDJ8nAYCf
MwNgoECfNANEAwKfNQEinzYCABafNwS8demzn0AFoACQ8AGfTAifIbAuDurEVA
==
</ICCRltdData>
</TxDtls>
</Tx>
</AuthstnReq>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>

7 Messages Examples - 289 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>26UTbkkcQeQ=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrAuthstnReq>
</Document>

Once unnecessary spaces and carriage returns are removed, the message body AuthstnReq (without
spaces or line breaks) is shown below:
0000 3C 41 75 74 68 73 74 6E 52 65 71 3E 3C 45 6E 76 |<AuthstnReq><Env|
0010 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
0020 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
0030 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|
0040 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0050 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0060 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0070 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0080 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 |Id>EPASMER001</I|
0090 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 45 |d></Id><CmonNm>E|
00A0 50 41 53 4F 72 67 20 4D 65 72 63 68 61 6E 74 20 |PASOrg Merchant |
00B0 31 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 4C 63 74 6E 43 |1</CmonNm><LctnC|
00C0 74 67 79 3E 46 49 58 44 3C 2F 4C 63 74 6E 43 74 |tgy>FIXD</LctnCt|
00D0 67 79 3E 3C 4C 63 74 6E 41 6E 64 43 74 63 74 3E |gy><LctnAndCtct>|
00E0 3C 50 73 74 6C 41 64 72 3E 3C 54 77 6E 4E 6D 3E |<PstlAdr><TwnNm>|
00F0 50 61 72 69 73 3C 2F 54 77 6E 4E 6D 3E 3C 43 74 |Paris</TwnNm><Ct|
0100 72 79 3E 46 52 3C 2F 43 74 72 79 3E 3C 2F 50 73 |ry>FR</Ctry></Ps|
0110 74 6C 41 64 72 3E 3C 2F 4C 63 74 6E 41 6E 64 43 |tlAdr></LctnAndC|
0120 74 63 74 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F |tct></Mrchnt><PO|
0130 49 3E 3C 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E |I><Id><Id>1</Id>|
0140 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 |<Issr>ACQR</Issr|
0150 3E 3C 2F 49 64 3E 3C 53 79 73 4E 6D 3E 50 4F 49 |></Id><SysNm>POI|
0160 30 31 3C 2F 53 79 73 4E 6D 3E 3C 43 70 62 6C 74 |01</SysNm><Cpblt|
0170 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
0180 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 |lties>CICC</Card|
0190 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 |RdngCpblties><Ca|
01A0 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D |rdRdngCpblties>M|
01B0 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |GST</CardRdngCpb|
01C0 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
01D0 70 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 |pblties>PHYS</Ca|
01E0 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
01F0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
0200 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 |lties>MNSG</Crdh|
0210 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
0220 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
0230 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 |Cpblties>FCPN</C|
0240 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0250 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0260 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 4E |ctnCpblties>FEPN|
0270 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
0280 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
0290 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E |VrfctnCpblties>N|
02A0 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |PIN</CrdhldrVrfc|
02B0 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 |tnCpblties><OnLi|
02C0 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C |neCpblties>SMON<|
02D0 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E |/OnLineCpblties>|
02E0 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
02F0 74 6E 3E 43 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E |tn>CDSP</Dstn><N|
0300 62 4F 66 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 |bOfLines>2</NbOf|
0310 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 |Lines><LineWidth|
0320 3E 32 30 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C |>20</LineWidth><|
0330 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 |/MsgCpblties><Ms|

7 Messages Examples - 290 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0340 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E |gCpblties><Dstn>|
0350 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 |MRCP</Dstn><NbOf|
0360 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 4C 69 6E |Lines>2</NbOfLin|
0370 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 34 30 |es><LineWidth>40|
0380 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 |</LineWidth></Ms|
0390 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |gCpblties></Cpbl|
03A0 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
03B0 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 49 74 |TERM</Tp><Id><It|
03C0 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E 3C 50 72 |mNb>1</ItmNb><Pr|
03D0 76 64 72 49 64 3E 45 50 41 53 56 65 6E 64 6F 72 |vdrId>EPASVendor|
03E0 30 30 31 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |001</PrvdrId><Id|
03F0 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 39 3C 2F |>SmartPOI-8539</|
0400 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 35 34 31 |Id><SrlNb>782541|
0410 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 |0759</SrlNb></Id|
0420 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E |></Cmpnt><Cmpnt>|
0430 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 |<Tp>APLI</Tp><Id|
0440 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 |><ItmNb>1</ItmNb|
0450 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 |><PrvdrId>EPASVe|
0460 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 |ndor001</PrvdrId|
0470 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
0480 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E 62 3E 3C |Nb>1.0</VrsnNb><|
0490 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|
04A0 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
04B0 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 72 73 6E |><Vrsn>3.0</Vrsn|
04C0 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 73 73 72 |><Issr>CIR</Issr|
04D0 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 2F 43 6D |></StdCmplc></Cm|
04E0 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |pnt></POI><Card>|
04F0 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 61 3E |<PrtctdCardData>|
0500 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E |<CnttTp>EVLP</Cn|
0510 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 |ttTp><EnvlpdData|
0520 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B |><Rcpt><KEK><KEK|
0530 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 |Id><KeyId>SpecV1|
0540 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C |TestKey</KeyId><|
0550 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 |KeyVrsn>20100607|
0560 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 |15</KeyVrsn><Der|
0570 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C |ivtnId>OYclpQE=<|
0580 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B |/DerivtnId></KEK|
0590 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 |Id><KeyNcrptnAlg|
05A0 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C |o><Algo>DKP9</Al|
05B0 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C |go></KeyNcrptnAl|
05C0 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 |go><NcrptdKey>4p|
05D0 41 67 41 42 63 3D 3C 2F 4E 63 72 70 74 64 4B 65 |AgABc=</NcrptdKe|
05E0 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C |y></KEK></Rcpt><|
05F0 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 |NcrptdCntt><Cntt|
0600 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E |Tp>DATA</CnttTp>|
0610 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E |<CnttNcrptnAlgo>|
0620 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F |<Algo>E3DC</Algo|
0630 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 |><Param><Initlst|
0640 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 |nVctr>onu0bRwwbg|
0650 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 |k=</InitlstnVctr|
0660 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E |></Param></CnttN|
0670 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 |crptnAlgo><Ncrpt|
0680 64 44 61 74 61 3E 79 34 56 49 38 76 4E 6A 50 45 |dData>y4VI8vNjPE|
0690 33 70 63 59 34 4C 38 59 58 6F 64 50 6C 61 31 41 |3pcY4L8YXodPla1A|
06A0 76 75 61 62 2F 50 36 76 74 38 56 38 45 4A 6D 46 |vuab/P6vt8V8EJmF|
06B0 2B 2B 75 71 64 67 52 64 51 76 44 69 36 50 52 39 |++uqdgRdQvDi6PR9|
06C0 4A 6B 4D 62 51 74 66 39 38 77 6F 2F 6B 68 74 6C |JkMbQtf98wo/khtl|
06D0 78 6D 6D 4E 37 4F 43 4D 6D 6B 52 49 4F 42 52 6E |xmmN7OCMmkRIOBRn|
06E0 4F 2F 33 67 58 53 4B 33 67 7A 4A 48 6C 6D 58 49 |O/3gXSK3gzJHlmXI|
06F0 79 5A 75 7A 63 52 65 5A 52 4D 4A 47 4D 57 4A 39 |yZuzcReZRMJGMWJ9|
0700 32 39 56 2B 6A 62 63 70 34 59 44 44 47 77 30 54 |29V+jbcp4YDDGw0T|
0710 53 74 6E 66 69 32 55 30 70 4B 4D 66 58 55 4F 6B |Stnfi2U0pKMfXUOk|
0720 42 30 5A 6A 50 39 35 75 71 64 77 6B 6D 36 58 70 |B0ZjP95uqdwkm6Xp|
0730 73 7A 35 38 58 2B 52 75 5A 4B 34 39 48 37 78 52 |sz58X+RuZK49H7xR|
0740 4C 70 65 72 52 35 2B 61 38 42 6A 43 46 63 44 66 |LperR5+a8BjCFcDf|
0750 74 57 71 65 4A 33 78 32 45 52 4F 64 63 39 48 6D |tWqeJ3x2EROdc9Hm|
0760 6B 6E 57 48 71 72 5A 61 2F 34 45 68 38 76 42 42 |knWHqrZa/4Eh8vBB|
0770 54 6A 72 4C 45 30 53 63 6E 43 57 6F 6B 4E 6B 6E |TjrLE0ScnCWokNkn|

7 Messages Examples - 291 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0780 75 62 34 4E 79 64 34 6F 35 6E 32 73 71 70 6F 54 |ub4Nyd4o5n2sqpoT|
0790 4D 3D 3C 2F 4E 63 72 70 74 64 44 61 74 61 3E 3C |M=</NcrptdData><|
07A0 2F 4E 63 72 70 74 64 43 6E 74 74 3E 3C 2F 45 6E |/NcrptdCntt></En|
07B0 76 6C 70 64 44 61 74 61 3E 3C 2F 50 72 74 63 74 |vlpdData></Prtct|
07C0 64 43 61 72 64 44 61 74 61 3E 3C 43 61 72 64 43 |dCardData><CardC|
07D0 74 72 79 43 64 3E 30 35 36 3C 2F 43 61 72 64 43 |tryCd>056</CardC|
07E0 74 72 79 43 64 3E 3C 43 61 72 64 50 64 63 74 50 |tryCd><CardPdctP|
07F0 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 |rfl>0003</CardPd|
0800 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E 64 |ctPrfl><CardBrnd|
0810 3E 54 65 73 74 43 61 72 64 3C 2F 43 61 72 64 42 |>TestCard</CardB|
0820 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 43 72 64 68 |rnd></Card><Crdh|
0830 6C 64 72 3E 3C 4C 61 6E 67 3E 66 72 3C 2F 4C 61 |ldr><Lang>fr</La|
0840 6E 67 3E 3C 54 78 56 72 66 63 74 6E 52 73 6C 74 |ng><TxVrfctnRslt|
0850 3E 3C 4D 74 64 3E 46 50 49 4E 3C 2F 4D 74 64 3E |><Mtd>FPIN</Mtd>|
0860 3C 56 72 66 63 74 6E 4E 74 74 79 3E 49 43 43 44 |<VrfctnNtty>ICCD|
0870 3C 2F 56 72 66 63 74 6E 4E 74 74 79 3E 3C 52 73 |</VrfctnNtty><Rs|
0880 6C 74 3E 53 55 43 43 3C 2F 52 73 6C 74 3E 3C 2F |lt>SUCC</Rslt></|
0890 54 78 56 72 66 63 74 6E 52 73 6C 74 3E 3C 2F 43 |TxVrfctnRslt></C|
08A0 72 64 68 6C 64 72 3E 3C 2F 45 6E 76 74 3E 3C 43 |rdhldr></Envt><C|
08B0 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
08C0 43 61 72 64 50 72 65 73 3E 74 72 75 65 3C 2F 43 |CardPres>true</C|
08D0 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C 64 72 |ardPres><Crdhldr|
08E0 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C |Pres>true</Crdhl|
08F0 64 72 50 72 65 73 3E 3C 41 74 74 6E 64 6E 63 43 |drPres><AttndncC|
0900 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
0910 6E 63 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 74 |ncCntxt><Attndnt|
0920 4D 73 67 43 70 62 6C 3E 74 72 75 65 3C 2F 41 74 |MsgCpbl>true</At|
0930 74 6E 64 6E 74 4D 73 67 43 70 62 6C 3E 3C 41 74 |tndntMsgCpbl><At|
0940 74 6E 64 6E 74 4C 61 6E 67 3E 66 72 3C 2F 41 74 |tndntLang>fr</At|
0950 74 6E 64 6E 74 4C 61 6E 67 3E 3C 43 61 72 64 44 |tndntLang><CardD|
0960 61 74 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F |ataNtryMd>CICC</|
0970 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C |CardDataNtryMd><|
0980 2F 50 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 |/PmtCntxt><SaleC|
0990 6E 74 78 74 3E 3C 53 61 6C 65 49 64 3E 53 54 30 |ntxt><SaleId>ST0|
09A0 36 3C 2F 53 61 6C 65 49 64 3E 3C 53 61 6C 65 52 |6</SaleId><SaleR|
09B0 65 66 4E 62 3E 53 37 38 2D 54 30 36 2D 30 30 32 |efNb>S78-T06-002|
09C0 39 3C 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 53 61 |9</SaleRefNb><Sa|
09D0 6C 65 52 63 6E 63 6C 74 6E 49 64 3E 53 37 38 2D |leRcncltnId>S78-|
09E0 38 34 36 39 3C 2F 53 61 6C 65 52 63 6E 63 6C 74 |8469</SaleRcnclt|
09F0 6E 49 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E |nId></SaleCntxt>|
0A00 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 43 |</Cntxt><Tx><TxC|
0A10 61 70 74 72 3E 66 61 6C 73 65 3C 2F 54 78 43 61 |aptr>false</TxCa|
0A20 70 74 72 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F |ptr><TxTp>CRDP</|
0A30 54 78 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 |TxTp><MrchntCtgy|
0A40 43 64 3E 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 |Cd>5411</MrchntC|
0A50 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 |tgyCd><TxId><TxD|
0A60 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 |tTm>2013-08-11T1|
0A70 37 3A 32 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 |7:22:04.51+01:00|
0A80 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|
0A90 30 30 32 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F |002949</TxRef></|
0AA0 54 78 49 64 3E 3C 52 63 6E 63 6C 74 6E 49 64 3E |TxId><RcncltnId>|
0AB0 38 34 36 39 3C 2F 52 63 6E 63 6C 74 6E 49 64 3E |8469</RcncltnId>|
0AC0 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 |<TxDtls><Ccy>EUR|
0AD0 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 34 33 |</Ccy><TtlAmt>43|
0AE0 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E 3C 4F 6E 4C |.14</TtlAmt><OnL|
0AF0 69 6E 65 52 73 6E 3E 49 43 43 46 3C 2F 4F 6E 4C |ineRsn>ICCF</OnL|
0B00 69 6E 65 52 73 6E 3E 3C 49 43 43 52 6C 74 64 44 |ineRsn><ICCRltdD|
0B10 61 74 61 3E 58 79 6F 43 43 58 68 66 4E 41 45 41 |ata>XyoCCXhfNAEA|
0B20 67 67 4A 38 41 49 51 48 6F 41 41 41 41 41 6B 31 |ggJ8AIQHoAAAAAk1|
0B30 45 4A 55 46 41 41 41 41 67 41 43 61 41 78 45 45 |EJUFAAAAgACaAxEE|
0B40 45 5A 77 42 41 4A 38 43 42 67 41 41 41 41 42 44 |EZwBAJ8CBgAAAABD|
0B50 46 4A 38 4A 41 67 41 43 6E 78 41 53 41 68 43 6E |FJ8JAgACnxASAhCn|
0B60 67 41 4D 45 41 41 43 66 49 51 41 41 41 41 41 41 |gAMEAACfIQAAAAAA|
0B70 41 41 44 2F 6E 78 6F 43 41 6C 43 66 4A 67 67 75 |AAD/nxoCAlCfJggu|
0B80 50 71 73 58 7A 75 78 51 44 4A 38 6E 41 59 43 66 |PqsXzuxQDJ8nAYCf|
0B90 4D 77 4E 67 6F 45 43 66 4E 41 4E 45 41 77 4B 66 |MwNgoECfNANEAwKf|
0BA0 4E 51 45 69 6E 7A 59 43 41 42 61 66 4E 77 53 38 |NQEinzYCABafNwS8|
0BB0 64 65 6D 7A 6E 30 41 46 6F 41 43 51 38 41 47 66 |demzn0AFoACQ8AGf|

7 Messages Examples - 292 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0BC0 54 41 69 66 49 62 41 75 44 75 72 45 56 41 3D 3D |TAifIbAuDurEVA==|
0BD0 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F |</ICCRltdData></|
0BE0 54 78 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 41 75 |TxDtls></Tx></Au|
0BF0 74 68 73 74 6E 52 65 71 3E |thstnReq> |

The SHA-256 digest of the message body AuthstnReq is:


0000 A5 B2 8F C7 6D EC DD C5 45 89 12 B4 AA 80 85 47 |....m...E......G|
0010 AF A7 C3 46 76 38 5D 5A BC BC FD 71 AE E3 37 81 |...Fv8]Z...q..7.|

7 Messages Examples - 293 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

After padding, the digest becomes:


0000 A5 B2 8F C7 6D EC DD C5 45 89 12 B4 AA 80 85 47 |....m...E......G|
0010 AF A7 C3 46 76 38 5D 5A BC BC FD 71 AE E3 37 81 |...Fv8]Z...q..7.|
0020 80 00 00 00 00 00 00 00 |........ |

After retail CBC encryption with the MAC Computation test Key (5E64F1AB F25D3BA1 7F629EC2
B302F8EA), we obtain the MAC of the AcceptorAuthorisationRequest DBA5136E491C41E4 and after
conversion into base64 "26UTbkkcQeQ=".
0000 AB 7F C0 BD F8 91 5E 37 F3 92 9B DD 09 25 82 5B |......^7.....%.[|
0010 FA 48 4C 51 10 F3 B3 C3 E8 15 22 97 C8 FA C0 D2 |.HLQ......".....|
0020 DB A5 13 6E 49 1C 41 E4 |...nI.A. |

The message sent by the transport protocol is:


0000 00 00 0F 43 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |...C<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 31 2E 30 30 31 2E 30 35 22 |caaa.001.001.05"|
00A0 3E 3C 41 63 63 70 74 72 41 75 74 68 73 74 6E 52 |><AccptrAuthstnR|
00B0 65 71 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E |eq><Hdr><MsgFctn|
00C0 3E 41 55 54 51 3C 2F 4D 73 67 46 63 74 6E 3E 3C |>AUTQ</MsgFctn><|
00D0 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F |PrtcolVrsn>5.0</|
00E0 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 |PrtcolVrsn><Xchg|
00F0 49 64 3E 31 34 39 3C 2F 58 63 68 67 49 64 3E 3C |Id>149</XchgId><|
0100 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |CreDtTm>2013-08-|
0110 31 31 54 31 37 3A 32 32 3A 35 34 2E 31 33 2B 30 |11T17:22:54.13+0|
0120 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 |1:00</CreDtTm><I|
0130 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 |nitgPty><Id>6600|
0140 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F |0001</Id><Tp>OPO|
0150 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 |I</Tp><Issr>ACQR|
0160 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 |</Issr></InitgPt|
0170 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 |y><RcptPty><Id>e|
0180 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F |pas-acquirer-1</|
0190 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E |Id><Tp>ACQR</Tp>|
01A0 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E |</RcptPty></Hdr>|
01B0 3C 41 75 74 68 73 74 6E 52 65 71 3E 3C 45 6E 76 |<AuthstnReq><Env|
01C0 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|
01F0 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0200 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0210 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0220 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0230 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 |Id>EPASMER001</I|
0240 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 45 |d></Id><CmonNm>E|

7 Messages Examples - 294 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0250 50 41 53 4F 72 67 20 4D 65 72 63 68 61 6E 74 20 |PASOrg Merchant |


0260 31 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 4C 63 74 6E 43 |1</CmonNm><LctnC|
0270 74 67 79 3E 46 49 58 44 3C 2F 4C 63 74 6E 43 74 |tgy>FIXD</LctnCt|
0280 67 79 3E 3C 4C 63 74 6E 41 6E 64 43 74 63 74 3E |gy><LctnAndCtct>|
0290 3C 50 73 74 6C 41 64 72 3E 3C 54 77 6E 4E 6D 3E |<PstlAdr><TwnNm>|
02A0 50 61 72 69 73 3C 2F 54 77 6E 4E 6D 3E 3C 43 74 |Paris</TwnNm><Ct|
02B0 72 79 3E 46 52 3C 2F 43 74 72 79 3E 3C 2F 50 73 |ry>FR</Ctry></Ps|
02C0 74 6C 41 64 72 3E 3C 2F 4C 63 74 6E 41 6E 64 43 |tlAdr></LctnAndC|
02D0 74 63 74 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F |tct></Mrchnt><PO|
02E0 49 3E 3C 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E |I><Id><Id>1</Id>|
02F0 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 |<Issr>ACQR</Issr|
0300 3E 3C 2F 49 64 3E 3C 53 79 73 4E 6D 3E 50 4F 49 |></Id><SysNm>POI|
0310 30 31 3C 2F 53 79 73 4E 6D 3E 3C 43 70 62 6C 74 |01</SysNm><Cpblt|
0320 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
0330 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 |lties>CICC</Card|
0340 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 |RdngCpblties><Ca|
0350 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D |rdRdngCpblties>M|
0360 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |GST</CardRdngCpb|
0370 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
0380 70 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 |pblties>PHYS</Ca|
0390 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
03A0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
03B0 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 |lties>MNSG</Crdh|
03C0 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
03D0 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
03E0 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 |Cpblties>FCPN</C|
03F0 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0400 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0410 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 4E |ctnCpblties>FEPN|
0420 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
0430 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
0440 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E |VrfctnCpblties>N|
0450 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |PIN</CrdhldrVrfc|
0460 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 |tnCpblties><OnLi|
0470 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C |neCpblties>SMON<|
0480 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E |/OnLineCpblties>|
0490 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
04A0 74 6E 3E 43 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E |tn>CDSP</Dstn><N|
04B0 62 4F 66 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 |bOfLines>2</NbOf|
04C0 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 |Lines><LineWidth|
04D0 3E 32 30 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C |>20</LineWidth><|
04E0 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 |/MsgCpblties><Ms|
04F0 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E |gCpblties><Dstn>|
0500 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 |MRCP</Dstn><NbOf|
0510 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 4C 69 6E |Lines>2</NbOfLin|
0520 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 34 30 |es><LineWidth>40|
0530 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 |</LineWidth></Ms|
0540 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |gCpblties></Cpbl|
0550 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
0560 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 49 74 |TERM</Tp><Id><It|
0570 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E 3C 50 72 |mNb>1</ItmNb><Pr|
0580 76 64 72 49 64 3E 45 50 41 53 56 65 6E 64 6F 72 |vdrId>EPASVendor|
0590 30 30 31 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |001</PrvdrId><Id|

7 Messages Examples - 295 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

05A0 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 39 3C 2F |>SmartPOI-8539</|
05B0 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 35 34 31 |Id><SrlNb>782541|
05C0 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 |0759</SrlNb></Id|
05D0 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E |></Cmpnt><Cmpnt>|
05E0 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 |<Tp>APLI</Tp><Id|
05F0 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 |><ItmNb>1</ItmNb|
0600 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 |><PrvdrId>EPASVe|
0610 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 |ndor001</PrvdrId|
0620 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
0630 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E 62 3E 3C |Nb>1.0</VrsnNb><|
0640 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|
0650 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
0660 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 72 73 6E |><Vrsn>3.0</Vrsn|
0670 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 73 73 72 |><Issr>CIR</Issr|
0680 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 2F 43 6D |></StdCmplc></Cm|
0690 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |pnt></POI><Card>|
06A0 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 61 3E |<PrtctdCardData>|
06B0 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E |<CnttTp>EVLP</Cn|
06C0 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 |ttTp><EnvlpdData|
06D0 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B |><Rcpt><KEK><KEK|
06E0 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 |Id><KeyId>SpecV1|
06F0 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C |TestKey</KeyId><|
0700 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 |KeyVrsn>20100607|
0710 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 |15</KeyVrsn><Der|
0720 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C |ivtnId>OYclpQE=<|
0730 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B |/DerivtnId></KEK|
0740 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 |Id><KeyNcrptnAlg|
0750 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C |o><Algo>DKP9</Al|
0760 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C |go></KeyNcrptnAl|
0770 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 |go><NcrptdKey>4p|
0780 41 67 41 42 63 3D 3C 2F 4E 63 72 70 74 64 4B 65 |AgABc=</NcrptdKe|
0790 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C |y></KEK></Rcpt><|
07A0 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 |NcrptdCntt><Cntt|
07B0 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E |Tp>DATA</CnttTp>|
07C0 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E |<CnttNcrptnAlgo>|
07D0 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F |<Algo>E3DC</Algo|
07E0 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 |><Param><Initlst|
07F0 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 |nVctr>onu0bRwwbg|
0800 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 |k=</InitlstnVctr|
0810 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E |></Param></CnttN|
0820 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 |crptnAlgo><Ncrpt|
0830 64 44 61 74 61 3E 79 34 56 49 38 76 4E 6A 50 45 |dData>y4VI8vNjPE|
0840 33 70 63 59 34 4C 38 59 58 6F 64 50 6C 61 31 41 |3pcY4L8YXodPla1A|
0850 76 75 61 62 2F 50 36 76 74 38 56 38 45 4A 6D 46 |vuab/P6vt8V8EJmF|
0860 2B 2B 75 71 64 67 52 64 51 76 44 69 36 50 52 39 |++uqdgRdQvDi6PR9|
0870 4A 6B 4D 62 51 74 66 39 38 77 6F 2F 6B 68 74 6C |JkMbQtf98wo/khtl|
0880 78 6D 6D 4E 37 4F 43 4D 6D 6B 52 49 4F 42 52 6E |xmmN7OCMmkRIOBRn|
0890 4F 2F 33 67 58 53 4B 33 67 7A 4A 48 6C 6D 58 49 |O/3gXSK3gzJHlmXI|
08A0 79 5A 75 7A 63 52 65 5A 52 4D 4A 47 4D 57 4A 39 |yZuzcReZRMJGMWJ9|
08B0 32 39 56 2B 6A 62 63 70 34 59 44 44 47 77 30 54 |29V+jbcp4YDDGw0T|
08C0 53 74 6E 66 69 32 55 30 70 4B 4D 66 58 55 4F 6B |Stnfi2U0pKMfXUOk|
08D0 42 30 5A 6A 50 39 35 75 71 64 77 6B 6D 36 58 70 |B0ZjP95uqdwkm6Xp|
08E0 73 7A 35 38 58 2B 52 75 5A 4B 34 39 48 37 78 52 |sz58X+RuZK49H7xR|

7 Messages Examples - 296 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

08F0 4C 70 65 72 52 35 2B 61 38 42 6A 43 46 63 44 66 |LperR5+a8BjCFcDf|
0900 74 57 71 65 4A 33 78 32 45 52 4F 64 63 39 48 6D |tWqeJ3x2EROdc9Hm|
0910 6B 6E 57 48 71 72 5A 61 2F 34 45 68 38 76 42 42 |knWHqrZa/4Eh8vBB|
0920 54 6A 72 4C 45 30 53 63 6E 43 57 6F 6B 4E 6B 6E |TjrLE0ScnCWokNkn|
0930 75 62 34 4E 79 64 34 6F 35 6E 32 73 71 70 6F 54 |ub4Nyd4o5n2sqpoT|
0940 4D 3D 3C 2F 4E 63 72 70 74 64 44 61 74 61 3E 3C |M=</NcrptdData><|
0950 2F 4E 63 72 70 74 64 43 6E 74 74 3E 3C 2F 45 6E |/NcrptdCntt></En|
0960 76 6C 70 64 44 61 74 61 3E 3C 2F 50 72 74 63 74 |vlpdData></Prtct|
0970 64 43 61 72 64 44 61 74 61 3E 3C 43 61 72 64 43 |dCardData><CardC|
0980 74 72 79 43 64 3E 30 35 36 3C 2F 43 61 72 64 43 |tryCd>056</CardC|
0990 74 72 79 43 64 3E 3C 43 61 72 64 50 64 63 74 50 |tryCd><CardPdctP|
09A0 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 |rfl>0003</CardPd|
09B0 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E 64 |ctPrfl><CardBrnd|
09C0 3E 54 65 73 74 43 61 72 64 3C 2F 43 61 72 64 42 |>TestCard</CardB|
09D0 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 43 72 64 68 |rnd></Card><Crdh|
09E0 6C 64 72 3E 3C 4C 61 6E 67 3E 66 72 3C 2F 4C 61 |ldr><Lang>fr</La|
09F0 6E 67 3E 3C 54 78 56 72 66 63 74 6E 52 73 6C 74 |ng><TxVrfctnRslt|
0A00 3E 3C 4D 74 64 3E 46 50 49 4E 3C 2F 4D 74 64 3E |><Mtd>FPIN</Mtd>|
0A10 3C 56 72 66 63 74 6E 4E 74 74 79 3E 49 43 43 44 |<VrfctnNtty>ICCD|
0A20 3C 2F 56 72 66 63 74 6E 4E 74 74 79 3E 3C 52 73 |</VrfctnNtty><Rs|
0A30 6C 74 3E 53 55 43 43 3C 2F 52 73 6C 74 3E 3C 2F |lt>SUCC</Rslt></|
0A40 54 78 56 72 66 63 74 6E 52 73 6C 74 3E 3C 2F 43 |TxVrfctnRslt></C|
0A50 72 64 68 6C 64 72 3E 3C 2F 45 6E 76 74 3E 3C 43 |rdhldr></Envt><C|
0A60 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
0A70 43 61 72 64 50 72 65 73 3E 74 72 75 65 3C 2F 43 |CardPres>true</C|
0A80 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C 64 72 |ardPres><Crdhldr|
0A90 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C |Pres>true</Crdhl|
0AA0 64 72 50 72 65 73 3E 3C 41 74 74 6E 64 6E 63 43 |drPres><AttndncC|
0AB0 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
0AC0 6E 63 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 74 |ncCntxt><Attndnt|
0AD0 4D 73 67 43 70 62 6C 3E 74 72 75 65 3C 2F 41 74 |MsgCpbl>true</At|
0AE0 74 6E 64 6E 74 4D 73 67 43 70 62 6C 3E 3C 41 74 |tndntMsgCpbl><At|
0AF0 74 6E 64 6E 74 4C 61 6E 67 3E 66 72 3C 2F 41 74 |tndntLang>fr</At|
0B00 74 6E 64 6E 74 4C 61 6E 67 3E 3C 43 61 72 64 44 |tndntLang><CardD|
0B10 61 74 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F |ataNtryMd>CICC</|
0B20 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C |CardDataNtryMd><|
0B30 2F 50 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 |/PmtCntxt><SaleC|
0B40 6E 74 78 74 3E 3C 53 61 6C 65 49 64 3E 53 54 30 |ntxt><SaleId>ST0|
0B50 36 3C 2F 53 61 6C 65 49 64 3E 3C 53 61 6C 65 52 |6</SaleId><SaleR|
0B60 65 66 4E 62 3E 53 37 38 2D 54 30 36 2D 30 30 32 |efNb>S78-T06-002|
0B70 39 3C 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 53 61 |9</SaleRefNb><Sa|
0B80 6C 65 52 63 6E 63 6C 74 6E 49 64 3E 53 37 38 2D |leRcncltnId>S78-|
0B90 38 34 36 39 3C 2F 53 61 6C 65 52 63 6E 63 6C 74 |8469</SaleRcnclt|
0BA0 6E 49 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E |nId></SaleCntxt>|
0BB0 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 43 |</Cntxt><Tx><TxC|
0BC0 61 70 74 72 3E 66 61 6C 73 65 3C 2F 54 78 43 61 |aptr>false</TxCa|
0BD0 70 74 72 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F |ptr><TxTp>CRDP</|
0BE0 54 78 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 |TxTp><MrchntCtgy|
0BF0 43 64 3E 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 |Cd>5411</MrchntC|
0C00 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 |tgyCd><TxId><TxD|
0C10 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 |tTm>2013-08-11T1|
0C20 37 3A 32 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 |7:22:04.51+01:00|
0C30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|

7 Messages Examples - 297 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0C40 30 30 32 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F |002949</TxRef></|
0C50 54 78 49 64 3E 3C 52 63 6E 63 6C 74 6E 49 64 3E |TxId><RcncltnId>|
0C60 38 34 36 39 3C 2F 52 63 6E 63 6C 74 6E 49 64 3E |8469</RcncltnId>|
0C70 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 |<TxDtls><Ccy>EUR|
0C80 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 34 33 |</Ccy><TtlAmt>43|
0C90 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E 3C 4F 6E 4C |.14</TtlAmt><OnL|
0CA0 69 6E 65 52 73 6E 3E 49 43 43 46 3C 2F 4F 6E 4C |ineRsn>ICCF</OnL|
0CB0 69 6E 65 52 73 6E 3E 3C 49 43 43 52 6C 74 64 44 |ineRsn><ICCRltdD|
0CC0 61 74 61 3E 58 79 6F 43 43 58 68 66 4E 41 45 41 |ata>XyoCCXhfNAEA|
0CD0 67 67 4A 38 41 49 51 48 6F 41 41 41 41 41 6B 31 |ggJ8AIQHoAAAAAk1|
0CE0 45 4A 55 46 41 41 41 41 67 41 43 61 41 78 45 45 |EJUFAAAAgACaAxEE|
0CF0 45 5A 77 42 41 4A 38 43 42 67 41 41 41 41 42 44 |EZwBAJ8CBgAAAABD|
0D00 46 4A 38 4A 41 67 41 43 6E 78 41 53 41 68 43 6E |FJ8JAgACnxASAhCn|
0D10 67 41 4D 45 41 41 43 66 49 51 41 41 41 41 41 41 |gAMEAACfIQAAAAAA|
0D20 41 41 44 2F 6E 78 6F 43 41 6C 43 66 4A 67 67 75 |AAD/nxoCAlCfJggu|
0D30 50 71 73 58 7A 75 78 51 44 4A 38 6E 41 59 43 66 |PqsXzuxQDJ8nAYCf|
0D40 4D 77 4E 67 6F 45 43 66 4E 41 4E 45 41 77 4B 66 |MwNgoECfNANEAwKf|
0D50 4E 51 45 69 6E 7A 59 43 41 42 61 66 4E 77 53 38 |NQEinzYCABafNwS8|
0D60 64 65 6D 7A 6E 30 41 46 6F 41 43 51 38 41 47 66 |demzn0AFoACQ8AGf|
0D70 54 41 69 66 49 62 41 75 44 75 72 45 56 41 3D 3D |TAifIbAuDurEVA==|
0D80 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F |</ICCRltdData></|
0D90 54 78 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 41 75 |TxDtls></Tx></Au|
0DA0 74 68 73 74 6E 52 65 71 3E 3C 53 63 74 79 54 72 |thstnReq><SctyTr|
0DB0 6C 72 3E 3C 43 6E 74 74 54 70 3E 41 55 54 48 3C |lr><CnttTp>AUTH<|
0DC0 2F 43 6E 74 74 54 70 3E 3C 41 75 74 68 6E 74 63 |/CnttTp><Authntc|
0DD0 64 44 61 74 61 3E 3C 52 63 70 74 3E 3C 4B 45 4B |dData><Rcpt><KEK|
0DE0 3E 3C 4B 45 4B 49 64 3E 3C 4B 65 79 49 64 3E 53 |><KEKId><KeyId>S|
0DF0 70 65 63 56 31 54 65 73 74 4B 65 79 3C 2F 4B 65 |pecV1TestKey</Ke|
0E00 79 49 64 3E 3C 4B 65 79 56 72 73 6E 3E 32 30 31 |yId><KeyVrsn>201|
0E10 30 30 36 30 37 31 35 3C 2F 4B 65 79 56 72 73 6E |0060715</KeyVrsn|
0E20 3E 3C 44 65 72 69 76 74 6E 49 64 3E 4F 59 63 6C |><DerivtnId>OYcl|
0E30 70 51 45 3D 3C 2F 44 65 72 69 76 74 6E 49 64 3E |pQE=</DerivtnId>|
0E40 3C 2F 4B 45 4B 49 64 3E 3C 4B 65 79 4E 63 72 70 |</KEKId><KeyNcrp|
0E50 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 |tnAlgo><Algo>DKP|
0E60 39 3C 2F 41 6C 67 6F 3E 3C 2F 4B 65 79 4E 63 72 |9</Algo></KeyNcr|
0E70 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 4B |ptnAlgo><NcrptdK|
0E80 65 79 3E 34 70 41 67 41 42 63 3D 3C 2F 4E 63 72 |ey>4pAgABc=</Ncr|
0E90 70 74 64 4B 65 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 |ptdKey></KEK></R|
0EA0 63 70 74 3E 3C 4D 41 43 41 6C 67 6F 3E 3C 41 6C |cpt><MACAlgo><Al|
0EB0 67 6F 3E 4D 43 43 53 3C 2F 41 6C 67 6F 3E 3C 2F |go>MCCS</Algo></|
0EC0 4D 41 43 41 6C 67 6F 3E 3C 4E 63 70 73 6C 74 64 |MACAlgo><Ncpsltd|
0ED0 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 41 54 |Cntt><CnttTp>DAT|
0EE0 41 3C 2F 43 6E 74 74 54 70 3E 3C 2F 4E 63 70 73 |A</CnttTp></Ncps|
0EF0 6C 74 64 43 6E 74 74 3E 3C 4D 41 43 3E 32 36 55 |ltdCntt><MAC>26U|
0F00 54 62 6B 6B 63 51 65 51 3D 3C 2F 4D 41 43 3E 3C |TbkkcQeQ=</MAC><|
0F10 2F 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 2F |/AuthntcdData></|
0F20 53 63 74 79 54 72 6C 72 3E 3C 2F 41 63 63 70 74 |SctyTrlr></Accpt|
0F30 72 41 75 74 68 73 74 6E 52 65 71 3E 3C 2F 44 6F |rAuthstnReq></Do|
0F40 63 75 6D 65 6E 74 3E |cument> |

7 Messages Examples - 298 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

7.2.2 AcceptorAuthorisationResponse

The transaction is approved by the Issuer who provides the authorisation code 032983.

Message Item Value


Transaction
TransactionIdentification
TransactionDateTime 2013-08-11T17:22:04.51+01:00
TransactionReference 002949
TransactionDetails
Currency EUR
TotalAmount 43.14
ICCRelatedData 910A74E52FC59D6ADE2A00128A023030
TransactionResponse
AuthorisationResult
AuthorisationEntity
Type CardIssuer
ResponseToAuthorisation
Response Approved
AuthorisationCode 032983
CompletionRequired True

The resulting XML encoded structures are:


<Tx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<ICCRltdData>kQp05S/FnWreKgASigIwMA==</ICCRltdData>
</TxDtls>
</Tx>
<TxRspn>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
<CmpltnReqrd>true</CmpltnReqrd>
</AuthstnRslt>
</TxRspn>

7 Messages Examples - 299 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorAuthorisationResponse is presented below, omitting data structure already


previously detailed.

Message Item Value


AcceptorAuthorisationResponse
Header
MessageFunction AuthorisationResponse
ProtocolVersion 5.0
ExchangeIdentifier 149
CreationDateTime 2013-08-11T17:22:55.11+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
AuthorisationResponse
Environment
AcquirerIdentification
Identification 9287351
Type Acquirer
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 1
Issuer Acquirer
ProtectedCardData
---
Transaction
---
TransactionResponse
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData

7 Messages Examples - 300 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

MAC BA5E3CC2BB8078E2
---

The AcceptorAuthorisationResponse XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.002.001.05">
<AccptrAuthstnRspn>
<Hdr>
<MsgFctn>AUTP</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>149</XchgId>
<CreDtTm>2013-08-11T17:22:55.11+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<AuthstnRspn>
<Envt>
<AcqrrId>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</AcqrrId>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>1</Id>
<Issr>ACQR</Issr>
</POIId>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>

7 Messages Examples - 301 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

</CnttNcrptnAlgo>
<NcrptdData>
CAagOqDDQiVw/J5uM3vWxfRy1hzoxccje0xums6+s/EmqMK5
+7xfxcx3y+FNTw1+5sU7Tu98xgODcLDaU2Nxmb7jyYe9mDlN
/Q1/NJHPTbtLkh981WSeWnjFqB2YGXmkNKmnvxBT+LB2H+n+
1hVpwA==
</NcrptdData>
</NcrptdCntt>
</EnvlpdData>
</PrtctdCardData>
</Card>
</Envt>
<Tx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<ICCRltdData>kQp05S/FnWreKgASigIwMA==</ICCRltdData>
</TxDtls>
</Tx>
<TxRspn>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
<CmpltnReqrd>true</CmpltnReqrd>
</AuthstnRslt>
</TxRspn>
</AuthstnRspn>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>ul48wruAeOI=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrAuthstnRspn>
</Document>

7 Messages Examples - 302 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body AuthstnRspn
(without spaces or line breaks) is dumped below:
0000 3C 41 75 74 68 73 74 6E 52 73 70 6E 3E 3C 45 6E |<AuthstnRspn><En|
0010 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 3E |vt><AcqrrId><Id>|
0020 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 3E |9287351</Id><Tp>|
0030 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 72 |ACQR</Tp></Acqrr|
0040 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 64 |Id><MrchntId><Id|
0050 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E |>EPASMER001</Id>|
0060 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 49 |</MrchntId><POII|
0070 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 |d><Id>1</Id><Iss|
0080 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 50 |r>ACQR</Issr></P|
0090 4F 49 49 64 3E 3C 43 61 72 64 3E 3C 50 72 74 63 |OIId><Card><Prtc|
00A0 74 64 43 61 72 64 44 61 74 61 3E 3C 43 6E 74 74 |tdCardData><Cntt|
00B0 54 70 3E 45 56 4C 50 3C 2F 43 6E 74 74 54 70 3E |Tp>EVLP</CnttTp>|
00C0 3C 45 6E 76 6C 70 64 44 61 74 61 3E 3C 52 63 70 |<EnvlpdData><Rcp|
00D0 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B |t><KEK><KEKId><K|
00E0 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 4B |eyId>SpecV1TestK|
00F0 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 |ey</KeyId><KeyVr|
0100 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F 4B |sn>2010060715</K|
0110 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 |eyVrsn><DerivtnI|
0120 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 |d>OYclpQE=</Deri|
0130 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B |vtnId></KEKId><K|
0140 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C |eyNcrptnAlgo><Al|
0150 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F |go>DKP9</Algo></|
0160 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E |KeyNcrptnAlgo><N|
0170 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 63 |crptdKey>4pAgABc|
0180 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B |=</NcrptdKey></K|
0190 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4E 63 72 70 74 |EK></Rcpt><Ncrpt|
01A0 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 41 |dCntt><CnttTp>DA|
01B0 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 43 6E 74 74 |TA</CnttTp><Cntt|
01C0 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F |NcrptnAlgo><Algo|
01D0 3E 45 33 44 43 3C 2F 41 6C 67 6F 3E 3C 50 61 72 |>E3DC</Algo><Par|
01E0 61 6D 3E 3C 49 6E 69 74 6C 73 74 6E 56 63 74 72 |am><InitlstnVctr|
01F0 3E 6F 6E 75 30 62 52 77 77 62 67 6B 3D 3C 2F 49 |>onu0bRwwbgk=</I|
0200 6E 69 74 6C 73 74 6E 56 63 74 72 3E 3C 2F 50 61 |nitlstnVctr></Pa|
0210 72 61 6D 3E 3C 2F 43 6E 74 74 4E 63 72 70 74 6E |ram></CnttNcrptn|
0220 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 44 61 74 61 |Algo><NcrptdData|
0230 3E 43 41 61 67 4F 71 44 44 51 69 56 77 2F 4A 35 |>CAagOqDDQiVw/J5|
0240 75 4D 33 76 57 78 66 52 79 31 68 7A 6F 78 63 63 |uM3vWxfRy1hzoxcc|
0250 6A 65 30 78 75 6D 73 36 2B 73 2F 45 6D 71 4D 4B |je0xums6+s/EmqMK|
0260 35 2B 37 78 66 78 63 78 33 79 2B 46 4E 54 77 31 |5+7xfxcx3y+FNTw1|
0270 2B 35 73 55 37 54 75 39 38 78 67 4F 44 63 4C 44 |+5sU7Tu98xgODcLD|
0280 61 55 32 4E 78 6D 62 37 6A 79 59 65 39 6D 44 6C |aU2Nxmb7jyYe9mDl|
0290 4E 2F 51 31 2F 4E 4A 48 50 54 62 74 4C 6B 68 39 |N/Q1/NJHPTbtLkh9|
02A0 38 31 57 53 65 57 6E 6A 46 71 42 32 59 47 58 6D |81WSeWnjFqB2YGXm|
02B0 6B 4E 4B 6D 6E 76 78 42 54 2B 4C 42 32 48 2B 6E |kNKmnvxBT+LB2H+n|
02C0 2B 31 68 56 70 77 41 3D 3D 3C 2F 4E 63 72 70 74 |+1hVpwA==</Ncrpt|
02D0 64 44 61 74 61 3E 3C 2F 4E 63 72 70 74 64 43 6E |dData></NcrptdCn|
02E0 74 74 3E 3C 2F 45 6E 76 6C 70 64 44 61 74 61 3E |tt></EnvlpdData>|
02F0 3C 2F 50 72 74 63 74 64 43 61 72 64 44 61 74 61 |</PrtctdCardData|
0300 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C |></Card></Envt><|
0310 54 78 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Tx><TxId><TxDtTm|

7 Messages Examples - 303 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0320 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 37 3A 32 |>2013-08-11T17:2|
0330 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 3C 2F 54 |2:04.51+01:00</T|
0340 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 32 |xDtTm><TxRef>002|
0350 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 |949</TxRef></TxI|
0360 64 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 |d><TxDtls><Ccy>E|
0370 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E |UR</Ccy><TtlAmt>|
0380 34 33 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E 3C 49 |43.14</TtlAmt><I|
0390 43 43 52 6C 74 64 44 61 74 61 3E 6B 51 70 30 35 |CCRltdData>kQp05|
03A0 53 2F 46 6E 57 72 65 4B 67 41 53 69 67 49 77 4D |S/FnWreKgASigIwM|
03B0 41 3D 3D 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 |A==</ICCRltdData|
03C0 3E 3C 2F 54 78 44 74 6C 73 3E 3C 2F 54 78 3E 3C |></TxDtls></Tx><|
03D0 54 78 52 73 70 6E 3E 3C 41 75 74 68 73 74 6E 52 |TxRspn><AuthstnR|
03E0 73 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 |slt><AuthstnNtty|
03F0 3E 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F |><Tp>CISS</Tp></|
0400 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 |AuthstnNtty><Rsp|
0410 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E |nToAuthstn><Rspn|
0420 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 |>APPR</Rspn></Rs|
0430 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 |pnToAuthstn><Aut|
0440 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 |hstnCd>032983</A|
0450 75 74 68 73 74 6E 43 64 3E 3C 43 6D 70 6C 74 6E |uthstnCd><Cmpltn|
0460 52 65 71 72 64 3E 74 72 75 65 3C 2F 43 6D 70 6C |Reqrd>true</Cmpl|
0470 74 6E 52 65 71 72 64 3E 3C 2F 41 75 74 68 73 74 |tnReqrd></Authst|
0480 6E 52 73 6C 74 3E 3C 2F 54 78 52 73 70 6E 3E 3C |nRslt></TxRspn><|
0490 2F 41 75 74 68 73 74 6E 52 73 70 6E 3E |/AuthstnRspn> |

The SHA-256 digest of the message body AuthstnRspn is:


0000 F8 82 B9 A2 54 E7 D1 A9 59 E4 63 8B A2 29 E2 7C |....T...Y.c..).||
0010 AA 75 8D CE 11 5E 47 72 88 52 81 BF 95 F5 D7 0A |.u...^Gr.R......|

After padding, the digest becomes:


0000 F8 82 B9 A2 54 E7 D1 A9 59 E4 63 8B A2 29 E2 7C |....T...Y.c..).||
0010 AA 75 8D CE 11 5E 47 72 88 52 81 BF 95 F5 D7 0A |.u...^Gr.R......|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (5E64F1AB 0D5DC4A1 7F629EC2
4C0207EA), we obtain the MAC of the AcceptorAuthorisationResponse BA5E3CC2BB8078E2 and
after conversion into base64 "ul48wruAeOI=".
0000 27 18 F6 88 F3 29 20 75 23 FB 47 A9 EE AD 05 75 |'....) u#.G....u|
0010 32 8B 81 13 2C 87 4C 63 31 A0 3F EE 69 AD 07 A8 |2...,.Lc1.?.i...|
0020 BA 5E 3C C2 BB 80 78 E2 |.^<...x. |

The message sent by the transport protocol is:


0000 00 00 07 E9 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|

7 Messages Examples - 304 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 32 2E 30 30 31 2E 30 35 22 |caaa.002.001.05"|
00A0 3E 3C 41 63 63 70 74 72 41 75 74 68 73 74 6E 52 |><AccptrAuthstnR|
00B0 73 70 6E 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 |spn><Hdr><MsgFct|
00C0 6E 3E 41 55 54 50 3C 2F 4D 73 67 46 63 74 6E 3E |n>AUTP</MsgFctn>|
00D0 3C 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C |<PrtcolVrsn>5.0<|
00E0 2F 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 |/PrtcolVrsn><Xch|
00F0 67 49 64 3E 31 34 39 3C 2F 58 63 68 67 49 64 3E |gId>149</XchgId>|
0100 3C 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 |<CreDtTm>2013-08|
0110 2D 31 31 54 31 37 3A 32 32 3A 35 35 2E 31 31 2B |-11T17:22:55.11+|
0120 30 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C |01:00</CreDtTm><|
0130 49 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 |InitgPty><Id>660|
0140 30 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 |00001</Id><Tp>OP|
0150 4F 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 |OI</Tp><Issr>ACQ|
0160 52 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 |R</Issr></InitgP|
0170 74 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E |ty><RcptPty><Id>|
0180 65 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C |epas-acquirer-1<|
0190 2F 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 |/Id><Tp>ACQR</Tp|
01A0 3E 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 |></RcptPty></Hdr|
01B0 3E 3C 41 75 74 68 73 74 6E 52 73 70 6E 3E 3C 45 |><AuthstnRspn><E|
01C0 6E 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 |nvt><AcqrrId><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 |>ACQR</Tp></Acqr|
01F0 72 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 |rId><MrchntId><I|
0200 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 |d>EPASMER001</Id|
0210 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 |></MrchntId><POI|
0220 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 |Id><Id>1</Id><Is|
0230 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F |sr>ACQR</Issr></|
0240 50 4F 49 49 64 3E 3C 43 61 72 64 3E 3C 50 72 74 |POIId><Card><Prt|
0250 63 74 64 43 61 72 64 44 61 74 61 3E 3C 43 6E 74 |ctdCardData><Cnt|
0260 74 54 70 3E 45 56 4C 50 3C 2F 43 6E 74 74 54 70 |tTp>EVLP</CnttTp|
0270 3E 3C 45 6E 76 6C 70 64 44 61 74 61 3E 3C 52 63 |><EnvlpdData><Rc|
0280 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C |pt><KEK><KEKId><|
0290 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 |KeyId>SpecV1Test|
02A0 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 |Key</KeyId><KeyV|
02B0 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F |rsn>2010060715</|
02C0 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E |KeyVrsn><Derivtn|
02D0 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 |Id>OYclpQE=</Der|
02E0 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C |ivtnId></KEKId><|
02F0 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |KeyNcrptnAlgo><A|
0300 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C |lgo>DKP9</Algo><|
0310 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |/KeyNcrptnAlgo><|
0320 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 |NcrptdKey>4pAgAB|
0330 63 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F |c=</NcrptdKey></|
0340 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4E 63 72 70 |KEK></Rcpt><Ncrp|
0350 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 |tdCntt><CnttTp>D|
0360 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 43 6E 74 |ATA</CnttTp><Cnt|
0370 74 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 |tNcrptnAlgo><Alg|
0380 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F 3E 3C 50 61 |o>E3DC</Algo><Pa|
0390 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 6E 56 63 74 |ram><InitlstnVct|

7 Messages Examples - 305 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

03A0 72 3E 6F 6E 75 30 62 52 77 77 62 67 6B 3D 3C 2F |r>onu0bRwwbgk=</|
03B0 49 6E 69 74 6C 73 74 6E 56 63 74 72 3E 3C 2F 50 |InitlstnVctr></P|
03C0 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E 63 72 70 74 |aram></CnttNcrpt|
03D0 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 44 61 74 |nAlgo><NcrptdDat|
03E0 61 3E 43 41 61 67 4F 71 44 44 51 69 56 77 2F 4A |a>CAagOqDDQiVw/J|
03F0 35 75 4D 33 76 57 78 66 52 79 31 68 7A 6F 78 63 |5uM3vWxfRy1hzoxc|
0400 63 6A 65 30 78 75 6D 73 36 2B 73 2F 45 6D 71 4D |cje0xums6+s/EmqM|
0410 4B 35 2B 37 78 66 78 63 78 33 79 2B 46 4E 54 77 |K5+7xfxcx3y+FNTw|
0420 31 2B 35 73 55 37 54 75 39 38 78 67 4F 44 63 4C |1+5sU7Tu98xgODcL|
0430 44 61 55 32 4E 78 6D 62 37 6A 79 59 65 39 6D 44 |DaU2Nxmb7jyYe9mD|
0440 6C 4E 2F 51 31 2F 4E 4A 48 50 54 62 74 4C 6B 68 |lN/Q1/NJHPTbtLkh|
0450 39 38 31 57 53 65 57 6E 6A 46 71 42 32 59 47 58 |981WSeWnjFqB2YGX|
0460 6D 6B 4E 4B 6D 6E 76 78 42 54 2B 4C 42 32 48 2B |mkNKmnvxBT+LB2H+|
0470 6E 2B 31 68 56 70 77 41 3D 3D 3C 2F 4E 63 72 70 |n+1hVpwA==</Ncrp|
0480 74 64 44 61 74 61 3E 3C 2F 4E 63 72 70 74 64 43 |tdData></NcrptdC|
0490 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 44 61 74 61 |ntt></EnvlpdData|
04A0 3E 3C 2F 50 72 74 63 74 64 43 61 72 64 44 61 74 |></PrtctdCardDat|
04B0 61 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E |a></Card></Envt>|
04C0 3C 54 78 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 |<Tx><TxId><TxDtT|
04D0 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 37 3A |m>2013-08-11T17:|
04E0 32 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 3C 2F |22:04.51+01:00</|
04F0 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 |TxDtTm><TxRef>00|
0500 32 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 |2949</TxRef></Tx|
0510 49 64 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E |Id><TxDtls><Ccy>|
0520 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 |EUR</Ccy><TtlAmt|
0530 3E 34 33 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E 3C |>43.14</TtlAmt><|
0540 49 43 43 52 6C 74 64 44 61 74 61 3E 6B 51 70 30 |ICCRltdData>kQp0|
0550 35 53 2F 46 6E 57 72 65 4B 67 41 53 69 67 49 77 |5S/FnWreKgASigIw|
0560 4D 41 3D 3D 3C 2F 49 43 43 52 6C 74 64 44 61 74 |MA==</ICCRltdDat|
0570 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C 2F 54 78 3E |a></TxDtls></Tx>|
0580 3C 54 78 52 73 70 6E 3E 3C 41 75 74 68 73 74 6E |<TxRspn><Authstn|
0590 52 73 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 |Rslt><AuthstnNtt|
05A0 79 3E 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C |y><Tp>CISS</Tp><|
05B0 2F 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 |/AuthstnNtty><Rs|
05C0 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 |pnToAuthstn><Rsp|
05D0 6E 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 |n>APPR</Rspn></R|
05E0 73 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 |spnToAuthstn><Au|
05F0 74 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F |thstnCd>032983</|
0600 41 75 74 68 73 74 6E 43 64 3E 3C 43 6D 70 6C 74 |AuthstnCd><Cmplt|
0610 6E 52 65 71 72 64 3E 74 72 75 65 3C 2F 43 6D 70 |nReqrd>true</Cmp|
0620 6C 74 6E 52 65 71 72 64 3E 3C 2F 41 75 74 68 73 |ltnReqrd></Auths|
0630 74 6E 52 73 6C 74 3E 3C 2F 54 78 52 73 70 6E 3E |tnRslt></TxRspn>|
0640 3C 2F 41 75 74 68 73 74 6E 52 73 70 6E 3E 3C 53 |</AuthstnRspn><S|
0650 63 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 70 3E |ctyTrlr><CnttTp>|
0660 41 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C 41 75 |AUTH</CnttTp><Au|
0670 74 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 70 74 |thntcdData><Rcpt|
0680 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B 65 |><KEK><KEKId><Ke|
0690 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 4B 65 |yId>SpecV1TestKe|
06A0 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 73 |y</KeyId><KeyVrs|
06B0 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F 4B 65 |n>2010060715</Ke|
06C0 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 64 |yVrsn><DerivtnId|
06D0 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 76 |>OYclpQE=</Deriv|
06E0 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B 65 |tnId></KEKId><Ke|

7 Messages Examples - 306 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

06F0 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 |yNcrptnAlgo><Alg|
0700 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F 4B |o>DKP9</Algo></K|
0710 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 |eyNcrptnAlgo><Nc|
0720 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 63 3D |rptdKey>4pAgABc=|
0730 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B 45 |</NcrptdKey></KE|
0740 4B 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 6C 67 |K></Rcpt><MACAlg|
0750 6F 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F 41 6C |o><Algo>MCCS</Al|
0760 67 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C 4E 63 |go></MACAlgo><Nc|
0770 70 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 |psltdCntt><CnttT|
0780 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C |p>DATA</CnttTp><|
0790 2F 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 4D 41 |/NcpsltdCntt><MA|
07A0 43 3E 75 6C 34 38 77 72 75 41 65 4F 49 3D 3C 2F |C>ul48wruAeOI=</|
07B0 4D 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 44 61 |MAC></AuthntcdDa|
07C0 74 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E 3C 2F |ta></SctyTrlr></|
07D0 41 63 63 70 74 72 41 75 74 68 73 74 6E 52 73 70 |AccptrAuthstnRsp|
07E0 6E 3E 3C 2F 44 6F 63 75 6D 65 6E 74 3E |n></Document> |

7 Messages Examples - 307 - 7.2 Authorisation Messages


Card Payments Message Usage Guide Version 5.0

7.3 Completion Messages

7.3.1 AcceptorCompletionAdvice

The transaction has been successfully completed by the Acceptor and must be captured with a
completion advice.

Message Item Value


Transaction
TransactionCapture True
TransactionType CardPayment
MerchantCategoryCode 5411
TransactionIdentification
TransactionDateTime 2013-08-11T17:22:04.51+01:00
TransactionReference 002949
TransactionSucess True
ReconciliationIdentification 8469
TransactionDetails
Currency EUR
TotalAmount 43.14
ICCRelatedData 5F2A0209785F34010082027C008407A00000000935108A02
3030910A74E52FC59D6ADE2A0012950500000080009A0311
04119C01009F02060000000043149F090200029F10120210
6780030400009F2100000000000000FF9F1A0202509F2608
29A3BC20E461E80C9F2701409F330360A0409F3403440302
9F3501229F360200169F3704BC75E9B39F4005A00090F001
9F4C089F21B02E0EEAC454
AuthorisationResult
AuthorisationEntity
Type CardIssuer
ResponseToAuthorisation
Response Approved
AuthorisationCode 032983
TransactionVerificationResult
Method OfflinePIN
VerificationEntity ICC
Result Successful

The resulting XML encoded structure is:


<Tx>
<TxCaptr>true</TxCaptr>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<ICCRltdData>
XyoCCXhfNAEAggJ8AIQHoAAAAAk1EIoCMDCRCnTlL8Wdat4qABKVBQAAAIAA

7 Messages Examples - 308 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

mgMRBBGcAQCfAgYAAAAAQxSfCQIAAp8QEgIQZ4ADBAAAnyEAAAAAAAAA/58a
AgJQnyYIKaO8IORh6AyfJwFAnzMDYKBAnzQDRAMCnzUBIp82AgAWnzcEvHXp
s59ABaAAkPABn0wInyGwLg7qxFQ=
</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
<TxVrfctnRslt>
<Mtd>FPIN</Mtd>
<VrfctnNtty>ICCD</VrfctnNtty>
<Rslt>SUCC</Rslt>
</TxVrfctnRslt>
</Tx>

7 Messages Examples - 309 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorCompletionAdvice is presented below, omitting data structure already


previously detailed.

Message Item Value


AcceptorCompletionAdvice
Header
MessageFunction FinancialCompletionAdvice
ProtocolVersion 5.0
ExchangeIdentifier 150
CreationDateTime 2013-08-11T17:22:59.35+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
CompletionAdvice
Environment
Acquirer
---
Merchant
---
POI
---
Card
---
CardHolder
---
Context
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200018
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData

7 Messages Examples - 310 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

MAC AC6DF8942C3C4103
---

The AcceptorCompletionAdvice XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.003.001.05">
<AccptrCmpltnAdvc>
<Hdr>
<MsgFctn>FCMV</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>150</XchgId>
<CreDtTm>2013-08-11T17:22:59.35+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<CmpltnAdvc>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>EPASMER001</Id>
</Id>
<CmonNm>EPASOrg Merchant 1</CmonNm>
<LctnCtgy>FIXD</LctnCtgy>
<LctnAndCtct>
<PstlAdr>
<TwnNm>Paris</TwnNm>
<Ctry>FR</Ctry>
</PstlAdr>
</LctnAndCtct>
</Mrchnt>
<POI>
<Id>
<Id>1</Id>
<Issr>ACQR</Issr>
</Id>
<SysNm>POI01</SysNm>
<Cpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>CDSP</Dstn>

7 Messages Examples - 311 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

<NbOfLines>2</NbOfLines>
<LineWidth>20</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>4</NbOfLines>
<LineWidth>40</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
<Id>SmartPOI-8539</Id>
<SrlNb>7825410759</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
</Id>
<Sts>
<VrsnNb>1.0</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.0</Vrsn>
<Issr>CIR</Issr>
</StdCmplc>
</Cmpnt>
</POI>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
dhg1XEC2olzVHlhdZo633BT5MtnPgdzCY2HSICQvUunFZY16
d2/id3gmemx9+0xHPWOTfjpqasffgTpr1/y0HWH94g06vk/B
p+mYj5rzvVnOxvD6RXd4Tm+w0nfmKpEgceweGaVESKiuu6j6
X7BIrw==
</NcrptdData>
</NcrptdCntt>
</EnvlpdData>

7 Messages Examples - 312 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

</PrtctdCardData>
<CardCtryCd>056</CardCtryCd>
<CardPdctPrfl>0003</CardPdctPrfl>
<CardBrnd>TestCard</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleId>ST06</SaleId>
<SaleRefNb>S78-T06-0029</SaleRefNb>
<SaleRcncltnId>S78-8469</SaleRcncltnId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxCaptr>true</TxCaptr>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
<ICCRltdData>
XyoCCXhfNAEAggJ8AIQHoAAAAAk1EIoCMDCRCnTlL8Wdat4qABKVBQAAAIAA
mgMRBBGcAQCfAgYAAAAAQxSfCQIAAp8QEgIQZ4ADBAAAnyEAAAAAAAAA/58a
AgJQnyYIKaO8IORh6AyfJwFAnzMDYKBAnzQDRAMCnzUBIp82AgAWnzcEvHXp
s59ABaAAkPABn0wInyGwLg7qxFQ=
</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
<TxVrfctnRslt>
<Mtd>FPIN</Mtd>
<VrfctnNtty>ICCD</VrfctnNtty>
<Rslt>SUCC</Rslt>
</TxVrfctnRslt>
</Tx>
</CmpltnAdvc>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>

7 Messages Examples - 313 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>rG34lCw8QQM=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrCmpltnAdvc>
</Document>

Once unnecessary spaces and carriage returns are removed, the message body CmpltnAdvc (without
spaces or line breaks) is dumped below:
0000 3C 43 6D 70 6C 74 6E 41 64 76 63 3E 3C 45 6E 76 |<CmpltnAdvc><Env|
0010 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
0020 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
0030 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|
0040 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0050 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0060 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0070 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0080 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 |Id>EPASMER001</I|
0090 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 45 |d></Id><CmonNm>E|
00A0 50 41 53 4F 72 67 20 4D 65 72 63 68 61 6E 74 20 |PASOrg Merchant |
00B0 31 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 4C 63 74 6E 43 |1</CmonNm><LctnC|
00C0 74 67 79 3E 46 49 58 44 3C 2F 4C 63 74 6E 43 74 |tgy>FIXD</LctnCt|
00D0 67 79 3E 3C 4C 63 74 6E 41 6E 64 43 74 63 74 3E |gy><LctnAndCtct>|
00E0 3C 50 73 74 6C 41 64 72 3E 3C 54 77 6E 4E 6D 3E |<PstlAdr><TwnNm>|
00F0 50 61 72 69 73 3C 2F 54 77 6E 4E 6D 3E 3C 43 74 |Paris</TwnNm><Ct|
0100 72 79 3E 46 52 3C 2F 43 74 72 79 3E 3C 2F 50 73 |ry>FR</Ctry></Ps|
0110 74 6C 41 64 72 3E 3C 2F 4C 63 74 6E 41 6E 64 43 |tlAdr></LctnAndC|
0120 74 63 74 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F |tct></Mrchnt><PO|
0130 49 3E 3C 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E |I><Id><Id>1</Id>|
0140 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 |<Issr>ACQR</Issr|
0150 3E 3C 2F 49 64 3E 3C 53 79 73 4E 6D 3E 50 4F 49 |></Id><SysNm>POI|
0160 30 31 3C 2F 53 79 73 4E 6D 3E 3C 43 70 62 6C 74 |01</SysNm><Cpblt|
0170 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
0180 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 |lties>CICC</Card|
0190 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 |RdngCpblties><Ca|
01A0 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D |rdRdngCpblties>M|
01B0 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |GST</CardRdngCpb|
01C0 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
01D0 70 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 |pblties>PHYS</Ca|
01E0 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
01F0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
0200 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 |lties>MNSG</Crdh|
0210 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
0220 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
0230 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 |Cpblties>FCPN</C|
0240 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0250 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0260 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 4E |ctnCpblties>FEPN|

7 Messages Examples - 314 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0270 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
0280 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
0290 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E |VrfctnCpblties>N|
02A0 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |PIN</CrdhldrVrfc|
02B0 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 |tnCpblties><OnLi|
02C0 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C |neCpblties>SMON<|
02D0 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E |/OnLineCpblties>|
02E0 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
02F0 74 6E 3E 43 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E |tn>CDSP</Dstn><N|
0300 62 4F 66 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 |bOfLines>2</NbOf|
0310 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 |Lines><LineWidth|
0320 3E 32 30 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C |>20</LineWidth><|
0330 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 |/MsgCpblties><Ms|
0340 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E |gCpblties><Dstn>|
0350 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 |MDSP</Dstn><NbOf|
0360 4C 69 6E 65 73 3E 34 3C 2F 4E 62 4F 66 4C 69 6E |Lines>4</NbOfLin|
0370 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 34 30 |es><LineWidth>40|
0380 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 |</LineWidth></Ms|
0390 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |gCpblties></Cpbl|
03A0 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
03B0 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 49 74 |TERM</Tp><Id><It|
03C0 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E 3C 50 72 |mNb>1</ItmNb><Pr|
03D0 76 64 72 49 64 3E 45 50 41 53 56 65 6E 64 6F 72 |vdrId>EPASVendor|
03E0 30 30 31 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |001</PrvdrId><Id|
03F0 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 39 3C 2F |>SmartPOI-8539</|
0400 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 35 34 31 |Id><SrlNb>782541|
0410 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 |0759</SrlNb></Id|
0420 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E |></Cmpnt><Cmpnt>|
0430 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 |<Tp>APLI</Tp><Id|
0440 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 |><ItmNb>1</ItmNb|
0450 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 |><PrvdrId>EPASVe|
0460 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 |ndor001</PrvdrId|
0470 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
0480 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E 62 3E 3C |Nb>1.0</VrsnNb><|
0490 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|
04A0 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
04B0 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 72 73 6E |><Vrsn>3.0</Vrsn|
04C0 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 73 73 72 |><Issr>CIR</Issr|
04D0 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 2F 43 6D |></StdCmplc></Cm|
04E0 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |pnt></POI><Card>|
04F0 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 61 3E |<PrtctdCardData>|
0500 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E |<CnttTp>EVLP</Cn|
0510 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 |ttTp><EnvlpdData|
0520 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B |><Rcpt><KEK><KEK|
0530 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 |Id><KeyId>SpecV1|
0540 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C |TestKey</KeyId><|
0550 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 |KeyVrsn>20100607|
0560 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 |15</KeyVrsn><Der|
0570 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C |ivtnId>OYclpQE=<|
0580 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B |/DerivtnId></KEK|
0590 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 |Id><KeyNcrptnAlg|
05A0 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C |o><Algo>DKP9</Al|
05B0 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C |go></KeyNcrptnAl|

7 Messages Examples - 315 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

05C0 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 |go><NcrptdKey>4p|
05D0 41 67 41 42 67 3D 3C 2F 4E 63 72 70 74 64 4B 65 |AgABg=</NcrptdKe|
05E0 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C |y></KEK></Rcpt><|
05F0 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 |NcrptdCntt><Cntt|
0600 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E |Tp>DATA</CnttTp>|
0610 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E |<CnttNcrptnAlgo>|
0620 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F |<Algo>E3DC</Algo|
0630 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 |><Param><Initlst|
0640 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 |nVctr>onu0bRwwbg|
0650 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 |k=</InitlstnVctr|
0660 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E |></Param></CnttN|
0670 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 |crptnAlgo><Ncrpt|
0680 64 44 61 74 61 3E 64 68 67 31 58 45 43 32 6F 6C |dData>dhg1XEC2ol|
0690 7A 56 48 6C 68 64 5A 6F 36 33 33 42 54 35 4D 74 |zVHlhdZo633BT5Mt|
06A0 6E 50 67 64 7A 43 59 32 48 53 49 43 51 76 55 75 |nPgdzCY2HSICQvUu|
06B0 6E 46 5A 59 31 36 64 32 2F 69 64 33 67 6D 65 6D |nFZY16d2/id3gmem|
06C0 78 39 2B 30 78 48 50 57 4F 54 66 6A 70 71 61 73 |x9+0xHPWOTfjpqas|
06D0 66 66 67 54 70 72 31 2F 79 30 48 57 48 39 34 67 |ffgTpr1/y0HWH94g|
06E0 30 36 76 6B 2F 42 70 2B 6D 59 6A 35 72 7A 76 56 |06vk/Bp+mYj5rzvV|
06F0 6E 4F 78 76 44 36 52 58 64 34 54 6D 2B 77 30 6E |nOxvD6RXd4Tm+w0n|
0700 66 6D 4B 70 45 67 63 65 77 65 47 61 56 45 53 4B |fmKpEgceweGaVESK|
0710 69 75 75 36 6A 36 58 37 42 49 72 77 3D 3D 3C 2F |iuu6j6X7BIrw==</|
0720 4E 63 72 70 74 64 44 61 74 61 3E 3C 2F 4E 63 72 |NcrptdData></Ncr|
0730 70 74 64 43 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 |ptdCntt></Envlpd|
0740 44 61 74 61 3E 3C 2F 50 72 74 63 74 64 43 61 72 |Data></PrtctdCar|
0750 64 44 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 |dData><CardCtryC|
0760 64 3E 30 35 36 3C 2F 43 61 72 64 43 74 72 79 43 |d>056</CardCtryC|
0770 64 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |d><CardPdctPrfl>|
0780 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 |0003</CardPdctPr|
0790 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 54 65 73 |fl><CardBrnd>Tes|
07A0 74 43 61 72 64 3C 2F 43 61 72 64 42 72 6E 64 3E |tCard</CardBrnd>|
07B0 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 |</Card></Envt><C|
07C0 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
07D0 43 61 72 64 50 72 65 73 3E 74 72 75 65 3C 2F 43 |CardPres>true</C|
07E0 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C 64 72 |ardPres><Crdhldr|
07F0 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C |Pres>true</Crdhl|
0800 64 72 50 72 65 73 3E 3C 41 74 74 6E 64 6E 63 43 |drPres><AttndncC|
0810 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
0820 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 |ncCntxt><CardDat|
0830 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 |aNtryMd>CICC</Ca|
0840 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 |rdDataNtryMd></P|
0850 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 |mtCntxt><SaleCnt|
0860 78 74 3E 3C 53 61 6C 65 49 64 3E 53 54 30 36 3C |xt><SaleId>ST06<|
0870 2F 53 61 6C 65 49 64 3E 3C 53 61 6C 65 52 65 66 |/SaleId><SaleRef|
0880 4E 62 3E 53 37 38 2D 54 30 36 2D 30 30 32 39 3C |Nb>S78-T06-0029<|
0890 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 53 61 6C 65 |/SaleRefNb><Sale|
08A0 52 63 6E 63 6C 74 6E 49 64 3E 53 37 38 2D 38 34 |RcncltnId>S78-84|
08B0 36 39 3C 2F 53 61 6C 65 52 63 6E 63 6C 74 6E 49 |69</SaleRcncltnI|
08C0 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F |d></SaleCntxt></|
08D0 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 43 61 70 |Cntxt><Tx><TxCap|
08E0 74 72 3E 74 72 75 65 3C 2F 54 78 43 61 70 74 72 |tr>true</TxCaptr|
08F0 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 78 54 |><TxTp>CRDP</TxT|
0900 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 3E |p><MrchntCtgyCd>|

7 Messages Examples - 316 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0910 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 74 67 79 |5411</MrchntCtgy|
0920 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Cd><TxId><TxDtTm|
0930 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 37 3A 32 |>2013-08-11T17:2|
0940 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 3C 2F 54 |2:04.51+01:00</T|
0950 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 32 |xDtTm><TxRef>002|
0960 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 |949</TxRef></TxI|
0970 64 3E 3C 54 78 53 75 63 73 73 3E 74 72 75 65 3C |d><TxSucss>true<|
0980 2F 54 78 53 75 63 73 73 3E 3C 52 63 6E 63 6C 74 |/TxSucss><Rcnclt|
0990 6E 49 64 3E 38 34 36 39 3C 2F 52 63 6E 63 6C 74 |nId>8469</Rcnclt|
09A0 6E 49 64 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 |nId><TxDtls><Ccy|
09B0 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D |>EUR</Ccy><TtlAm|
09C0 74 3E 34 33 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E |t>43.14</TtlAmt>|
09D0 3C 49 43 43 52 6C 74 64 44 61 74 61 3E 58 79 6F |<ICCRltdData>Xyo|
09E0 43 43 58 68 66 4E 41 45 41 67 67 4A 38 41 49 51 |CCXhfNAEAggJ8AIQ|
09F0 48 6F 41 41 41 41 41 6B 31 45 49 6F 43 4D 44 43 |HoAAAAAk1EIoCMDC|
0A00 52 43 6E 54 6C 4C 38 57 64 61 74 34 71 41 42 4B |RCnTlL8Wdat4qABK|
0A10 56 42 51 41 41 41 49 41 41 6D 67 4D 52 42 42 47 |VBQAAAIAAmgMRBBG|
0A20 63 41 51 43 66 41 67 59 41 41 41 41 41 51 78 53 |cAQCfAgYAAAAAQxS|
0A30 66 43 51 49 41 41 70 38 51 45 67 49 51 5A 34 41 |fCQIAAp8QEgIQZ4A|
0A40 44 42 41 41 41 6E 79 45 41 41 41 41 41 41 41 41 |DBAAAnyEAAAAAAAA|
0A50 41 2F 35 38 61 41 67 4A 51 6E 79 59 49 4B 61 4F |A/58aAgJQnyYIKaO|
0A60 38 49 4F 52 68 36 41 79 66 4A 77 46 41 6E 7A 4D |8IORh6AyfJwFAnzM|
0A70 44 59 4B 42 41 6E 7A 51 44 52 41 4D 43 6E 7A 55 |DYKBAnzQDRAMCnzU|
0A80 42 49 70 38 32 41 67 41 57 6E 7A 63 45 76 48 58 |BIp82AgAWnzcEvHX|
0A90 70 73 35 39 41 42 61 41 41 6B 50 41 42 6E 30 77 |ps59ABaAAkPABn0w|
0AA0 49 6E 79 47 77 4C 67 37 71 78 46 51 3D 3C 2F 49 |InyGwLg7qxFQ=</I|
0AB0 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F 54 78 44 |CCRltdData></TxD|
0AC0 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 6C 74 |tls><AuthstnRslt|
0AD0 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 54 |><AuthstnNtty><T|
0AE0 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 74 |p>CISS</Tp></Aut|
0AF0 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 6F |hstnNtty><RspnTo|
0B00 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 50 |Authstn><Rspn>AP|
0B10 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E 54 |PR</Rspn></RspnT|
0B20 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 74 |oAuthstn><Authst|
0B30 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 68 |nCd>032983</Auth|
0B40 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 6E 52 |stnCd></AuthstnR|
0B50 73 6C 74 3E 3C 54 78 56 72 66 63 74 6E 52 73 6C |slt><TxVrfctnRsl|
0B60 74 3E 3C 4D 74 64 3E 46 50 49 4E 3C 2F 4D 74 64 |t><Mtd>FPIN</Mtd|
0B70 3E 3C 56 72 66 63 74 6E 4E 74 74 79 3E 49 43 43 |><VrfctnNtty>ICC|
0B80 44 3C 2F 56 72 66 63 74 6E 4E 74 74 79 3E 3C 52 |D</VrfctnNtty><R|
0B90 73 6C 74 3E 53 55 43 43 3C 2F 52 73 6C 74 3E 3C |slt>SUCC</Rslt><|
0BA0 2F 54 78 56 72 66 63 74 6E 52 73 6C 74 3E 3C 2F |/TxVrfctnRslt></|
0BB0 54 78 3E 3C 2F 43 6D 70 6C 74 6E 41 64 76 63 3E |Tx></CmpltnAdvc>|

7 Messages Examples - 317 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

The SHA-256 digest of the message body CmpltnAdvc is:


0000 00 61 77 21 75 FB BF 63 BA 68 44 B4 47 57 BF 23 |.aw!u..c.hD.GW.#|
0010 1B 2F 6C E7 E3 3F 50 06 E2 EA F7 AF 3C F5 CE 01 |./l..?P.....<...|

After padding, the digest becomes:


0000 00 61 77 21 75 FB BF 63 BA 68 44 B4 47 57 BF 23 |.aw!u..c.hD.GW.#|
0010 1B 2F 6C E7 E3 3F 50 06 E2 EA F7 AF 3C F5 CE 01 |./l..?P.....<...|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (1391756B 68DF9DFE 977F10BF
AE4F250D), we obtain the MAC of the AcceptorCompletionAdvice AC6DF8942C3C4103A and after
conversion into base64 "rG34lCw8QQM=".
0000 7D 57 3F 30 71 B5 7C 29 4B 48 B6 71 73 80 51 E6 |}W?0q.|)KH.qs.Q.|
0010 AE 15 96 3E 16 46 58 DE 93 92 FC E6 B8 77 3A E1 |...>.FX......w:.|
0020 95 BB F1 A0 74 7D 91 7A |....t}.z |

The message sent by the transport protocol is:


0000 00 00 0F 0B 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 33 2E 30 30 31 2E 30 35 22 |caaa.003.001.05"|
00A0 3E 3C 41 63 63 70 74 72 43 6D 70 6C 74 6E 41 64 |><AccptrCmpltnAd|
00B0 76 63 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E |vc><Hdr><MsgFctn|
00C0 3E 46 43 4D 56 3C 2F 4D 73 67 46 63 74 6E 3E 3C |>FCMV</MsgFctn><|
00D0 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F |PrtcolVrsn>5.0</|
00E0 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 |PrtcolVrsn><Xchg|
00F0 49 64 3E 31 35 30 3C 2F 58 63 68 67 49 64 3E 3C |Id>150</XchgId><|
0100 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |CreDtTm>2013-08-|
0110 31 31 54 31 37 3A 32 32 3A 35 39 2E 33 35 2B 30 |11T17:22:59.35+0|
0120 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 |1:00</CreDtTm><I|
0130 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 |nitgPty><Id>6600|
0140 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F |0001</Id><Tp>OPO|
0150 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 |I</Tp><Issr>ACQR|
0160 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 |</Issr></InitgPt|
0170 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 |y><RcptPty><Id>e|
0180 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F |pas-acquirer-1</|
0190 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E |Id><Tp>ACQR</Tp>|
01A0 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E |</RcptPty></Hdr>|
01B0 3C 43 6D 70 6C 74 6E 41 64 76 63 3E 3C 45 6E 76 |<CmpltnAdvc><Env|
01C0 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|

7 Messages Examples - 318 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

01F0 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0200 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0210 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0220 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0230 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 |Id>EPASMER001</I|
0240 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 45 |d></Id><CmonNm>E|
0250 50 41 53 4F 72 67 20 4D 65 72 63 68 61 6E 74 20 |PASOrg Merchant |
0260 31 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 4C 63 74 6E 43 |1</CmonNm><LctnC|
0270 74 67 79 3E 46 49 58 44 3C 2F 4C 63 74 6E 43 74 |tgy>FIXD</LctnCt|
0280 67 79 3E 3C 4C 63 74 6E 41 6E 64 43 74 63 74 3E |gy><LctnAndCtct>|
0290 3C 50 73 74 6C 41 64 72 3E 3C 54 77 6E 4E 6D 3E |<PstlAdr><TwnNm>|
02A0 50 61 72 69 73 3C 2F 54 77 6E 4E 6D 3E 3C 43 74 |Paris</TwnNm><Ct|
02B0 72 79 3E 46 52 3C 2F 43 74 72 79 3E 3C 2F 50 73 |ry>FR</Ctry></Ps|
02C0 74 6C 41 64 72 3E 3C 2F 4C 63 74 6E 41 6E 64 43 |tlAdr></LctnAndC|
02D0 74 63 74 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F |tct></Mrchnt><PO|
02E0 49 3E 3C 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E |I><Id><Id>1</Id>|
02F0 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 |<Issr>ACQR</Issr|
0300 3E 3C 2F 49 64 3E 3C 53 79 73 4E 6D 3E 50 4F 49 |></Id><SysNm>POI|
0310 30 31 3C 2F 53 79 73 4E 6D 3E 3C 43 70 62 6C 74 |01</SysNm><Cpblt|
0320 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
0330 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 |lties>CICC</Card|
0340 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 |RdngCpblties><Ca|
0350 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D |rdRdngCpblties>M|
0360 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |GST</CardRdngCpb|
0370 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
0380 70 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 |pblties>PHYS</Ca|
0390 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
03A0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
03B0 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 |lties>MNSG</Crdh|
03C0 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
03D0 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
03E0 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 |Cpblties>FCPN</C|
03F0 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0400 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0410 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 4E |ctnCpblties>FEPN|
0420 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
0430 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
0440 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E |VrfctnCpblties>N|
0450 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |PIN</CrdhldrVrfc|
0460 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 |tnCpblties><OnLi|
0470 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C |neCpblties>SMON<|
0480 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E |/OnLineCpblties>|
0490 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
04A0 74 6E 3E 43 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E |tn>CDSP</Dstn><N|
04B0 62 4F 66 4C 69 6E 65 73 3E 32 3C 2F 4E 62 4F 66 |bOfLines>2</NbOf|
04C0 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 |Lines><LineWidth|
04D0 3E 32 30 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C |>20</LineWidth><|
04E0 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 |/MsgCpblties><Ms|
04F0 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E |gCpblties><Dstn>|
0500 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 |MDSP</Dstn><NbOf|
0510 4C 69 6E 65 73 3E 34 3C 2F 4E 62 4F 66 4C 69 6E |Lines>4</NbOfLin|
0520 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 34 30 |es><LineWidth>40|
0530 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 |</LineWidth></Ms|

7 Messages Examples - 319 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0540 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |gCpblties></Cpbl|
0550 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
0560 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 49 74 |TERM</Tp><Id><It|
0570 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E 3C 50 72 |mNb>1</ItmNb><Pr|
0580 76 64 72 49 64 3E 45 50 41 53 56 65 6E 64 6F 72 |vdrId>EPASVendor|
0590 30 30 31 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |001</PrvdrId><Id|
05A0 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 39 3C 2F |>SmartPOI-8539</|
05B0 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 35 34 31 |Id><SrlNb>782541|
05C0 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 |0759</SrlNb></Id|
05D0 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E |></Cmpnt><Cmpnt>|
05E0 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 |<Tp>APLI</Tp><Id|
05F0 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 |><ItmNb>1</ItmNb|
0600 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 |><PrvdrId>EPASVe|
0610 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 |ndor001</PrvdrId|
0620 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
0630 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E 62 3E 3C |Nb>1.0</VrsnNb><|
0640 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|
0650 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
0660 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 72 73 6E |><Vrsn>3.0</Vrsn|
0670 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 73 73 72 |><Issr>CIR</Issr|
0680 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 2F 43 6D |></StdCmplc></Cm|
0690 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |pnt></POI><Card>|
06A0 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 61 3E |<PrtctdCardData>|
06B0 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E |<CnttTp>EVLP</Cn|
06C0 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 |ttTp><EnvlpdData|
06D0 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B |><Rcpt><KEK><KEK|
06E0 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 |Id><KeyId>SpecV1|
06F0 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C |TestKey</KeyId><|
0700 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 |KeyVrsn>20100607|
0710 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 |15</KeyVrsn><Der|
0720 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C |ivtnId>OYclpQE=<|
0730 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B |/DerivtnId></KEK|
0740 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 |Id><KeyNcrptnAlg|
0750 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C |o><Algo>DKP9</Al|
0760 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C |go></KeyNcrptnAl|
0770 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 |go><NcrptdKey>4p|
0780 41 67 41 42 67 3D 3C 2F 4E 63 72 70 74 64 4B 65 |AgABg=</NcrptdKe|
0790 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C |y></KEK></Rcpt><|
07A0 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 |NcrptdCntt><Cntt|
07B0 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E |Tp>DATA</CnttTp>|
07C0 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E |<CnttNcrptnAlgo>|
07D0 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F |<Algo>E3DC</Algo|
07E0 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 |><Param><Initlst|
07F0 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 |nVctr>onu0bRwwbg|
0800 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 |k=</InitlstnVctr|
0810 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E |></Param></CnttN|
0820 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 |crptnAlgo><Ncrpt|
0830 64 44 61 74 61 3E 64 68 67 31 58 45 43 32 6F 6C |dData>dhg1XEC2ol|
0840 7A 56 48 6C 68 64 5A 6F 36 33 33 42 54 35 4D 74 |zVHlhdZo633BT5Mt|
0850 6E 50 67 64 7A 43 59 32 48 53 49 43 51 76 55 75 |nPgdzCY2HSICQvUu|
0860 6E 46 5A 59 31 36 64 32 2F 69 64 33 67 6D 65 6D |nFZY16d2/id3gmem|
0870 78 39 2B 30 78 48 50 57 4F 54 66 6A 70 71 61 73 |x9+0xHPWOTfjpqas|
0880 66 66 67 54 70 72 31 2F 79 30 48 57 48 39 34 67 |ffgTpr1/y0HWH94g|

7 Messages Examples - 320 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0890 30 36 76 6B 2F 42 70 2B 6D 59 6A 35 72 7A 76 56 |06vk/Bp+mYj5rzvV|
08A0 6E 4F 78 76 44 36 52 58 64 34 54 6D 2B 77 30 6E |nOxvD6RXd4Tm+w0n|
08B0 66 6D 4B 70 45 67 63 65 77 65 47 61 56 45 53 4B |fmKpEgceweGaVESK|
08C0 69 75 75 36 6A 36 58 37 42 49 72 77 3D 3D 3C 2F |iuu6j6X7BIrw==</|
08D0 4E 63 72 70 74 64 44 61 74 61 3E 3C 2F 4E 63 72 |NcrptdData></Ncr|
08E0 70 74 64 43 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 |ptdCntt></Envlpd|
08F0 44 61 74 61 3E 3C 2F 50 72 74 63 74 64 43 61 72 |Data></PrtctdCar|
0900 64 44 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 |dData><CardCtryC|
0910 64 3E 30 35 36 3C 2F 43 61 72 64 43 74 72 79 43 |d>056</CardCtryC|
0920 64 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |d><CardPdctPrfl>|
0930 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 |0003</CardPdctPr|
0940 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 54 65 73 |fl><CardBrnd>Tes|
0950 74 43 61 72 64 3C 2F 43 61 72 64 42 72 6E 64 3E |tCard</CardBrnd>|
0960 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 |</Card></Envt><C|
0970 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
0980 43 61 72 64 50 72 65 73 3E 74 72 75 65 3C 2F 43 |CardPres>true</C|
0990 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C 64 72 |ardPres><Crdhldr|
09A0 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C |Pres>true</Crdhl|
09B0 64 72 50 72 65 73 3E 3C 41 74 74 6E 64 6E 63 43 |drPres><AttndncC|
09C0 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
09D0 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 |ncCntxt><CardDat|
09E0 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 |aNtryMd>CICC</Ca|
09F0 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 |rdDataNtryMd></P|
0A00 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 |mtCntxt><SaleCnt|
0A10 78 74 3E 3C 53 61 6C 65 49 64 3E 53 54 30 36 3C |xt><SaleId>ST06<|
0A20 2F 53 61 6C 65 49 64 3E 3C 53 61 6C 65 52 65 66 |/SaleId><SaleRef|
0A30 4E 62 3E 53 37 38 2D 54 30 36 2D 30 30 32 39 3C |Nb>S78-T06-0029<|
0A40 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 53 61 6C 65 |/SaleRefNb><Sale|
0A50 52 63 6E 63 6C 74 6E 49 64 3E 53 37 38 2D 38 34 |RcncltnId>S78-84|
0A60 36 39 3C 2F 53 61 6C 65 52 63 6E 63 6C 74 6E 49 |69</SaleRcncltnI|
0A70 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F |d></SaleCntxt></|
0A80 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 43 61 70 |Cntxt><Tx><TxCap|
0A90 74 72 3E 74 72 75 65 3C 2F 54 78 43 61 70 74 72 |tr>true</TxCaptr|
0AA0 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 78 54 |><TxTp>CRDP</TxT|
0AB0 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 3E |p><MrchntCtgyCd>|
0AC0 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 74 67 79 |5411</MrchntCtgy|
0AD0 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Cd><TxId><TxDtTm|
0AE0 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 37 3A 32 |>2013-08-11T17:2|
0AF0 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 3C 2F 54 |2:04.51+01:00</T|
0B00 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 32 |xDtTm><TxRef>002|
0B10 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 |949</TxRef></TxI|
0B20 64 3E 3C 54 78 53 75 63 73 73 3E 74 72 75 65 3C |d><TxSucss>true<|
0B30 2F 54 78 53 75 63 73 73 3E 3C 52 63 6E 63 6C 74 |/TxSucss><Rcnclt|
0B40 6E 49 64 3E 38 34 36 39 3C 2F 52 63 6E 63 6C 74 |nId>8469</Rcnclt|
0B50 6E 49 64 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 |nId><TxDtls><Ccy|
0B60 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D |>EUR</Ccy><TtlAm|
0B70 74 3E 34 33 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E |t>43.14</TtlAmt>|
0B80 3C 49 43 43 52 6C 74 64 44 61 74 61 3E 58 79 6F |<ICCRltdData>Xyo|
0B90 43 43 58 68 66 4E 41 45 41 67 67 4A 38 41 49 51 |CCXhfNAEAggJ8AIQ|
0BA0 48 6F 41 41 41 41 41 6B 31 45 49 6F 43 4D 44 43 |HoAAAAAk1EIoCMDC|
0BB0 52 43 6E 54 6C 4C 38 57 64 61 74 34 71 41 42 4B |RCnTlL8Wdat4qABK|
0BC0 56 42 51 41 41 41 49 41 41 6D 67 4D 52 42 42 47 |VBQAAAIAAmgMRBBG|
0BD0 63 41 51 43 66 41 67 59 41 41 41 41 41 51 78 53 |cAQCfAgYAAAAAQxS|

7 Messages Examples - 321 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0BE0 66 43 51 49 41 41 70 38 51 45 67 49 51 5A 34 41 |fCQIAAp8QEgIQZ4A|
0BF0 44 42 41 41 41 6E 79 45 41 41 41 41 41 41 41 41 |DBAAAnyEAAAAAAAA|
0C00 41 2F 35 38 61 41 67 4A 51 6E 79 59 49 4B 61 4F |A/58aAgJQnyYIKaO|
0C10 38 49 4F 52 68 36 41 79 66 4A 77 46 41 6E 7A 4D |8IORh6AyfJwFAnzM|
0C20 44 59 4B 42 41 6E 7A 51 44 52 41 4D 43 6E 7A 55 |DYKBAnzQDRAMCnzU|
0C30 42 49 70 38 32 41 67 41 57 6E 7A 63 45 76 48 58 |BIp82AgAWnzcEvHX|
0C40 70 73 35 39 41 42 61 41 41 6B 50 41 42 6E 30 77 |ps59ABaAAkPABn0w|
0C50 49 6E 79 47 77 4C 67 37 71 78 46 51 3D 3C 2F 49 |InyGwLg7qxFQ=</I|
0C60 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F 54 78 44 |CCRltdData></TxD|
0C70 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 6C 74 |tls><AuthstnRslt|
0C80 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 54 |><AuthstnNtty><T|
0C90 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 74 |p>CISS</Tp></Aut|
0CA0 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 6F |hstnNtty><RspnTo|
0CB0 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 50 |Authstn><Rspn>AP|
0CC0 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E 54 |PR</Rspn></RspnT|
0CD0 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 74 |oAuthstn><Authst|
0CE0 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 68 |nCd>032983</Auth|
0CF0 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 6E 52 |stnCd></AuthstnR|
0D00 73 6C 74 3E 3C 54 78 56 72 66 63 74 6E 52 73 6C |slt><TxVrfctnRsl|
0D10 74 3E 3C 4D 74 64 3E 46 50 49 4E 3C 2F 4D 74 64 |t><Mtd>FPIN</Mtd|
0D20 3E 3C 56 72 66 63 74 6E 4E 74 74 79 3E 49 43 43 |><VrfctnNtty>ICC|
0D30 44 3C 2F 56 72 66 63 74 6E 4E 74 74 79 3E 3C 52 |D</VrfctnNtty><R|
0D40 73 6C 74 3E 53 55 43 43 3C 2F 52 73 6C 74 3E 3C |slt>SUCC</Rslt><|
0D50 2F 54 78 56 72 66 63 74 6E 52 73 6C 74 3E 3C 2F |/TxVrfctnRslt></|
0D60 54 78 3E 3C 2F 43 6D 70 6C 74 6E 41 64 76 63 3E |Tx></CmpltnAdvc>|
0D70 3C 53 63 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 |<SctyTrlr><CnttT|
0D80 70 3E 41 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C |p>AUTH</CnttTp><|
0D90 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 |AuthntcdData><Rc|
0DA0 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C |pt><KEK><KEKId><|
0DB0 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 |KeyId>SpecV1Test|
0DC0 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 |Key</KeyId><KeyV|
0DD0 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F |rsn>2010060715</|
0DE0 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E |KeyVrsn><Derivtn|
0DF0 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 |Id>OYclpQE=</Der|
0E00 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C |ivtnId></KEKId><|
0E10 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |KeyNcrptnAlgo><A|
0E20 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C |lgo>DKP9</Algo><|
0E30 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |/KeyNcrptnAlgo><|
0E40 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 |NcrptdKey>4pAgAB|
0E50 67 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F |g=</NcrptdKey></|
0E60 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 |KEK></Rcpt><MACA|
0E70 6C 67 6F 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F |lgo><Algo>MCCS</|
0E80 41 6C 67 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C |Algo></MACAlgo><|
0E90 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 |NcpsltdCntt><Cnt|
0EA0 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 |tTp>DATA</CnttTp|
0EB0 3E 3C 2F 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C |></NcpsltdCntt><|
0EC0 4D 41 43 3E 72 47 33 34 6C 43 77 38 51 51 4D 3D |MAC>rG34lCw8QQM=|
0ED0 3C 2F 4D 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 |</MAC></Authntcd|
0EE0 44 61 74 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E |Data></SctyTrlr>|
0EF0 3C 2F 41 63 63 70 74 72 43 6D 70 6C 74 6E 41 64 |</AccptrCmpltnAd|
0F00 76 63 3E 3C 2F 44 6F 63 75 6D 65 6E 74 3E 20 |vc></Document> |
0ED0 75 6D 65 6E 74 3E |ument> |

7 Messages Examples - 322 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

7 Messages Examples - 323 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

7.3.2 AcceptorCompletionAdviceResponse

The data capture of the transaction has been successfully performed by the Acquirer.

Message Item Value


Transaction
TransactionIdentification
TransactionDateTime 2013-08-11T17:22:04.51+01:00
TransactionReference 002949
Response Approved

The resulting XML encoded structure is:


<Tx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<Rspn>APPR</Rspn>
</Tx>

7 Messages Examples - 324 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorCompletionAdviceResponse is presented below, omitting data structure


already previously detailed.

Message Item Value


AcceptorCompletionAdviceResponse
Header
MessageFunction FinancialCompletionAdviceResponse
ProtocolVersion 2.0
ExchangeIdentifier 150
CreationDateTime 2013-08-11T17:22:59.81+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
CompletionAdviceResponse
Environment
AcquirerIdentification
Identification 9287351
Type Acquirer
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 1
Issuer Acquirer
ProtectedCardData
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200018
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC 5CB0752CE3E8922D
---

7 Messages Examples - 325 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorCompletionAdviceResponse XML message is presented below:


<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.004.001.05">
<AccptrCmpltnAdvcRspn>
<Hdr>
<MsgFctn>FCMK</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>150</XchgId>
<CreDtTm>2013-08-11T17:22:59.81+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<CmpltnAdvcRspn>
<Envt>
<AcqrrId>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</AcqrrId>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>1</Id>
<Issr>ACQR</Issr>
</POIId>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
pRVcmC94QFPyUVnMIUNMBDnTTCrI/4goKD1Bt/DsT7SC+vp2
PuHNjtF7VCXVtHOwfLafH4UhK86y5bKpD3h0O0q3DMGrmC2T
qbluzNewyMtReZT+xsV/Z2DA1ZKqYzSLgpnktWj4BEzaXZw5
G819yw==

7 Messages Examples - 326 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

</NcrptdData>
</NcrptdCntt>
</EnvlpdData>
</PrtctdCardData>
</Card>
</Envt>
<Tx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<Rspn>APPR</Rspn>
</Tx>
</CmpltnAdvcRspn>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABg=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>XLB1LOPoki0=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrCmpltnAdvcRspn>
</Document>

Once unnecessary spaces and carriage returns are removed, the message body CmpltnAdvcRspn
(without spaces or line breaks) is dumped below:
0000 3C 43 6D 70 6C 74 6E 41 64 76 63 52 73 70 6E 3E |<CmpltnAdvcRspn>|
0010 3C 45 6E 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C |<Envt><AcqrrId><|
0020 49 64 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C |Id>9287351</Id><|
0030 54 70 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 |Tp>ACQR</Tp></Ac|
0040 71 72 72 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E |qrrId><MrchntId>|
0050 3C 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F |<Id>EPASMER001</|
0060 49 64 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 |Id></MrchntId><P|
0070 4F 49 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C |OIId><Id>1</Id><|
0080 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E |Issr>ACQR</Issr>|
0090 3C 2F 50 4F 49 49 64 3E 3C 43 61 72 64 3E 3C 50 |</POIId><Card><P|
00A0 72 74 63 74 64 43 61 72 64 44 61 74 61 3E 3C 43 |rtctdCardData><C|
00B0 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E 74 74 |nttTp>EVLP</Cntt|
00C0 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 3E 3C |Tp><EnvlpdData><|
00D0 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 |Rcpt><KEK><KEKId|
00E0 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 |><KeyId>SpecV1Te|
00F0 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 |stKey</KeyId><Ke|

7 Messages Examples - 327 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0100 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 |yVrsn>2010060715|
0110 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 |</KeyVrsn><Deriv|
0120 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 |tnId>OYclpQE=</D|
0130 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 |erivtnId></KEKId|
0140 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E |><KeyNcrptnAlgo>|
0150 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F |<Algo>DKP9</Algo|
0160 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F |></KeyNcrptnAlgo|
0170 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 |><NcrptdKey>4pAg|
0180 41 42 67 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E |ABg=</NcrptdKey>|
0190 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4E 63 |</KEK></Rcpt><Nc|
01A0 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 |rptdCntt><CnttTp|
01B0 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 43 |>DATA</CnttTp><C|
01C0 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |nttNcrptnAlgo><A|
01D0 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F 3E 3C |lgo>E3DC</Algo><|
01E0 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 6E 56 |Param><InitlstnV|
01F0 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 6B 3D |ctr>onu0bRwwbgk=|
0200 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 3E 3C |</InitlstnVctr><|
0210 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E 63 72 |/Param></CnttNcr|
0220 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 44 |ptnAlgo><NcrptdD|
0230 61 74 61 3E 70 52 56 63 6D 43 39 34 51 46 50 79 |ata>pRVcmC94QFPy|
0240 55 56 6E 4D 49 55 4E 4D 42 44 6E 54 54 43 72 49 |UVnMIUNMBDnTTCrI|
0250 2F 34 67 6F 4B 44 31 42 74 2F 44 73 54 37 53 43 |/4goKD1Bt/DsT7SC|
0260 2B 76 70 32 50 75 48 4E 6A 74 46 37 56 43 58 56 |+vp2PuHNjtF7VCXV|
0270 74 48 4F 77 66 4C 61 66 48 34 55 68 4B 38 36 79 |tHOwfLafH4UhK86y|
0280 35 62 4B 70 44 33 68 30 4F 30 71 33 44 4D 47 72 |5bKpD3h0O0q3DMGr|
0290 6D 43 32 54 71 62 6C 75 7A 4E 65 77 79 4D 74 52 |mC2TqbluzNewyMtR|
02A0 65 5A 54 2B 78 73 56 2F 5A 32 44 41 31 5A 4B 71 |eZT+xsV/Z2DA1ZKq|
02B0 59 7A 53 4C 67 70 6E 6B 74 57 6A 34 42 45 7A 61 |YzSLgpnktWj4BEza|
02C0 58 5A 77 35 47 38 31 39 79 77 3D 3D 3C 2F 4E 63 |XZw5G819yw==</Nc|
02D0 72 70 74 64 44 61 74 61 3E 3C 2F 4E 63 72 70 74 |rptdData></Ncrpt|
02E0 64 43 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 44 61 |dCntt></EnvlpdDa|
02F0 74 61 3E 3C 2F 50 72 74 63 74 64 43 61 72 64 44 |ta></PrtctdCardD|
0300 61 74 61 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 |ata></Card></Env|
0310 74 3E 3C 54 78 3E 3C 54 78 49 64 3E 3C 54 78 44 |t><Tx><TxId><TxD|
0320 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 |tTm>2013-08-11T1|
0330 37 3A 32 32 3A 30 34 2E 35 31 2B 30 31 3A 30 30 |7:22:04.51+01:00|
0340 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|
0350 30 30 32 39 34 39 3C 2F 54 78 52 65 66 3E 3C 2F |002949</TxRef></|
0360 54 78 49 64 3E 3C 52 73 70 6E 3E 41 50 50 52 3C |TxId><Rspn>APPR<|
0370 2F 52 73 70 6E 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 |/Rspn></Tx></Cmp|
0380 6C 74 6E 41 64 76 63 52 73 70 6E 3E |ltnAdvcRspn> |

The SHA-256 digest of the message body CmpltnAdvcRspn is:


0000 66 94 6E 87 B1 36 90 BE 22 BD 79 90 88 7C 67 58 |f.n..6..".y..|gX|
0010 34 13 21 F6 AE C2 5F B1 54 3B 36 D4 B8 AE 6D D8 |4.!..._.T;6...m.|

7 Messages Examples - 328 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

After padding, the digest becomes:


000 66 94 6E 87 B1 36 90 BE 22 BD 79 90 88 7C 67 58 |f.n..6..".y..|gX|
0010 34 13 21 F6 AE C2 5F B1 54 3B 36 D4 B8 AE 6D D8 |4.!..._.T;6...m.|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (1391756B 97DF62FE 977F10BF
514FDA0D), we obtain the MAC of the AcceptorCompletionAdviceResponse 5CB0752CE3E8922D
and after conversion into base64 "XLB1LOPoki0=".
0000 66 48 D0 27 47 31 12 8B EB BE 56 FE 84 BB BA BA |fH.'G1....V.....|
0010 70 E0 9A DF A0 86 30 F7 CC DF 1F 5D 90 8A 68 DA |p.....0....]..h.|
0020 BC 2C E6 B2 4F 6D C5 6E |.,..Om.n |

The message sent by the transport protocol is:


0000 00 00 06 DE 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 34 2E 30 30 31 2E 30 35 22 |caaa.004.001.05"|
00A0 3E 3C 41 63 63 70 74 72 43 6D 70 6C 74 6E 41 64 |><AccptrCmpltnAd|
00B0 76 63 52 73 70 6E 3E 3C 48 64 72 3E 3C 4D 73 67 |vcRspn><Hdr><Msg|
00C0 46 63 74 6E 3E 46 43 4D 4B 3C 2F 4D 73 67 46 63 |Fctn>FCMK</MsgFc|
00D0 74 6E 3E 3C 50 72 74 63 6F 6C 56 72 73 6E 3E 35 |tn><PrtcolVrsn>5|
00E0 2E 30 3C 2F 50 72 74 63 6F 6C 56 72 73 6E 3E 3C |.0</PrtcolVrsn><|
00F0 58 63 68 67 49 64 3E 31 35 30 3C 2F 58 63 68 67 |XchgId>150</Xchg|
0100 49 64 3E 3C 43 72 65 44 74 54 6D 3E 32 30 31 33 |Id><CreDtTm>2013|
0110 2D 30 38 2D 31 31 54 31 37 3A 32 32 3A 35 39 2E |-08-11T17:22:59.|
0120 38 31 2B 30 31 3A 30 30 3C 2F 43 72 65 44 74 54 |81+01:00</CreDtT|
0130 6D 3E 3C 49 6E 69 74 67 50 74 79 3E 3C 49 64 3E |m><InitgPty><Id>|
0140 36 36 30 30 30 30 30 31 3C 2F 49 64 3E 3C 54 70 |66000001</Id><Tp|
0150 3E 4F 50 4F 49 3C 2F 54 70 3E 3C 49 73 73 72 3E |>OPOI</Tp><Issr>|
0160 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 |ACQR</Issr></Ini|
0170 74 67 50 74 79 3E 3C 52 63 70 74 50 74 79 3E 3C |tgPty><RcptPty><|
0180 49 64 3E 65 70 61 73 2D 61 63 71 75 69 72 65 72 |Id>epas-acquirer|
0190 2D 31 3C 2F 49 64 3E 3C 54 70 3E 41 43 51 52 3C |-1</Id><Tp>ACQR<|
01A0 2F 54 70 3E 3C 2F 52 63 70 74 50 74 79 3E 3C 2F |/Tp></RcptPty></|
01B0 48 64 72 3E 3C 43 6D 70 6C 74 6E 41 64 76 63 52 |Hdr><CmpltnAdvcR|
01C0 73 70 6E 3E 3C 45 6E 76 74 3E 3C 41 63 71 72 72 |spn><Envt><Acqrr|
01D0 49 64 3E 3C 49 64 3E 39 32 38 37 33 35 31 3C 2F |Id><Id>9287351</|
01E0 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E |Id><Tp>ACQR</Tp>|
01F0 3C 2F 41 63 71 72 72 49 64 3E 3C 4D 72 63 68 6E |</AcqrrId><Mrchn|
0200 74 49 64 3E 3C 49 64 3E 45 50 41 53 4D 45 52 30 |tId><Id>EPASMER0|
0210 30 31 3C 2F 49 64 3E 3C 2F 4D 72 63 68 6E 74 49 |01</Id></MrchntI|
0220 64 3E 3C 50 4F 49 49 64 3E 3C 49 64 3E 31 3C 2F |d><POIId><Id>1</|
0230 49 64 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 |Id><Issr>ACQR</I|

7 Messages Examples - 329 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0240 73 73 72 3E 3C 2F 50 4F 49 49 64 3E 3C 43 61 72 |ssr></POIId><Car|
0250 64 3E 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 |d><PrtctdCardDat|
0260 61 3E 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F |a><CnttTp>EVLP</|
0270 43 6E 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 |CnttTp><EnvlpdDa|
0280 74 61 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B |ta><Rcpt><KEK><K|
0290 45 4B 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 |EKId><KeyId>Spec|
02A0 56 31 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 |V1TestKey</KeyId|
02B0 3E 3C 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 |><KeyVrsn>201006|
02C0 30 37 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 |0715</KeyVrsn><D|
02D0 65 72 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 |erivtnId>OYclpQE|
02E0 3D 3C 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B |=</DerivtnId></K|
02F0 45 4B 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 |EKId><KeyNcrptnA|
0300 6C 67 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F |lgo><Algo>DKP9</|
0310 41 6C 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E |Algo></KeyNcrptn|
0320 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E |Algo><NcrptdKey>|
0330 34 70 41 67 41 42 67 3D 3C 2F 4E 63 72 70 74 64 |4pAgABg=</Ncrptd|
0340 4B 65 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 |Key></KEK></Rcpt|
0350 3E 3C 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E |><NcrptdCntt><Cn|
0360 74 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 |ttTp>DATA</CnttT|
0370 70 3E 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 |p><CnttNcrptnAlg|
0380 6F 3E 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C |o><Algo>E3DC</Al|
0390 67 6F 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C |go><Param><Initl|
03A0 73 74 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 |stnVctr>onu0bRww|
03B0 62 67 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 |bgk=</InitlstnVc|
03C0 74 72 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 |tr></Param></Cnt|
03D0 74 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 |tNcrptnAlgo><Ncr|
03E0 70 74 64 44 61 74 61 3E 70 52 56 63 6D 43 39 34 |ptdData>pRVcmC94|
03F0 51 46 50 79 55 56 6E 4D 49 55 4E 4D 42 44 6E 54 |QFPyUVnMIUNMBDnT|
0400 54 43 72 49 2F 34 67 6F 4B 44 31 42 74 2F 44 73 |TCrI/4goKD1Bt/Ds|
0410 54 37 53 43 2B 76 70 32 50 75 48 4E 6A 74 46 37 |T7SC+vp2PuHNjtF7|
0420 56 43 58 56 74 48 4F 77 66 4C 61 66 48 34 55 68 |VCXVtHOwfLafH4Uh|
0430 4B 38 36 79 35 62 4B 70 44 33 68 30 4F 30 71 33 |K86y5bKpD3h0O0q3|
0440 44 4D 47 72 6D 43 32 54 71 62 6C 75 7A 4E 65 77 |DMGrmC2TqbluzNew|
0450 79 4D 74 52 65 5A 54 2B 78 73 56 2F 5A 32 44 41 |yMtReZT+xsV/Z2DA|
0460 31 5A 4B 71 59 7A 53 4C 67 70 6E 6B 74 57 6A 34 |1ZKqYzSLgpnktWj4|
0470 42 45 7A 61 58 5A 77 35 47 38 31 39 79 77 3D 3D |BEzaXZw5G819yw==|
0480 3C 2F 4E 63 72 70 74 64 44 61 74 61 3E 3C 2F 4E |</NcrptdData></N|
0490 63 72 70 74 64 43 6E 74 74 3E 3C 2F 45 6E 76 6C |crptdCntt></Envl|
04A0 70 64 44 61 74 61 3E 3C 2F 50 72 74 63 74 64 43 |pdData></PrtctdC|
04B0 61 72 64 44 61 74 61 3E 3C 2F 43 61 72 64 3E 3C |ardData></Card><|
04C0 2F 45 6E 76 74 3E 3C 54 78 3E 3C 54 78 49 64 3E |/Envt><Tx><TxId>|
04D0 3C 54 78 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |<TxDtTm>2013-08-|
04E0 31 31 54 31 37 3A 32 32 3A 30 34 2E 35 31 2B 30 |11T17:22:04.51+0|
04F0 31 3A 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 |1:00</TxDtTm><Tx|
0500 52 65 66 3E 30 30 32 39 34 39 3C 2F 54 78 52 65 |Ref>002949</TxRe|
0510 66 3E 3C 2F 54 78 49 64 3E 3C 52 73 70 6E 3E 41 |f></TxId><Rspn>A|
0520 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 54 78 3E 3C |PPR</Rspn></Tx><|
0530 2F 43 6D 70 6C 74 6E 41 64 76 63 52 73 70 6E 3E |/CmpltnAdvcRspn>|
0540 3C 53 63 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 |<SctyTrlr><CnttT|
0550 70 3E 41 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C |p>AUTH</CnttTp><|
0560 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 |AuthntcdData><Rc|
0570 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C |pt><KEK><KEKId><|
0580 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 |KeyId>SpecV1Test|

7 Messages Examples - 330 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

0590 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 |Key</KeyId><KeyV|
05A0 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F |rsn>2010060715</|
05B0 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E |KeyVrsn><Derivtn|
05C0 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 |Id>OYclpQE=</Der|
05D0 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C |ivtnId></KEKId><|
05E0 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |KeyNcrptnAlgo><A|
05F0 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C |lgo>DKP9</Algo><|
0600 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |/KeyNcrptnAlgo><|
0610 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 |NcrptdKey>4pAgAB|
0620 67 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F |g=</NcrptdKey></|
0630 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 |KEK></Rcpt><MACA|
0640 6C 67 6F 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F |lgo><Algo>MCCS</|
0650 41 6C 67 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C |Algo></MACAlgo><|
0660 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 |NcpsltdCntt><Cnt|
0670 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 |tTp>DATA</CnttTp|
0680 3E 3C 2F 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C |></NcpsltdCntt><|
0690 4D 41 43 3E 58 4C 42 31 4C 4F 50 6F 6B 69 30 3D |MAC>XLB1LOPoki0=|
06A0 3C 2F 4D 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 |</MAC></Authntcd|
06B0 44 61 74 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E |Data></SctyTrlr>|
06C0 3C 2F 41 63 63 70 74 72 43 6D 70 6C 74 6E 41 64 |</AccptrCmpltnAd|
06D0 76 63 52 73 70 6E 3E 3C 2F 44 6F 63 75 6D 65 6E |vcRspn></Documen|
06E0 74 3E |t> |

7 Messages Examples - 331 - 7.3 Completion Messages


Card Payments Message Usage Guide Version 5.0

7.4 Cancellation Messages

7.4.1 AcceptorCancellationAdvice

The Acceptor has cancelled the transaction before the reconciliation. A notification is sent to the
Acquirer.

Message Item Value


Transaction
MerchantCategoryCode 5411
TransactionIdentification
TransactionDateTime 2013-08-11T18:34:19.00+01:00
TransactionReference 002950
OriginalTransaction
TransactionIdentification
TransactionDateTime 2013-08-11T17:45:04.51+01:00
TransactionReference 002949
TransactionType CardPayment
TransactionResult
AuthorisationEntity
Type CardIssuer
ResponseToAuthorisation
Response Approved
AuthorisationCode 032983
TransactionSucess True
ReconciliationIdentification 8469
TransactionDetails
Currency EUR
TotalAmount 43.14

The resulting XML encoded structure is:


<Tx>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T18:34:19.00+01:00</TxDtTm>
<TxRef>002950</TxRef>
</TxId>
<OrgnlTx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxTp>CRDP</TxTp>
<TxRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</TxRslt>
</OrgnlTx>
<TxSucss>true</TxSucss>

7 Messages Examples - 332 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
</TxDtls>
</Tx>

7 Messages Examples - 333 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorCancellationAdvice is presented below, without data structure already


described.

Message Item Value


AcceptorCancellationAdvice
Header
MessageFunction CancellationAdvice
ProtocolVersion 5.0
ExchangeIdentifier 151
CreationDateTime 2013-08-11T18:34:44.00+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
CancellationAdvice
Environment
Acquirer
---
Merchant
---
POI
---
Card
---
CardHolder
---
Context
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
398725A501
DerivationIdentification

KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200019
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent

7 Messages Examples - 334 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

ContentType PlainData
MAC FE33AA8DBACBA809
---

The AcceptorCancellationAdvice XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.007.001.05">
<AccptrCxlAdvc>
<Hdr>
<MsgFctn>CCAV</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>151</XchgId>
<CreDtTm>2013-08-11T18:34:44.00+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<CxlAdvc>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>EPASMER001</Id>
</Id>
<CmonNm>EPASOrg Merchant 1</CmonNm>
<LctnCtgy>FIXD</LctnCtgy>
<LctnAndCtct>
<PstlAdr>
<TwnNm>Paris</TwnNm>
<Ctry>FR</Ctry>
</PstlAdr>
</LctnAndCtct>
</Mrchnt>
<POI>
<Id>
<Id>1</Id>
<Issr>ACQR</Issr>
</Id>
<SysNm>POI01</SysNm>
<Cpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
</Cpblties>

7 Messages Examples - 335 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

<Cmpnt>
<Tp>TERM</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
<Id>SmartPOI-8539</Id>
<SrlNb>7825410759</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<ItmNb>1</ItmNb>
<PrvdrId>EPASVendor001</PrvdrId>
</Id>
<Sts>
<VrsnNb>1.0</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.0</Vrsn>
<Issr>CIR</Issr>
</StdCmplc>
</Cmpnt>
</POI>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
XGPHcvxnMG2V/586YcjX73/lsiSul3UYgAhL7YseefIjZPQ0
83T2QPFxa4Uc3Vfgw1RqrOf8C6+7/r/UuT3HByDoIeANdNcz
FNOSeGsec1RpT6fLDcl8JxYju0bfC8PFLwJIwFyp8aLZW9p3
1Y80kg==
</NcrptdData>
</NcrptdCntt>
</EnvlpdData>
</PrtctdCardData>
<CardCtryCd>056</CardCtryCd>
<CardPdctPrfl>0003</CardPdctPrfl>
<CardBrnd>TestCard</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>

7 Messages Examples - 336 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleId>ST06</SaleId>
<SaleRefNb>S78-T06-0029</SaleRefNb>
<SaleRcncltnId>S78-8469</SaleRcncltnId>
</SaleCntxt>
</Cntxt>
<Tx>
<MrchntCtgyCd>5411</MrchntCtgyCd>
<TxId>
<TxDtTm>2013-08-11T18:34:19.00+01:00</TxDtTm>
<TxRef>002950</TxRef>
</TxId>
<OrgnlTx>
<TxId>
<TxDtTm>2013-08-11T17:22:04.51+01:00</TxDtTm>
<TxRef>002949</TxRef>
</TxId>
<TxTp>CRDP</TxTp>
<TxRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</TxRslt>
</OrgnlTx>
<TxSucss>true</TxSucss>
<RcncltnId>8469</RcncltnId>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>43.14</TtlAmt>
</TxDtls>
</Tx>
</CxlAdvc>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>/jOqjbrLqAk=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrCxlAdvc>
</Document>

7 Messages Examples - 337 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body CxlAdvc (without
spaces or line breaks) is dumped below:
0000 3C 43 78 6C 41 64 76 63 3E 3C 45 6E 76 74 3E 3C |<CxlAdvc><Envt><|
0010 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 39 32 |Acqrr><Id><Id>92|
0020 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 3E 41 43 |87351</Id><Tp>AC|
0030 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C 50 61 72 |QR</Tp></Id><Par|
0040 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D 30 38 2D |amsVrsn>2013-08-|
0050 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F 50 61 72 |07 08:00:00</Par|
0060 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 72 72 3E |amsVrsn></Acqrr>|
0070 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E |<Mrchnt><Id><Id>|
0080 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E 3C |EPASMER001</Id><|
0090 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 45 50 41 53 |/Id><CmonNm>EPAS|
00A0 4F 72 67 20 4D 65 72 63 68 61 6E 74 20 31 3C 2F |Org Merchant 1</|
00B0 43 6D 6F 6E 4E 6D 3E 3C 4C 63 74 6E 43 74 67 79 |CmonNm><LctnCtgy|
00C0 3E 46 49 58 44 3C 2F 4C 63 74 6E 43 74 67 79 3E |>FIXD</LctnCtgy>|
00D0 3C 4C 63 74 6E 41 6E 64 43 74 63 74 3E 3C 50 73 |<LctnAndCtct><Ps|
00E0 74 6C 41 64 72 3E 3C 54 77 6E 4E 6D 3E 50 61 72 |tlAdr><TwnNm>Par|
00F0 69 73 3C 2F 54 77 6E 4E 6D 3E 3C 43 74 72 79 3E |is</TwnNm><Ctry>|
0100 46 52 3C 2F 43 74 72 79 3E 3C 2F 50 73 74 6C 41 |FR</Ctry></PstlA|
0110 64 72 3E 3C 2F 4C 63 74 6E 41 6E 64 43 74 63 74 |dr></LctnAndCtct|
0120 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C |></Mrchnt><POI><|
0130 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 |Id><Id>1</Id><Is|
0140 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F |sr>ACQR</Issr></|
0150 49 64 3E 3C 53 79 73 4E 6D 3E 50 4F 49 30 31 3C |Id><SysNm>POI01<|
0160 2F 53 79 73 4E 6D 3E 3C 43 70 62 6C 74 69 65 73 |/SysNm><Cpblties|
0170 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |><CardRdngCpblti|
0180 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 52 64 6E |es>CICC</CardRdn|
0190 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 |gCpblties><CardR|
01A0 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 |dngCpblties>MGST|
01B0 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |</CardRdngCpblti|
01C0 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C |es><CardRdngCpbl|
01D0 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 72 64 52 |ties>PHYS</CardR|
01E0 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 |dngCpblties><Crd|
01F0 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
0200 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 72 |es>MNSG</Crdhldr|
0210 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C |VrfctnCpblties><|
0220 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
0230 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 72 64 68 |lties>FCPN</Crdh|
0240 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
0250 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
0260 43 70 62 6C 74 69 65 73 3E 46 45 50 4E 3C 2F 43 |Cpblties>FEPN</C|
0270 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0280 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0290 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E |ctnCpblties>NPIN|
02A0 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
02B0 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 43 |pblties><OnLineC|
02C0 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F 6E |pblties>SMON</On|
02D0 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 3C 2F 43 |LineCpblties></C|
02E0 70 62 6C 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C |pblties><Cmpnt><|
02F0 54 70 3E 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E |Tp>TERM</Tp><Id>|
0300 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E |<ItmNb>1</ItmNb>|
0310 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 6E |<PrvdrId>EPASVen|

7 Messages Examples - 338 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0320 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 3E |dor001</PrvdrId>|
0330 3C 49 64 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 |<Id>SmartPOI-853|
0340 39 3C 2F 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 |9</Id><SrlNb>782|
0350 35 34 31 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C |5410759</SrlNb><|
0360 2F 49 64 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 |/Id></Cmpnt><Cmp|
0370 6E 74 3E 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E |nt><Tp>APLI</Tp>|
0380 3C 49 64 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 |<Id><ItmNb>1</It|
0390 6D 4E 62 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 |mNb><PrvdrId>EPA|
03A0 53 56 65 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 |SVendor001</Prvd|
03B0 72 49 64 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 |rId></Id><Sts><V|
03C0 72 73 6E 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E |rsnNb>1.0</VrsnN|
03D0 62 3E 3C 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C |b></Sts><StdCmpl|
03E0 63 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 3C |c><Id>SEPA-FAST<|
03F0 2F 49 64 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 |/Id><Vrsn>3.0</V|
0400 72 73 6E 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 |rsn><Issr>CIR</I|
0410 73 73 72 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C |ssr></StdCmplc><|
0420 2F 43 6D 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 |/Cmpnt></POI><Ca|
0430 72 64 3E 3C 50 72 74 63 74 64 43 61 72 64 44 61 |rd><PrtctdCardDa|
0440 74 61 3E 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C |ta><CnttTp>EVLP<|
0450 2F 43 6E 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 |/CnttTp><EnvlpdD|
0460 61 74 61 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C |ata><Rcpt><KEK><|
0470 4B 45 4B 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 |KEKId><KeyId>Spe|
0480 63 56 31 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 |cV1TestKey</KeyI|
0490 64 3E 3C 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 |d><KeyVrsn>20100|
04A0 36 30 37 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C |60715</KeyVrsn><|
04B0 44 65 72 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 |DerivtnId>OYclpQ|
04C0 45 3D 3C 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F |E=</DerivtnId></|
04D0 4B 45 4B 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E |KEKId><KeyNcrptn|
04E0 41 6C 67 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C |Algo><Algo>DKP9<|
04F0 2F 41 6C 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 |/Algo></KeyNcrpt|
0500 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 |nAlgo><NcrptdKey|
0510 3E 34 70 41 67 41 42 6B 3D 3C 2F 4E 63 72 70 74 |>4pAgABk=</Ncrpt|
0520 64 4B 65 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 |dKey></KEK></Rcp|
0530 74 3E 3C 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 |t><NcrptdCntt><C|
0540 6E 74 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 |nttTp>DATA</Cntt|
0550 54 70 3E 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C |Tp><CnttNcrptnAl|
0560 67 6F 3E 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 |go><Algo>E3DC</A|
0570 6C 67 6F 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 |lgo><Param><Init|
0580 6C 73 74 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 |lstnVctr>onu0bRw|
0590 77 62 67 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 |wbgk=</InitlstnV|
05A0 63 74 72 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E |ctr></Param></Cn|
05B0 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 |ttNcrptnAlgo><Nc|
05C0 72 70 74 64 44 61 74 61 3E 58 47 50 48 63 76 78 |rptdData>XGPHcvx|
05D0 6E 4D 47 32 56 2F 35 38 36 59 63 6A 58 37 33 2F |nMG2V/586YcjX73/|
05E0 6C 73 69 53 75 6C 33 55 59 67 41 68 4C 37 59 73 |lsiSul3UYgAhL7Ys|
05F0 65 65 66 49 6A 5A 50 51 30 38 33 54 32 51 50 46 |eefIjZPQ083T2QPF|
0600 78 61 34 55 63 33 56 66 67 77 31 52 71 72 4F 66 |xa4Uc3Vfgw1RqrOf|
0610 38 43 36 2B 37 2F 72 2F 55 75 54 33 48 42 79 44 |8C6+7/r/UuT3HByD|
0620 6F 49 65 41 4E 64 4E 63 7A 46 4E 4F 53 65 47 73 |oIeANdNczFNOSeGs|
0630 65 63 31 52 70 54 36 66 4C 44 63 6C 38 4A 78 59 |ec1RpT6fLDcl8JxY|
0640 6A 75 30 62 66 43 38 50 46 4C 77 4A 49 77 46 79 |ju0bfC8PFLwJIwFy|
0650 70 38 61 4C 5A 57 39 70 33 31 59 38 30 6B 67 3D |p8aLZW9p31Y80kg=|
0660 3D 3C 2F 4E 63 72 70 74 64 44 61 74 61 3E 3C 2F |=</NcrptdData></|

7 Messages Examples - 339 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0670 4E 63 72 70 74 64 43 6E 74 74 3E 3C 2F 45 6E 76 |NcrptdCntt></Env|
0680 6C 70 64 44 61 74 61 3E 3C 2F 50 72 74 63 74 64 |lpdData></Prtctd|
0690 43 61 72 64 44 61 74 61 3E 3C 43 61 72 64 43 74 |CardData><CardCt|
06A0 72 79 43 64 3E 30 35 36 3C 2F 43 61 72 64 43 74 |ryCd>056</CardCt|
06B0 72 79 43 64 3E 3C 43 61 72 64 50 64 63 74 50 72 |ryCd><CardPdctPr|
06C0 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 63 |fl>0003</CardPdc|
06D0 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E |tPrfl><CardBrnd>|
06E0 54 65 73 74 43 61 72 64 3C 2F 43 61 72 64 42 72 |TestCard</CardBr|
06F0 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 |nd></Card></Envt|
0700 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 |><Cntxt><PmtCntx|
0710 74 3E 3C 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E |t><AttndncCntxt>|
0720 41 54 54 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 |ATTD</AttndncCnt|
0730 78 74 3E 3C 43 61 72 64 44 61 74 61 4E 74 72 79 |xt><CardDataNtry|
0740 4D 64 3E 43 49 43 43 3C 2F 43 61 72 64 44 61 74 |Md>CICC</CardDat|
0750 61 4E 74 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 |aNtryMd></PmtCnt|
0760 78 74 3E 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 |xt><SaleCntxt><S|
0770 61 6C 65 49 64 3E 53 54 30 36 3C 2F 53 61 6C 65 |aleId>ST06</Sale|
0780 49 64 3E 3C 53 61 6C 65 52 65 66 4E 62 3E 53 37 |Id><SaleRefNb>S7|
0790 38 2D 54 30 36 2D 30 30 32 39 3C 2F 53 61 6C 65 |8-T06-0029</Sale|
07A0 52 65 66 4E 62 3E 3C 53 61 6C 65 52 63 6E 63 6C |RefNb><SaleRcncl|
07B0 74 6E 49 64 3E 53 37 38 2D 38 34 36 39 3C 2F 53 |tnId>S78-8469</S|
07C0 61 6C 65 52 63 6E 63 6C 74 6E 49 64 3E 3C 2F 53 |aleRcncltnId></S|
07D0 61 6C 65 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 |aleCntxt></Cntxt|
07E0 3E 3C 54 78 3E 3C 4D 72 63 68 6E 74 43 74 67 79 |><Tx><MrchntCtgy|
07F0 43 64 3E 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 |Cd>5411</MrchntC|
0800 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 |tgyCd><TxId><TxD|
0810 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 |tTm>2013-08-11T1|
0820 38 3A 33 34 3A 31 39 2E 30 30 2B 30 31 3A 30 30 |8:34:19.00+01:00|
0830 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|
0840 30 30 32 39 35 30 3C 2F 54 78 52 65 66 3E 3C 2F |002950</TxRef></|
0850 54 78 49 64 3E 3C 4F 72 67 6E 6C 54 78 3E 3C 54 |TxId><OrgnlTx><T|
0860 78 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 33 |xId><TxDtTm>2013|
0870 2D 30 38 2D 31 31 54 31 37 3A 32 32 3A 30 34 2E |-08-11T17:22:04.|
0880 35 31 2B 30 31 3A 30 30 3C 2F 54 78 44 74 54 6D |51+01:00</TxDtTm|
0890 3E 3C 54 78 52 65 66 3E 30 30 32 39 34 39 3C 2F |><TxRef>002949</|
08A0 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 78 |TxRef></TxId><Tx|
08B0 54 70 3E 43 52 44 50 3C 2F 54 78 54 70 3E 3C 54 |Tp>CRDP</TxTp><T|
08C0 78 52 73 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 |xRslt><AuthstnNt|
08D0 74 79 3E 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E |ty><Tp>CISS</Tp>|
08E0 3C 2F 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 |</AuthstnNtty><R|
08F0 73 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 |spnToAuthstn><Rs|
0900 70 6E 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F |pn>APPR</Rspn></|
0910 52 73 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 |RspnToAuthstn><A|
0920 75 74 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C |uthstnCd>032983<|
0930 2F 41 75 74 68 73 74 6E 43 64 3E 3C 2F 54 78 52 |/AuthstnCd></TxR|
0940 73 6C 74 3E 3C 2F 4F 72 67 6E 6C 54 78 3E 3C 54 |slt></OrgnlTx><T|
0950 78 53 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 |xSucss>true</TxS|
0960 75 63 73 73 3E 3C 52 63 6E 63 6C 74 6E 49 64 3E |ucss><RcncltnId>|
0970 38 34 36 39 3C 2F 52 63 6E 63 6C 74 6E 49 64 3E |8469</RcncltnId>|
0980 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 |<TxDtls><Ccy>EUR|
0990 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 34 33 |</Ccy><TtlAmt>43|
09A0 2E 31 34 3C 2F 54 74 6C 41 6D 74 3E 3C 2F 54 78 |.14</TtlAmt></Tx|
09B0 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 41 |Dtls></Tx></CxlA|

7 Messages Examples - 340 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

09C0 64 76 63 3E |dvc> |

The SHA-256 digest of the message body CxlAdvc is:


0000 54 FB 4C 6E EE 39 44 95 5B 9A E6 4A 3C 9E 6B 6C |T.Ln.9D.[..J<.kl|
0010 03 F9 37 E9 A1 32 DE ED AF 87 B0 26 6D 76 65 D1 |..7..2.....&mve.|

7 Messages Examples - 341 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

After padding, the digest becomes:


0000 54 FB 4C 6E EE 39 44 95 5B 9A E6 4A 3C 9E 6B 6C |T.Ln.9D.[..J<.kl|
0010 03 F9 37 E9 A1 32 DE ED AF 87 B0 26 6D 76 65 D1 |..7..2.....&mve.|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (23EC3237 B0FED957 38B9E0EF
54F7269D), we obtain the MAC of the AcceptorCancellationAdvice FE33AA8DBACBA809 and after
conversion into base64 "/jOqjbrLqAk=".
0000 F0 DB 6A B9 CC 15 83 3C D0 0E 8F 51 F8 A2 DD E4 |..j....<...Q....|
0010 97 65 A8 B5 06 A4 66 E9 98 BC 43 3E 03 64 8E C0 |.e....f...C>.d..|
0020 FE 33 AA 8D BA CB A8 09 |.3...... |

The message sent by the transport protocol is:


0000 00 00 0D 08 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 37 2E 30 30 31 2E 30 35 22 |caaa.007.001.05"|
00A0 3E 3C 41 63 63 70 74 72 43 78 6C 41 64 76 63 3E |><AccptrCxlAdvc>|
00B0 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E 3E 43 43 |<Hdr><MsgFctn>CC|
00C0 41 56 3C 2F 4D 73 67 46 63 74 6E 3E 3C 50 72 74 |AV</MsgFctn><Prt|
00D0 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F 50 72 74 |colVrsn>5.0</Prt|
00E0 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 49 64 3E |colVrsn><XchgId>|
00F0 31 35 31 3C 2F 58 63 68 67 49 64 3E 3C 43 72 65 |151</XchgId><Cre|
0100 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 |DtTm>2013-08-11T|
0110 31 38 3A 33 34 3A 34 34 2E 30 30 2B 30 31 3A 30 |18:34:44.00+01:0|
0120 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 6E 69 74 |0</CreDtTm><Init|
0130 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 30 30 30 |gPty><Id>6600000|
0140 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F |1</Id><Tp>OPOI</|
0150 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 |Tp><Issr>ACQR</I|
0160 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 79 3E 3C |ssr></InitgPty><|
0170 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 70 61 73 |RcptPty><Id>epas|
0180 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F 49 64 3E |-acquirer-1</Id>|
0190 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 52 |<Tp>ACQR</Tp></R|
01A0 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E 3C 43 78 |cptPty></Hdr><Cx|
01B0 6C 41 64 76 63 3E 3C 45 6E 76 74 3E 3C 41 63 71 |lAdvc><Envt><Acq|
01C0 72 72 3E 3C 49 64 3E 3C 49 64 3E 39 32 38 37 33 |rr><Id><Id>92873|
01D0 35 31 3C 2F 49 64 3E 3C 54 70 3E 41 43 51 52 3C |51</Id><Tp>ACQR<|
01E0 2F 54 70 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 |/Tp></Id><Params|
01F0 56 72 73 6E 3E 32 30 31 33 2D 30 38 2D 30 37 20 |Vrsn>2013-08-07 |
0200 30 38 3A 30 30 3A 30 30 3C 2F 50 61 72 61 6D 73 |08:00:00</Params|
0210 56 72 73 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D 72 |Vrsn></Acqrr><Mr|
0220 63 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E 45 50 41 |chnt><Id><Id>EPA|
0230 53 4D 45 52 30 30 31 3C 2F 49 64 3E 3C 2F 49 64 |SMER001</Id></Id|

7 Messages Examples - 342 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0240 3E 3C 43 6D 6F 6E 4E 6D 3E 45 50 41 53 4F 72 67 |><CmonNm>EPASOrg|
0250 20 4D 65 72 63 68 61 6E 74 20 31 3C 2F 43 6D 6F | Merchant 1</Cmo|
0260 6E 4E 6D 3E 3C 4C 63 74 6E 43 74 67 79 3E 46 49 |nNm><LctnCtgy>FI|
0270 58 44 3C 2F 4C 63 74 6E 43 74 67 79 3E 3C 4C 63 |XD</LctnCtgy><Lc|
0280 74 6E 41 6E 64 43 74 63 74 3E 3C 50 73 74 6C 41 |tnAndCtct><PstlA|
0290 64 72 3E 3C 54 77 6E 4E 6D 3E 50 61 72 69 73 3C |dr><TwnNm>Paris<|
02A0 2F 54 77 6E 4E 6D 3E 3C 43 74 72 79 3E 46 52 3C |/TwnNm><Ctry>FR<|
02B0 2F 43 74 72 79 3E 3C 2F 50 73 74 6C 41 64 72 3E |/Ctry></PstlAdr>|
02C0 3C 2F 4C 63 74 6E 41 6E 64 43 74 63 74 3E 3C 2F |</LctnAndCtct></|
02D0 4D 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E |Mrchnt><POI><Id>|
02E0 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 72 3E |<Id>1</Id><Issr>|
02F0 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 49 64 3E |ACQR</Issr></Id>|
0300 3C 53 79 73 4E 6D 3E 50 4F 49 30 31 3C 2F 53 79 |<SysNm>POI01</Sy|
0310 73 4E 6D 3E 3C 43 70 62 6C 74 69 65 73 3E 3C 43 |sNm><Cpblties><C|
0320 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
0330 43 49 43 43 3C 2F 43 61 72 64 52 64 6E 67 43 70 |CICC</CardRdngCp|
0340 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 |blties><CardRdng|
0350 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F 43 |Cpblties>MGST</C|
0360 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
0370 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |<CardRdngCpbltie|
0380 73 3E 50 48 59 53 3C 2F 43 61 72 64 52 64 6E 67 |s>PHYS</CardRdng|
0390 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 |Cpblties><Crdhld|
03A0 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
03B0 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 |MNSG</CrdhldrVrf|
03C0 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 |ctnCpblties><Crd|
03D0 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
03E0 65 73 3E 46 43 50 4E 3C 2F 43 72 64 68 6C 64 72 |es>FCPN</Crdhldr|
03F0 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C |VrfctnCpblties><|
0400 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
0410 6C 74 69 65 73 3E 46 45 50 4E 3C 2F 43 72 64 68 |lties>FEPN</Crdh|
0420 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
0430 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
0440 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E 3C 2F 43 |Cpblties>NPIN</C|
0450 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
0460 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 43 70 62 6C |ties><OnLineCpbl|
0470 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F 6E 4C 69 6E |ties>SMON</OnLin|
0480 65 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |eCpblties></Cpbl|
0490 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
04A0 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 49 74 |TERM</Tp><Id><It|
04B0 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 3E 3C 50 72 |mNb>1</ItmNb><Pr|
04C0 76 64 72 49 64 3E 45 50 41 53 56 65 6E 64 6F 72 |vdrId>EPASVendor|
04D0 30 30 31 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |001</PrvdrId><Id|
04E0 3E 53 6D 61 72 74 50 4F 49 2D 38 35 33 39 3C 2F |>SmartPOI-8539</|
04F0 49 64 3E 3C 53 72 6C 4E 62 3E 37 38 32 35 34 31 |Id><SrlNb>782541|
0500 30 37 35 39 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 |0759</SrlNb></Id|
0510 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E |></Cmpnt><Cmpnt>|
0520 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 |<Tp>APLI</Tp><Id|
0530 3E 3C 49 74 6D 4E 62 3E 31 3C 2F 49 74 6D 4E 62 |><ItmNb>1</ItmNb|
0540 3E 3C 50 72 76 64 72 49 64 3E 45 50 41 53 56 65 |><PrvdrId>EPASVe|
0550 6E 64 6F 72 30 30 31 3C 2F 50 72 76 64 72 49 64 |ndor001</PrvdrId|
0560 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
0570 4E 62 3E 31 2E 30 3C 2F 56 72 73 6E 4E 62 3E 3C |Nb>1.0</VrsnNb><|
0580 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|

7 Messages Examples - 343 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0590 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
05A0 3E 3C 56 72 73 6E 3E 33 2E 30 3C 2F 56 72 73 6E |><Vrsn>3.0</Vrsn|
05B0 3E 3C 49 73 73 72 3E 43 49 52 3C 2F 49 73 73 72 |><Issr>CIR</Issr|
05C0 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 2F 43 6D |></StdCmplc></Cm|
05D0 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |pnt></POI><Card>|
05E0 3C 50 72 74 63 74 64 43 61 72 64 44 61 74 61 3E |<PrtctdCardData>|
05F0 3C 43 6E 74 74 54 70 3E 45 56 4C 50 3C 2F 43 6E |<CnttTp>EVLP</Cn|
0600 74 74 54 70 3E 3C 45 6E 76 6C 70 64 44 61 74 61 |ttTp><EnvlpdData|
0610 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B |><Rcpt><KEK><KEK|
0620 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 |Id><KeyId>SpecV1|
0630 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C |TestKey</KeyId><|
0640 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 36 30 37 |KeyVrsn>20100607|
0650 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 |15</KeyVrsn><Der|
0660 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C |ivtnId>OYclpQE=<|
0670 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B |/DerivtnId></KEK|
0680 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 |Id><KeyNcrptnAlg|
0690 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C |o><Algo>DKP9</Al|
06A0 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C |go></KeyNcrptnAl|
06B0 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 |go><NcrptdKey>4p|
06C0 41 67 41 42 6B 3D 3C 2F 4E 63 72 70 74 64 4B 65 |AgABk=</NcrptdKe|
06D0 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C |y></KEK></Rcpt><|
06E0 4E 63 72 70 74 64 43 6E 74 74 3E 3C 43 6E 74 74 |NcrptdCntt><Cntt|
06F0 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E |Tp>DATA</CnttTp>|
0700 3C 43 6E 74 74 4E 63 72 70 74 6E 41 6C 67 6F 3E |<CnttNcrptnAlgo>|
0710 3C 41 6C 67 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F |<Algo>E3DC</Algo|
0720 3E 3C 50 61 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 |><Param><Initlst|
0730 6E 56 63 74 72 3E 6F 6E 75 30 62 52 77 77 62 67 |nVctr>onu0bRwwbg|
0740 6B 3D 3C 2F 49 6E 69 74 6C 73 74 6E 56 63 74 72 |k=</InitlstnVctr|
0750 3E 3C 2F 50 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E |></Param></CnttN|
0760 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 |crptnAlgo><Ncrpt|
0770 64 44 61 74 61 3E 58 47 50 48 63 76 78 6E 4D 47 |dData>XGPHcvxnMG|
0780 32 56 2F 35 38 36 59 63 6A 58 37 33 2F 6C 73 69 |2V/586YcjX73/lsi|
0790 53 75 6C 33 55 59 67 41 68 4C 37 59 73 65 65 66 |Sul3UYgAhL7Yseef|
07A0 49 6A 5A 50 51 30 38 33 54 32 51 50 46 78 61 34 |IjZPQ083T2QPFxa4|
07B0 55 63 33 56 66 67 77 31 52 71 72 4F 66 38 43 36 |Uc3Vfgw1RqrOf8C6|
07C0 2B 37 2F 72 2F 55 75 54 33 48 42 79 44 6F 49 65 |+7/r/UuT3HByDoIe|
07D0 41 4E 64 4E 63 7A 46 4E 4F 53 65 47 73 65 63 31 |ANdNczFNOSeGsec1|
07E0 52 70 54 36 66 4C 44 63 6C 38 4A 78 59 6A 75 30 |RpT6fLDcl8JxYju0|
07F0 62 66 43 38 50 46 4C 77 4A 49 77 46 79 70 38 61 |bfC8PFLwJIwFyp8a|
0800 4C 5A 57 39 70 33 31 59 38 30 6B 67 3D 3D 3C 2F |LZW9p31Y80kg==</|
0810 4E 63 72 70 74 64 44 61 74 61 3E 3C 2F 4E 63 72 |NcrptdData></Ncr|
0820 70 74 64 43 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 |ptdCntt></Envlpd|
0830 44 61 74 61 3E 3C 2F 50 72 74 63 74 64 43 61 72 |Data></PrtctdCar|
0840 64 44 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 |dData><CardCtryC|
0850 64 3E 30 35 36 3C 2F 43 61 72 64 43 74 72 79 43 |d>056</CardCtryC|
0860 64 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |d><CardPdctPrfl>|
0870 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 |0003</CardPdctPr|
0880 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 54 65 73 |fl><CardBrnd>Tes|
0890 74 43 61 72 64 3C 2F 43 61 72 64 42 72 6E 64 3E |tCard</CardBrnd>|
08A0 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 |</Card></Envt><C|
08B0 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
08C0 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 54 |AttndncCntxt>ATT|
08D0 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E |D</AttndncCntxt>|

7 Messages Examples - 344 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

08E0 3C 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E |<CardDataNtryMd>|
08F0 43 49 43 43 3C 2F 43 61 72 64 44 61 74 61 4E 74 |CICC</CardDataNt|
0900 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E |ryMd></PmtCntxt>|
0910 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C 65 |<SaleCntxt><Sale|
0920 49 64 3E 53 54 30 36 3C 2F 53 61 6C 65 49 64 3E |Id>ST06</SaleId>|
0930 3C 53 61 6C 65 52 65 66 4E 62 3E 53 37 38 2D 54 |<SaleRefNb>S78-T|
0940 30 36 2D 30 30 32 39 3C 2F 53 61 6C 65 52 65 66 |06-0029</SaleRef|
0950 4E 62 3E 3C 53 61 6C 65 52 63 6E 63 6C 74 6E 49 |Nb><SaleRcncltnI|
0960 64 3E 53 37 38 2D 38 34 36 39 3C 2F 53 61 6C 65 |d>S78-8469</Sale|
0970 52 63 6E 63 6C 74 6E 49 64 3E 3C 2F 53 61 6C 65 |RcncltnId></Sale|
0980 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C 54 |Cntxt></Cntxt><T|
0990 78 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 3E |x><MrchntCtgyCd>|
09A0 35 34 31 31 3C 2F 4D 72 63 68 6E 74 43 74 67 79 |5411</MrchntCtgy|
09B0 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Cd><TxId><TxDtTm|
09C0 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 38 3A 33 |>2013-08-11T18:3|
09D0 34 3A 31 39 2E 30 30 2B 30 31 3A 30 30 3C 2F 54 |4:19.00+01:00</T|
09E0 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 32 |xDtTm><TxRef>002|
09F0 39 35 30 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 |950</TxRef></TxI|
0A00 64 3E 3C 4F 72 67 6E 6C 54 78 3E 3C 54 78 49 64 |d><OrgnlTx><TxId|
0A10 3E 3C 54 78 44 74 54 6D 3E 32 30 31 33 2D 30 38 |><TxDtTm>2013-08|
0A20 2D 31 31 54 31 37 3A 32 32 3A 30 34 2E 35 31 2B |-11T17:22:04.51+|
0A30 30 31 3A 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 |01:00</TxDtTm><T|
0A40 78 52 65 66 3E 30 30 32 39 34 39 3C 2F 54 78 52 |xRef>002949</TxR|
0A50 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 78 54 70 3E |ef></TxId><TxTp>|
0A60 43 52 44 50 3C 2F 54 78 54 70 3E 3C 54 78 52 73 |CRDP</TxTp><TxRs|
0A70 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E |lt><AuthstnNtty>|
0A80 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 |<Tp>CISS</Tp></A|
0A90 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E |uthstnNtty><Rspn|
0AA0 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E |ToAuthstn><Rspn>|
0AB0 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 |APPR</Rspn></Rsp|
0AC0 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 |nToAuthstn><Auth|
0AD0 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 |stnCd>032983</Au|
0AE0 74 68 73 74 6E 43 64 3E 3C 2F 54 78 52 73 6C 74 |thstnCd></TxRslt|
0AF0 3E 3C 2F 4F 72 67 6E 6C 54 78 3E 3C 54 78 53 75 |></OrgnlTx><TxSu|
0B00 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 75 63 73 |css>true</TxSucs|
0B10 73 3E 3C 52 63 6E 63 6C 74 6E 49 64 3E 38 34 36 |s><RcncltnId>846|
0B20 39 3C 2F 52 63 6E 63 6C 74 6E 49 64 3E 3C 54 78 |9</RcncltnId><Tx|
0B30 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 |Dtls><Ccy>EUR</C|
0B40 63 79 3E 3C 54 74 6C 41 6D 74 3E 34 33 2E 31 34 |cy><TtlAmt>43.14|
0B50 3C 2F 54 74 6C 41 6D 74 3E 3C 2F 54 78 44 74 6C |</TtlAmt></TxDtl|
0B60 73 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 41 64 76 63 |s></Tx></CxlAdvc|
0B70 3E 3C 53 63 74 79 54 72 6C 72 3E 3C 43 6E 74 74 |><SctyTrlr><Cntt|
0B80 54 70 3E 41 55 54 48 3C 2F 43 6E 74 74 54 70 3E |Tp>AUTH</CnttTp>|
0B90 3C 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 52 |<AuthntcdData><R|
0BA0 63 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E |cpt><KEK><KEKId>|
0BB0 3C 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 |<KeyId>SpecV1Tes|
0BC0 74 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 |tKey</KeyId><Key|
0BD0 56 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C |Vrsn>2010060715<|
0BE0 2F 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 |/KeyVrsn><Derivt|
0BF0 6E 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 |nId>OYclpQE=</De|
0C00 72 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E |rivtnId></KEKId>|
0C10 3C 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |<KeyNcrptnAlgo><|
0C20 41 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E |Algo>DKP9</Algo>|

7 Messages Examples - 345 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0C30 3C 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E |</KeyNcrptnAlgo>|
0C40 3C 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 |<NcrptdKey>4pAgA|
0C50 42 6B 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C |Bk=</NcrptdKey><|
0C60 2F 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 |/KEK></Rcpt><MAC|
0C70 41 6C 67 6F 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C |Algo><Algo>MCCS<|
0C80 2F 41 6C 67 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E |/Algo></MACAlgo>|
0C90 3C 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 43 6E |<NcpsltdCntt><Cn|
0CA0 74 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 |ttTp>DATA</CnttT|
0CB0 70 3E 3C 2F 4E 63 70 73 6C 74 64 43 6E 74 74 3E |p></NcpsltdCntt>|
0CC0 3C 4D 41 43 3E 2F 6A 4F 71 6A 62 72 4C 71 41 6B |<MAC>/jOqjbrLqAk|
0CD0 3D 3C 2F 4D 41 43 3E 3C 2F 41 75 74 68 6E 74 63 |=</MAC></Authntc|
0CE0 64 44 61 74 61 3E 3C 2F 53 63 74 79 54 72 6C 72 |dData></SctyTrlr|
0CF0 3E 3C 2F 41 63 63 70 74 72 43 78 6C 41 64 76 63 |></AccptrCxlAdvc|
0D00 3E 3C 2F 44 6F 63 75 6D 65 6E 74 3E |></Document> |

7 Messages Examples - 346 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

7.4.2 AcceptorCancellationAdviceResponse

The cancellation has been accepted by the Acquirer.

Message Item Value


Transaction
TransactionIdentification
TransactionDateTime 2013-08-11T18:34:19.00+01:00
TransactionReference 002950
Response Approved

The resulting XML encoded structure is:


<Tx>
<TxId>
<TxDtTm>2013-08-11T18:34:19.00+01:00</TxDtTm>
<TxRef>002950</TxRef>
</TxId>
</Tx>

7 Messages Examples - 347 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorCancellationAdviceResponse is presented below, omitting data structure


already previously detailed.

Message Item Value


CancellationAdviceResponse
Header
MessageFunction CancellationAdviceResponse
ProtocolVersion 5.0
ExchangeIdentifier 151
CreationDateTime 2013-08-11T18:34:57.00+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
CancellationAdviceResponse
Environment
AcquirerIdentification
Identification 9287351
Type Acquirer
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 1
Issuer Acquirer
ProtectedCardData
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200019
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC BBC72BFF2A64FE33

7 Messages Examples - 348 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorCancellationAdviceResponse XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.008.001.05">
<AccptrCxlAdvcRspn>
<Hdr>
<MsgFctn>FCMK</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>151</XchgId>
<CreDtTm>2013-08-11T18:34:57.00+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<CxlAdvcRspn>
<Envt>
<AcqrrId>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</AcqrrId>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>1</Id>
<Issr>ACQR</Issr>
</POIId>
<Card>
<PrtctdCardData>
<CnttTp>EVLP</CnttTp>
<EnvlpdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>
</Rcpt>
<NcrptdCntt>
<CnttTp>DATA</CnttTp>
<CnttNcrptnAlgo>
<Algo>E3DC</Algo>
<Param>
<InitlstnVctr>onu0bRwwbgk=</InitlstnVctr>
</Param>
</CnttNcrptnAlgo>
<NcrptdData>
wv8V7CK7RnSJ9O6uBJge2EzoEzvVtCpvk53N/XoIMnm9JWveJCB6iqpc
kE/HbMHeDXYesikOcCl3HStNXXqfV/ALqRNI2mmsfyKV94Wt6JLmMWrO
VaFP2ne1x9Cf5+HpGKzqWc2nITcV4PozcjTSEQ==
</NcrptdData>
</NcrptdCntt>

7 Messages Examples - 349 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

</EnvlpdData>
</PrtctdCardData>
</Card>
</Envt>
<Tx>
<TxId>
<TxDtTm>2013-08-11T18:34:19.00+01:00</TxDtTm>
<TxRef>002950</TxRef>
</TxId>
<Rspn>APPR</Rspn>
</Tx>
</CxlAdvcRspn>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABk=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>u8cr/ypk/jM=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrCxlAdvcRspn>
</Document>

Once unnecessary spaces and carriage returns are removed, the message body AccptrCxlAdvcRspn
(without spaces or line breaks) is dumped below:
0000 3C 43 78 6C 41 64 76 63 52 73 70 6E 3E 3C 45 6E |<CxlAdvcRspn><En|
0010 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 3E |vt><AcqrrId><Id>|
0020 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 3E |9287351</Id><Tp>|
0030 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 72 |ACQR</Tp></Acqrr|
0040 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 64 |Id><MrchntId><Id|
0050 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E |>EPASMER001</Id>|
0060 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 49 |</MrchntId><POII|
0070 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 |d><Id>1</Id><Iss|
0080 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 50 |r>ACQR</Issr></P|
0090 4F 49 49 64 3E 3C 43 61 72 64 3E 3C 50 72 74 63 |OIId><Card><Prtc|
00A0 74 64 43 61 72 64 44 61 74 61 3E 3C 43 6E 74 74 |tdCardData><Cntt|
00B0 54 70 3E 45 56 4C 50 3C 2F 43 6E 74 74 54 70 3E |Tp>EVLP</CnttTp>|
00C0 3C 45 6E 76 6C 70 64 44 61 74 61 3E 3C 52 63 70 |<EnvlpdData><Rcp|
00D0 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B |t><KEK><KEKId><K|
00E0 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 4B |eyId>SpecV1TestK|
00F0 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 |ey</KeyId><KeyVr|
0100 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F 4B |sn>2010060715</K|

7 Messages Examples - 350 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0110 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 |eyVrsn><DerivtnI|
0120 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 |d>OYclpQE=</Deri|
0130 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B |vtnId></KEKId><K|
0140 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C |eyNcrptnAlgo><Al|
0150 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F |go>DKP9</Algo></|
0160 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E |KeyNcrptnAlgo><N|
0170 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 6B |crptdKey>4pAgABk|
0180 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B |=</NcrptdKey></K|
0190 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4E 63 72 70 74 |EK></Rcpt><Ncrpt|
01A0 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 41 |dCntt><CnttTp>DA|
01B0 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 43 6E 74 74 |TA</CnttTp><Cntt|
01C0 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F |NcrptnAlgo><Algo|
01D0 3E 45 33 44 43 3C 2F 41 6C 67 6F 3E 3C 50 61 72 |>E3DC</Algo><Par|
01E0 61 6D 3E 3C 49 6E 69 74 6C 73 74 6E 56 63 74 72 |am><InitlstnVctr|
01F0 3E 6F 6E 75 30 62 52 77 77 62 67 6B 3D 3C 2F 49 |>onu0bRwwbgk=</I|
0200 6E 69 74 6C 73 74 6E 56 63 74 72 3E 3C 2F 50 61 |nitlstnVctr></Pa|
0210 72 61 6D 3E 3C 2F 43 6E 74 74 4E 63 72 70 74 6E |ram></CnttNcrptn|
0220 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 44 61 74 61 |Algo><NcrptdData|
0230 3E 77 76 38 56 37 43 4B 37 52 6E 53 4A 39 4F 36 |>wv8V7CK7RnSJ9O6|
0240 75 42 4A 67 65 32 45 7A 6F 45 7A 76 56 74 43 70 |uBJge2EzoEzvVtCp|
0250 76 6B 35 33 4E 2F 58 6F 49 4D 6E 6D 39 4A 57 76 |vk53N/XoIMnm9JWv|
0260 65 4A 43 42 36 69 71 70 63 6B 45 2F 48 62 4D 48 |eJCB6iqpckE/HbMH|
0270 65 44 58 59 65 73 69 6B 4F 63 43 6C 33 48 53 74 |eDXYesikOcCl3HSt|
0280 4E 58 58 71 66 56 2F 41 4C 71 52 4E 49 32 6D 6D |NXXqfV/ALqRNI2mm|
0290 73 66 79 4B 56 39 34 57 74 36 4A 4C 6D 4D 57 72 |sfyKV94Wt6JLmMWr|
02A0 4F 56 61 46 50 32 6E 65 31 78 39 43 66 35 2B 48 |OVaFP2ne1x9Cf5+H|
02B0 70 47 4B 7A 71 57 63 32 6E 49 54 63 56 34 50 6F |pGKzqWc2nITcV4Po|
02C0 7A 63 6A 54 53 45 51 3D 3D 3C 2F 4E 63 72 70 74 |zcjTSEQ==</Ncrpt|
02D0 64 44 61 74 61 3E 3C 2F 4E 63 72 70 74 64 43 6E |dData></NcrptdCn|
02E0 74 74 3E 3C 2F 45 6E 76 6C 70 64 44 61 74 61 3E |tt></EnvlpdData>|
02F0 3C 2F 50 72 74 63 74 64 43 61 72 64 44 61 74 61 |</PrtctdCardData|
0300 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C |></Card></Envt><|
0310 54 78 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Tx><TxId><TxDtTm|
0320 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 38 3A 33 |>2013-08-11T18:3|
0330 34 3A 31 39 2E 30 30 2B 30 31 3A 30 30 3C 2F 54 |4:19.00+01:00</T|
0340 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 32 |xDtTm><TxRef>002|
0350 39 35 30 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 |950</TxRef></TxI|
0360 64 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F 52 73 |d><Rspn>APPR</Rs|
0370 70 6E 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 41 64 76 |pn></Tx></CxlAdv|
0380 63 52 73 70 6E 3E |cRspn> |

The SHA-256 digest of the message body AccptrCxlAdvcRspn is:


0000 88 68 78 95 95 F7 EA AA 0B 91 5A A1 39 5F 93 43 |.hx.......Z.9_.C|
0010 A3 70 35 0C A6 3D 6A DE 8A A1 E8 FF 5C 46 A2 F5 |.p5..=j.....\F..|

After padding, the digest becomes:


0000 88 68 78 95 95 F7 EA AA 0B 91 5A A1 39 5F 93 43 |.hx.......Z.9_.C|
0010 A3 70 35 0C A6 3D 6A DE 8A A1 E8 FF 5C 46 A2 F5 |.p5..=j.....\F..|
0020 80 00 00 00 00 00 00 00 |........ |

7 Messages Examples - 351 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

Retail CBC encryption with the MAC Computation test Key (23EC3237 4FFE2657 38B9E0EF
ABF7D99D), we obtain the MAC of the AcceptorCancellationAdviceResponse BBC72BFF2A64FE33
and after conversion into base64 "u8cr/ypk/jM=".
0000 1B 3A D2 42 21 AD E2 15 7E 51 09 F2 DA 37 6B AE |.:.B!...~Q...7k.|
0010 21 B9 CC 53 B1 AE 28 50 C5 9C A8 5B 9A 33 A6 86 |!..S..(P...[.3..|
0020 BB C7 2B FF 2A 64 FE 33 |..+.*d.3 |

7 Messages Examples - 352 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

The message sent by the transport protocol is:


0000 00 00 06 D2 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 38 2E 30 30 31 2E 30 35 22 |caaa.008.001.05"|
00A0 3E 3C 41 63 63 70 74 72 43 78 6C 41 64 76 63 52 |><AccptrCxlAdvcR|
00B0 73 70 6E 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 |spn><Hdr><MsgFct|
00C0 6E 3E 46 43 4D 4B 3C 2F 4D 73 67 46 63 74 6E 3E |n>FCMK</MsgFctn>|
00D0 3C 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C |<PrtcolVrsn>5.0<|
00E0 2F 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 |/PrtcolVrsn><Xch|
00F0 67 49 64 3E 31 35 31 3C 2F 58 63 68 67 49 64 3E |gId>151</XchgId>|
0100 3C 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 |<CreDtTm>2013-08|
0110 2D 31 31 54 31 38 3A 33 34 3A 35 37 2E 30 30 2B |-11T18:34:57.00+|
0120 30 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C |01:00</CreDtTm><|
0130 49 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 |InitgPty><Id>660|
0140 30 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 |00001</Id><Tp>OP|
0150 4F 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 |OI</Tp><Issr>ACQ|
0160 52 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 |R</Issr></InitgP|
0170 74 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E |ty><RcptPty><Id>|
0180 65 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C |epas-acquirer-1<|
0190 2F 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 |/Id><Tp>ACQR</Tp|
01A0 3E 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 |></RcptPty></Hdr|
01B0 3E 3C 43 78 6C 41 64 76 63 52 73 70 6E 3E 3C 45 |><CxlAdvcRspn><E|
01C0 6E 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 |nvt><AcqrrId><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 |>ACQR</Tp></Acqr|
01F0 72 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 |rId><MrchntId><I|
0200 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 |d>EPASMER001</Id|
0210 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 |></MrchntId><POI|
0220 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 |Id><Id>1</Id><Is|
0230 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F |sr>ACQR</Issr></|
0240 50 4F 49 49 64 3E 3C 43 61 72 64 3E 3C 50 72 74 |POIId><Card><Prt|
0250 63 74 64 43 61 72 64 44 61 74 61 3E 3C 43 6E 74 |ctdCardData><Cnt|
0260 74 54 70 3E 45 56 4C 50 3C 2F 43 6E 74 74 54 70 |tTp>EVLP</CnttTp|
0270 3E 3C 45 6E 76 6C 70 64 44 61 74 61 3E 3C 52 63 |><EnvlpdData><Rc|
0280 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C |pt><KEK><KEKId><|
0290 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 |KeyId>SpecV1Test|
02A0 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 |Key</KeyId><KeyV|
02B0 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F |rsn>2010060715</|
02C0 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E |KeyVrsn><Derivtn|
02D0 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 |Id>OYclpQE=</Der|
02E0 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C |ivtnId></KEKId><|
02F0 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |KeyNcrptnAlgo><A|
0300 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C |lgo>DKP9</Algo><|
0310 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |/KeyNcrptnAlgo><|
0320 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 |NcrptdKey>4pAgAB|

7 Messages Examples - 353 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0330 6B 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F |k=</NcrptdKey></|
0340 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4E 63 72 70 |KEK></Rcpt><Ncrp|
0350 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 |tdCntt><CnttTp>D|
0360 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 43 6E 74 |ATA</CnttTp><Cnt|
0370 74 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 |tNcrptnAlgo><Alg|
0380 6F 3E 45 33 44 43 3C 2F 41 6C 67 6F 3E 3C 50 61 |o>E3DC</Algo><Pa|
0390 72 61 6D 3E 3C 49 6E 69 74 6C 73 74 6E 56 63 74 |ram><InitlstnVct|
03A0 72 3E 6F 6E 75 30 62 52 77 77 62 67 6B 3D 3C 2F |r>onu0bRwwbgk=</|
03B0 49 6E 69 74 6C 73 74 6E 56 63 74 72 3E 3C 2F 50 |InitlstnVctr></P|
03C0 61 72 61 6D 3E 3C 2F 43 6E 74 74 4E 63 72 70 74 |aram></CnttNcrpt|
03D0 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 44 61 74 |nAlgo><NcrptdDat|
03E0 61 3E 77 76 38 56 37 43 4B 37 52 6E 53 4A 39 4F |a>wv8V7CK7RnSJ9O|
03F0 36 75 42 4A 67 65 32 45 7A 6F 45 7A 76 56 74 43 |6uBJge2EzoEzvVtC|
0400 70 76 6B 35 33 4E 2F 58 6F 49 4D 6E 6D 39 4A 57 |pvk53N/XoIMnm9JW|
0410 76 65 4A 43 42 36 69 71 70 63 6B 45 2F 48 62 4D |veJCB6iqpckE/HbM|
0420 48 65 44 58 59 65 73 69 6B 4F 63 43 6C 33 48 53 |HeDXYesikOcCl3HS|
0430 74 4E 58 58 71 66 56 2F 41 4C 71 52 4E 49 32 6D |tNXXqfV/ALqRNI2m|
0440 6D 73 66 79 4B 56 39 34 57 74 36 4A 4C 6D 4D 57 |msfyKV94Wt6JLmMW|
0450 72 4F 56 61 46 50 32 6E 65 31 78 39 43 66 35 2B |rOVaFP2ne1x9Cf5+|
0460 48 70 47 4B 7A 71 57 63 32 6E 49 54 63 56 34 50 |HpGKzqWc2nITcV4P|
0470 6F 7A 63 6A 54 53 45 51 3D 3D 3C 2F 4E 63 72 70 |ozcjTSEQ==</Ncrp|
0480 74 64 44 61 74 61 3E 3C 2F 4E 63 72 70 74 64 43 |tdData></NcrptdC|
0490 6E 74 74 3E 3C 2F 45 6E 76 6C 70 64 44 61 74 61 |ntt></EnvlpdData|
04A0 3E 3C 2F 50 72 74 63 74 64 43 61 72 64 44 61 74 |></PrtctdCardDat|
04B0 61 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E |a></Card></Envt>|
04C0 3C 54 78 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 |<Tx><TxId><TxDtT|
04D0 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 31 38 3A |m>2013-08-11T18:|
04E0 33 34 3A 31 39 2E 30 30 2B 30 31 3A 30 30 3C 2F |34:19.00+01:00</|
04F0 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 30 30 |TxDtTm><TxRef>00|
0500 32 39 35 30 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 |2950</TxRef></Tx|
0510 49 64 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F 52 |Id><Rspn>APPR</R|
0520 73 70 6E 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 41 64 |spn></Tx></CxlAd|
0530 76 63 52 73 70 6E 3E 3C 53 63 74 79 54 72 6C 72 |vcRspn><SctyTrlr|
0540 3E 3C 43 6E 74 74 54 70 3E 41 55 54 48 3C 2F 43 |><CnttTp>AUTH</C|
0550 6E 74 74 54 70 3E 3C 41 75 74 68 6E 74 63 64 44 |nttTp><AuthntcdD|
0560 61 74 61 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E 3C |ata><Rcpt><KEK><|
0570 4B 45 4B 49 64 3E 3C 4B 65 79 49 64 3E 53 70 65 |KEKId><KeyId>Spe|
0580 63 56 31 54 65 73 74 4B 65 79 3C 2F 4B 65 79 49 |cV1TestKey</KeyI|
0590 64 3E 3C 4B 65 79 56 72 73 6E 3E 32 30 31 30 30 |d><KeyVrsn>20100|
05A0 36 30 37 31 35 3C 2F 4B 65 79 56 72 73 6E 3E 3C |60715</KeyVrsn><|
05B0 44 65 72 69 76 74 6E 49 64 3E 4F 59 63 6C 70 51 |DerivtnId>OYclpQ|
05C0 45 3D 3C 2F 44 65 72 69 76 74 6E 49 64 3E 3C 2F |E=</DerivtnId></|
05D0 4B 45 4B 49 64 3E 3C 4B 65 79 4E 63 72 70 74 6E |KEKId><KeyNcrptn|
05E0 41 6C 67 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 3C |Algo><Algo>DKP9<|
05F0 2F 41 6C 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 74 |/Algo></KeyNcrpt|
0600 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 79 |nAlgo><NcrptdKey|
0610 3E 34 70 41 67 41 42 6B 3D 3C 2F 4E 63 72 70 74 |>4pAgABk=</Ncrpt|
0620 64 4B 65 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 70 |dKey></KEK></Rcp|
0630 74 3E 3C 4D 41 43 41 6C 67 6F 3E 3C 41 6C 67 6F |t><MACAlgo><Algo|
0640 3E 4D 43 43 53 3C 2F 41 6C 67 6F 3E 3C 2F 4D 41 |>MCCS</Algo></MA|
0650 43 41 6C 67 6F 3E 3C 4E 63 70 73 6C 74 64 43 6E |CAlgo><NcpsltdCn|
0660 74 74 3E 3C 43 6E 74 74 54 70 3E 44 41 54 41 3C |tt><CnttTp>DATA<|
0670 2F 43 6E 74 74 54 70 3E 3C 2F 4E 63 70 73 6C 74 |/CnttTp></Ncpslt|

7 Messages Examples - 354 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

0680 64 43 6E 74 74 3E 3C 4D 41 43 3E 75 38 63 72 2F |dCntt><MAC>u8cr/|
0690 79 70 6B 2F 6A 4D 3D 3C 2F 4D 41 43 3E 3C 2F 41 |ypk/jM=</MAC></A|
06A0 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 2F 53 63 |uthntcdData></Sc|
06B0 74 79 54 72 6C 72 3E 3C 2F 41 63 63 70 74 72 43 |tyTrlr></AccptrC|
06C0 78 6C 41 64 76 63 52 73 70 6E 3E 3C 2F 44 6F 63 |xlAdvcRspn></Doc|
06D0 75 6D 65 6E 74 3E |ument> |

7 Messages Examples - 355 - 7.4 Cancellation Messages


Card Payments Message Usage Guide Version 5.0

7.5 Reconciliation Messages

7.5.1 AcceptorReconciliationRequest

For the simplicity of the example, only the two first transactions of the period have been presented.
The reconciliation period 8469 includes the following transactions:

Message Item Transaction 1 Transaction 2 Transaction 3 Transaction 4 Transaction 5 Transaction 6


Auth/Compl Cancellation Auth/Compl Auth/Compl Auth/Compl Auth/Compl
POIGroupIdentification - - - - - -
CardProductProfile 0003 0003 0003 0003 0003 0003
TransactionType CardPayment CardPayment CardPayment Refund CardPayment CardPayment
TransactionDateTime 2013-08- 2013-08- 2013-08- 2013-08- 2013-08- 2013-08-
11T17:22:04. 11T18:34:19. 11T18:41:37. 11T18:42:26. 11T18:48:02. 11T18:50:49.
51+01:00 00+01:00 00+01:00 00+01:00 00+01:00 00+01:00
TransactionReference 002949 002950 002951 002950 002953 002954
OriginalTransaction/ - 002949 - - - -
TransactionReference
Currency EUR EUR EUR EUR EUR EUR
TotalAmount 43.14 43.14 35 29.99 75.50 125.75
Auth.Response Approved - - Approved Approved Declined
TransactionSuccess True - True True True False
type for reconciliation Debit DebitReverse Debit Credit Debit -

The Transaction component of the AcceptorReconciliationRequest contains the information below:

Message Item Value


Transaction
ReconciliationTransaction-
Identification
TransactionDateTime 2013-08-11T19:05:20.39+01:00
TransactionReference 002951
ReconciliationIdentification 8469
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Debit
TotalNumber 3
CumulativeAmount 153.64
TransactionTotals
CardProductProfile 0003
Currency EUR
Type DebitReverse
TotalNumber 1
CumulativeAmount 43.14
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Credit
TotalNumber 1

7 Messages Examples - 356 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

CumulativeAmount 29.99
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Failed
TotalNumber 1
CumulativeAmount 125.75

The resulting XML encoded structure is:


<Tx>
<RcncltnTxId>
<TxDtTm>2013-08-11T19:05:20.39+01:00</TxDtTm>
<TxRef>002951</TxRef>
</RcncltnTxId>
<RcncltnId>8469</RcncltnId>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DEBT</Tp>
<TtlNb>3</TtlNb>
<CmltvAmt>153.64</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>43.14</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>CRDT</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>29.99</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>125.75</CmltvAmt>
</TxTtls>
</Tx>

7 Messages Examples - 357 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorReconciliationRequest is presented below, omitting data structure already


previously detailed.

Message Item Value


AcceptorReconciliationRequest
Header
MessageFunction ReconciliationRequest
ProtocolVersion 5.0
ExchangeIdentifier 152
CreationDateTime 2013-08-11T19:05:40.10+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
ReconciliationRequest
Environment
Acquirer
Identification
Identification 9287351
Type Acquirer
AcquirerParametersVersion 2013-08-07 08:00:00
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 1
Issuer Acquirer
ProtectedCardData
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200022
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData

7 Messages Examples - 358 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

MAC 5B95CF3C7DE65E78

7 Messages Examples - 359 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorReconciliationRequest XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.009.001.05">
<AccptrRcncltnReq>
<Hdr>
<MsgFctn>RCLQ</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>152</XchgId>
<CreDtTm>2013-08-11T19:05:40.10+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<RcncltnReq>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>1</Id>
<Issr>ACQR</Issr>
</POIId>
</Envt>
<Tx>
<RcncltnTxId>
<TxDtTm>2013-08-11T19:05:20.39+01:00</TxDtTm>
<TxRef>002951</TxRef>
</RcncltnTxId>
<RcncltnId>8469</RcncltnId>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DEBT</Tp>
<TtlNb>3</TtlNb>
<CmltvAmt>153.64</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>43.14</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>CRDT</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>29.99</CmltvAmt>
</TxTtls>

7 Messages Examples - 360 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>125.75</CmltvAmt>
</TxTtls>
</Tx>
</RcncltnReq>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgACI=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>4G/gYc9/3us=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrRcncltnReq>
</Document>

7 Messages Examples - 361 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body RcncltnReq (without
spaces or line breaks) is dumped below:
0000 3C 52 63 6E 63 6C 74 6E 52 65 71 3E 3C 45 6E 76 |<RcncltnReq><Env|
0010 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
0020 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
0030 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|
0040 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0050 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0060 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0070 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 64 |rr><MrchntId><Id|
0080 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E |>EPASMER001</Id>|
0090 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 49 |</MrchntId><POII|
00A0 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 |d><Id>1</Id><Iss|
00B0 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 50 |r>ACQR</Issr></P|
00C0 4F 49 49 64 3E 3C 2F 45 6E 76 74 3E 3C 54 78 3E |OIId></Envt><Tx>|
00D0 3C 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C 54 78 |<RcncltnTxId><Tx|
00E0 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 |DtTm>2013-08-11T|
00F0 31 39 3A 30 35 3A 32 30 2E 33 39 2B 30 31 3A 30 |19:05:20.39+01:0|
0100 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 |0</TxDtTm><TxRef|
0110 3E 30 30 32 39 35 31 3C 2F 54 78 52 65 66 3E 3C |>002951</TxRef><|
0120 2F 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C 52 63 |/RcncltnTxId><Rc|
0130 6E 63 6C 74 6E 49 64 3E 38 34 36 39 3C 2F 52 63 |ncltnId>8469</Rc|
0140 6E 63 6C 74 6E 49 64 3E 3C 54 78 54 74 6C 73 3E |ncltnId><TxTtls>|
0150 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 |<CardPdctPrfl>00|
0160 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C |03</CardPdctPrfl|
0170 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C |><Ccy>EUR</Ccy><|
0180 54 70 3E 44 45 42 54 3C 2F 54 70 3E 3C 54 74 6C |Tp>DEBT</Tp><Ttl|
0190 4E 62 3E 33 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C |Nb>3</TtlNb><Cml|
01A0 74 76 41 6D 74 3E 31 35 33 2E 36 34 3C 2F 43 6D |tvAmt>153.64</Cm|
01B0 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E |ltvAmt></TxTtls>|
01C0 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 63 |<TxTtls><CardPdc|
01D0 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 |tPrfl>0003</Card|
01E0 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 55 |PdctPrfl><Ccy>EU|
01F0 52 3C 2F 43 63 79 3E 3C 54 70 3E 44 42 54 52 3C |R</Ccy><Tp>DBTR<|
0200 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 |/Tp><TtlNb>1</Tt|
0210 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 34 33 |lNb><CmltvAmt>43|
0220 2E 31 34 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F |.14</CmltvAmt></|
0230 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C |TxTtls><TxTtls><|
0240 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 30 |CardPdctPrfl>000|
0250 33 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E |3</CardPdctPrfl>|
0260 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 |<Ccy>EUR</Ccy><T|
0270 70 3E 43 52 44 54 3C 2F 54 70 3E 3C 54 74 6C 4E |p>CRDT</Tp><TtlN|
0280 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 |b>1</TtlNb><Cmlt|
0290 76 41 6D 74 3E 32 39 2E 39 39 3C 2F 43 6D 6C 74 |vAmt>29.99</Cmlt|
02A0 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 |vAmt></TxTtls><T|
02B0 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 63 74 50 |xTtls><CardPdctP|
02C0 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 |rfl>0003</CardPd|
02D0 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 55 52 3C |ctPrfl><Ccy>EUR<|
02E0 2F 43 63 79 3E 3C 54 70 3E 46 41 49 4C 3C 2F 54 |/Ccy><Tp>FAIL</T|
02F0 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E |p><TtlNb>1</TtlN|
0300 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 31 32 35 2E |b><CmltvAmt>125.|
0310 37 35 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 |75</CmltvAmt></T|

7 Messages Examples - 362 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0320 78 54 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 52 63 6E |xTtls></Tx></Rcn|
0330 63 6C 74 6E 52 65 71 3E |cltnReq> |

7 Messages Examples - 363 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

The SHA-256 digest of the message body RcncltnReq is:


0000 ED E3 8C 6A E1 F0 17 6A D0 F9 EE 6A 75 92 70 CD |...j...j...ju.p.|
0010 C0 6E 5E DA 9A 76 D7 77 95 CD 87 0B DC 84 04 1A |.n^..v.w........|

After padding, the digest becomes:


0000 ED E3 8C 6A E1 F0 17 6A D0 F9 EE 6A 75 92 70 CD |...j...j...ju.p.|
0010 C0 6E 5E DA 9A 76 D7 77 95 CD 87 0B DC 84 04 1A |.n^..v.w........|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (6D76756D CB46E907 E0C798AD
83256257), we obtain the MAC of the AcceptorReconciliationRequest E06FE061CF7FDEEB and after
conversion into base64 " 4G/gYc9/3us=".
0000 CE CF AD 10 D6 F4 BC 6F 63 C7 65 A0 9C CD 8D E0 |.......oc.e.....|
0010 ED 12 F9 51 4D CD F6 F5 C3 9A 2D 3C 25 2F B0 41 |...QM.....-<%/.A|
0020 E0 6F E0 61 CF 7F DE EB |.o.a.... |

The message sent by the transport protocol is:


0000 00 00 06 84 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 30 39 2E 30 30 31 2E 30 35 22 |caaa.009.001.05"|
00A0 3E 3C 41 63 63 70 74 72 52 63 6E 63 6C 74 6E 52 |><AccptrRcncltnR|
00B0 65 71 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E |eq><Hdr><MsgFctn|
00C0 3E 52 43 4C 51 3C 2F 4D 73 67 46 63 74 6E 3E 3C |>RCLQ</MsgFctn><|
00D0 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F |PrtcolVrsn>5.0</|
00E0 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 |PrtcolVrsn><Xchg|
00F0 49 64 3E 31 35 32 3C 2F 58 63 68 67 49 64 3E 3C |Id>152</XchgId><|
0100 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |CreDtTm>2013-08-|
0110 31 31 54 31 39 3A 30 35 3A 34 30 2E 31 30 2B 30 |11T19:05:40.10+0|
0120 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 |1:00</CreDtTm><I|
0130 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 |nitgPty><Id>6600|
0140 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F |0001</Id><Tp>OPO|
0150 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 |I</Tp><Issr>ACQR|
0160 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 |</Issr></InitgPt|
0170 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 |y><RcptPty><Id>e|
0180 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F |pas-acquirer-1</|
0190 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E |Id><Tp>ACQR</Tp>|
01A0 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E |</RcptPty></Hdr>|
01B0 3C 52 63 6E 63 6C 74 6E 52 65 71 3E 3C 45 6E 76 |<RcncltnReq><Env|
01C0 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 49 64 3E 3C |>ACQR</Tp></Id><|
01F0 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 2D |ParamsVrsn>2013-|
0200 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C 2F |08-07 08:00:00</|
0210 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|

7 Messages Examples - 364 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0220 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 64 |rr><MrchntId><Id|
0230 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E |>EPASMER001</Id>|
0240 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 49 |</MrchntId><POII|
0250 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 |d><Id>1</Id><Iss|
0260 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 50 |r>ACQR</Issr></P|
0270 4F 49 49 64 3E 3C 2F 45 6E 76 74 3E 3C 54 78 3E |OIId></Envt><Tx>|
0280 3C 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C 54 78 |<RcncltnTxId><Tx|
0290 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 31 54 |DtTm>2013-08-11T|
02A0 31 39 3A 30 35 3A 32 30 2E 33 39 2B 30 31 3A 30 |19:05:20.39+01:0|
02B0 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 |0</TxDtTm><TxRef|
02C0 3E 30 30 32 39 35 31 3C 2F 54 78 52 65 66 3E 3C |>002951</TxRef><|
02D0 2F 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C 52 63 |/RcncltnTxId><Rc|
02E0 6E 63 6C 74 6E 49 64 3E 38 34 36 39 3C 2F 52 63 |ncltnId>8469</Rc|
02F0 6E 63 6C 74 6E 49 64 3E 3C 54 78 54 74 6C 73 3E |ncltnId><TxTtls>|
0300 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 |<CardPdctPrfl>00|
0310 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C |03</CardPdctPrfl|
0320 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C |><Ccy>EUR</Ccy><|
0330 54 70 3E 44 45 42 54 3C 2F 54 70 3E 3C 54 74 6C |Tp>DEBT</Tp><Ttl|
0340 4E 62 3E 33 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C |Nb>3</TtlNb><Cml|
0350 74 76 41 6D 74 3E 31 35 33 2E 36 34 3C 2F 43 6D |tvAmt>153.64</Cm|
0360 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E |ltvAmt></TxTtls>|
0370 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 63 |<TxTtls><CardPdc|
0380 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 |tPrfl>0003</Card|
0390 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 55 |PdctPrfl><Ccy>EU|
03A0 52 3C 2F 43 63 79 3E 3C 54 70 3E 44 42 54 52 3C |R</Ccy><Tp>DBTR<|
03B0 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 |/Tp><TtlNb>1</Tt|
03C0 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 34 33 |lNb><CmltvAmt>43|
03D0 2E 31 34 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F |.14</CmltvAmt></|
03E0 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C |TxTtls><TxTtls><|
03F0 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 30 |CardPdctPrfl>000|
0400 33 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E |3</CardPdctPrfl>|
0410 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 |<Ccy>EUR</Ccy><T|
0420 70 3E 43 52 44 54 3C 2F 54 70 3E 3C 54 74 6C 4E |p>CRDT</Tp><TtlN|
0430 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 |b>1</TtlNb><Cmlt|
0440 76 41 6D 74 3E 32 39 2E 39 39 3C 2F 43 6D 6C 74 |vAmt>29.99</Cmlt|
0450 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 |vAmt></TxTtls><T|
0460 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 63 74 50 |xTtls><CardPdctP|
0470 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 |rfl>0003</CardPd|
0480 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 55 52 3C |ctPrfl><Ccy>EUR<|
0490 2F 43 63 79 3E 3C 54 70 3E 46 41 49 4C 3C 2F 54 |/Ccy><Tp>FAIL</T|
04A0 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E |p><TtlNb>1</TtlN|
04B0 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 31 32 35 2E |b><CmltvAmt>125.|
04C0 37 35 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 |75</CmltvAmt></T|
04D0 78 54 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 52 63 6E |xTtls></Tx></Rcn|
04E0 63 6C 74 6E 52 65 71 3E 3C 53 63 74 79 54 72 6C |cltnReq><SctyTrl|
04F0 72 3E 3C 43 6E 74 74 54 70 3E 41 55 54 48 3C 2F |r><CnttTp>AUTH</|
0500 43 6E 74 74 54 70 3E 3C 41 75 74 68 6E 74 63 64 |CnttTp><Authntcd|
0510 44 61 74 61 3E 3C 52 63 70 74 3E 3C 4B 45 4B 3E |Data><Rcpt><KEK>|
0520 3C 4B 45 4B 49 64 3E 3C 4B 65 79 49 64 3E 53 70 |<KEKId><KeyId>Sp|
0530 65 63 56 31 54 65 73 74 4B 65 79 3C 2F 4B 65 79 |ecV1TestKey</Key|
0540 49 64 3E 3C 4B 65 79 56 72 73 6E 3E 32 30 31 30 |Id><KeyVrsn>2010|
0550 30 36 30 37 31 35 3C 2F 4B 65 79 56 72 73 6E 3E |060715</KeyVrsn>|
0560 3C 44 65 72 69 76 74 6E 49 64 3E 4F 59 63 6C 70 |<DerivtnId>OYclp|

7 Messages Examples - 365 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0570 51 45 3D 3C 2F 44 65 72 69 76 74 6E 49 64 3E 3C |QE=</DerivtnId><|
0580 2F 4B 45 4B 49 64 3E 3C 4B 65 79 4E 63 72 70 74 |/KEKId><KeyNcrpt|
0590 6E 41 6C 67 6F 3E 3C 41 6C 67 6F 3E 44 4B 50 39 |nAlgo><Algo>DKP9|
05A0 3C 2F 41 6C 67 6F 3E 3C 2F 4B 65 79 4E 63 72 70 |</Algo></KeyNcrp|
05B0 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 74 64 4B 65 |tnAlgo><NcrptdKe|
05C0 79 3E 34 70 41 67 41 43 49 3D 3C 2F 4E 63 72 70 |y>4pAgACI=</Ncrp|
05D0 74 64 4B 65 79 3E 3C 2F 4B 45 4B 3E 3C 2F 52 63 |tdKey></KEK></Rc|
05E0 70 74 3E 3C 4D 41 43 41 6C 67 6F 3E 3C 41 6C 67 |pt><MACAlgo><Alg|
05F0 6F 3E 4D 43 43 53 3C 2F 41 6C 67 6F 3E 3C 2F 4D |o>MCCS</Algo></M|
0600 41 43 41 6C 67 6F 3E 3C 4E 63 70 73 6C 74 64 43 |ACAlgo><NcpsltdC|
0610 6E 74 74 3E 3C 43 6E 74 74 54 70 3E 44 41 54 41 |ntt><CnttTp>DATA|
0620 3C 2F 43 6E 74 74 54 70 3E 3C 2F 4E 63 70 73 6C |</CnttTp></Ncpsl|
0630 74 64 43 6E 74 74 3E 3C 4D 41 43 3E 57 35 58 50 |tdCntt><MAC>W5XP|
0640 50 48 33 6D 58 6E 67 3D 3C 2F 4D 41 43 3E 3C 2F |PH3mXng=</MAC></|
0650 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 2F 53 |AuthntcdData></S|
0660 63 74 79 54 72 6C 72 3E 3C 2F 41 63 63 70 74 72 |ctyTrlr></Accptr|
0670 52 63 6E 63 6C 74 6E 52 65 71 3E 3C 2F 44 6F 63 |RcncltnReq></Doc|
0680 75 6D 65 6E 74 3E 20 0A |ument> . |

7 Messages Examples - 366 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

7.5.2 AcceptorReconciliationResponse

The response returns the same totals as computed by the Acquirer.

Message Item Value


TransactionResponse
Response Approved
Transaction
ReconciliationTransaction-
Identification
TransactionDateTime 2013-08-11T19:05:20.39+01:00
TransactionReference 002951
ReconciliationIdentification 8469
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Debit
TotalNumber 3
CumulativeAmount 153.64
TransactionTotals
CardProductProfile 0003
Currency EUR
Type DebitReverse
TotalNumber 1
CumulativeAmount 43.14
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Credit
TotalNumber 1
CumulativeAmount 29.99
TransactionTotals
CardProductProfile 0003
Currency EUR
Type Failed
TotalNumber 1
CumulativeAmount 125.75

The resulting XML encoded structures are:


<TxRspn>
<Rspn>APPR</Rspn>
</TxRspn>
<Tx>
<RcncltnTxId>
<TxDtTm>2013-08-11T19:05:20.39+01:00</TxDtTm>
<TxRef>002951</TxRef>
</RcncltnTxId>
<RcncltnId>8469</RcncltnId>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DEBT</Tp>

7 Messages Examples - 367 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

<TtlNb>3</TtlNb>
<CmltvAmt>153.64</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>43.14</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>CRDT</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>29.99</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>125.75</CmltvAmt>
</TxTtls>
</Tx>

7 Messages Examples - 368 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

The complete AcceptorReconciliationResponse is presented below, omitting data structure already


previously detailed.

Message Item Value


AcceptorReconciliationResponse
Header
MessageFunction ReconciliationResponse
ProtocolVersion 5.0
ExchangeIdentifier 152
CreationDateTime 2013-08-11T19:05:51.10+01:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
ReconciliationResponse
Environment
AcquirerIdentification
Identification 9287351
Type Acquirer
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 1
Issuer Acquirer
ProtectedCardData
---
TransactionResponse
---
Transaction
---
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200022
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData

7 Messages Examples - 369 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

MAC 8EB6A42441CEACC6

The AcceptorReconciliationResponse XML message is presented below:

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.010.001.05">
<AccptrRcncltnRspn>
<Hdr>
<MsgFctn>RCLP</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>152</XchgId>
<CreDtTm>2013-08-11T19:05:51.10+01:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<RcncltnRspn>
<Envt>
<AcqrrId>
<Id>9287351</Id>
<Tp>ACQR</Tp>
</AcqrrId>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>1</Id>
<Issr>ACQR</Issr>
</POIId>
</Envt>
<TxRspn>
<Rspn>APPR</Rspn>
</TxRspn>
<Tx>
<RcncltnTxId>
<TxDtTm>2013-08-11T19:05:20.39+01:00</TxDtTm>
<TxRef>002951</TxRef>
</RcncltnTxId>
<RcncltnId>8469</RcncltnId>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DEBT</Tp>
<TtlNb>3</TtlNb>
<CmltvAmt>153.64</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>43.14</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>CRDT</Tp>

7 Messages Examples - 370 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

<TtlNb>1</TtlNb>
<CmltvAmt>29.99</CmltvAmt>
</TxTtls>
<TxTtls>
<CardPdctPrfl>0003</CardPdctPrfl>
<Ccy>EUR</Ccy>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>125.75</CmltvAmt>
</TxTtls>
</Tx>
</RcncltnRspn>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgACI=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>Wk4qVxybL0c=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrRcncltnRspn>
</Document>

7 Messages Examples - 371 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body RcncltnRspn
(without spaces or line breaks) is dumped below:
0000 3C 52 63 6E 63 6C 74 6E 52 73 70 6E 3E 3C 45 6E |<RcncltnRspn><En|
0010 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 3E |vt><AcqrrId><Id>|
0020 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 3E |9287351</Id><Tp>|
0030 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 72 |ACQR</Tp></Acqrr|
0040 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 64 |Id><MrchntId><Id|
0050 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 3E |>EPASMER001</Id>|
0060 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 49 |</MrchntId><POII|
0070 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 73 |d><Id>1</Id><Iss|
0080 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F 50 |r>ACQR</Issr></P|
0090 4F 49 49 64 3E 3C 2F 45 6E 76 74 3E 3C 54 78 52 |OIId></Envt><TxR|
00A0 73 70 6E 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F |spn><Rspn>APPR</|
00B0 52 73 70 6E 3E 3C 2F 54 78 52 73 70 6E 3E 3C 54 |Rspn></TxRspn><T|
00C0 78 3E 3C 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C |x><RcncltnTxId><|
00D0 54 78 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D 31 |TxDtTm>2013-08-1|
00E0 31 54 31 39 3A 30 35 3A 32 30 2E 33 39 2B 30 31 |1T19:05:20.39+01|
00F0 3A 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 |:00</TxDtTm><TxR|
0100 65 66 3E 30 30 32 39 35 31 3C 2F 54 78 52 65 66 |ef>002951</TxRef|
0110 3E 3C 2F 52 63 6E 63 6C 74 6E 54 78 49 64 3E 3C |></RcncltnTxId><|
0120 52 63 6E 63 6C 74 6E 49 64 3E 38 34 36 39 3C 2F |RcncltnId>8469</|
0130 52 63 6E 63 6C 74 6E 49 64 3E 3C 54 78 54 74 6C |RcncltnId><TxTtl|
0140 73 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |s><CardPdctPrfl>|
0150 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 |0003</CardPdctPr|
0160 66 6C 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 |fl><Ccy>EUR</Ccy|
0170 3E 3C 54 70 3E 44 45 42 54 3C 2F 54 70 3E 3C 54 |><Tp>DEBT</Tp><T|
0180 74 6C 4E 62 3E 33 3C 2F 54 74 6C 4E 62 3E 3C 43 |tlNb>3</TtlNb><C|
0190 6D 6C 74 76 41 6D 74 3E 31 35 33 2E 36 34 3C 2F |mltvAmt>153.64</|
01A0 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C |CmltvAmt></TxTtl|
01B0 73 3E 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 50 |s><TxTtls><CardP|
01C0 64 63 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 61 |dctPrfl>0003</Ca|
01D0 72 64 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 3E |rdPdctPrfl><Ccy>|
01E0 45 55 52 3C 2F 43 63 79 3E 3C 54 70 3E 44 42 54 |EUR</Ccy><Tp>DBT|
01F0 52 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F |R</Tp><TtlNb>1</|
0200 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E |TtlNb><CmltvAmt>|
0210 34 33 2E 31 34 3C 2F 43 6D 6C 74 76 41 6D 74 3E |43.14</CmltvAmt>|
0220 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C 73 |</TxTtls><TxTtls|
0230 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 |><CardPdctPrfl>0|
0240 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 66 |003</CardPdctPrf|
0250 6C 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E |l><Ccy>EUR</Ccy>|
0260 3C 54 70 3E 43 52 44 54 3C 2F 54 70 3E 3C 54 74 |<Tp>CRDT</Tp><Tt|
0270 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D |lNb>1</TtlNb><Cm|
0280 6C 74 76 41 6D 74 3E 32 39 2E 39 39 3C 2F 43 6D |ltvAmt>29.99</Cm|
0290 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E |ltvAmt></TxTtls>|
02A0 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 63 |<TxTtls><CardPdc|
02B0 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 64 |tPrfl>0003</Card|
02C0 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 55 |PdctPrfl><Ccy>EU|
02D0 52 3C 2F 43 63 79 3E 3C 54 70 3E 46 41 49 4C 3C |R</Ccy><Tp>FAIL<|
02E0 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 |/Tp><TtlNb>1</Tt|
02F0 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 31 32 |lNb><CmltvAmt>12|
0300 35 2E 37 35 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C |5.75</CmltvAmt><|
0310 2F 54 78 54 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 52 |/TxTtls></Tx></R|

7 Messages Examples - 372 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0320 63 6E 63 6C 74 6E 52 73 70 6E 3E |cncltnRspn> |

7 Messages Examples - 373 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

The SHA-256 digest of the message body RcncltnRspn is:


0000 CD C8 6D E4 D0 8E FE FD 81 CD B0 FB 77 38 19 88 |..m.........w8..|
0010 6F 5A 8F A2 7E 07 D5 E8 FE 86 8E 2E E6 EB 9F 1F |oZ..~...........|

After padding, the digest becomes:


0000 CD C8 6D E4 D0 8E FE FD 81 CD B0 FB 77 38 19 88 |..m.........w8..|
0010 6F 5A 8F A2 7E 07 D5 E8 FE 86 8E 2E E6 EB 9F 1F |oZ..~...........|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (6D76756D 34461607 E0C798AD
7C259D57), we obtain the MAC of the AcceptorReconciliationResponse 5A4E2A571C9B2F47 and
after conversion into base64 "Wk4qVxybL0c=".
0000 C9 39 B7 22 EE 38 8C 6B BC 2A B8 28 FE 8E 31 8A |.9.".8.k.*.(..1.|
0010 79 1B 11 9B A6 66 C7 B5 A6 6C 8E 57 FC 79 4E 75 |y....f...l.W.yNu|
0020 5A 4E 2A 57 1C 9B 2F 47 |ZN*W../G |

The message sent by the transport protocol is:


0000 00 00 06 77 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |...w<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 31 30 2E 30 30 31 2E 30 35 22 |caaa.010.001.05"|
00A0 3E 3C 41 63 63 70 74 72 52 63 6E 63 6C 74 6E 52 |><AccptrRcncltnR|
00B0 73 70 6E 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 |spn><Hdr><MsgFct|
00C0 6E 3E 52 43 4C 50 3C 2F 4D 73 67 46 63 74 6E 3E |n>RCLP</MsgFctn>|
00D0 3C 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C |<PrtcolVrsn>5.0<|
00E0 2F 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 |/PrtcolVrsn><Xch|
00F0 67 49 64 3E 31 35 32 3C 2F 58 63 68 67 49 64 3E |gId>152</XchgId>|
0100 3C 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 |<CreDtTm>2013-08|
0110 2D 31 31 54 31 39 3A 30 35 3A 35 31 2E 31 30 2B |-11T19:05:51.10+|
0120 30 31 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C |01:00</CreDtTm><|
0130 49 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 |InitgPty><Id>660|
0140 30 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 |00001</Id><Tp>OP|
0150 4F 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 |OI</Tp><Issr>ACQ|
0160 52 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 |R</Issr></InitgP|
0170 74 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E |ty><RcptPty><Id>|
0180 65 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C |epas-acquirer-1<|
0190 2F 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 |/Id><Tp>ACQR</Tp|
01A0 3E 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 |></RcptPty></Hdr|
01B0 3E 3C 52 63 6E 63 6C 74 6E 52 73 70 6E 3E 3C 45 |><RcncltnRspn><E|
01C0 6E 76 74 3E 3C 41 63 71 72 72 49 64 3E 3C 49 64 |nvt><AcqrrId><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 54 70 |>9287351</Id><Tp|
01E0 3E 41 43 51 52 3C 2F 54 70 3E 3C 2F 41 63 71 72 |>ACQR</Tp></Acqr|
01F0 72 49 64 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 |rId><MrchntId><I|
0200 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 |d>EPASMER001</Id|
0210 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 |></MrchntId><POI|

7 Messages Examples - 374 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0220 49 64 3E 3C 49 64 3E 31 3C 2F 49 64 3E 3C 49 73 |Id><Id>1</Id><Is|
0230 73 72 3E 41 43 51 52 3C 2F 49 73 73 72 3E 3C 2F |sr>ACQR</Issr></|
0240 50 4F 49 49 64 3E 3C 2F 45 6E 76 74 3E 3C 54 78 |POIId></Envt><Tx|
0250 52 73 70 6E 3E 3C 52 73 70 6E 3E 41 50 50 52 3C |Rspn><Rspn>APPR<|
0260 2F 52 73 70 6E 3E 3C 2F 54 78 52 73 70 6E 3E 3C |/Rspn></TxRspn><|
0270 54 78 3E 3C 52 63 6E 63 6C 74 6E 54 78 49 64 3E |Tx><RcncltnTxId>|
0280 3C 54 78 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |<TxDtTm>2013-08-|
0290 31 31 54 31 39 3A 30 35 3A 32 30 2E 33 39 2B 30 |11T19:05:20.39+0|
02A0 31 3A 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 |1:00</TxDtTm><Tx|
02B0 52 65 66 3E 30 30 32 39 35 31 3C 2F 54 78 52 65 |Ref>002951</TxRe|
02C0 66 3E 3C 2F 52 63 6E 63 6C 74 6E 54 78 49 64 3E |f></RcncltnTxId>|
02D0 3C 52 63 6E 63 6C 74 6E 49 64 3E 38 34 36 39 3C |<RcncltnId>8469<|
02E0 2F 52 63 6E 63 6C 74 6E 49 64 3E 3C 54 78 54 74 |/RcncltnId><TxTt|
02F0 6C 73 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C |ls><CardPdctPrfl|
0300 3E 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 |>0003</CardPdctP|
0310 72 66 6C 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 |rfl><Ccy>EUR</Cc|
0320 79 3E 3C 54 70 3E 44 45 42 54 3C 2F 54 70 3E 3C |y><Tp>DEBT</Tp><|
0330 54 74 6C 4E 62 3E 33 3C 2F 54 74 6C 4E 62 3E 3C |TtlNb>3</TtlNb><|
0340 43 6D 6C 74 76 41 6D 74 3E 31 35 33 2E 36 34 3C |CmltvAmt>153.64<|
0350 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 |/CmltvAmt></TxTt|
0360 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 |ls><TxTtls><Card|
0370 50 64 63 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 |PdctPrfl>0003</C|
0380 61 72 64 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 |ardPdctPrfl><Ccy|
0390 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 70 3E 44 42 |>EUR</Ccy><Tp>DB|
03A0 54 52 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C |TR</Tp><TtlNb>1<|
03B0 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 |/TtlNb><CmltvAmt|
03C0 3E 34 33 2E 31 34 3C 2F 43 6D 6C 74 76 41 6D 74 |>43.14</CmltvAmt|
03D0 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C |></TxTtls><TxTtl|
03E0 73 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |s><CardPdctPrfl>|
03F0 30 30 30 33 3C 2F 43 61 72 64 50 64 63 74 50 72 |0003</CardPdctPr|
0400 66 6C 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 |fl><Ccy>EUR</Ccy|
0410 3E 3C 54 70 3E 43 52 44 54 3C 2F 54 70 3E 3C 54 |><Tp>CRDT</Tp><T|
0420 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 |tlNb>1</TtlNb><C|
0430 6D 6C 74 76 41 6D 74 3E 32 39 2E 39 39 3C 2F 43 |mltvAmt>29.99</C|
0440 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 |mltvAmt></TxTtls|
0450 3E 3C 54 78 54 74 6C 73 3E 3C 43 61 72 64 50 64 |><TxTtls><CardPd|
0460 63 74 50 72 66 6C 3E 30 30 30 33 3C 2F 43 61 72 |ctPrfl>0003</Car|
0470 64 50 64 63 74 50 72 66 6C 3E 3C 43 63 79 3E 45 |dPdctPrfl><Ccy>E|
0480 55 52 3C 2F 43 63 79 3E 3C 54 70 3E 46 41 49 4C |UR</Ccy><Tp>FAIL|
0490 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 |</Tp><TtlNb>1</T|
04A0 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 31 |tlNb><CmltvAmt>1|
04B0 32 35 2E 37 35 3C 2F 43 6D 6C 74 76 41 6D 74 3E |25.75</CmltvAmt>|
04C0 3C 2F 54 78 54 74 6C 73 3E 3C 2F 54 78 3E 3C 2F |</TxTtls></Tx></|
04D0 52 63 6E 63 6C 74 6E 52 73 70 6E 3E 3C 53 63 74 |RcncltnRspn><Sct|
04E0 79 54 72 6C 72 3E 3C 43 6E 74 74 54 70 3E 41 55 |yTrlr><CnttTp>AU|
04F0 54 48 3C 2F 43 6E 74 74 54 70 3E 3C 41 75 74 68 |TH</CnttTp><Auth|
0500 6E 74 63 64 44 61 74 61 3E 3C 52 63 70 74 3E 3C |ntcdData><Rcpt><|
0510 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B 65 79 49 |KEK><KEKId><KeyI|
0520 64 3E 53 70 65 63 56 31 54 65 73 74 4B 65 79 3C |d>SpecV1TestKey<|
0530 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 73 6E 3E |/KeyId><KeyVrsn>|
0540 32 30 31 30 30 36 30 37 31 35 3C 2F 4B 65 79 56 |2010060715</KeyV|
0550 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 64 3E 4F |rsn><DerivtnId>O|
0560 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 76 74 6E |YclpQE=</Derivtn|

7 Messages Examples - 375 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

0570 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B 65 79 4E |Id></KEKId><KeyN|
0580 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F 3E |crptnAlgo><Algo>|
0590 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F 4B 65 79 |DKP9</Algo></Key|
05A0 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 70 |NcrptnAlgo><Ncrp|
05B0 74 64 4B 65 79 3E 34 70 41 67 41 43 49 3D 3C 2F |tdKey>4pAgACI=</|
05C0 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B 45 4B 3E |NcrptdKey></KEK>|
05D0 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 6C 67 6F 3E |</Rcpt><MACAlgo>|
05E0 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F 41 6C 67 6F |<Algo>MCCS</Algo|
05F0 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C 4E 63 70 73 |></MACAlgo><Ncps|
0600 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 3E |ltdCntt><CnttTp>|
0610 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 2F 4E |DATA</CnttTp></N|
0620 63 70 73 6C 74 64 43 6E 74 74 3E 3C 4D 41 43 3E |cpsltdCntt><MAC>|
0630 6A 72 61 6B 4A 45 48 4F 72 4D 59 3D 3C 2F 4D 41 |jrakJEHOrMY=</MA|
0640 43 3E 3C 2F 41 75 74 68 6E 74 63 64 44 61 74 61 |C></AuthntcdData|
0650 3E 3C 2F 53 63 74 79 54 72 6C 72 3E 3C 2F 41 63 |></SctyTrlr></Ac|
0660 63 70 74 72 52 63 6E 63 6C 74 6E 52 73 70 6E 3E |cptrRcncltnRspn>|
0670 3C 2F 44 6F 63 75 6D 65 6E 74 3E |</Document> |

7 Messages Examples - 376 - 7.5 Reconciliation Messages


Card Payments Message Usage Guide Version 5.0

7.6 Batch Transfer messages

The Key Encryption Key is the DUKPT key, named SpecV1TesKey, with the version 2010060715,
which is the test key with the following values:
BDK (Base Derivation Key): 37233E89 0B0104E9 BC943D0E 45EAE5A7
KSN (Key Serial Number): 398725A501 E290200017
TIK (Terminal Initial Key): EE3AE644 1C2EEE18 3F3B4179 2DBCD318
MAC Encryption Key Request: 5E64F1AB F25D3BA1 7F629EC2 B302F8EA
MAC Encryption Key Response: 5E64F1AB 0D5DC4A1 7F629EC2 4C0207EA

7.6.1 AcceptorBatchTransfer
The acceptor batch transfer 433 includes the following transactions:

Message Item Transaction 1 Transaction 2 Transaction 3 Transaction 4 Transaction 5 Transaction 6 Transaction 7 Transaction 8
Cancellation Cancellation Completion Completion Completion Completion Completion Completion
CardProductProfile 0017 0017 0018 0018 0017 0017 0017 018
TransactionType - - CardPayment CardPayment CardPayment CardPayment Refund Refund
TransactionDateTime 2015-12- 2015-12- 2015-12- 2015-12- 2015-12- 2015-12- 2015-12- 2015-12-
03T14:43:50. 03T14:36:46.00 03T14:33:03.00 03T14:31:34.00 03T14:28:40.00 03T14:23:37.00 03T14:22:15. 03T14:07:55.00
000 0 0 0 0 0 000 0
TransactionReference 130220 130219 130218 130217 130216 130215 130214 130213
OriginalTransaction/ 130213 130216 - - - - - -
TransactionReference
TransactionType of Refund CardPayment - - - - - -
OriginalTransaction
Currency EUR EUR EUR EUR EUR EUR EUR EUR
TotalAmount 2.16 2.18 0.01 15.21 2.18 2.17 2.17 2.16
Auth.Response - - Approved Approved Approved Approved - -
TransactionSuccess True True True True True True False True

The Transaction component of the AcceptorReconciliationRequest contains the information below:


Message Item Value
AcceptorBatchTransfer
Header
DownloadTransfer false
CreationDateTime 2015-12-03T15:33:52.366Z
ExchangeIdentification 433
BatchTransfer
TransactionTotals
Type CreditReverse
TotalNumber 1
CumulativeAmount 2.16
TransactionTotals
Type DebitReverse
TotalNumber 1
CumulativeAmount 2.18
TransactionTotals
Type Debit
TotalNumber 4
CumulativeAmount 19.57

7 Messages Examples - 377 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

TransactionTotals
Type Failed
TotalNumber 1
CumulativeAmount 2.17
TransactionTotals
Type Credit
TotalNumber 1
CumulativeAmount 2.16

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.011.001.05">
<AccptrBtchTrf>
<Hdr>
<DwnldTrf>false</DwnldTrf>
<FrmtVrsn>5.0</FrmtVrsn>
<XchgId>433</XchgId>
<CreDtTm>2015-12-03T15:33:52.366Z</CreDtTm>
<InitgPty>
<Id>POI ID set by ACQ 03</Id>
</InitgPty>
</Hdr>
<BtchTrf>
<TxTtls>
<Tp>CRDR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.16</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.18</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>DEBT</Tp>
<TtlNb>3</TtlNb>
<CmltvAmt>17.39</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.17</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>CRDT</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.16</CmltvAmt>
</TxTtls>
<DataSet>
<DataSetId>
<Nm>DataSet0</Nm>
<Tp>TXCP</Tp>

7 Messages Examples - 378 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<CreDtTm>2015-12-03T15:33:52.349Z</CreDtTm>
</DataSetId>
<TxTtls>
<Tp>CRDR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.16</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>DBTR</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.18</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>DEBT</Tp>
<TtlNb>4</TtlNb>
<CmltvAmt>19.57</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>FAIL</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.17</CmltvAmt>
</TxTtls>
<TxTtls>
<Tp>CRDT</Tp>
<TtlNb>1</TtlNb>
<CmltvAmt>2.16</CmltvAmt>
</TxTtls>
<Tx>
<Cxl>
<TxSeqCntr>1</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
</POI>
<Card>
<PlainCardData>
<PAN>5071009999100013</PAN>
<CardSeqNb>01</CardSeqNb>
<FctvDt>2012-01</FctvDt>

7 Messages Examples - 379 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<XpryDt>2020-12</XpryDt>
<SvcCd>901</SvcCd>
</PlainCardData>
<CardCtryCd>FRA</CardCtryCd>
<CardPdctPrfl>0017</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<OnLineCntxt>false</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
</Cntxt>
<Tx>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:03:50.000</TxDtTm>
<TxRef>130220</TxRef>
</TxId>
<OrgnlTx>
<TxId>
<TxDtTm>2015-12-03T14:07:55.000</TxDtTm>
<TxRef>130213</TxRef>
</TxId>
<TxTp>RFND</TxTp>
<TxRslt>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</TxRslt>
</OrgnlTx>
<TxSucss>true</TxSucss>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>2.16</TtlAmt>
<ICCRltdData>nwIGAAAAAAIRnwMGAAAAAAAAnyYI4q1Ux/OxIbtfJQMSAQGCAj0
AhwEBnzYCAH2fCQIAAp8nAQCfNAM/AACEB6AAAABCEBCfHggwMTEyMjMzNJ8Q
EgEQAAAAAAAAAAAAAAAAAAAAAJ8zA+D4yJ8aAgAQnzUBIpUFAAAAAABfKgIJe
JoDFRIDn0E DEwIRnAEAnzcEvx8tlsoE3ggQAMUBAJsCIAA=</ICCRltdData>
</TxDtls>
</Tx>
</Cxl>
</Tx>
<Tx>
<Cxl>
<TxSeqCntr>2</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>

7 Messages Examples - 380 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
</POI>
<Card>
<PlainCardData>
<PAN>5071009999100013</PAN>
<CardSeqNb>01</CardSeqNb>
<FctvDt>2012-01</FctvDt>
<XpryDt>2020-12</XpryDt>
<SvcCd>901</SvcCd>
</PlainCardData>
<CardCtryCd>FRA</CardCtryCd>
<CardPdctPrfl>0017</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<OnLineCntxt>false</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
</Cntxt>
<Tx>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:36:46.000</TxDtTm>
<TxRef>130219</TxRef>
</TxId>
<OrgnlTx>
<TxId>
<TxDtTm>2015-12-03T14:28:40.000</TxDtTm>
<TxRef>130216</TxRef>
</TxId>
<TxTp>CRDP</TxTp>
</OrgnlTx>
<TxSucss>true</TxSucss>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>2.01</TtlAmt>
<ICCRltdData>nwIGAAAAAAIBnwMGAAAAAAAAnyYICM6qQatyZvJfJQMSAQGCAj0
AhwEBnzYCAH2fCQIAAp8nAQCfNAM/AACEB6AAAABCEBCfHggwMTEyMjMzNJ8Q

7 Messages Examples - 381 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

EgEQAAAAAAAAAAAAAAAAAAAAAJ8zA+D4yJ8aAgAQnzUBIpUFAAAAAABfKgIJe
JoDFRIDn0EDEwIJnAEAnzcE+eslScoE3ggQAMUBAJsCIAA=</ICCRltdData>
</TxDtls>
</Tx>
</Cxl>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>3</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>

7 Messages Examples - 382 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>
<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>5413330010000710</PAN>
<CardSeqNb>00</CardSeqNb>
<FctvDt>2010-12</FctvDt>
<XpryDt>2015-12</XpryDt>
<SvcCd>201</SvcCd>
</PlainCardData>
<CardCtryCd>DEU</CardCtryCd>
<CardPdctPrfl>0018</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CrdhldrPres>true</CrdhldrPres>
<OnLineCntxt>true</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203143303</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>

7 Messages Examples - 383 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<TxDtTm>2015-12-03T14:33:03.000</TxDtTm>
<TxRef>130218</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<Rvsl>false</Rvsl>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>0.01</TtlAmt>
<ICCRltdData>nwIGAAAAAAABnwMGAAAAAAAAnyYI2nt5MGXoqUlfJQMQEgGCAlg
AnzYCESKfCQIAAp8nAUCfNANBAwKEB6AAAAAEEBCfHggwMTEyMjMzNJ8QEgEQ
AAAAAAAAAAAAAAAAAAAAAJ8zA+D4yJ8aAgAQnzUBIpUFAgAAAABfKgIJeJoDF
RIDn0EDEwIYnAEAnzcEfvCtgsoE//xQAMUBAJsC6AA=</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
</Tx>
</Cmpltn>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>4</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>

7 Messages Examples - 384 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>
<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>5413330010000710</PAN>
<CardSeqNb>00</CardSeqNb>
<FctvDt>2010-12</FctvDt>
<XpryDt>2015-12</XpryDt>
<SvcCd>201</SvcCd>
</PlainCardData>
<CardCtryCd>DEU</CardCtryCd>
<CardPdctPrfl>0018</CardPdctPrfl>

7 Messages Examples - 385 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CrdhldrPres>true</CrdhldrPres>
<OnLineCntxt>true</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203143134</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:31:34.000</TxDtTm>
<TxRef>130217</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<Rvsl>false</Rvsl>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>15.21</TtlAmt>
<ICCRltdData>nwIGAAAAABUhnwMGAAAAAAAAnyYISdok4KmN04lfJQMQEgGCAlg
AnzYCESKfCQIAAp8nAUCfNANBAwKEB6AAAAAEEBCfHggwMTEyMjMzNJ8QEgEQ
AAAAAAAAAAAAAAAAAAAAAJ8zA+D4yJ8aAgAQnzUBIpUFAgAAAABfKgIJeJoDF
RIDn0EDEwIXnAEAnzcEWjCuxsoE//xQAMUBAJsC6AA=</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
</Tx>
</Cmpltn>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>5</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>

7 Messages Examples - 386 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>

7 Messages Examples - 387 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>5071009999100013</PAN>
<XpryDt>2020-12</XpryDt>
</PlainCardData>
<CardPdctPrfl>0017</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CardPres>false</CardPres>
<CrdhldrPres>false</CrdhldrPres>
<OnLineCntxt>true</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>PHYS</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203142840</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:28:40.000</TxDtTm>
<TxRef>130216</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<Rvsl>false</Rvsl>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>2.18</TtlAmt>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>

7 Messages Examples - 388 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

</Tx>
</Cmpltn>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>6</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>

7 Messages Examples - 389 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>
<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>50710099112277049</PAN>
<XpryDt>2018-03</XpryDt>
</PlainCardData>
<CardPdctPrfl>0017</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CrdhldrPres>true</CrdhldrPres>
<OnLineCntxt>true</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>MGST</CardDataNtryMd>
<FllbckInd>FFLB</FllbckInd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203142337</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>CRDP</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:23:37.000</TxDtTm>
<TxRef>130215</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<Rvsl>false</Rvsl>
<TxDtls>

7 Messages Examples - 390 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<Ccy>EUR</Ccy>
<TtlAmt>2.17</TtlAmt>
<ICCRltdData>nwIGAAAAAAIXnwMGAAAAAAAAnwkCAACfNAM/AACfHggwMTEyMjM
zNJ8zA+D4yJ8aAgAQnzUBIpUFBAAAAABfKgIJeJoDFRIDn0EDEwIVnAEAygTf
+AfgxQEEmwLIAA==</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
</Tx>
</Cmpltn>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>7</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>
<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>

7 Messages Examples - 391 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>
<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>5071009999100013</PAN>
<CardSeqNb>01</CardSeqNb>
<FctvDt>2012-01</FctvDt>
<XpryDt>2020-12</XpryDt>
<SvcCd>901</SvcCd>
</PlainCardData>
<CardCtryCd>FRA</CardCtryCd>
<CardPdctPrfl>0017</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CrdhldrPres>true</CrdhldrPres>
<OnLineCntxt>false</OnLineCntxt>

7 Messages Examples - 392 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203142215</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>RFND</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:22:15.000</TxDtTm>
<TxRef>130214</TxRef>
</TxId>
<TxSucss>false</TxSucss>
<Rvsl>false</Rvsl>
<FailrRsn>UCMP</FailrRsn>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>2.17</TtlAmt>
<ICCRltdData>nwIGAAAAAAIXnwMGAAAAAAAAXyUDEgEBggI9AIcBAZ8JagACnz
QDPwAAhAegAAAAQhAQnx4IMDExMjIzMzSfMwPg+MIfGgIAEJ81ASKVBQAAAA
AAXyoCCXiaAxUSA59BAxMCFJwBAJ83BOP9DcbKBN4IEADFAQCbAgAA
</ICCRltdData>
</TxDtls>
</Tx>
</Cmpltn>
</Tx>
<Tx>
<Cmpltn>
<TxSeqCntr>8</TxSeqCntr>
<Envt>
<Acqrr>
<Id>
<Id>000000000123</Id>
</Id>
<ParamsVrsn>20110913123456</ParamsVrsn>
</Acqrr>
<Mrchnt>
<Id>
<Id>MyMerchantID000</Id>
</Id>
<CmonNm>TestLab,certificationAVE,SEPA</CmonNm>
</Mrchnt>
<POI>
<Id>
<Id>88000001</Id>
</Id>
<Cpblties>
<CardRdngCpblties>PHYS</CardRdngCpblties>
<CardRdngCpblties>MGST</CardRdngCpblties>
<CardRdngCpblties>CICC</CardRdngCpblties>

7 Messages Examples - 393 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<CardRdngCpblties>ECTL</CardRdngCpblties>
<CrdhldrVrfctnCpblties>FCPN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>NPIN</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>MNSG</CrdhldrVrfctnCpblties>
<CrdhldrVrfctnCpblties>FEPN</CrdhldrVrfctnCpblties>
<OnLineCpblties>SMON</OnLineCpblties>
<MsgCpblties>
<Dstn>MDSP</Dstn>
<NbOfLines>8</NbOfLines>
<LineWidth>15</LineWidth>
</MsgCpblties>
<MsgCpblties>
<Dstn>MRCP</Dstn>
<LineWidth>24</LineWidth>
</MsgCpblties>
</Cpblties>
<Cmpnt>
<Tp>TERM</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>ICT250</Id>
<SrlNb>1122334</SrlNb>
</Id>
</Cmpnt>
<Cmpnt>
<Tp>APLI</Tp>
<Id>
<PrvdrId>INGENICO</PrvdrId>
<Id>SEPA-FAST</Id>
</Id>
<Sts>
<VrsnNb>04.10</VrsnNb>
</Sts>
<StdCmplc>
<Id>SEPA-FAST</Id>
<Vrsn>3.1</Vrsn>
<Issr>OSCAR</Issr>
</StdCmplc>
<Assmnt>
<Tp>CERT</Tp>
<Assgnr>OSCAR</Assgnr>
<DlvryDt>2014-05-14T17:12:05.000Z</DlvryDt>
<XprtnDt>2021-01-12T09:07:18.000Z</XprtnDt>
<Nb>PAY.ELI.ING.POI.120.13030002</Nb>
</Assmnt>
</Cmpnt>
</POI>
<Card>
<PlainCardData>
<PAN>5413330010000710</PAN>
<CardSeqNb>00</CardSeqNb>
<FctvDt>2010-12</FctvDt>
<XpryDt>2015-12</XpryDt>

7 Messages Examples - 394 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<SvcCd>201</SvcCd>
</PlainCardData>
<CardCtryCd>DEU</CardCtryCd>
<CardPdctPrfl>0018</CardPdctPrfl>
<CardBrnd>CB</CardBrnd>
</Card>
</Envt>
<Cntxt>
<PmtCntxt>
<CrdhldrPres>true</CrdhldrPres>
<OnLineCntxt>true</OnLineCntxt>
<AttndncCntxt>ATTD</AttndncCntxt>
<CardDataNtryMd>CICC</CardDataNtryMd>
</PmtCntxt>
<SaleCntxt>
<SaleRefNb>0000000011111111/20151203140755</SaleRefNb>
<CshrId>00000001</CshrId>
</SaleCntxt>
</Cntxt>
<Tx>
<TxTp>RFND</TxTp>
<MrchntCtgyCd>5999</MrchntCtgyCd>
<TxId>
<TxDtTm>2015-12-03T14:07:55.000</TxDtTm>
<TxRef>130213</TxRef>
</TxId>
<TxSucss>true</TxSucss>
<Rvsl>false</Rvsl>
<TxDtls>
<Ccy>EUR</Ccy>
<TtlAmt>2.16</TtlAmt>
<ICCRltdData>nwIGAAAAAAIWnwMGAAAAAAAAnyYIUcB/x3j58/BfJQMQEgGCAlg
AnzYCESKfCQIAAp8nAQCfNAM/AACEB6AAAAAEEBCfHggwMTEyMjMzNJ8QEgEQ
AAAAAAAAAAAAAAAAAAAAAJ8zA+D4yJ8aAgAQnzUBIpUFAAAAAABfKgIJeJoDF
RIDn0EDEwITnAEAnzcEJo1jMMoE/gwQAMUBAJsCIAA=</ICCRltdData>
</TxDtls>
<AuthstnRslt>
<AuthstnNtty>
<Tp>CISS</Tp>
</AuthstnNtty>
<RspnToAuthstn>
<Rspn>APPR</Rspn>
</RspnToAuthstn>
<AuthstnCd>032983</AuthstnCd>
</AuthstnRslt>
</Tx>
</Cmpltn>
</Tx>
</DataSet>
</BtchTrf>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>

7 Messages Examples - 395 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>yvGTVKwvnXI=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrBtchTrf>
</Document>

The XML encoded message body BtchTrf (without spaces or line breaks) is dumped below:
0000 3C 42 74 63 68 54 72 66 3E 3C 54 78 54 74 6C 73 |<BtchTrf><TxTtls|
0010 3E 3C 54 70 3E 43 52 44 52 3C 2F 54 70 3E 3C 54 |><Tp>CRDR</Tp><T|
0020 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 |tlNb>1</TtlNb><C|
0030 6D 6C 74 76 41 6D 74 3E 32 2E 31 36 3C 2F 43 6D |mltvAmt>2.16</Cm|
0040 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E |ltvAmt></TxTtls>|
0050 3C 54 78 54 74 6C 73 3E 3C 54 70 3E 44 42 54 52 |<TxTtls><Tp>DBTR|
0060 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 |</Tp><TtlNb>1</T|
0070 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 |tlNb><CmltvAmt>2|
0080 2E 31 38 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F |.18</CmltvAmt></|
0090 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C |TxTtls><TxTtls><|
00A0 54 70 3E 44 45 42 54 3C 2F 54 70 3E 3C 54 74 6C |Tp>DEBT</Tp><Ttl|
00B0 4E 62 3E 33 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C |Nb>3</TtlNb><Cml|
00C0 74 76 41 6D 74 3E 31 37 2E 33 39 3C 2F 43 6D 6C |tvAmt>17.39</Cml|
00D0 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C |tvAmt></TxTtls><|
00E0 54 78 54 74 6C 73 3E 3C 54 70 3E 46 41 49 4C 3C |TxTtls><Tp>FAIL<|
00F0 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 |/Tp><TtlNb>1</Tt|
0100 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E |lNb><CmltvAmt>2.|
0110 31 37 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 |17</CmltvAmt></T|
0120 78 54 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 |xTtls><TxTtls><T|
0130 70 3E 43 52 44 54 3C 2F 54 70 3E 3C 54 74 6C 4E |p>CRDT</Tp><TtlN|
0140 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 |b>1</TtlNb><Cmlt|
0150 76 41 6D 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 76 |vAmt>2.16</Cmltv|
0160 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 44 61 |Amt></TxTtls><Da|
0170 74 61 53 65 74 3E 3C 44 61 74 61 53 65 74 49 64 |taSet><DataSetId|
0180 3E 3C 4E 6D 3E 44 61 74 61 53 65 74 30 3C 2F 4E |><Nm>DataSet0</N|
0190 6D 3E 3C 54 70 3E 54 58 43 50 3C 2F 54 70 3E 3C |m><Tp>TXCP</Tp><|
01A0 43 72 65 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D |CreDtTm>2015-12-|
01B0 30 33 54 31 35 3A 33 33 3A 35 32 2E 33 34 39 5A |03T15:33:52.349Z|
01C0 3C 2F 43 72 65 44 74 54 6D 3E 3C 2F 44 61 74 61 |</CreDtTm></Data|
01D0 53 65 74 49 64 3E 3C 54 78 54 74 6C 73 3E 3C 54 |SetId><TxTtls><T|
01E0 70 3E 43 52 44 52 3C 2F 54 70 3E 3C 54 74 6C 4E |p>CRDR</Tp><TtlN|
01F0 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 |b>1</TtlNb><Cmlt|
0200 76 41 6D 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 76 |vAmt>2.16</Cmltv|
0210 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 |Amt></TxTtls><Tx|

7 Messages Examples - 396 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0220 54 74 6C 73 3E 3C 54 70 3E 44 42 54 52 3C 2F 54 |Ttls><Tp>DBTR</T|
0230 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E |p><TtlNb>1</TtlN|
0240 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 38 |b><CmltvAmt>2.18|
0250 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 |</CmltvAmt></TxT|
0260 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E |tls><TxTtls><Tp>|
0270 44 45 42 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E |DEBT</Tp><TtlNb>|
0280 34 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 |4</TtlNb><CmltvA|
0290 6D 74 3E 31 39 2E 35 37 3C 2F 43 6D 6C 74 76 41 |mt>19.57</CmltvA|
02A0 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 54 |mt></TxTtls><TxT|
02B0 74 6C 73 3E 3C 54 70 3E 46 41 49 4C 3C 2F 54 70 |tls><Tp>FAIL</Tp|
02C0 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 |><TtlNb>1</TtlNb|
02D0 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 37 3C |><CmltvAmt>2.17<|
02E0 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 |/CmltvAmt></TxTt|
02F0 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E 43 |ls><TxTtls><Tp>C|
0300 52 44 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 |RDT</Tp><TtlNb>1|
0310 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D |</TtlNb><CmltvAm|
0320 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 76 41 6D 74 |t>2.16</CmltvAmt|
0330 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 3E 3C 43 |></TxTtls><Tx><C|
0340 78 6C 3E 3C 54 78 53 65 71 43 6E 74 72 3E 31 3C |xl><TxSeqCntr>1<|
0350 2F 54 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 |/TxSeqCntr><Envt|
0360 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E |><Acqrr><Id><Id>|
0370 30 30 30 30 30 30 30 30 30 31 32 33 3C 2F 49 64 |000000000123</Id|
0380 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 |></Id><ParamsVrs|
0390 6E 3E 32 30 31 31 30 39 31 33 31 32 33 34 35 36 |n>20110913123456|
03A0 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 |</ParamsVrsn></A|
03B0 63 71 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 |cqrr><Mrchnt><Id|
03C0 3E 3C 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 |><Id>MyMerchantI|
03D0 44 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 |D000</Id></Id><C|
03E0 6D 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 |monNm>TestLab,ce|
03F0 72 74 69 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 |rtificationAVE,S|
0400 45 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 |EPA</CmonNm></Mr|
0410 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 |chnt><POI><Id><I|
0420 64 3E 38 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C |d>88000001</Id><|
0430 2F 49 64 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E |/Id></POI><Card>|
0440 3C 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C |<PlainCardData><|
0450 50 41 4E 3E 35 30 37 31 30 30 39 39 39 39 31 30 |PAN>507100999910|
0460 30 30 31 33 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 |0013</PAN><CardS|
0470 65 71 4E 62 3E 30 31 3C 2F 43 61 72 64 53 65 71 |eqNb>01</CardSeq|
0480 4E 62 3E 3C 46 63 74 76 44 74 3E 32 30 31 32 2D |Nb><FctvDt>2012-|
0490 30 31 3C 2F 46 63 74 76 44 74 3E 3C 58 70 72 79 |01</FctvDt><Xpry|
04A0 44 74 3E 32 30 32 30 2D 31 32 3C 2F 58 70 72 79 |Dt>2020-12</Xpry|
04B0 44 74 3E 3C 53 76 63 43 64 3E 39 30 31 3C 2F 53 |Dt><SvcCd>901</S|
04C0 76 63 43 64 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 |vcCd></PlainCard|
04D0 44 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 64 |Data><CardCtryCd|
04E0 3E 46 52 41 3C 2F 43 61 72 64 43 74 72 79 43 64 |>FRA</CardCtryCd|
04F0 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 |><CardPdctPrfl>0|
0500 30 31 37 3C 2F 43 61 72 64 50 64 63 74 50 72 66 |017</CardPdctPrf|
0510 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F |l><CardBrnd>CB</|
0520 43 61 72 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E |CardBrnd></Card>|
0530 3C 2F 45 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 |</Envt><Cntxt><P|
0540 6D 74 43 6E 74 78 74 3E 3C 4F 6E 4C 69 6E 65 43 |mtCntxt><OnLineC|
0550 6E 74 78 74 3E 66 61 6C 73 65 3C 2F 4F 6E 4C 69 |ntxt>false</OnLi|
0560 6E 65 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 |neCntxt><Attndnc|
0570 43 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E |Cntxt>ATTD</Attn|
0580 64 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 |dncCntxt><CardDa|
0590 74 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 |taNtryMd>CICC</C|
05A0 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F |ardDataNtryMd></|
05B0 50 6D 74 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 |PmtCntxt></Cntxt|
05C0 3E 3C 54 78 3E 3C 4D 72 63 68 6E 74 43 74 67 79 |><Tx><MrchntCtgy|
05D0 43 64 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 |Cd>5999</MrchntC|
05E0 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 |tgyCd><TxId><TxD|
05F0 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 |tTm>2015-12-03T1|
0600 34 3A 30 33 3A 35 30 2E 30 30 30 3C 2F 54 78 44 |4:03:50.000</TxD|
0610 74 54 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 32 |tTm><TxRef>13022|
0620 30 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E |0</TxRef></TxId>|
0630 3C 4F 72 67 6E 6C 54 78 3E 3C 54 78 49 64 3E 3C |<OrgnlTx><TxId><|
0640 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 |TxDtTm>2015-12-0|
0650 33 54 31 34 3A 30 37 3A 35 35 2E 30 30 30 3C 2F |3T14:07:55.000</|

7 Messages Examples - 397 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0660 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 31 33 |TxDtTm><TxRef>13|
0670 30 32 31 33 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 |0213</TxRef></Tx|
0680 49 64 3E 3C 54 78 54 70 3E 52 46 4E 44 3C 2F 54 |Id><TxTp>RFND</T|
0690 78 54 70 3E 3C 54 78 52 73 6C 74 3E 3C 52 73 70 |xTp><TxRslt><Rsp|
06A0 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E |nToAuthstn><Rspn|
06B0 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 |>APPR</Rspn></Rs|
06C0 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 |pnToAuthstn><Aut|
06D0 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 |hstnCd>032983</A|
06E0 75 74 68 73 74 6E 43 64 3E 3C 2F 54 78 52 73 6C |uthstnCd></TxRsl|
06F0 74 3E 3C 2F 4F 72 67 6E 6C 54 78 3E 3C 54 78 53 |t></OrgnlTx><TxS|
0700 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 75 63 |ucss>true</TxSuc|
0710 73 73 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E |ss><TxDtls><Ccy>|
0720 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 |EUR</Ccy><TtlAmt|
0730 3E 32 2E 31 36 3C 2F 54 74 6C 41 6D 74 3E 3C 49 |>2.16</TtlAmt><I|
0740 43 43 52 6C 74 64 44 61 74 61 3E 6E 77 49 47 41 |CCRltdData>nwIGA|
0750 41 41 41 41 41 49 52 6E 77 4D 47 41 41 41 41 41 |AAAAAIRnwMGAAAAA|
0760 41 41 41 6E 79 59 49 34 71 31 55 78 2F 4F 78 49 |AAAnyYI4q1Ux/OxI|
0770 62 74 66 4A 51 4D 53 41 51 47 43 41 6A 30 41 68 |btfJQMSAQGCAj0Ah|
0780 77 45 42 6E 7A 59 43 41 48 32 66 43 51 49 41 41 |wEBnzYCAH2fCQIAA|
0790 70 38 6E 41 51 43 66 4E 41 4D 2F 41 41 43 45 42 |p8nAQCfNAM/AACEB|
07A0 36 41 41 41 41 42 43 45 42 43 66 48 67 67 77 4D |6AAAABCEBCfHggwM|
07B0 54 45 79 4D 6A 4D 7A 4E 4A 38 51 45 67 45 51 41 |TEyMjMzNJ8QEgEQA|
07C0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
07D0 41 41 41 41 4A 38 7A 41 2B 44 34 79 4A 38 61 41 |AAAAJ8zA+D4yJ8aA|
07E0 67 41 51 6E 7A 55 42 49 70 55 46 41 41 41 41 41 |gAQnzUBIpUFAAAAA|
07F0 41 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 6E |ABfKgIJeJoDFRIDn|
0800 30 45 20 20 20 44 45 77 49 52 6E 41 45 41 6E 7A |0E DEwIRnAEAnz|
0810 63 45 76 78 38 74 6C 73 6F 45 33 67 67 51 41 4D |cEvx8tlsoE3ggQAM|
0820 55 42 41 4A 73 43 49 41 41 3D 3C 2F 49 43 43 52 |UBAJsCIAA=</ICCR|
0830 6C 74 64 44 61 74 61 3E 3C 2F 54 78 44 74 6C 73 |ltdData></TxDtls|
0840 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 3E 3C 2F 54 78 |></Tx></Cxl></Tx|
0850 3E 3C 54 78 3E 3C 43 78 6C 3E 3C 54 78 53 65 71 |><Tx><Cxl><TxSeq|
0860 43 6E 74 72 3E 32 3C 2F 54 78 53 65 71 43 6E 74 |Cntr>2</TxSeqCnt|
0870 72 3E 3C 45 6E 76 74 3E 3C 41 63 71 72 72 3E 3C |r><Envt><Acqrr><|
0880 49 64 3E 3C 49 64 3E 30 30 30 30 30 30 30 30 30 |Id><Id>000000000|
0890 31 32 33 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 50 61 |123</Id></Id><Pa|
08A0 72 61 6D 73 56 72 73 6E 3E 32 30 31 31 30 39 31 |ramsVrsn>2011091|
08B0 33 31 32 33 34 35 36 3C 2F 50 61 72 61 6D 73 56 |3123456</ParamsV|
08C0 72 73 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D 72 63 |rsn></Acqrr><Mrc|
08D0 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E 4D 79 4D 65 |hnt><Id><Id>MyMe|
08E0 72 63 68 61 6E 74 49 44 30 30 30 3C 2F 49 64 3E |rchantID000</Id>|
08F0 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 54 65 73 |</Id><CmonNm>Tes|
0900 74 4C 61 62 2C 63 65 72 74 69 66 69 63 61 74 69 |tLab,certificati|
0910 6F 6E 41 56 45 2C 53 45 50 41 3C 2F 43 6D 6F 6E |onAVE,SEPA</Cmon|
0920 4E 6D 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 |Nm></Mrchnt><POI|
0930 3E 3C 49 64 3E 3C 49 64 3E 38 38 30 30 30 30 30 |><Id><Id>8800000|
0940 31 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 2F 50 4F 49 |1</Id></Id></POI|
0950 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 6E 43 61 72 |><Card><PlainCar|
0960 64 44 61 74 61 3E 3C 50 41 4E 3E 35 30 37 31 30 |dData><PAN>50710|
0970 30 39 39 39 39 31 30 30 30 31 33 3C 2F 50 41 4E |09999100013</PAN|
0980 3E 3C 43 61 72 64 53 65 71 4E 62 3E 30 31 3C 2F |><CardSeqNb>01</|
0990 43 61 72 64 53 65 71 4E 62 3E 3C 46 63 74 76 44 |CardSeqNb><FctvD|
09A0 74 3E 32 30 31 32 2D 30 31 3C 2F 46 63 74 76 44 |t>2012-01</FctvD|
09B0 74 3E 3C 58 70 72 79 44 74 3E 32 30 32 30 2D 31 |t><XpryDt>2020-1|
09C0 32 3C 2F 58 70 72 79 44 74 3E 3C 53 76 63 43 64 |2</XpryDt><SvcCd|
09D0 3E 39 30 31 3C 2F 53 76 63 43 64 3E 3C 2F 50 6C |>901</SvcCd></Pl|
09E0 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 43 61 72 |ainCardData><Car|
09F0 64 43 74 72 79 43 64 3E 46 52 41 3C 2F 43 61 72 |dCtryCd>FRA</Car|
0A00 64 43 74 72 79 43 64 3E 3C 43 61 72 64 50 64 63 |dCtryCd><CardPdc|
0A10 74 50 72 66 6C 3E 30 30 31 37 3C 2F 43 61 72 64 |tPrfl>0017</Card|
0A20 50 64 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 |PdctPrfl><CardBr|
0A30 6E 64 3E 43 42 3C 2F 43 61 72 64 42 72 6E 64 3E |nd>CB</CardBrnd>|
0A40 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 |</Card></Envt><C|
0A50 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
0A60 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 66 61 6C 73 |OnLineCntxt>fals|
0A70 65 3C 2F 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 3C |e</OnLineCntxt><|
0A80 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 54 |AttndncCntxt>ATT|
0A90 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E |D</AttndncCntxt>|

7 Messages Examples - 398 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0AA0 3C 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E |<CardDataNtryMd>|
0AB0 43 49 43 43 3C 2F 43 61 72 64 44 61 74 61 4E 74 |CICC</CardDataNt|
0AC0 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E |ryMd></PmtCntxt>|
0AD0 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E 3C 4D 72 63 |</Cntxt><Tx><Mrc|
0AE0 68 6E 74 43 74 67 79 43 64 3E 35 39 39 39 3C 2F |hntCtgyCd>5999</|
0AF0 4D 72 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 78 |MrchntCtgyCd><Tx|
0B00 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 2D |Id><TxDtTm>2015-|
0B10 31 32 2D 30 33 54 31 34 3A 33 36 3A 34 36 2E 30 |12-03T14:36:46.0|
0B20 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 |00</TxDtTm><TxRe|
0B30 66 3E 31 33 30 32 31 39 3C 2F 54 78 52 65 66 3E |f>130219</TxRef>|
0B40 3C 2F 54 78 49 64 3E 3C 4F 72 67 6E 6C 54 78 3E |</TxId><OrgnlTx>|
0B50 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 |<TxId><TxDtTm>20|
0B60 31 35 2D 31 32 2D 30 33 54 31 34 3A 32 38 3A 34 |15-12-03T14:28:4|
0B70 30 2E 30 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 |0.000</TxDtTm><T|
0B80 78 52 65 66 3E 31 33 30 32 31 36 3C 2F 54 78 52 |xRef>130216</TxR|
0B90 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 78 54 70 3E |ef></TxId><TxTp>|
0BA0 43 52 44 50 3C 2F 54 78 54 70 3E 3C 2F 4F 72 67 |CRDP</TxTp></Org|
0BB0 6E 6C 54 78 3E 3C 54 78 53 75 63 73 73 3E 74 72 |nlTx><TxSucss>tr|
0BC0 75 65 3C 2F 54 78 53 75 63 73 73 3E 3C 54 78 44 |ue</TxSucss><TxD|
0BD0 74 6C 73 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 |tls><Ccy>EUR</Cc|
0BE0 79 3E 3C 54 74 6C 41 6D 74 3E 32 2E 30 31 3C 2F |y><TtlAmt>2.01</|
0BF0 54 74 6C 41 6D 74 3E 3C 49 43 43 52 6C 74 64 44 |TtlAmt><ICCRltdD|
0C00 61 74 61 3E 6E 77 49 47 41 41 41 41 41 41 49 42 |ata>nwIGAAAAAAIB|
0C10 6E 77 4D 47 41 41 41 41 41 41 41 41 6E 79 59 49 |nwMGAAAAAAAAnyYI|
0C20 43 4D 36 71 51 61 74 79 5A 76 4A 66 4A 51 4D 53 |CM6qQatyZvJfJQMS|
0C30 41 51 47 43 41 6A 30 41 68 77 45 42 6E 7A 59 43 |AQGCAj0AhwEBnzYC|
0C40 41 48 32 66 43 51 49 41 41 70 38 6E 41 51 43 66 |AH2fCQIAAp8nAQCf|
0C50 4E 41 4D 2F 41 41 43 45 42 36 41 41 41 41 42 43 |NAM/AACEB6AAAABC|
0C60 45 42 43 66 48 67 67 77 4D 54 45 79 4D 6A 4D 7A |EBCfHggwMTEyMjMz|
0C70 4E 4A 38 51 45 67 45 51 41 41 41 41 41 41 41 41 |NJ8QEgEQAAAAAAAA|
0C80 41 41 41 41 41 41 41 41 41 41 41 41 41 4A 38 7A |AAAAAAAAAAAAAJ8z|
0C90 41 2B 44 34 79 4A 38 61 41 67 41 51 6E 7A 55 42 |A+D4yJ8aAgAQnzUB|
0CA0 49 70 55 46 41 41 41 41 41 41 42 66 4B 67 49 4A |IpUFAAAAAABfKgIJ|
0CB0 65 4A 6F 44 46 52 49 44 6E 30 45 44 45 77 49 4A |eJoDFRIDn0EDEwIJ|
0CC0 6E 41 45 41 6E 7A 63 45 2B 65 73 6C 53 63 6F 45 |nAEAnzcE+eslScoE|
0CD0 33 67 67 51 41 4D 55 42 41 4A 73 43 49 41 41 3D |3ggQAMUBAJsCIAA=|
0CE0 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F |</ICCRltdData></|
0CF0 54 78 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 43 78 |TxDtls></Tx></Cx|
0D00 6C 3E 3C 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 6C |l></Tx><Tx><Cmpl|
0D10 74 6E 3E 3C 54 78 53 65 71 43 6E 74 72 3E 33 3C |tn><TxSeqCntr>3<|
0D20 2F 54 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 |/TxSeqCntr><Envt|
0D30 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E |><Acqrr><Id><Id>|
0D40 30 30 30 30 30 30 30 30 30 31 32 33 3C 2F 49 64 |000000000123</Id|
0D50 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 |></Id><ParamsVrs|
0D60 6E 3E 32 30 31 31 30 39 31 33 31 32 33 34 35 36 |n>20110913123456|
0D70 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 |</ParamsVrsn></A|
0D80 63 71 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 |cqrr><Mrchnt><Id|
0D90 3E 3C 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 |><Id>MyMerchantI|
0DA0 44 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 |D000</Id></Id><C|
0DB0 6D 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 |monNm>TestLab,ce|
0DC0 72 74 69 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 |rtificationAVE,S|
0DD0 45 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 |EPA</CmonNm></Mr|
0DE0 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 |chnt><POI><Id><I|
0DF0 64 3E 38 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C |d>88000001</Id><|
0E00 2F 49 64 3E 3C 43 70 62 6C 74 69 65 73 3E 3C 43 |/Id><Cpblties><C|
0E10 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
0E20 50 48 59 53 3C 2F 43 61 72 64 52 64 6E 67 43 70 |PHYS</CardRdngCp|
0E30 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 |blties><CardRdng|
0E40 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F 43 |Cpblties>MGST</C|
0E50 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
0E60 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |<CardRdngCpbltie|
0E70 73 3E 43 49 43 43 3C 2F 43 61 72 64 52 64 6E 67 |s>CICC</CardRdng|
0E80 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 |Cpblties><CardRd|
0E90 6E 67 43 70 62 6C 74 69 65 73 3E 45 43 54 4C 3C |ngCpblties>ECTL<|
0EA0 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |/CardRdngCpbltie|
0EB0 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
0EC0 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 |Cpblties>FCPN</C|
0ED0 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|

7 Messages Examples - 399 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0EE0 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
0EF0 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E |ctnCpblties>NPIN|
0F00 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
0F10 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
0F20 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4D |VrfctnCpblties>M|
0F30 4E 53 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |NSG</CrdhldrVrfc|
0F40 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 |tnCpblties><Crdh|
0F50 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
0F60 73 3E 46 45 50 4E 3C 2F 43 72 64 68 6C 64 72 56 |s>FEPN</CrdhldrV|
0F70 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F |rfctnCpblties><O|
0F80 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D |nLineCpblties>SM|
0F90 4F 4E 3C 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 |ON</OnLineCpblti|
0FA0 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E |es><MsgCpblties>|
0FB0 3C 44 73 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 6E |<Dstn>MDSP</Dstn|
0FC0 3E 3C 4E 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F 4E |><NbOfLines>8</N|
0FD0 62 4F 66 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 |bOfLines><LineWi|
0FE0 64 74 68 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 74 |dth>15</LineWidt|
0FF0 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E |h></MsgCpblties>|
1000 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
1010 74 6E 3E 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4C |tn>MRCP</Dstn><L|
1020 69 6E 65 57 69 64 74 68 3E 32 34 3C 2F 4C 69 6E |ineWidth>24</Lin|
1030 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C |eWidth></MsgCpbl|
1040 74 69 65 73 3E 3C 2F 43 70 62 6C 74 69 65 73 3E |ties></Cpblties>|
1050 3C 43 6D 70 6E 74 3E 3C 54 70 3E 54 45 52 4D 3C |<Cmpnt><Tp>TERM<|
1060 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 |/Tp><Id><PrvdrId|
1070 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 |>INGENICO</Prvdr|
1080 49 64 3E 3C 49 64 3E 49 43 54 32 35 30 3C 2F 49 |Id><Id>ICT250</I|
1090 64 3E 3C 53 72 6C 4E 62 3E 31 31 32 32 33 33 34 |d><SrlNb>1122334|
10A0 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 |</SrlNb></Id></C|
10B0 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |mpnt><Cmpnt><Tp>|
10C0 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 |APLI</Tp><Id><Pr|
10D0 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F |vdrId>INGENICO</|
10E0 50 72 76 64 72 49 64 3E 3C 49 64 3E 53 45 50 41 |PrvdrId><Id>SEPA|
10F0 2D 46 41 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |-FAST</Id></Id><|
1100 53 74 73 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E 31 |Sts><VrsnNb>04.1|
1110 30 3C 2F 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 3E |0</VrsnNb></Sts>|
1120 3C 53 74 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 45 |<StdCmplc><Id>SE|
1130 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 56 72 73 |PA-FAST</Id><Vrs|
1140 6E 3E 33 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 73 |n>3.1</Vrsn><Iss|
1150 72 3E 4F 53 43 41 52 3C 2F 49 73 73 72 3E 3C 2F |r>OSCAR</Issr></|
1160 53 74 64 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E 74 |StdCmplc><Assmnt|
1170 3E 3C 54 70 3E 43 45 52 54 3C 2F 54 70 3E 3C 41 |><Tp>CERT</Tp><A|
1180 73 73 67 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 73 |ssgnr>OSCAR</Ass|
1190 67 6E 72 3E 3C 44 6C 76 72 79 44 74 3E 32 30 31 |gnr><DlvryDt>201|
11A0 34 2D 30 35 2D 31 34 54 31 37 3A 31 32 3A 30 35 |4-05-14T17:12:05|
11B0 2E 30 30 30 5A 3C 2F 44 6C 76 72 79 44 74 3E 3C |.000Z</DlvryDt><|
11C0 58 70 72 74 6E 44 74 3E 32 30 32 31 2D 30 31 2D |XprtnDt>2021-01-|
11D0 31 32 54 30 39 3A 30 37 3A 31 38 2E 30 30 30 5A |12T09:07:18.000Z|
11E0 3C 2F 58 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 41 |</XprtnDt><Nb>PA|
11F0 59 2E 45 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 32 |Y.ELI.ING.POI.12|
1200 30 2E 31 33 30 33 30 30 30 32 3C 2F 4E 62 3E 3C |0.13030002</Nb><|
1210 2F 41 73 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 3E |/Assmnt></Cmpnt>|
1220 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C 61 |</POI><Card><Pla|
1230 69 6E 43 61 72 64 44 61 74 61 3E 3C 50 41 4E 3E |inCardData><PAN>|
1240 35 34 31 33 33 33 30 30 31 30 30 30 30 37 31 30 |5413330010000710|
1250 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 65 71 4E 62 |</PAN><CardSeqNb|
1260 3E 30 30 3C 2F 43 61 72 64 53 65 71 4E 62 3E 3C |>00</CardSeqNb><|
1270 46 63 74 76 44 74 3E 32 30 31 30 2D 31 32 3C 2F |FctvDt>2010-12</|
1280 46 63 74 76 44 74 3E 3C 58 70 72 79 44 74 3E 32 |FctvDt><XpryDt>2|
1290 30 31 35 2D 31 32 3C 2F 58 70 72 79 44 74 3E 3C |015-12</XpryDt><|
12A0 53 76 63 43 64 3E 32 30 31 3C 2F 53 76 63 43 64 |SvcCd>201</SvcCd|
12B0 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 44 61 74 61 |></PlainCardData|
12C0 3E 3C 43 61 72 64 43 74 72 79 43 64 3E 44 45 55 |><CardCtryCd>DEU|
12D0 3C 2F 43 61 72 64 43 74 72 79 43 64 3E 3C 43 61 |</CardCtryCd><Ca|
12E0 72 64 50 64 63 74 50 72 66 6C 3E 30 30 31 38 3C |rdPdctPrfl>0018<|
12F0 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E 3C 43 |/CardPdctPrfl><C|
1300 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 61 72 64 |ardBrnd>CB</Card|
1310 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E |Brnd></Card></En|

7 Messages Examples - 400 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1320 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 6E |vt><Cntxt><PmtCn|
1330 74 78 74 3E 3C 43 72 64 68 6C 64 72 50 72 65 73 |txt><CrdhldrPres|
1340 3E 74 72 75 65 3C 2F 43 72 64 68 6C 64 72 50 72 |>true</CrdhldrPr|
1350 65 73 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E |es><OnLineCntxt>|
1360 74 72 75 65 3C 2F 4F 6E 4C 69 6E 65 43 6E 74 78 |true</OnLineCntx|
1370 74 3E 3C 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E |t><AttndncCntxt>|
1380 41 54 54 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 |ATTD</AttndncCnt|
1390 78 74 3E 3C 43 61 72 64 44 61 74 61 4E 74 72 79 |xt><CardDataNtry|
13A0 4D 64 3E 43 49 43 43 3C 2F 43 61 72 64 44 61 74 |Md>CICC</CardDat|
13B0 61 4E 74 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 |aNtryMd></PmtCnt|
13C0 78 74 3E 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 |xt><SaleCntxt><S|
13D0 61 6C 65 52 65 66 4E 62 3E 30 30 30 30 30 30 30 |aleRefNb>0000000|
13E0 30 31 31 31 31 31 31 31 31 2F 32 30 31 35 31 32 |011111111/201512|
13F0 30 33 31 34 33 33 30 33 3C 2F 53 61 6C 65 52 65 |03143303</SaleRe|
1400 66 4E 62 3E 3C 43 73 68 72 49 64 3E 30 30 30 30 |fNb><CshrId>0000|
1410 30 30 30 31 3C 2F 43 73 68 72 49 64 3E 3C 2F 53 |0001</CshrId></S|
1420 61 6C 65 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 |aleCntxt></Cntxt|
1430 3E 3C 54 78 3E 3C 54 78 54 70 3E 43 52 44 50 3C |><Tx><TxTp>CRDP<|
1440 2F 54 78 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 |/TxTp><MrchntCtg|
1450 79 43 64 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 |yCd>5999</Mrchnt|
1460 43 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 |CtgyCd><TxId><Tx|
1470 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 |DtTm>2015-12-03T|
1480 31 34 3A 33 33 3A 30 33 2E 30 30 30 3C 2F 54 78 |14:33:03.000</Tx|
1490 44 74 54 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 |DtTm><TxRef>1302|
14A0 31 38 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 |18</TxRef></TxId|
14B0 3E 3C 54 78 53 75 63 73 73 3E 74 72 75 65 3C 2F |><TxSucss>true</|
14C0 54 78 53 75 63 73 73 3E 3C 52 76 73 6C 3E 66 61 |TxSucss><Rvsl>fa|
14D0 6C 73 65 3C 2F 52 76 73 6C 3E 3C 54 78 44 74 6C |lse</Rvsl><TxDtl|
14E0 73 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E |s><Ccy>EUR</Ccy>|
14F0 3C 54 74 6C 41 6D 74 3E 30 2E 30 31 3C 2F 54 74 |<TtlAmt>0.01</Tt|
1500 6C 41 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 |lAmt><ICCRltdDat|
1510 61 3E 6E 77 49 47 41 41 41 41 41 41 41 42 6E 77 |a>nwIGAAAAAAABnw|
1520 4D 47 41 41 41 41 41 41 41 41 6E 79 59 49 32 6E |MGAAAAAAAAnyYI2n|
1530 74 35 4D 47 58 6F 71 55 6C 66 4A 51 4D 51 45 67 |t5MGXoqUlfJQMQEg|
1540 47 43 41 6C 67 41 6E 7A 59 43 45 53 4B 66 43 51 |GCAlgAnzYCESKfCQ|
1550 49 41 41 70 38 6E 41 55 43 66 4E 41 4E 42 41 77 |IAAp8nAUCfNANBAw|
1560 4B 45 42 36 41 41 41 41 41 45 45 42 43 66 48 67 |KEB6AAAAAEEBCfHg|
1570 67 77 4D 54 45 79 4D 6A 4D 7A 4E 4A 38 51 45 67 |gwMTEyMjMzNJ8QEg|
1580 45 51 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |EQAAAAAAAAAAAAAA|
1590 41 41 41 41 41 41 41 4A 38 7A 41 2B 44 34 79 4A |AAAAAAAJ8zA+D4yJ|
15A0 38 61 41 67 41 51 6E 7A 55 42 49 70 55 46 41 67 |8aAgAQnzUBIpUFAg|
15B0 41 41 41 41 42 66 4B 67 49 4A 65 4A 6F 44 46 52 |AAAABfKgIJeJoDFR|
15C0 49 44 6E 30 45 44 45 77 49 59 6E 41 45 41 6E 7A |IDn0EDEwIYnAEAnz|
15D0 63 45 66 76 43 74 67 73 6F 45 2F 2F 78 51 41 4D |cEfvCtgsoE//xQAM|
15E0 55 42 41 4A 73 43 36 41 41 3D 3C 2F 49 43 43 52 |UBAJsC6AA=</ICCR|
15F0 6C 74 64 44 61 74 61 3E 3C 2F 54 78 44 74 6C 73 |ltdData></TxDtls|
1600 3E 3C 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C 41 |><AuthstnRslt><A|
1610 75 74 68 73 74 6E 4E 74 74 79 3E 3C 54 70 3E 43 |uthstnNtty><Tp>C|
1620 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 74 68 73 74 |ISS</Tp></Authst|
1630 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 6F 41 75 74 |nNtty><RspnToAut|
1640 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 50 50 52 3C |hstn><Rspn>APPR<|
1650 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E 54 6F 41 75 |/Rspn></RspnToAu|
1660 74 68 73 74 6E 3E 3C 41 75 74 68 73 74 6E 43 64 |thstn><AuthstnCd|
1670 3E 30 33 32 39 38 33 3C 2F 41 75 74 68 73 74 6E |>032983</Authstn|
1680 43 64 3E 3C 2F 41 75 74 68 73 74 6E 52 73 6C 74 |Cd></AuthstnRslt|
1690 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 6C 74 6E 3E 3C |></Tx></Cmpltn><|
16A0 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 6C 74 6E 3E |/Tx><Tx><Cmpltn>|
16B0 3C 54 78 53 65 71 43 6E 74 72 3E 34 3C 2F 54 78 |<TxSeqCntr>4</Tx|
16C0 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 3E 3C 41 |SeqCntr><Envt><A|
16D0 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 30 30 |cqrr><Id><Id>000|
16E0 30 30 30 30 30 30 31 32 33 3C 2F 49 64 3E 3C 2F |000000123</Id></|
16F0 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 |Id><ParamsVrsn>2|
1700 30 31 31 30 39 31 33 31 32 33 34 35 36 3C 2F 50 |0110913123456</P|
1710 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 72 |aramsVrsn></Acqr|
1720 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C 49 |r><Mrchnt><Id><I|
1730 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 44 30 30 |d>MyMerchantID00|
1740 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E |0</Id></Id><Cmon|
1750 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 72 74 69 |Nm>TestLab,certi|

7 Messages Examples - 401 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1760 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 45 50 41 |ficationAVE,SEPA|
1770 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 6E |</CmonNm></Mrchn|
1780 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 3E 38 |t><POI><Id><Id>8|
1790 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C 2F 49 64 |8000001</Id></Id|
17A0 3E 3C 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 |><Cpblties><Card|
17B0 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 50 48 59 |RdngCpblties>PHY|
17C0 53 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |S</CardRdngCpblt|
17D0 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
17E0 6C 74 69 65 73 3E 4D 47 53 54 3C 2F 43 61 72 64 |lties>MGST</Card|
17F0 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 |RdngCpblties><Ca|
1800 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 43 |rdRdngCpblties>C|
1810 49 43 43 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |ICC</CardRdngCpb|
1820 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
1830 70 62 6C 74 69 65 73 3E 45 43 54 4C 3C 2F 43 61 |pblties>ECTL</Ca|
1840 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
1850 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
1860 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 72 64 68 |lties>FCPN</Crdh|
1870 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
1880 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
1890 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E 3C 2F 43 |Cpblties>NPIN</C|
18A0 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
18B0 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
18C0 63 74 6E 43 70 62 6C 74 69 65 73 3E 4D 4E 53 47 |ctnCpblties>MNSG|
18D0 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
18E0 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
18F0 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 |VrfctnCpblties>F|
1900 45 50 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |EPN</CrdhldrVrfc|
1910 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 |tnCpblties><OnLi|
1920 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C |neCpblties>SMON<|
1930 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E |/OnLineCpblties>|
1940 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 |<MsgCpblties><Ds|
1950 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E |tn>MDSP</Dstn><N|
1960 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F 4E 62 4F 66 |bOfLines>8</NbOf|
1970 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 |Lines><LineWidth|
1980 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C |>15</LineWidth><|
1990 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 |/MsgCpblties><Ms|
19A0 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E |gCpblties><Dstn>|
19B0 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4C 69 6E 65 |MRCP</Dstn><Line|
19C0 57 69 64 74 68 3E 32 34 3C 2F 4C 69 6E 65 57 69 |Width>24</LineWi|
19D0 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 |dth></MsgCpbltie|
19E0 73 3E 3C 2F 43 70 62 6C 74 69 65 73 3E 3C 43 6D |s></Cpblties><Cm|
19F0 70 6E 74 3E 3C 54 70 3E 54 45 52 4D 3C 2F 54 70 |pnt><Tp>TERM</Tp|
1A00 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 4E |><Id><PrvdrId>IN|
1A10 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 3E |GENICO</PrvdrId>|
1A20 3C 49 64 3E 49 43 54 32 35 30 3C 2F 49 64 3E 3C |<Id>ICT250</Id><|
1A30 53 72 6C 4E 62 3E 31 31 32 32 33 33 34 3C 2F 53 |SrlNb>1122334</S|
1A40 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 6D 70 6E |rlNb></Id></Cmpn|
1A50 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 41 50 4C |t><Cmpnt><Tp>APL|
1A60 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 |I</Tp><Id><Prvdr|
1A70 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 |Id>INGENICO</Prv|
1A80 64 72 49 64 3E 3C 49 64 3E 53 45 50 41 2D 46 41 |drId><Id>SEPA-FA|
1A90 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 53 74 73 |ST</Id></Id><Sts|
1AA0 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E 31 30 3C 2F |><VrsnNb>04.10</|
1AB0 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 3E 3C 53 74 |VrsnNb></Sts><St|
1AC0 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 45 50 41 2D |dCmplc><Id>SEPA-|
1AD0 46 41 53 54 3C 2F 49 64 3E 3C 56 72 73 6E 3E 33 |FAST</Id><Vrsn>3|
1AE0 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 73 72 3E 4F |.1</Vrsn><Issr>O|
1AF0 53 43 41 52 3C 2F 49 73 73 72 3E 3C 2F 53 74 64 |SCAR</Issr></Std|
1B00 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E 74 3E 3C 54 |Cmplc><Assmnt><T|
1B10 70 3E 43 45 52 54 3C 2F 54 70 3E 3C 41 73 73 67 |p>CERT</Tp><Assg|
1B20 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 73 67 6E 72 |nr>OSCAR</Assgnr|
1B30 3E 3C 44 6C 76 72 79 44 74 3E 32 30 31 34 2D 30 |><DlvryDt>2014-0|
1B40 35 2D 31 34 54 31 37 3A 31 32 3A 30 35 2E 30 30 |5-14T17:12:05.00|
1B50 30 5A 3C 2F 44 6C 76 72 79 44 74 3E 3C 58 70 72 |0Z</DlvryDt><Xpr|
1B60 74 6E 44 74 3E 32 30 32 31 2D 30 31 2D 31 32 54 |tnDt>2021-01-12T|
1B70 30 39 3A 30 37 3A 31 38 2E 30 30 30 5A 3C 2F 58 |09:07:18.000Z</X|
1B80 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 41 59 2E 45 |prtnDt><Nb>PAY.E|
1B90 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 32 30 2E 31 |LI.ING.POI.120.1|

7 Messages Examples - 402 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1BA0 33 30 33 30 30 30 32 3C 2F 4E 62 3E 3C 2F 41 73 |3030002</Nb></As|
1BB0 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 3E 3C 2F 50 |smnt></Cmpnt></P|
1BC0 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 6E 43 |OI><Card><PlainC|
1BD0 61 72 64 44 61 74 61 3E 3C 50 41 4E 3E 35 34 31 |ardData><PAN>541|
1BE0 33 33 33 30 30 31 30 30 30 30 37 31 30 3C 2F 50 |3330010000710</P|
1BF0 41 4E 3E 3C 43 61 72 64 53 65 71 4E 62 3E 30 30 |AN><CardSeqNb>00|
1C00 3C 2F 43 61 72 64 53 65 71 4E 62 3E 3C 46 63 74 |</CardSeqNb><Fct|
1C10 76 44 74 3E 32 30 31 30 2D 31 32 3C 2F 46 63 74 |vDt>2010-12</Fct|
1C20 76 44 74 3E 3C 58 70 72 79 44 74 3E 32 30 31 35 |vDt><XpryDt>2015|
1C30 2D 31 32 3C 2F 58 70 72 79 44 74 3E 3C 53 76 63 |-12</XpryDt><Svc|
1C40 43 64 3E 32 30 31 3C 2F 53 76 63 43 64 3E 3C 2F |Cd>201</SvcCd></|
1C50 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 43 |PlainCardData><C|
1C60 61 72 64 43 74 72 79 43 64 3E 44 45 55 3C 2F 43 |ardCtryCd>DEU</C|
1C70 61 72 64 43 74 72 79 43 64 3E 3C 43 61 72 64 50 |ardCtryCd><CardP|
1C80 64 63 74 50 72 66 6C 3E 30 30 31 38 3C 2F 43 61 |dctPrfl>0018</Ca|
1C90 72 64 50 64 63 74 50 72 66 6C 3E 3C 43 61 72 64 |rdPdctPrfl><Card|
1CA0 42 72 6E 64 3E 43 42 3C 2F 43 61 72 64 42 72 6E |Brnd>CB</CardBrn|
1CB0 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E |d></Card></Envt>|
1CC0 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 |<Cntxt><PmtCntxt|
1CD0 3E 3C 43 72 64 68 6C 64 72 50 72 65 73 3E 74 72 |><CrdhldrPres>tr|
1CE0 75 65 3C 2F 43 72 64 68 6C 64 72 50 72 65 73 3E |ue</CrdhldrPres>|
1CF0 3C 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 74 72 75 |<OnLineCntxt>tru|
1D00 65 3C 2F 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 3C |e</OnLineCntxt><|
1D10 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 54 |AttndncCntxt>ATT|
1D20 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E |D</AttndncCntxt>|
1D30 3C 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E |<CardDataNtryMd>|
1D40 43 49 43 43 3C 2F 43 61 72 64 44 61 74 61 4E 74 |CICC</CardDataNt|
1D50 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E |ryMd></PmtCntxt>|
1D60 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C 65 |<SaleCntxt><Sale|
1D70 52 65 66 4E 62 3E 30 30 30 30 30 30 30 30 31 31 |RefNb>0000000011|
1D80 31 31 31 31 31 31 2F 32 30 31 35 31 32 30 33 31 |111111/201512031|
1D90 34 33 31 33 34 3C 2F 53 61 6C 65 52 65 66 4E 62 |43134</SaleRefNb|
1DA0 3E 3C 43 73 68 72 49 64 3E 30 30 30 30 30 30 30 |><CshrId>0000000|
1DB0 31 3C 2F 43 73 68 72 49 64 3E 3C 2F 53 61 6C 65 |1</CshrId></Sale|
1DC0 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C 54 |Cntxt></Cntxt><T|
1DD0 78 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 78 |x><TxTp>CRDP</Tx|
1DE0 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 |Tp><MrchntCtgyCd|
1DF0 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 67 |>5999</MrchntCtg|
1E00 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 |yCd><TxId><TxDtT|
1E10 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 34 3A |m>2015-12-03T14:|
1E20 33 31 3A 33 34 2E 30 30 30 3C 2F 54 78 44 74 54 |31:34.000</TxDtT|
1E30 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 31 37 3C |m><TxRef>130217<|
1E40 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 |/TxRef></TxId><T|
1E50 78 53 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 |xSucss>true</TxS|
1E60 75 63 73 73 3E 3C 52 76 73 6C 3E 66 61 6C 73 65 |ucss><Rvsl>false|
1E70 3C 2F 52 76 73 6C 3E 3C 54 78 44 74 6C 73 3E 3C |</Rvsl><TxDtls><|
1E80 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 |Ccy>EUR</Ccy><Tt|
1E90 6C 41 6D 74 3E 31 35 2E 32 31 3C 2F 54 74 6C 41 |lAmt>15.21</TtlA|
1EA0 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E |mt><ICCRltdData>|
1EB0 6E 77 49 47 41 41 41 41 41 42 55 68 6E 77 4D 47 |nwIGAAAAABUhnwMG|
1EC0 41 41 41 41 41 41 41 41 6E 79 59 49 53 64 6F 6B |AAAAAAAAnyYISdok|
1ED0 34 4B 6D 4E 30 34 6C 66 4A 51 4D 51 45 67 47 43 |4KmN04lfJQMQEgGC|
1EE0 41 6C 67 41 6E 7A 59 43 45 53 4B 66 43 51 49 41 |AlgAnzYCESKfCQIA|
1EF0 41 70 38 6E 41 55 43 66 4E 41 4E 42 41 77 4B 45 |Ap8nAUCfNANBAwKE|
1F00 42 36 41 41 41 41 41 45 45 42 43 66 48 67 67 77 |B6AAAAAEEBCfHggw|
1F10 4D 54 45 79 4D 6A 4D 7A 4E 4A 38 51 45 67 45 51 |MTEyMjMzNJ8QEgEQ|
1F20 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
1F30 41 41 41 41 41 4A 38 7A 41 2B 44 34 79 4A 38 61 |AAAAAJ8zA+D4yJ8a|
1F40 41 67 41 51 6E 7A 55 42 49 70 55 46 41 67 41 41 |AgAQnzUBIpUFAgAA|
1F50 41 41 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 |AABfKgIJeJoDFRID|
1F60 6E 30 45 44 45 77 49 58 6E 41 45 41 6E 7A 63 45 |n0EDEwIXnAEAnzcE|
1F70 57 6A 43 75 78 73 6F 45 2F 2F 78 51 41 4D 55 42 |WjCuxsoE//xQAMUB|
1F80 41 4A 73 43 36 41 41 3D 3C 2F 49 43 43 52 6C 74 |AJsC6AA=</ICCRlt|
1F90 64 44 61 74 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C |dData></TxDtls><|
1FA0 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C 41 75 74 |AuthstnRslt><Aut|
1FB0 68 73 74 6E 4E 74 74 79 3E 3C 54 70 3E 43 49 53 |hstnNtty><Tp>CIS|
1FC0 53 3C 2F 54 70 3E 3C 2F 41 75 74 68 73 74 6E 4E |S</Tp></AuthstnN|
1FD0 74 74 79 3E 3C 52 73 70 6E 54 6F 41 75 74 68 73 |tty><RspnToAuths|

7 Messages Examples - 403 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1FE0 74 6E 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F 52 |tn><Rspn>APPR</R|
1FF0 73 70 6E 3E 3C 2F 52 73 70 6E 54 6F 41 75 74 68 |spn></RspnToAuth|
2000 73 74 6E 3E 3C 41 75 74 68 73 74 6E 43 64 3E 30 |stn><AuthstnCd>0|
2010 33 32 39 38 33 3C 2F 41 75 74 68 73 74 6E 43 64 |32983</AuthstnCd|
2020 3E 3C 2F 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C |></AuthstnRslt><|
2030 2F 54 78 3E 3C 2F 43 6D 70 6C 74 6E 3E 3C 2F 54 |/Tx></Cmpltn></T|
2040 78 3E 3C 54 78 3E 3C 43 6D 70 6C 74 6E 3E 3C 54 |x><Tx><Cmpltn><T|
2050 78 53 65 71 43 6E 74 72 3E 35 3C 2F 54 78 53 65 |xSeqCntr>5</TxSe|
2060 71 43 6E 74 72 3E 3C 45 6E 76 74 3E 3C 41 63 71 |qCntr><Envt><Acq|
2070 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 30 30 30 30 |rr><Id><Id>00000|
2080 30 30 30 30 31 32 33 3C 2F 49 64 3E 3C 2F 49 64 |0000123</Id></Id|
2090 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 |><ParamsVrsn>201|
20A0 31 30 39 31 33 31 32 33 34 35 36 3C 2F 50 61 72 |10913123456</Par|
20B0 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 72 72 3E |amsVrsn></Acqrr>|
20C0 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E |<Mrchnt><Id><Id>|
20D0 4D 79 4D 65 72 63 68 61 6E 74 49 44 30 30 30 3C |MyMerchantID000<|
20E0 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D |/Id></Id><CmonNm|
20F0 3E 54 65 73 74 4C 61 62 2C 63 65 72 74 69 66 69 |>TestLab,certifi|
2100 63 61 74 69 6F 6E 41 56 45 2C 53 45 50 41 3C 2F |cationAVE,SEPA</|
2110 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 6E 74 3E |CmonNm></Mrchnt>|
2120 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 3E 38 38 30 |<POI><Id><Id>880|
2130 30 30 30 30 31 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |00001</Id></Id><|
2140 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 |Cpblties><CardRd|
2150 6E 67 43 70 62 6C 74 69 65 73 3E 50 48 59 53 3C |ngCpblties>PHYS<|
2160 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |/CardRdngCpbltie|
2170 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |s><CardRdngCpblt|
2180 69 65 73 3E 4D 47 53 54 3C 2F 43 61 72 64 52 64 |ies>MGST</CardRd|
2190 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 |ngCpblties><Card|
21A0 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 43 49 43 |RdngCpblties>CIC|
21B0 43 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |C</CardRdngCpblt|
21C0 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
21D0 6C 74 69 65 73 3E 45 43 54 4C 3C 2F 43 61 72 64 |lties>ECTL</Card|
21E0 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 72 |RdngCpblties><Cr|
21F0 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 |dhldrVrfctnCpblt|
2200 69 65 73 3E 46 43 50 4E 3C 2F 43 72 64 68 6C 64 |ies>FCPN</Crdhld|
2210 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
2220 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |<CrdhldrVrfctnCp|
2230 62 6C 74 69 65 73 3E 4E 50 49 4E 3C 2F 43 72 64 |blties>NPIN</Crd|
2240 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
2250 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 |es><CrdhldrVrfct|
2260 6E 43 70 62 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F |nCpblties>MNSG</|
2270 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
2280 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 |lties><CrdhldrVr|
2290 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 |fctnCpblties>FEP|
22A0 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E |N</CrdhldrVrfctn|
22B0 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 |Cpblties><OnLine|
22C0 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F |Cpblties>SMON</O|
22D0 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 3C 4D |nLineCpblties><M|
22E0 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E |sgCpblties><Dstn|
22F0 3E 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F |>MDSP</Dstn><NbO|
2300 66 4C 69 6E 65 73 3E 38 3C 2F 4E 62 4F 66 4C 69 |fLines>8</NbOfLi|
2310 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 31 |nes><LineWidth>1|
2320 35 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D |5</LineWidth></M|
2330 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 67 43 |sgCpblties><MsgC|
2340 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E 4D 52 |pblties><Dstn>MR|
2350 43 50 3C 2F 44 73 74 6E 3E 3C 4C 69 6E 65 57 69 |CP</Dstn><LineWi|
2360 64 74 68 3E 32 34 3C 2F 4C 69 6E 65 57 69 64 74 |dth>24</LineWidt|
2370 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E |h></MsgCpblties>|
2380 3C 2F 43 70 62 6C 74 69 65 73 3E 3C 43 6D 70 6E |</Cpblties><Cmpn|
2390 74 3E 3C 54 70 3E 54 45 52 4D 3C 2F 54 70 3E 3C |t><Tp>TERM</Tp><|
23A0 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 4E 47 45 |Id><PrvdrId>INGE|
23B0 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 3E 3C 49 |NICO</PrvdrId><I|
23C0 64 3E 49 43 54 32 35 30 3C 2F 49 64 3E 3C 53 72 |d>ICT250</Id><Sr|
23D0 6C 4E 62 3E 31 31 32 32 33 33 34 3C 2F 53 72 6C |lNb>1122334</Srl|
23E0 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 6D 70 6E 74 3E |Nb></Id></Cmpnt>|
23F0 3C 43 6D 70 6E 74 3E 3C 54 70 3E 41 50 4C 49 3C |<Cmpnt><Tp>APLI<|
2400 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 |/Tp><Id><PrvdrId|
2410 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 |>INGENICO</Prvdr|

7 Messages Examples - 404 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2420 49 64 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 |Id><Id>SEPA-FAST|
2430 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C |</Id></Id><Sts><|
2440 56 72 73 6E 4E 62 3E 30 34 2E 31 30 3C 2F 56 72 |VrsnNb>04.10</Vr|
2450 73 6E 4E 62 3E 3C 2F 53 74 73 3E 3C 53 74 64 43 |snNb></Sts><StdC|
2460 6D 70 6C 63 3E 3C 49 64 3E 53 45 50 41 2D 46 41 |mplc><Id>SEPA-FA|
2470 53 54 3C 2F 49 64 3E 3C 56 72 73 6E 3E 33 2E 31 |ST</Id><Vrsn>3.1|
2480 3C 2F 56 72 73 6E 3E 3C 49 73 73 72 3E 4F 53 43 |</Vrsn><Issr>OSC|
2490 41 52 3C 2F 49 73 73 72 3E 3C 2F 53 74 64 43 6D |AR</Issr></StdCm|
24A0 70 6C 63 3E 3C 41 73 73 6D 6E 74 3E 3C 54 70 3E |plc><Assmnt><Tp>|
24B0 43 45 52 54 3C 2F 54 70 3E 3C 41 73 73 67 6E 72 |CERT</Tp><Assgnr|
24C0 3E 4F 53 43 41 52 3C 2F 41 73 73 67 6E 72 3E 3C |>OSCAR</Assgnr><|
24D0 44 6C 76 72 79 44 74 3E 32 30 31 34 2D 30 35 2D |DlvryDt>2014-05-|
24E0 31 34 54 31 37 3A 31 32 3A 30 35 2E 30 30 30 5A |14T17:12:05.000Z|
24F0 3C 2F 44 6C 76 72 79 44 74 3E 3C 58 70 72 74 6E |</DlvryDt><Xprtn|
2500 44 74 3E 32 30 32 31 2D 30 31 2D 31 32 54 30 39 |Dt>2021-01-12T09|
2510 3A 30 37 3A 31 38 2E 30 30 30 5A 3C 2F 58 70 72 |:07:18.000Z</Xpr|
2520 74 6E 44 74 3E 3C 4E 62 3E 50 41 59 2E 45 4C 49 |tnDt><Nb>PAY.ELI|
2530 2E 49 4E 47 2E 50 4F 49 2E 31 32 30 2E 31 33 30 |.ING.POI.120.130|
2540 33 30 30 30 32 3C 2F 4E 62 3E 3C 2F 41 73 73 6D |30002</Nb></Assm|
2550 6E 74 3E 3C 2F 43 6D 70 6E 74 3E 3C 2F 50 4F 49 |nt></Cmpnt></POI|
2560 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 6E 43 61 72 |><Card><PlainCar|
2570 64 44 61 74 61 3E 3C 50 41 4E 3E 35 30 37 31 30 |dData><PAN>50710|
2580 30 39 39 39 39 31 30 30 30 31 33 3C 2F 50 41 4E |09999100013</PAN|
2590 3E 3C 58 70 72 79 44 74 3E 32 30 32 30 2D 31 32 |><XpryDt>2020-12|
25A0 3C 2F 58 70 72 79 44 74 3E 3C 2F 50 6C 61 69 6E |</XpryDt></Plain|
25B0 43 61 72 64 44 61 74 61 3E 3C 43 61 72 64 50 64 |CardData><CardPd|
25C0 63 74 50 72 66 6C 3E 30 30 31 37 3C 2F 43 61 72 |ctPrfl>0017</Car|
25D0 64 50 64 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 |dPdctPrfl><CardB|
25E0 72 6E 64 3E 43 42 3C 2F 43 61 72 64 42 72 6E 64 |rnd>CB</CardBrnd|
25F0 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C |></Card></Envt><|
2600 43 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E |Cntxt><PmtCntxt>|
2610 3C 43 61 72 64 50 72 65 73 3E 66 61 6C 73 65 3C |<CardPres>false<|
2620 2F 43 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C |/CardPres><Crdhl|
2630 64 72 50 72 65 73 3E 66 61 6C 73 65 3C 2F 43 72 |drPres>false</Cr|
2640 64 68 6C 64 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E |dhldrPres><OnLin|
2650 65 43 6E 74 78 74 3E 74 72 75 65 3C 2F 4F 6E 4C |eCntxt>true</OnL|
2660 69 6E 65 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E |ineCntxt><Attndn|
2670 63 43 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 |cCntxt>ATTD</Att|
2680 6E 64 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 |ndncCntxt><CardD|
2690 61 74 61 4E 74 72 79 4D 64 3E 50 48 59 53 3C 2F |ataNtryMd>PHYS</|
26A0 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C |CardDataNtryMd><|
26B0 2F 50 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 |/PmtCntxt><SaleC|
26C0 6E 74 78 74 3E 3C 53 61 6C 65 52 65 66 4E 62 3E |ntxt><SaleRefNb>|
26D0 30 30 30 30 30 30 30 30 31 31 31 31 31 31 31 31 |0000000011111111|
26E0 2F 32 30 31 35 31 32 30 33 31 34 32 38 34 30 3C |/20151203142840<|
26F0 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 43 73 68 72 |/SaleRefNb><Cshr|
2700 49 64 3E 30 30 30 30 30 30 30 31 3C 2F 43 73 68 |Id>00000001</Csh|
2710 72 49 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E |rId></SaleCntxt>|
2720 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 54 |</Cntxt><Tx><TxT|
2730 70 3E 43 52 44 50 3C 2F 54 78 54 70 3E 3C 4D 72 |p>CRDP</TxTp><Mr|
2740 63 68 6E 74 43 74 67 79 43 64 3E 35 39 39 39 3C |chntCtgyCd>5999<|
2750 2F 4D 72 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 |/MrchntCtgyCd><T|
2760 78 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 |xId><TxDtTm>2015|
2770 2D 31 32 2D 30 33 54 31 34 3A 32 38 3A 34 30 2E |-12-03T14:28:40.|
2780 30 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 |000</TxDtTm><TxR|
2790 65 66 3E 31 33 30 32 31 36 3C 2F 54 78 52 65 66 |ef>130216</TxRef|
27A0 3E 3C 2F 54 78 49 64 3E 3C 54 78 53 75 63 73 73 |></TxId><TxSucss|
27B0 3E 74 72 75 65 3C 2F 54 78 53 75 63 73 73 3E 3C |>true</TxSucss><|
27C0 52 76 73 6C 3E 66 61 6C 73 65 3C 2F 52 76 73 6C |Rvsl>false</Rvsl|
27D0 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 |><TxDtls><Ccy>EU|
27E0 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 32 |R</Ccy><TtlAmt>2|
27F0 2E 31 38 3C 2F 54 74 6C 41 6D 74 3E 3C 2F 54 78 |.18</TtlAmt></Tx|
2800 44 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 6C |Dtls><AuthstnRsl|
2810 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C |t><AuthstnNtty><|
2820 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 |Tp>CISS</Tp></Au|
2830 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 |thstnNtty><RspnT|
2840 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 |oAuthstn><Rspn>A|
2850 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E |PPR</Rspn></Rspn|

7 Messages Examples - 405 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2860 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 |ToAuthstn><Auths|
2870 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 |tnCd>032983</Aut|
2880 68 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 6E |hstnCd></Authstn|
2890 52 73 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 6C |Rslt></Tx></Cmpl|
28A0 74 6E 3E 3C 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 |tn></Tx><Tx><Cmp|
28B0 6C 74 6E 3E 3C 54 78 53 65 71 43 6E 74 72 3E 36 |ltn><TxSeqCntr>6|
28C0 3C 2F 54 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 |</TxSeqCntr><Env|
28D0 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
28E0 3E 30 30 30 30 30 30 30 30 30 31 32 33 3C 2F 49 |>000000000123</I|
28F0 64 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 |d></Id><ParamsVr|
2900 73 6E 3E 32 30 31 31 30 39 31 33 31 32 33 34 35 |sn>2011091312345|
2910 36 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F |6</ParamsVrsn></|
2920 41 63 71 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 |Acqrr><Mrchnt><I|
2930 64 3E 3C 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 |d><Id>MyMerchant|
2940 49 44 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |ID000</Id></Id><|
2950 43 6D 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 |CmonNm>TestLab,c|
2960 65 72 74 69 66 69 63 61 74 69 6F 6E 41 56 45 2C |ertificationAVE,|
2970 53 45 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D |SEPA</CmonNm></M|
2980 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C |rchnt><POI><Id><|
2990 49 64 3E 38 38 30 30 30 30 30 31 3C 2F 49 64 3E |Id>88000001</Id>|
29A0 3C 2F 49 64 3E 3C 43 70 62 6C 74 69 65 73 3E 3C |</Id><Cpblties><|
29B0 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
29C0 3E 50 48 59 53 3C 2F 43 61 72 64 52 64 6E 67 43 |>PHYS</CardRdngC|
29D0 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E |pblties><CardRdn|
29E0 67 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F |gCpblties>MGST</|
29F0 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
2A00 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |><CardRdngCpblti|
2A10 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 52 64 6E |es>CICC</CardRdn|
2A20 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 |gCpblties><CardR|
2A30 64 6E 67 43 70 62 6C 74 69 65 73 3E 45 43 54 4C |dngCpblties>ECTL|
2A40 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |</CardRdngCpblti|
2A50 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 |es><CrdhldrVrfct|
2A60 6E 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F |nCpblties>FCPN</|
2A70 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
2A80 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 |lties><CrdhldrVr|
2A90 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 |fctnCpblties>NPI|
2AA0 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E |N</CrdhldrVrfctn|
2AB0 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 |Cpblties><Crdhld|
2AC0 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
2AD0 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 |MNSG</CrdhldrVrf|
2AE0 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 |ctnCpblties><Crd|
2AF0 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
2B00 65 73 3E 46 45 50 4E 3C 2F 43 72 64 68 6C 64 72 |es>FEPN</Crdhldr|
2B10 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C |VrfctnCpblties><|
2B20 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 53 |OnLineCpblties>S|
2B30 4D 4F 4E 3C 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 |MON</OnLineCpblt|
2B40 69 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 |ies><MsgCpblties|
2B50 3E 3C 44 73 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 |><Dstn>MDSP</Dst|
2B60 6E 3E 3C 4E 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F |n><NbOfLines>8</|
2B70 4E 62 4F 66 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 |NbOfLines><LineW|
2B80 69 64 74 68 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 |idth>15</LineWid|
2B90 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 |th></MsgCpblties|
2BA0 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 |><MsgCpblties><D|
2BB0 73 74 6E 3E 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C |stn>MRCP</Dstn><|
2BC0 4C 69 6E 65 57 69 64 74 68 3E 32 34 3C 2F 4C 69 |LineWidth>24</Li|
2BD0 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 |neWidth></MsgCpb|
2BE0 6C 74 69 65 73 3E 3C 2F 43 70 62 6C 74 69 65 73 |lties></Cpblties|
2BF0 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 54 45 52 4D |><Cmpnt><Tp>TERM|
2C00 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 |</Tp><Id><PrvdrI|
2C10 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 |d>INGENICO</Prvd|
2C20 72 49 64 3E 3C 49 64 3E 49 43 54 32 35 30 3C 2F |rId><Id>ICT250</|
2C30 49 64 3E 3C 53 72 6C 4E 62 3E 31 31 32 32 33 33 |Id><SrlNb>112233|
2C40 34 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F |4</SrlNb></Id></|
2C50 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 |Cmpnt><Cmpnt><Tp|
2C60 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 |>APLI</Tp><Id><P|
2C70 72 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C |rvdrId>INGENICO<|
2C80 2F 50 72 76 64 72 49 64 3E 3C 49 64 3E 53 45 50 |/PrvdrId><Id>SEP|
2C90 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E |A-FAST</Id></Id>|

7 Messages Examples - 406 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2CA0 3C 53 74 73 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E |<Sts><VrsnNb>04.|
2CB0 31 30 3C 2F 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 |10</VrsnNb></Sts|
2CC0 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 |><StdCmplc><Id>S|
2CD0 45 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 56 72 |EPA-FAST</Id><Vr|
2CE0 73 6E 3E 33 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 |sn>3.1</Vrsn><Is|
2CF0 73 72 3E 4F 53 43 41 52 3C 2F 49 73 73 72 3E 3C |sr>OSCAR</Issr><|
2D00 2F 53 74 64 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E |/StdCmplc><Assmn|
2D10 74 3E 3C 54 70 3E 43 45 52 54 3C 2F 54 70 3E 3C |t><Tp>CERT</Tp><|
2D20 41 73 73 67 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 |Assgnr>OSCAR</As|
2D30 73 67 6E 72 3E 3C 44 6C 76 72 79 44 74 3E 32 30 |sgnr><DlvryDt>20|
2D40 31 34 2D 30 35 2D 31 34 54 31 37 3A 31 32 3A 30 |14-05-14T17:12:0|
2D50 35 2E 30 30 30 5A 3C 2F 44 6C 76 72 79 44 74 3E |5.000Z</DlvryDt>|
2D60 3C 58 70 72 74 6E 44 74 3E 32 30 32 31 2D 30 31 |<XprtnDt>2021-01|
2D70 2D 31 32 54 30 39 3A 30 37 3A 31 38 2E 30 30 30 |-12T09:07:18.000|
2D80 5A 3C 2F 58 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 |Z</XprtnDt><Nb>P|
2D90 41 59 2E 45 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 |AY.ELI.ING.POI.1|
2DA0 32 30 2E 31 33 30 33 30 30 30 32 3C 2F 4E 62 3E |20.13030002</Nb>|
2DB0 3C 2F 41 73 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 |</Assmnt></Cmpnt|
2DC0 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C |></POI><Card><Pl|
2DD0 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 50 41 4E |ainCardData><PAN|
2DE0 3E 35 30 37 31 30 30 39 39 31 31 32 32 37 37 30 |>507100991122770|
2DF0 34 39 3C 2F 50 41 4E 3E 3C 58 70 72 79 44 74 3E |49</PAN><XpryDt>|
2E00 32 30 31 38 2D 30 33 3C 2F 58 70 72 79 44 74 3E |2018-03</XpryDt>|
2E10 3C 2F 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E |</PlainCardData>|
2E20 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 |<CardPdctPrfl>00|
2E30 31 37 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C |17</CardPdctPrfl|
2E40 3E 3C 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 |><CardBrnd>CB</C|
2E50 61 72 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C |ardBrnd></Card><|
2E60 2F 45 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D |/Envt><Cntxt><Pm|
2E70 74 43 6E 74 78 74 3E 3C 43 72 64 68 6C 64 72 50 |tCntxt><CrdhldrP|
2E80 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C 64 |res>true</Crdhld|
2E90 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 |rPres><OnLineCnt|
2EA0 78 74 3E 74 72 75 65 3C 2F 4F 6E 4C 69 6E 65 43 |xt>true</OnLineC|
2EB0 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 6E 74 |ntxt><AttndncCnt|
2EC0 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 6E 63 |xt>ATTD</Attndnc|
2ED0 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 61 4E |Cntxt><CardDataN|
2EE0 74 72 79 4D 64 3E 4D 47 53 54 3C 2F 43 61 72 64 |tryMd>MGST</Card|
2EF0 44 61 74 61 4E 74 72 79 4D 64 3E 3C 46 6C 6C 62 |DataNtryMd><Fllb|
2F00 63 6B 49 6E 64 3E 46 46 4C 42 3C 2F 46 6C 6C 62 |ckInd>FFLB</Fllb|
2F10 63 6B 49 6E 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 |ckInd></PmtCntxt|
2F20 3E 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C |><SaleCntxt><Sal|
2F30 65 52 65 66 4E 62 3E 30 30 30 30 30 30 30 30 31 |eRefNb>000000001|
2F40 31 31 31 31 31 31 31 2F 32 30 31 35 31 32 30 33 |1111111/20151203|
2F50 31 34 32 33 33 37 3C 2F 53 61 6C 65 52 65 66 4E |142337</SaleRefN|
2F60 62 3E 3C 43 73 68 72 49 64 3E 30 30 30 30 30 30 |b><CshrId>000000|
2F70 30 31 3C 2F 43 73 68 72 49 64 3E 3C 2F 53 61 6C |01</CshrId></Sal|
2F80 65 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C |eCntxt></Cntxt><|
2F90 54 78 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 |Tx><TxTp>CRDP</T|
2FA0 78 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 |xTp><MrchntCtgyC|
2FB0 64 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 |d>5999</MrchntCt|
2FC0 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 |gyCd><TxId><TxDt|
2FD0 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 34 |Tm>2015-12-03T14|
2FE0 3A 32 33 3A 33 37 2E 30 30 30 3C 2F 54 78 44 74 |:23:37.000</TxDt|
2FF0 54 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 31 35 |Tm><TxRef>130215|
3000 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C |</TxRef></TxId><|
3010 54 78 53 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 |TxSucss>true</Tx|
3020 53 75 63 73 73 3E 3C 52 76 73 6C 3E 66 61 6C 73 |Sucss><Rvsl>fals|
3030 65 3C 2F 52 76 73 6C 3E 3C 54 78 44 74 6C 73 3E |e</Rvsl><TxDtls>|
3040 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 |<Ccy>EUR</Ccy><T|
3050 74 6C 41 6D 74 3E 32 2E 31 37 3C 2F 54 74 6C 41 |tlAmt>2.17</TtlA|
3060 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E |mt><ICCRltdData>|
3070 6E 77 49 47 41 41 41 41 41 41 49 58 6E 77 4D 47 |nwIGAAAAAAIXnwMG|
3080 41 41 41 41 41 41 41 41 6E 77 6B 43 41 41 43 66 |AAAAAAAAnwkCAACf|
3090 4E 41 4D 2F 41 41 43 66 48 67 67 77 4D 54 45 79 |NAM/AACfHggwMTEy|
30A0 4D 6A 4D 7A 4E 4A 38 7A 41 2B 44 34 79 4A 38 61 |MjMzNJ8zA+D4yJ8a|
30B0 41 67 41 51 6E 7A 55 42 49 70 55 46 42 41 41 41 |AgAQnzUBIpUFBAAA|
30C0 41 41 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 |AABfKgIJeJoDFRID|
30D0 6E 30 45 44 45 77 49 56 6E 41 45 41 79 67 54 66 |n0EDEwIVnAEAygTf|

7 Messages Examples - 407 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

30E0 2B 41 66 67 78 51 45 45 6D 77 4C 49 41 41 3D 3D |+AfgxQEEmwLIAA==|
30F0 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F |</ICCRltdData></|
3100 54 78 44 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 |TxDtls><AuthstnR|
3110 73 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 |slt><AuthstnNtty|
3120 3E 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F |><Tp>CISS</Tp></|
3130 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 |AuthstnNtty><Rsp|
3140 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E |nToAuthstn><Rspn|
3150 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 |>APPR</Rspn></Rs|
3160 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 |pnToAuthstn><Aut|
3170 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 |hstnCd>032983</A|
3180 75 74 68 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 |uthstnCd></Auths|
3190 74 6E 52 73 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 6D |tnRslt></Tx></Cm|
31A0 70 6C 74 6E 3E 3C 2F 54 78 3E 3C 54 78 3E 3C 43 |pltn></Tx><Tx><C|
31B0 6D 70 6C 74 6E 3E 3C 54 78 53 65 71 43 6E 74 72 |mpltn><TxSeqCntr|
31C0 3E 37 3C 2F 54 78 53 65 71 43 6E 74 72 3E 3C 45 |>7</TxSeqCntr><E|
31D0 6E 76 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C |nvt><Acqrr><Id><|
31E0 49 64 3E 30 30 30 30 30 30 30 30 30 31 32 33 3C |Id>000000000123<|
31F0 2F 49 64 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 |/Id></Id><Params|
3200 56 72 73 6E 3E 32 30 31 31 30 39 31 33 31 32 33 |Vrsn>20110913123|
3210 34 35 36 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E |456</ParamsVrsn>|
3220 3C 2F 41 63 71 72 72 3E 3C 4D 72 63 68 6E 74 3E |</Acqrr><Mrchnt>|
3230 3C 49 64 3E 3C 49 64 3E 4D 79 4D 65 72 63 68 61 |<Id><Id>MyMercha|
3240 6E 74 49 44 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 |ntID000</Id></Id|
3250 3E 3C 43 6D 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 |><CmonNm>TestLab|
3260 2C 63 65 72 74 69 66 69 63 61 74 69 6F 6E 41 56 |,certificationAV|
3270 45 2C 53 45 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C |E,SEPA</CmonNm><|
3280 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 |/Mrchnt><POI><Id|
3290 3E 3C 49 64 3E 38 38 30 30 30 30 30 31 3C 2F 49 |><Id>88000001</I|
32A0 64 3E 3C 2F 49 64 3E 3C 43 70 62 6C 74 69 65 73 |d></Id><Cpblties|
32B0 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |><CardRdngCpblti|
32C0 65 73 3E 50 48 59 53 3C 2F 43 61 72 64 52 64 6E |es>PHYS</CardRdn|
32D0 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 |gCpblties><CardR|
32E0 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 |dngCpblties>MGST|
32F0 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |</CardRdngCpblti|
3300 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C |es><CardRdngCpbl|
3310 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 52 |ties>CICC</CardR|
3320 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 |dngCpblties><Car|
3330 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 45 43 |dRdngCpblties>EC|
3340 54 4C 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C |TL</CardRdngCpbl|
3350 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 |ties><CrdhldrVrf|
3360 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 43 50 4E |ctnCpblties>FCPN|
3370 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |</CrdhldrVrfctnC|
3380 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 |pblties><Crdhldr|
3390 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E |VrfctnCpblties>N|
33A0 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 |PIN</CrdhldrVrfc|
33B0 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 |tnCpblties><Crdh|
33C0 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
33D0 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 72 56 |s>MNSG</CrdhldrV|
33E0 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 |rfctnCpblties><C|
33F0 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
3400 74 69 65 73 3E 46 45 50 4E 3C 2F 43 72 64 68 6C |ties>FEPN</Crdhl|
3410 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 |drVrfctnCpblties|
3420 3E 3C 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 |><OnLineCpblties|
3430 3E 53 4D 4F 4E 3C 2F 4F 6E 4C 69 6E 65 43 70 62 |>SMON</OnLineCpb|
3440 6C 74 69 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 |lties><MsgCpblti|
3450 65 73 3E 3C 44 73 74 6E 3E 4D 44 53 50 3C 2F 44 |es><Dstn>MDSP</D|
3460 73 74 6E 3E 3C 4E 62 4F 66 4C 69 6E 65 73 3E 38 |stn><NbOfLines>8|
3470 3C 2F 4E 62 4F 66 4C 69 6E 65 73 3E 3C 4C 69 6E |</NbOfLines><Lin|
3480 65 57 69 64 74 68 3E 31 35 3C 2F 4C 69 6E 65 57 |eWidth>15</LineW|
3490 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 |idth></MsgCpblti|
34A0 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E |es><MsgCpblties>|
34B0 3C 44 73 74 6E 3E 4D 52 43 50 3C 2F 44 73 74 6E |<Dstn>MRCP</Dstn|
34C0 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 32 34 3C 2F |><LineWidth>24</|
34D0 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 |LineWidth></MsgC|
34E0 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C 74 69 |pblties></Cpblti|
34F0 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 54 45 |es><Cmpnt><Tp>TE|
3500 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 |RM</Tp><Id><Prvd|
3510 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 |rId>INGENICO</Pr|

7 Messages Examples - 408 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3520 76 64 72 49 64 3E 3C 49 64 3E 49 43 54 32 35 30 |vdrId><Id>ICT250|
3530 3C 2F 49 64 3E 3C 53 72 6C 4E 62 3E 31 31 32 32 |</Id><SrlNb>1122|
3540 33 33 34 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 3E |334</SrlNb></Id>|
3550 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E 3C |</Cmpnt><Cmpnt><|
3560 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 3E |Tp>APLI</Tp><Id>|
3570 3C 50 72 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 |<PrvdrId>INGENIC|
3580 4F 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 3E 53 |O</PrvdrId><Id>S|
3590 45 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 2F 49 |EPA-FAST</Id></I|
35A0 64 3E 3C 53 74 73 3E 3C 56 72 73 6E 4E 62 3E 30 |d><Sts><VrsnNb>0|
35B0 34 2E 31 30 3C 2F 56 72 73 6E 4E 62 3E 3C 2F 53 |4.10</VrsnNb></S|
35C0 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C 49 64 |ts><StdCmplc><Id|
35D0 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C |>SEPA-FAST</Id><|
35E0 56 72 73 6E 3E 33 2E 31 3C 2F 56 72 73 6E 3E 3C |Vrsn>3.1</Vrsn><|
35F0 49 73 73 72 3E 4F 53 43 41 52 3C 2F 49 73 73 72 |Issr>OSCAR</Issr|
3600 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 41 73 73 |></StdCmplc><Ass|
3610 6D 6E 74 3E 3C 54 70 3E 43 45 52 54 3C 2F 54 70 |mnt><Tp>CERT</Tp|
3620 3E 3C 41 73 73 67 6E 72 3E 4F 53 43 41 52 3C 2F |><Assgnr>OSCAR</|
3630 41 73 73 67 6E 72 3E 3C 44 6C 76 72 79 44 74 3E |Assgnr><DlvryDt>|
3640 32 30 31 34 2D 30 35 2D 31 34 54 31 37 3A 31 32 |2014-05-14T17:12|
3650 3A 30 35 2E 30 30 30 5A 3C 2F 44 6C 76 72 79 44 |:05.000Z</DlvryD|
3660 74 3E 3C 58 70 72 74 6E 44 74 3E 32 30 32 31 2D |t><XprtnDt>2021-|
3670 30 31 2D 31 32 54 30 39 3A 30 37 3A 31 38 2E 30 |01-12T09:07:18.0|
3680 30 30 5A 3C 2F 58 70 72 74 6E 44 74 3E 3C 4E 62 |00Z</XprtnDt><Nb|
3690 3E 50 41 59 2E 45 4C 49 2E 49 4E 47 2E 50 4F 49 |>PAY.ELI.ING.POI|
36A0 2E 31 32 30 2E 31 33 30 33 30 30 30 32 3C 2F 4E |.120.13030002</N|
36B0 62 3E 3C 2F 41 73 73 6D 6E 74 3E 3C 2F 43 6D 70 |b></Assmnt></Cmp|
36C0 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C |nt></POI><Card><|
36D0 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 50 |PlainCardData><P|
36E0 41 4E 3E 35 30 37 31 30 30 39 39 39 39 31 30 30 |AN>5071009999100|
36F0 30 31 33 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 65 |013</PAN><CardSe|
3700 71 4E 62 3E 30 31 3C 2F 43 61 72 64 53 65 71 4E |qNb>01</CardSeqN|
3710 62 3E 3C 46 63 74 76 44 74 3E 32 30 31 32 2D 30 |b><FctvDt>2012-0|
3720 31 3C 2F 46 63 74 76 44 74 3E 3C 58 70 72 79 44 |1</FctvDt><XpryD|
3730 74 3E 32 30 32 30 2D 31 32 3C 2F 58 70 72 79 44 |t>2020-12</XpryD|
3740 74 3E 3C 53 76 63 43 64 3E 39 30 31 3C 2F 53 76 |t><SvcCd>901</Sv|
3750 63 43 64 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 44 |cCd></PlainCardD|
3760 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 64 3E |ata><CardCtryCd>|
3770 46 52 41 3C 2F 43 61 72 64 43 74 72 79 43 64 3E |FRA</CardCtryCd>|
3780 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 |<CardPdctPrfl>00|
3790 31 37 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C |17</CardPdctPrfl|
37A0 3E 3C 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 |><CardBrnd>CB</C|
37B0 61 72 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C |ardBrnd></Card><|
37C0 2F 45 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D |/Envt><Cntxt><Pm|
37D0 74 43 6E 74 78 74 3E 3C 43 72 64 68 6C 64 72 50 |tCntxt><CrdhldrP|
37E0 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C 64 |res>true</Crdhld|
37F0 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 |rPres><OnLineCnt|
3800 78 74 3E 66 61 6C 73 65 3C 2F 4F 6E 4C 69 6E 65 |xt>false</OnLine|
3810 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 6E |Cntxt><AttndncCn|
3820 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 6E |txt>ATTD</Attndn|
3830 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 61 |cCntxt><CardData|
3840 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 72 |NtryMd>CICC</Car|
3850 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 6D |dDataNtryMd></Pm|
3860 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 78 |tCntxt><SaleCntx|
3870 74 3E 3C 53 61 6C 65 52 65 66 4E 62 3E 30 30 30 |t><SaleRefNb>000|
3880 30 30 30 30 30 31 31 31 31 31 31 31 31 2F 32 30 |0000011111111/20|
3890 31 35 31 32 30 33 31 34 32 32 31 35 3C 2F 53 61 |151203142215</Sa|
38A0 6C 65 52 65 66 4E 62 3E 3C 43 73 68 72 49 64 3E |leRefNb><CshrId>|
38B0 30 30 30 30 30 30 30 31 3C 2F 43 73 68 72 49 64 |00000001</CshrId|
38C0 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F 43 |></SaleCntxt></C|
38D0 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 54 70 3E 52 |ntxt><Tx><TxTp>R|
38E0 46 4E 44 3C 2F 54 78 54 70 3E 3C 4D 72 63 68 6E |FND</TxTp><Mrchn|
38F0 74 43 74 67 79 43 64 3E 35 39 39 39 3C 2F 4D 72 |tCtgyCd>5999</Mr|
3900 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 78 49 64 |chntCtgyCd><TxId|
3910 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 32 |><TxDtTm>2015-12|
3920 2D 30 33 54 31 34 3A 32 32 3A 31 35 2E 30 30 30 |-03T14:22:15.000|
3930 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|
3940 31 33 30 32 31 34 3C 2F 54 78 52 65 66 3E 3C 2F |130214</TxRef></|
3950 54 78 49 64 3E 3C 54 78 53 75 63 73 73 3E 66 61 |TxId><TxSucss>fa|

7 Messages Examples - 409 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3960 6C 73 65 3C 2F 54 78 53 75 63 73 73 3E 3C 52 76 |lse</TxSucss><Rv|
3970 73 6C 3E 66 61 6C 73 65 3C 2F 52 76 73 6C 3E 3C |sl>false</Rvsl><|
3980 46 61 69 6C 72 52 73 6E 3E 55 43 4D 50 3C 2F 46 |FailrRsn>UCMP</F|
3990 61 69 6C 72 52 73 6E 3E 3C 54 78 44 74 6C 73 3E |ailrRsn><TxDtls>|
39A0 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 |<Ccy>EUR</Ccy><T|
39B0 74 6C 41 6D 74 3E 32 2E 31 37 3C 2F 54 74 6C 41 |tlAmt>2.17</TtlA|
39C0 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E |mt><ICCRltdData>|
39D0 6E 77 49 47 41 41 41 41 41 41 49 58 6E 77 4D 47 |nwIGAAAAAAIXnwMG|
39E0 41 41 41 41 41 41 41 41 58 79 55 44 45 67 45 42 |AAAAAAAAXyUDEgEB|
39F0 67 67 49 39 41 49 63 42 41 5A 38 4A 61 67 41 43 |ggI9AIcBAZ8JagAC|
3A00 6E 7A 51 44 50 77 41 41 68 41 65 67 41 41 41 41 |nzQDPwAAhAegAAAA|
3A10 51 68 41 51 6E 78 34 49 4D 44 45 78 4D 6A 49 7A |QhAQnx4IMDExMjIz|
3A20 4D 7A 53 66 4D 77 50 67 2B 4D 49 66 47 67 49 41 |MzSfMwPg+MIfGgIA|
3A30 45 4A 38 31 41 53 4B 56 42 51 41 41 41 41 41 41 |EJ81ASKVBQAAAAAA|
3A40 58 79 6F 43 43 58 69 61 41 78 55 53 41 35 39 42 |XyoCCXiaAxUSA59B|
3A50 41 78 4D 43 46 4A 77 42 41 4A 38 33 42 4F 50 39 |AxMCFJwBAJ83BOP9|
3A60 44 63 62 4B 42 4E 34 49 45 41 44 46 41 51 43 62 |DcbKBN4IEADFAQCb|
3A70 41 67 41 41 3C 2F 49 43 43 52 6C 74 64 44 61 74 |AgAA</ICCRltdDat|
3A80 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C 2F 54 78 3E |a></TxDtls></Tx>|
3A90 3C 2F 43 6D 70 6C 74 6E 3E 3C 2F 54 78 3E 3C 54 |</Cmpltn></Tx><T|
3AA0 78 3E 3C 43 6D 70 6C 74 6E 3E 3C 54 78 53 65 71 |x><Cmpltn><TxSeq|
3AB0 43 6E 74 72 3E 38 3C 2F 54 78 53 65 71 43 6E 74 |Cntr>8</TxSeqCnt|
3AC0 72 3E 3C 45 6E 76 74 3E 3C 41 63 71 72 72 3E 3C |r><Envt><Acqrr><|
3AD0 49 64 3E 3C 49 64 3E 30 30 30 30 30 30 30 30 30 |Id><Id>000000000|
3AE0 31 32 33 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 50 61 |123</Id></Id><Pa|
3AF0 72 61 6D 73 56 72 73 6E 3E 32 30 31 31 30 39 31 |ramsVrsn>2011091|
3B00 33 31 32 33 34 35 36 3C 2F 50 61 72 61 6D 73 56 |3123456</ParamsV|
3B10 72 73 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D 72 63 |rsn></Acqrr><Mrc|
3B20 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E 4D 79 4D 65 |hnt><Id><Id>MyMe|
3B30 72 63 68 61 6E 74 49 44 30 30 30 3C 2F 49 64 3E |rchantID000</Id>|
3B40 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 54 65 73 |</Id><CmonNm>Tes|
3B50 74 4C 61 62 2C 63 65 72 74 69 66 69 63 61 74 69 |tLab,certificati|
3B60 6F 6E 41 56 45 2C 53 45 50 41 3C 2F 43 6D 6F 6E |onAVE,SEPA</Cmon|
3B70 4E 6D 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 |Nm></Mrchnt><POI|
3B80 3E 3C 49 64 3E 3C 49 64 3E 38 38 30 30 30 30 30 |><Id><Id>8800000|
3B90 31 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 70 62 6C |1</Id></Id><Cpbl|
3BA0 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 |ties><CardRdngCp|
3BB0 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 72 |blties>PHYS</Car|
3BC0 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 |dRdngCpblties><C|
3BD0 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
3BE0 4D 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 |MGST</CardRdngCp|
3BF0 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 |blties><CardRdng|
3C00 43 70 62 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 |Cpblties>CICC</C|
3C10 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
3C20 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |<CardRdngCpbltie|
3C30 73 3E 45 43 54 4C 3C 2F 43 61 72 64 52 64 6E 67 |s>ECTL</CardRdng|
3C40 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 |Cpblties><Crdhld|
3C50 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
3C60 46 43 50 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 |FCPN</CrdhldrVrf|
3C70 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 |ctnCpblties><Crd|
3C80 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
3C90 65 73 3E 4E 50 49 4E 3C 2F 43 72 64 68 6C 64 72 |es>NPIN</Crdhldr|
3CA0 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C |VrfctnCpblties><|
3CB0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
3CC0 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 |lties>MNSG</Crdh|
3CD0 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
3CE0 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E |s><CrdhldrVrfctn|
3CF0 43 70 62 6C 74 69 65 73 3E 46 45 50 4E 3C 2F 43 |Cpblties>FEPN</C|
3D00 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
3D10 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 43 70 62 6C |ties><OnLineCpbl|
3D20 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F 6E 4C 69 6E |ties>SMON</OnLin|
3D30 65 43 70 62 6C 74 69 65 73 3E 3C 4D 73 67 43 70 |eCpblties><MsgCp|
3D40 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E 4D 44 53 |blties><Dstn>MDS|
3D50 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 4C 69 6E |P</Dstn><NbOfLin|
3D60 65 73 3E 38 3C 2F 4E 62 4F 66 4C 69 6E 65 73 3E |es>8</NbOfLines>|
3D70 3C 4C 69 6E 65 57 69 64 74 68 3E 31 35 3C 2F 4C |<LineWidth>15</L|
3D80 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 |ineWidth></MsgCp|
3D90 62 6C 74 69 65 73 3E 3C 4D 73 67 43 70 62 6C 74 |blties><MsgCpblt|

7 Messages Examples - 410 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3DA0 69 65 73 3E 3C 44 73 74 6E 3E 4D 52 43 50 3C 2F |ies><Dstn>MRCP</|
3DB0 44 73 74 6E 3E 3C 4C 69 6E 65 57 69 64 74 68 3E |Dstn><LineWidth>|
3DC0 32 34 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F |24</LineWidth></|
3DD0 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 |MsgCpblties></Cp|
3DE0 62 6C 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 |blties><Cmpnt><T|
3DF0 70 3E 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C |p>TERM</Tp><Id><|
3E00 50 72 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F |PrvdrId>INGENICO|
3E10 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 3E 49 43 |</PrvdrId><Id>IC|
3E20 54 32 35 30 3C 2F 49 64 3E 3C 53 72 6C 4E 62 3E |T250</Id><SrlNb>|
3E30 31 31 32 32 33 33 34 3C 2F 53 72 6C 4E 62 3E 3C |1122334</SrlNb><|
3E40 2F 49 64 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 |/Id></Cmpnt><Cmp|
3E50 6E 74 3E 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E |nt><Tp>APLI</Tp>|
3E60 3C 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 4E 47 |<Id><PrvdrId>ING|
3E70 45 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 3E 3C |ENICO</PrvdrId><|
3E80 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
3E90 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E |></Id><Sts><Vrsn|
3EA0 4E 62 3E 30 34 2E 31 30 3C 2F 56 72 73 6E 4E 62 |Nb>04.10</VrsnNb|
3EB0 3E 3C 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 |></Sts><StdCmplc|
3EC0 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F |><Id>SEPA-FAST</|
3ED0 49 64 3E 3C 56 72 73 6E 3E 33 2E 31 3C 2F 56 72 |Id><Vrsn>3.1</Vr|
3EE0 73 6E 3E 3C 49 73 73 72 3E 4F 53 43 41 52 3C 2F |sn><Issr>OSCAR</|
3EF0 49 73 73 72 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E |Issr></StdCmplc>|
3F00 3C 41 73 73 6D 6E 74 3E 3C 54 70 3E 43 45 52 54 |<Assmnt><Tp>CERT|
3F10 3C 2F 54 70 3E 3C 41 73 73 67 6E 72 3E 4F 53 43 |</Tp><Assgnr>OSC|
3F20 41 52 3C 2F 41 73 73 67 6E 72 3E 3C 44 6C 76 72 |AR</Assgnr><Dlvr|
3F30 79 44 74 3E 32 30 31 34 2D 30 35 2D 31 34 54 31 |yDt>2014-05-14T1|
3F40 37 3A 31 32 3A 30 35 2E 30 30 30 5A 3C 2F 44 6C |7:12:05.000Z</Dl|
3F50 76 72 79 44 74 3E 3C 58 70 72 74 6E 44 74 3E 32 |vryDt><XprtnDt>2|
3F60 30 32 31 2D 30 31 2D 31 32 54 30 39 3A 30 37 3A |021-01-12T09:07:|
3F70 31 38 2E 30 30 30 5A 3C 2F 58 70 72 74 6E 44 74 |18.000Z</XprtnDt|
3F80 3E 3C 4E 62 3E 50 41 59 2E 45 4C 49 2E 49 4E 47 |><Nb>PAY.ELI.ING|
3F90 2E 50 4F 49 2E 31 32 30 2E 31 33 30 33 30 30 30 |.POI.120.1303000|
3FA0 32 3C 2F 4E 62 3E 3C 2F 41 73 73 6D 6E 74 3E 3C |2</Nb></Assmnt><|
3FB0 2F 43 6D 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 |/Cmpnt></POI><Ca|
3FC0 72 64 3E 3C 50 6C 61 69 6E 43 61 72 64 44 61 74 |rd><PlainCardDat|
3FD0 61 3E 3C 50 41 4E 3E 35 34 31 33 33 33 30 30 31 |a><PAN>541333001|
3FE0 30 30 30 30 37 31 30 3C 2F 50 41 4E 3E 3C 43 61 |0000710</PAN><Ca|
3FF0 72 64 53 65 71 4E 62 3E 30 30 3C 2F 43 61 72 64 |rdSeqNb>00</Card|
4000 53 65 71 4E 62 3E 3C 46 63 74 76 44 74 3E 32 30 |SeqNb><FctvDt>20|
4010 31 30 2D 31 32 3C 2F 46 63 74 76 44 74 3E 3C 58 |10-12</FctvDt><X|
4020 70 72 79 44 74 3E 32 30 31 35 2D 31 32 3C 2F 58 |pryDt>2015-12</X|
4030 70 72 79 44 74 3E 3C 53 76 63 43 64 3E 32 30 31 |pryDt><SvcCd>201|
4040 3C 2F 53 76 63 43 64 3E 3C 2F 50 6C 61 69 6E 43 |</SvcCd></PlainC|
4050 61 72 64 44 61 74 61 3E 3C 43 61 72 64 43 74 72 |ardData><CardCtr|
4060 79 43 64 3E 44 45 55 3C 2F 43 61 72 64 43 74 72 |yCd>DEU</CardCtr|
4070 79 43 64 3E 3C 43 61 72 64 50 64 63 74 50 72 66 |yCd><CardPdctPrf|
4080 6C 3E 30 30 31 38 3C 2F 43 61 72 64 50 64 63 74 |l>0018</CardPdct|
4090 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 43 |Prfl><CardBrnd>C|
40A0 42 3C 2F 43 61 72 64 42 72 6E 64 3E 3C 2F 43 61 |B</CardBrnd></Ca|
40B0 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 6E 74 78 74 |rd></Envt><Cntxt|
40C0 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C 43 72 64 68 |><PmtCntxt><Crdh|
40D0 6C 64 72 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 |ldrPres>true</Cr|
40E0 64 68 6C 64 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E |dhldrPres><OnLin|
40F0 65 43 6E 74 78 74 3E 74 72 75 65 3C 2F 4F 6E 4C |eCntxt>true</OnL|
4100 69 6E 65 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E |ineCntxt><Attndn|
4110 63 43 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 |cCntxt>ATTD</Att|
4120 6E 64 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 |ndncCntxt><CardD|
4130 61 74 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F |ataNtryMd>CICC</|
4140 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C |CardDataNtryMd><|
4150 2F 50 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 |/PmtCntxt><SaleC|
4160 6E 74 78 74 3E 3C 53 61 6C 65 52 65 66 4E 62 3E |ntxt><SaleRefNb>|
4170 30 30 30 30 30 30 30 30 31 31 31 31 31 31 31 31 |0000000011111111|
4180 2F 32 30 31 35 31 32 30 33 31 34 30 37 35 35 3C |/20151203140755<|
4190 2F 53 61 6C 65 52 65 66 4E 62 3E 3C 43 73 68 72 |/SaleRefNb><Cshr|
41A0 49 64 3E 30 30 30 30 30 30 30 31 3C 2F 43 73 68 |Id>00000001</Csh|
41B0 72 49 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E |rId></SaleCntxt>|
41C0 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 54 |</Cntxt><Tx><TxT|
41D0 70 3E 52 46 4E 44 3C 2F 54 78 54 70 3E 3C 4D 72 |p>RFND</TxTp><Mr|

7 Messages Examples - 411 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

41E0 63 68 6E 74 43 74 67 79 43 64 3E 35 39 39 39 3C |chntCtgyCd>5999<|
41F0 2F 4D 72 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 |/MrchntCtgyCd><T|
4200 78 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 |xId><TxDtTm>2015|
4210 2D 31 32 2D 30 33 54 31 34 3A 30 37 3A 35 35 2E |-12-03T14:07:55.|
4220 30 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 |000</TxDtTm><TxR|
4230 65 66 3E 31 33 30 32 31 33 3C 2F 54 78 52 65 66 |ef>130213</TxRef|
4240 3E 3C 2F 54 78 49 64 3E 3C 54 78 53 75 63 73 73 |></TxId><TxSucss|
4250 3E 74 72 75 65 3C 2F 54 78 53 75 63 73 73 3E 3C |>true</TxSucss><|
4260 52 76 73 6C 3E 66 61 6C 73 65 3C 2F 52 76 73 6C |Rvsl>false</Rvsl|
4270 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 |><TxDtls><Ccy>EU|
4280 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 32 |R</Ccy><TtlAmt>2|
4290 2E 31 36 3C 2F 54 74 6C 41 6D 74 3E 3C 49 43 43 |.16</TtlAmt><ICC|
42A0 52 6C 74 64 44 61 74 61 3E 6E 77 49 47 41 41 41 |RltdData>nwIGAAA|
42B0 41 41 41 49 57 6E 77 4D 47 41 41 41 41 41 41 41 |AAAIWnwMGAAAAAAA|
42C0 41 6E 79 59 49 55 63 42 2F 78 33 6A 35 38 2F 42 |AnyYIUcB/x3j58/B|
42D0 66 4A 51 4D 51 45 67 47 43 41 6C 67 41 6E 7A 59 |fJQMQEgGCAlgAnzY|
42E0 43 45 53 4B 66 43 51 49 41 41 70 38 6E 41 51 43 |CESKfCQIAAp8nAQC|
42F0 66 4E 41 4D 2F 41 41 43 45 42 36 41 41 41 41 41 |fNAM/AACEB6AAAAA|
4300 45 45 42 43 66 48 67 67 77 4D 54 45 79 4D 6A 4D |EEBCfHggwMTEyMjM|
4310 7A 4E 4A 38 51 45 67 45 51 41 41 41 41 41 41 41 |zNJ8QEgEQAAAAAAA|
4320 41 41 41 41 41 41 41 41 41 41 41 41 41 41 4A 38 |AAAAAAAAAAAAAAJ8|
4330 7A 41 2B 44 34 79 4A 38 61 41 67 41 51 6E 7A 55 |zA+D4yJ8aAgAQnzU|
4340 42 49 70 55 46 41 41 41 41 41 41 42 66 4B 67 49 |BIpUFAAAAAABfKgI|
4350 4A 65 4A 6F 44 46 52 49 44 6E 30 45 44 45 77 49 |JeJoDFRIDn0EDEwI|
4360 54 6E 41 45 41 6E 7A 63 45 4A 6F 31 6A 4D 4D 6F |TnAEAnzcEJo1jMMo|
4370 45 2F 67 77 51 41 4D 55 42 41 4A 73 43 49 41 41 |E/gwQAMUBAJsCIAA|
4380 3D 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C |=</ICCRltdData><|
4390 2F 54 78 44 74 6C 73 3E 3C 41 75 74 68 73 74 6E |/TxDtls><Authstn|
43A0 52 73 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 |Rslt><AuthstnNtt|
43B0 79 3E 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C |y><Tp>CISS</Tp><|
43C0 2F 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 |/AuthstnNtty><Rs|
43D0 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 |pnToAuthstn><Rsp|
43E0 6E 3E 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 |n>APPR</Rspn></R|
43F0 73 70 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 |spnToAuthstn><Au|
4400 74 68 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F |thstnCd>032983</|
4410 41 75 74 68 73 74 6E 43 64 3E 3C 2F 41 75 74 68 |AuthstnCd></Auth|
4420 73 74 6E 52 73 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 |stnRslt></Tx></C|
4430 6D 70 6C 74 6E 3E 3C 2F 54 78 3E 3C 2F 44 61 74 |mpltn></Tx></Dat|
4440 61 53 65 74 3E 3C 2F 42 74 63 68 54 72 66 3E |aSet></BtchTrf> |

The SHA-256 digest of the message body BtchTrf is:


0000 A8 B2 8E 71 65 05 4C 73 CE CC C9 9B 29 82 D4 1F |...qe.Ls....)...|
0010 8F F8 8F 35 2F 3F 51 7B B4 FD DF 41 09 5F DF 1E |...5/?Q{...A._..|

Applying the padding process, the hexadecimal 80 is appended, followed by 7 null bytes to reach a
length of 40 bytes, multiple of 8:
0000 A8 B2 8E 71 65 05 4C 73 CE CC C9 9B 29 82 D4 1F |...qe.Ls....)...|
0010 8F F8 8F 35 2F 3F 51 7B B4 FD DF 41 09 5F DF 1E |...5/?Q{...A._..|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (5E64F1AB F25D3BA1 7F629EC2
B302F8EA), we obtain the MAC of the AcceptorBatchTransfer CAF19354AC2F9D72 and after conversion
into base64 " yvGTVKwvnXI= ".
0000 BE 87 57 D0 58 63 9B 84 A0 09 BD F2 83 04 48 D4 |..W.Xc........H.|
0010 46 F5 AF 02 DC 03 C0 80 9E AD 50 21 DF D9 75 E2 |F.........P!..u.|
0020 CA F1 93 54 AC 2F 9D 72 |...T./.r |

The message sent by the transport protocol is:


0000 00 00 47 45 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |..GE<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|

7 Messages Examples - 412 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|


0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 31 31 2E 30 30 31 2E 30 35 22 |caaa.011.001.05"|
00A0 3E 3C 41 63 63 70 74 72 42 74 63 68 54 72 66 3E |><AccptrBtchTrf>|
00B0 3C 48 64 72 3E 3C 44 77 6E 6C 64 54 72 66 3E 66 |<Hdr><DwnldTrf>f|
00C0 61 6C 73 65 3C 2F 44 77 6E 6C 64 54 72 66 3E 3C |alse</DwnldTrf><|
00D0 46 72 6D 74 56 72 73 6E 3E 35 2E 30 3C 2F 46 72 |FrmtVrsn>5.0</Fr|
00E0 6D 74 56 72 73 6E 3E 3C 58 63 68 67 49 64 3E 34 |mtVrsn><XchgId>4|
00F0 33 33 3C 2F 58 63 68 67 49 64 3E 3C 43 72 65 44 |33</XchgId><CreD|
0100 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 |tTm>2015-12-03T1|
0110 35 3A 33 33 3A 35 32 2E 33 36 36 5A 3C 2F 43 72 |5:33:52.366Z</Cr|
0120 65 44 74 54 6D 3E 3C 49 6E 69 74 67 50 74 79 3E |eDtTm><InitgPty>|
0130 3C 49 64 3E 50 4F 49 20 49 44 20 73 65 74 20 62 |<Id>POI ID set b|
0140 79 20 41 43 51 20 30 33 3C 2F 49 64 3E 3C 2F 49 |y ACQ 03</Id></I|
0150 6E 69 74 67 50 74 79 3E 3C 2F 48 64 72 3E 3C 42 |nitgPty></Hdr><B|
0160 74 63 68 54 72 66 3E 3C 54 78 54 74 6C 73 3E 3C |tchTrf><TxTtls><|
0170 54 70 3E 43 52 44 52 3C 2F 54 70 3E 3C 54 74 6C |Tp>CRDR</Tp><Ttl|
0180 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C |Nb>1</TtlNb><Cml|
0190 74 76 41 6D 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 |tvAmt>2.16</Cmlt|
01A0 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 |vAmt></TxTtls><T|
01B0 78 54 74 6C 73 3E 3C 54 70 3E 44 42 54 52 3C 2F |xTtls><Tp>DBTR</|
01C0 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C |Tp><TtlNb>1</Ttl|
01D0 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 |Nb><CmltvAmt>2.1|
01E0 38 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 |8</CmltvAmt></Tx|
01F0 54 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 |Ttls><TxTtls><Tp|
0200 3E 44 45 42 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 |>DEBT</Tp><TtlNb|
0210 3E 33 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 |>3</TtlNb><Cmltv|
0220 41 6D 74 3E 31 37 2E 33 39 3C 2F 43 6D 6C 74 76 |Amt>17.39</Cmltv|
0230 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 |Amt></TxTtls><Tx|
0240 54 74 6C 73 3E 3C 54 70 3E 46 41 49 4C 3C 2F 54 |Ttls><Tp>FAIL</T|
0250 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E |p><TtlNb>1</TtlN|
0260 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 37 |b><CmltvAmt>2.17|
0270 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 |</CmltvAmt></TxT|
0280 74 6C 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E |tls><TxTtls><Tp>|
0290 43 52 44 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E |CRDT</Tp><TtlNb>|
02A0 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 |1</TtlNb><CmltvA|
02B0 6D 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 76 41 6D |mt>2.16</CmltvAm|
02C0 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 44 61 74 61 |t></TxTtls><Data|
02D0 53 65 74 3E 3C 44 61 74 61 53 65 74 49 64 3E 3C |Set><DataSetId><|
02E0 4E 6D 3E 44 61 74 61 53 65 74 30 3C 2F 4E 6D 3E |Nm>DataSet0</Nm>|
02F0 3C 54 70 3E 54 58 43 50 3C 2F 54 70 3E 3C 43 72 |<Tp>TXCP</Tp><Cr|
0300 65 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 |eDtTm>2015-12-03|
0310 54 31 35 3A 33 33 3A 35 32 2E 33 34 39 5A 3C 2F |T15:33:52.349Z</|
0320 43 72 65 44 74 54 6D 3E 3C 2F 44 61 74 61 53 65 |CreDtTm></DataSe|
0330 74 49 64 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E |tId><TxTtls><Tp>|
0340 43 52 44 52 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E |CRDR</Tp><TtlNb>|
0350 31 3C 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 |1</TtlNb><CmltvA|
0360 6D 74 3E 32 2E 31 36 3C 2F 43 6D 6C 74 76 41 6D |mt>2.16</CmltvAm|
0370 74 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 54 74 |t></TxTtls><TxTt|
0380 6C 73 3E 3C 54 70 3E 44 42 54 52 3C 2F 54 70 3E |ls><Tp>DBTR</Tp>|
0390 3C 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E |<TtlNb>1</TtlNb>|
03A0 3C 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 38 3C 2F |<CmltvAmt>2.18</|
03B0 43 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C |CmltvAmt></TxTtl|
03C0 73 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E 44 45 |s><TxTtls><Tp>DE|
03D0 42 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 34 3C |BT</Tp><TtlNb>4<|
03E0 2F 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 |/TtlNb><CmltvAmt|
03F0 3E 31 39 2E 35 37 3C 2F 43 6D 6C 74 76 41 6D 74 |>19.57</CmltvAmt|
0400 3E 3C 2F 54 78 54 74 6C 73 3E 3C 54 78 54 74 6C |></TxTtls><TxTtl|
0410 73 3E 3C 54 70 3E 46 41 49 4C 3C 2F 54 70 3E 3C |s><Tp>FAIL</Tp><|
0420 54 74 6C 4E 62 3E 31 3C 2F 54 74 6C 4E 62 3E 3C |TtlNb>1</TtlNb><|
0430 43 6D 6C 74 76 41 6D 74 3E 32 2E 31 37 3C 2F 43 |CmltvAmt>2.17</C|
0440 6D 6C 74 76 41 6D 74 3E 3C 2F 54 78 54 74 6C 73 |mltvAmt></TxTtls|
0450 3E 3C 54 78 54 74 6C 73 3E 3C 54 70 3E 43 52 44 |><TxTtls><Tp>CRD|
0460 54 3C 2F 54 70 3E 3C 54 74 6C 4E 62 3E 31 3C 2F |T</Tp><TtlNb>1</|

7 Messages Examples - 413 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0470 54 74 6C 4E 62 3E 3C 43 6D 6C 74 76 41 6D 74 3E |TtlNb><CmltvAmt>|
0480 32 2E 31 36 3C 2F 43 6D 6C 74 76 41 6D 74 3E 3C |2.16</CmltvAmt><|
0490 2F 54 78 54 74 6C 73 3E 3C 54 78 3E 3C 43 78 6C |/TxTtls><Tx><Cxl|
04A0 3E 3C 54 78 53 65 71 43 6E 74 72 3E 31 3C 2F 54 |><TxSeqCntr>1</T|
04B0 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 3E 3C |xSeqCntr><Envt><|
04C0 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 30 |Acqrr><Id><Id>00|
04D0 30 30 30 30 30 30 30 31 32 33 3C 2F 49 64 3E 3C |0000000123</Id><|
04E0 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E |/Id><ParamsVrsn>|
04F0 32 30 31 31 30 39 31 33 31 32 33 34 35 36 3C 2F |20110913123456</|
0500 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0510 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0520 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 44 30 |Id>MyMerchantID0|
0530 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D 6F |00</Id></Id><Cmo|
0540 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 72 74 |nNm>TestLab,cert|
0550 69 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 45 50 |ificationAVE,SEP|
0560 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 |A</CmonNm></Mrch|
0570 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 3E |nt><POI><Id><Id>|
0580 38 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C 2F 49 |88000001</Id></I|
0590 64 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 |d></POI><Card><P|
05A0 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 50 41 |lainCardData><PA|
05B0 4E 3E 35 30 37 31 30 30 39 39 39 39 31 30 30 30 |N>50710099991000|
05C0 31 33 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 65 71 |13</PAN><CardSeq|
05D0 4E 62 3E 30 31 3C 2F 43 61 72 64 53 65 71 4E 62 |Nb>01</CardSeqNb|
05E0 3E 3C 46 63 74 76 44 74 3E 32 30 31 32 2D 30 31 |><FctvDt>2012-01|
05F0 3C 2F 46 63 74 76 44 74 3E 3C 58 70 72 79 44 74 |</FctvDt><XpryDt|
0600 3E 32 30 32 30 2D 31 32 3C 2F 58 70 72 79 44 74 |>2020-12</XpryDt|
0610 3E 3C 53 76 63 43 64 3E 39 30 31 3C 2F 53 76 63 |><SvcCd>901</Svc|
0620 43 64 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 44 61 |Cd></PlainCardDa|
0630 74 61 3E 3C 43 61 72 64 43 74 72 79 43 64 3E 46 |ta><CardCtryCd>F|
0640 52 41 3C 2F 43 61 72 64 43 74 72 79 43 64 3E 3C |RA</CardCtryCd><|
0650 43 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 31 |CardPdctPrfl>001|
0660 37 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E |7</CardPdctPrfl>|
0670 3C 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 61 |<CardBrnd>CB</Ca|
0680 72 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F |rdBrnd></Card></|
0690 45 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 |Envt><Cntxt><Pmt|
06A0 43 6E 74 78 74 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 |Cntxt><OnLineCnt|
06B0 78 74 3E 66 61 6C 73 65 3C 2F 4F 6E 4C 69 6E 65 |xt>false</OnLine|
06C0 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 6E |Cntxt><AttndncCn|
06D0 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 6E |txt>ATTD</Attndn|
06E0 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 61 |cCntxt><CardData|
06F0 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 72 |NtryMd>CICC</Car|
0700 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 6D |dDataNtryMd></Pm|
0710 74 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C |tCntxt></Cntxt><|
0720 54 78 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 |Tx><MrchntCtgyCd|
0730 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 67 |>5999</MrchntCtg|
0740 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 |yCd><TxId><TxDtT|
0750 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 34 3A |m>2015-12-03T14:|
0760 30 33 3A 35 30 2E 30 30 30 3C 2F 54 78 44 74 54 |03:50.000</TxDtT|
0770 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 32 30 3C |m><TxRef>130220<|
0780 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C 4F |/TxRef></TxId><O|
0790 72 67 6E 6C 54 78 3E 3C 54 78 49 64 3E 3C 54 78 |rgnlTx><TxId><Tx|
07A0 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 |DtTm>2015-12-03T|
07B0 31 34 3A 30 37 3A 35 35 2E 30 30 30 3C 2F 54 78 |14:07:55.000</Tx|
07C0 44 74 54 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 |DtTm><TxRef>1302|
07D0 31 33 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 |13</TxRef></TxId|
07E0 3E 3C 54 78 54 70 3E 52 46 4E 44 3C 2F 54 78 54 |><TxTp>RFND</TxT|
07F0 70 3E 3C 54 78 52 73 6C 74 3E 3C 52 73 70 6E 54 |p><TxRslt><RspnT|
0800 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 |oAuthstn><Rspn>A|
0810 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E |PPR</Rspn></Rspn|
0820 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 |ToAuthstn><Auths|
0830 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 |tnCd>032983</Aut|
0840 68 73 74 6E 43 64 3E 3C 2F 54 78 52 73 6C 74 3E |hstnCd></TxRslt>|
0850 3C 2F 4F 72 67 6E 6C 54 78 3E 3C 54 78 53 75 63 |</OrgnlTx><TxSuc|
0860 73 73 3E 74 72 75 65 3C 2F 54 78 53 75 63 73 73 |ss>true</TxSucss|
0870 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 |><TxDtls><Ccy>EU|
0880 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 32 |R</Ccy><TtlAmt>2|
0890 2E 31 36 3C 2F 54 74 6C 41 6D 74 3E 3C 49 43 43 |.16</TtlAmt><ICC|
08A0 52 6C 74 64 44 61 74 61 3E 6E 77 49 47 41 41 41 |RltdData>nwIGAAA|

7 Messages Examples - 414 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

08B0 41 41 41 49 52 6E 77 4D 47 41 41 41 41 41 41 41 |AAAIRnwMGAAAAAAA|
08C0 41 6E 79 59 49 34 71 31 55 78 2F 4F 78 49 62 74 |AnyYI4q1Ux/OxIbt|
08D0 66 4A 51 4D 53 41 51 47 43 41 6A 30 41 68 77 45 |fJQMSAQGCAj0AhwE|
08E0 42 6E 7A 59 43 41 48 32 66 43 51 49 41 41 70 38 |BnzYCAH2fCQIAAp8|
08F0 6E 41 51 43 66 4E 41 4D 2F 41 41 43 45 42 36 41 |nAQCfNAM/AACEB6A|
0900 41 41 41 42 43 45 42 43 66 48 67 67 77 4D 54 45 |AAABCEBCfHggwMTE|
0910 79 4D 6A 4D 7A 4E 4A 38 51 45 67 45 51 41 41 41 |yMjMzNJ8QEgEQAAA|
0920 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
0930 41 41 4A 38 7A 41 2B 44 34 79 4A 38 61 41 67 41 |AAJ8zA+D4yJ8aAgA|
0940 51 6E 7A 55 42 49 70 55 46 41 41 41 41 41 41 42 |QnzUBIpUFAAAAAAB|
0950 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 6E 30 45 |fKgIJeJoDFRIDn0E|
0960 20 20 20 44 45 77 49 52 6E 41 45 41 6E 7A 63 45 | DEwIRnAEAnzcE|
0970 76 78 38 74 6C 73 6F 45 33 67 67 51 41 4D 55 42 |vx8tlsoE3ggQAMUB|
0980 41 4A 73 43 49 41 41 3D 3C 2F 49 43 43 52 6C 74 |AJsCIAA=</ICCRlt|
0990 64 44 61 74 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C |dData></TxDtls><|
09A0 2F 54 78 3E 3C 2F 43 78 6C 3E 3C 2F 54 78 3E 3C |/Tx></Cxl></Tx><|
09B0 54 78 3E 3C 43 78 6C 3E 3C 54 78 53 65 71 43 6E |Tx><Cxl><TxSeqCn|
09C0 74 72 3E 32 3C 2F 54 78 53 65 71 43 6E 74 72 3E |tr>2</TxSeqCntr>|
09D0 3C 45 6E 76 74 3E 3C 41 63 71 72 72 3E 3C 49 64 |<Envt><Acqrr><Id|
09E0 3E 3C 49 64 3E 30 30 30 30 30 30 30 30 30 31 32 |><Id>00000000012|
09F0 33 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 50 61 72 61 |3</Id></Id><Para|
0A00 6D 73 56 72 73 6E 3E 32 30 31 31 30 39 31 33 31 |msVrsn>201109131|
0A10 32 33 34 35 36 3C 2F 50 61 72 61 6D 73 56 72 73 |23456</ParamsVrs|
0A20 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D 72 63 68 6E |n></Acqrr><Mrchn|
0A30 74 3E 3C 49 64 3E 3C 49 64 3E 4D 79 4D 65 72 63 |t><Id><Id>MyMerc|
0A40 68 61 6E 74 49 44 30 30 30 3C 2F 49 64 3E 3C 2F |hantID000</Id></|
0A50 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 54 65 73 74 4C |Id><CmonNm>TestL|
0A60 61 62 2C 63 65 72 74 69 66 69 63 61 74 69 6F 6E |ab,certification|
0A70 41 56 45 2C 53 45 50 41 3C 2F 43 6D 6F 6E 4E 6D |AVE,SEPA</CmonNm|
0A80 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C |></Mrchnt><POI><|
0A90 49 64 3E 3C 49 64 3E 38 38 30 30 30 30 30 31 3C |Id><Id>88000001<|
0AA0 2F 49 64 3E 3C 2F 49 64 3E 3C 2F 50 4F 49 3E 3C |/Id></Id></POI><|
0AB0 43 61 72 64 3E 3C 50 6C 61 69 6E 43 61 72 64 44 |Card><PlainCardD|
0AC0 61 74 61 3E 3C 50 41 4E 3E 35 30 37 31 30 30 39 |ata><PAN>5071009|
0AD0 39 39 39 31 30 30 30 31 33 3C 2F 50 41 4E 3E 3C |999100013</PAN><|
0AE0 43 61 72 64 53 65 71 4E 62 3E 30 31 3C 2F 43 61 |CardSeqNb>01</Ca|
0AF0 72 64 53 65 71 4E 62 3E 3C 46 63 74 76 44 74 3E |rdSeqNb><FctvDt>|
0B00 32 30 31 32 2D 30 31 3C 2F 46 63 74 76 44 74 3E |2012-01</FctvDt>|
0B10 3C 58 70 72 79 44 74 3E 32 30 32 30 2D 31 32 3C |<XpryDt>2020-12<|
0B20 2F 58 70 72 79 44 74 3E 3C 53 76 63 43 64 3E 39 |/XpryDt><SvcCd>9|
0B30 30 31 3C 2F 53 76 63 43 64 3E 3C 2F 50 6C 61 69 |01</SvcCd></Plai|
0B40 6E 43 61 72 64 44 61 74 61 3E 3C 43 61 72 64 43 |nCardData><CardC|
0B50 74 72 79 43 64 3E 46 52 41 3C 2F 43 61 72 64 43 |tryCd>FRA</CardC|
0B60 74 72 79 43 64 3E 3C 43 61 72 64 50 64 63 74 50 |tryCd><CardPdctP|
0B70 72 66 6C 3E 30 30 31 37 3C 2F 43 61 72 64 50 64 |rfl>0017</CardPd|
0B80 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E 64 |ctPrfl><CardBrnd|
0B90 3E 43 42 3C 2F 43 61 72 64 42 72 6E 64 3E 3C 2F |>CB</CardBrnd></|
0BA0 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 6E 74 |Card></Envt><Cnt|
0BB0 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C 4F 6E |xt><PmtCntxt><On|
0BC0 4C 69 6E 65 43 6E 74 78 74 3E 66 61 6C 73 65 3C |LineCntxt>false<|
0BD0 2F 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 3C 41 74 |/OnLineCntxt><At|
0BE0 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 54 44 3C |tndncCntxt>ATTD<|
0BF0 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 3C 43 |/AttndncCntxt><C|
0C00 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 43 49 |ardDataNtryMd>CI|
0C10 43 43 3C 2F 43 61 72 64 44 61 74 61 4E 74 72 79 |CC</CardDataNtry|
0C20 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E 3C 2F |Md></PmtCntxt></|
0C30 43 6E 74 78 74 3E 3C 54 78 3E 3C 4D 72 63 68 6E |Cntxt><Tx><Mrchn|
0C40 74 43 74 67 79 43 64 3E 35 39 39 39 3C 2F 4D 72 |tCtgyCd>5999</Mr|
0C50 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 78 49 64 |chntCtgyCd><TxId|
0C60 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 32 |><TxDtTm>2015-12|
0C70 2D 30 33 54 31 34 3A 33 36 3A 34 36 2E 30 30 30 |-03T14:36:46.000|
0C80 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E |</TxDtTm><TxRef>|
0C90 31 33 30 32 31 39 3C 2F 54 78 52 65 66 3E 3C 2F |130219</TxRef></|
0CA0 54 78 49 64 3E 3C 4F 72 67 6E 6C 54 78 3E 3C 54 |TxId><OrgnlTx><T|
0CB0 78 49 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 |xId><TxDtTm>2015|
0CC0 2D 31 32 2D 30 33 54 31 34 3A 32 38 3A 34 30 2E |-12-03T14:28:40.|
0CD0 30 30 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 |000</TxDtTm><TxR|
0CE0 65 66 3E 31 33 30 32 31 36 3C 2F 54 78 52 65 66 |ef>130216</TxRef|

7 Messages Examples - 415 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

0CF0 3E 3C 2F 54 78 49 64 3E 3C 54 78 54 70 3E 43 52 |></TxId><TxTp>CR|
0D00 44 50 3C 2F 54 78 54 70 3E 3C 2F 4F 72 67 6E 6C |DP</TxTp></Orgnl|
0D10 54 78 3E 3C 54 78 53 75 63 73 73 3E 74 72 75 65 |Tx><TxSucss>true|
0D20 3C 2F 54 78 53 75 63 73 73 3E 3C 54 78 44 74 6C |</TxSucss><TxDtl|
0D30 73 3E 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E |s><Ccy>EUR</Ccy>|
0D40 3C 54 74 6C 41 6D 74 3E 32 2E 30 31 3C 2F 54 74 |<TtlAmt>2.01</Tt|
0D50 6C 41 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 |lAmt><ICCRltdDat|
0D60 61 3E 6E 77 49 47 41 41 41 41 41 41 49 42 6E 77 |a>nwIGAAAAAAIBnw|
0D70 4D 47 41 41 41 41 41 41 41 41 6E 79 59 49 43 4D |MGAAAAAAAAnyYICM|
0D80 36 71 51 61 74 79 5A 76 4A 66 4A 51 4D 53 41 51 |6qQatyZvJfJQMSAQ|
0D90 47 43 41 6A 30 41 68 77 45 42 6E 7A 59 43 41 48 |GCAj0AhwEBnzYCAH|
0DA0 32 66 43 51 49 41 41 70 38 6E 41 51 43 66 4E 41 |2fCQIAAp8nAQCfNA|
0DB0 4D 2F 41 41 43 45 42 36 41 41 41 41 42 43 45 42 |M/AACEB6AAAABCEB|
0DC0 43 66 48 67 67 77 4D 54 45 79 4D 6A 4D 7A 4E 4A |CfHggwMTEyMjMzNJ|
0DD0 38 51 45 67 45 51 41 41 41 41 41 41 41 41 41 41 |8QEgEQAAAAAAAAAA|
0DE0 41 41 41 41 41 41 41 41 41 41 41 4A 38 7A 41 2B |AAAAAAAAAAAJ8zA+|
0DF0 44 34 79 4A 38 61 41 67 41 51 6E 7A 55 42 49 70 |D4yJ8aAgAQnzUBIp|
0E00 55 46 41 41 41 41 41 41 42 66 4B 67 49 4A 65 4A |UFAAAAAABfKgIJeJ|
0E10 6F 44 46 52 49 44 6E 30 45 44 45 77 49 4A 6E 41 |oDFRIDn0EDEwIJnA|
0E20 45 41 6E 7A 63 45 2B 65 73 6C 53 63 6F 45 33 67 |EAnzcE+eslScoE3g|
0E30 67 51 41 4D 55 42 41 4A 73 43 49 41 41 3D 3C 2F |gQAMUBAJsCIAA=</|
0E40 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F 54 78 |ICCRltdData></Tx|
0E50 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F 43 78 6C 3E |Dtls></Tx></Cxl>|
0E60 3C 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 6C 74 6E |</Tx><Tx><Cmpltn|
0E70 3E 3C 54 78 53 65 71 43 6E 74 72 3E 33 3C 2F 54 |><TxSeqCntr>3</T|
0E80 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 3E 3C |xSeqCntr><Envt><|
0E90 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 30 |Acqrr><Id><Id>00|
0EA0 30 30 30 30 30 30 30 31 32 33 3C 2F 49 64 3E 3C |0000000123</Id><|
0EB0 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E |/Id><ParamsVrsn>|
0EC0 32 30 31 31 30 39 31 33 31 32 33 34 35 36 3C 2F |20110913123456</|
0ED0 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 |ParamsVrsn></Acq|
0EE0 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C |rr><Mrchnt><Id><|
0EF0 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 44 30 |Id>MyMerchantID0|
0F00 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D 6F |00</Id></Id><Cmo|
0F10 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 72 74 |nNm>TestLab,cert|
0F20 69 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 45 50 |ificationAVE,SEP|
0F30 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 |A</CmonNm></Mrch|
0F40 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 3E |nt><POI><Id><Id>|
0F50 38 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C 2F 49 |88000001</Id></I|
0F60 64 3E 3C 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 |d><Cpblties><Car|
0F70 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 50 48 |dRdngCpblties>PH|
0F80 59 53 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C |YS</CardRdngCpbl|
0F90 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 |ties><CardRdngCp|
0FA0 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F 43 61 72 |blties>MGST</Car|
0FB0 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 |dRdngCpblties><C|
0FC0 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
0FD0 43 49 43 43 3C 2F 43 61 72 64 52 64 6E 67 43 70 |CICC</CardRdngCp|
0FE0 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 |blties><CardRdng|
0FF0 43 70 62 6C 74 69 65 73 3E 45 43 54 4C 3C 2F 43 |Cpblties>ECTL</C|
1000 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
1010 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |<CrdhldrVrfctnCp|
1020 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 72 64 |blties>FCPN</Crd|
1030 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
1040 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 |es><CrdhldrVrfct|
1050 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E 3C 2F |nCpblties>NPIN</|
1060 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
1070 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 |lties><CrdhldrVr|
1080 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4D 4E 53 |fctnCpblties>MNS|
1090 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E |G</CrdhldrVrfctn|
10A0 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 |Cpblties><Crdhld|
10B0 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
10C0 46 45 50 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 |FEPN</CrdhldrVrf|
10D0 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C |ctnCpblties><OnL|
10E0 69 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E |ineCpblties>SMON|
10F0 3C 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 |</OnLineCpblties|
1100 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 |><MsgCpblties><D|
1110 73 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C |stn>MDSP</Dstn><|
1120 4E 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F 4E 62 4F |NbOfLines>8</NbO|

7 Messages Examples - 416 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1130 66 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 |fLines><LineWidt|
1140 68 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 74 68 3E |h>15</LineWidth>|
1150 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D |</MsgCpblties><M|
1160 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E |sgCpblties><Dstn|
1170 3E 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4C 69 6E |>MRCP</Dstn><Lin|
1180 65 57 69 64 74 68 3E 32 34 3C 2F 4C 69 6E 65 57 |eWidth>24</LineW|
1190 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 |idth></MsgCpblti|
11A0 65 73 3E 3C 2F 43 70 62 6C 74 69 65 73 3E 3C 43 |es></Cpblties><C|
11B0 6D 70 6E 74 3E 3C 54 70 3E 54 45 52 4D 3C 2F 54 |mpnt><Tp>TERM</T|
11C0 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 |p><Id><PrvdrId>I|
11D0 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 |NGENICO</PrvdrId|
11E0 3E 3C 49 64 3E 49 43 54 32 35 30 3C 2F 49 64 3E |><Id>ICT250</Id>|
11F0 3C 53 72 6C 4E 62 3E 31 31 32 32 33 33 34 3C 2F |<SrlNb>1122334</|
1200 53 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 6D 70 |SrlNb></Id></Cmp|
1210 6E 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 41 50 |nt><Cmpnt><Tp>AP|
1220 4C 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 |LI</Tp><Id><Prvd|
1230 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 |rId>INGENICO</Pr|
1240 76 64 72 49 64 3E 3C 49 64 3E 53 45 50 41 2D 46 |vdrId><Id>SEPA-F|
1250 41 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 53 74 |AST</Id></Id><St|
1260 73 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E 31 30 3C |s><VrsnNb>04.10<|
1270 2F 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 3E 3C 53 |/VrsnNb></Sts><S|
1280 74 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 45 50 41 |tdCmplc><Id>SEPA|
1290 2D 46 41 53 54 3C 2F 49 64 3E 3C 56 72 73 6E 3E |-FAST</Id><Vrsn>|
12A0 33 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 73 72 3E |3.1</Vrsn><Issr>|
12B0 4F 53 43 41 52 3C 2F 49 73 73 72 3E 3C 2F 53 74 |OSCAR</Issr></St|
12C0 64 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E 74 3E 3C |dCmplc><Assmnt><|
12D0 54 70 3E 43 45 52 54 3C 2F 54 70 3E 3C 41 73 73 |Tp>CERT</Tp><Ass|
12E0 67 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 73 67 6E |gnr>OSCAR</Assgn|
12F0 72 3E 3C 44 6C 76 72 79 44 74 3E 32 30 31 34 2D |r><DlvryDt>2014-|
1300 30 35 2D 31 34 54 31 37 3A 31 32 3A 30 35 2E 30 |05-14T17:12:05.0|
1310 30 30 5A 3C 2F 44 6C 76 72 79 44 74 3E 3C 58 70 |00Z</DlvryDt><Xp|
1320 72 74 6E 44 74 3E 32 30 32 31 2D 30 31 2D 31 32 |rtnDt>2021-01-12|
1330 54 30 39 3A 30 37 3A 31 38 2E 30 30 30 5A 3C 2F |T09:07:18.000Z</|
1340 58 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 41 59 2E |XprtnDt><Nb>PAY.|
1350 45 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 32 30 2E |ELI.ING.POI.120.|
1360 31 33 30 33 30 30 30 32 3C 2F 4E 62 3E 3C 2F 41 |13030002</Nb></A|
1370 73 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 3E 3C 2F |ssmnt></Cmpnt></|
1380 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 6E |POI><Card><Plain|
1390 43 61 72 64 44 61 74 61 3E 3C 50 41 4E 3E 35 34 |CardData><PAN>54|
13A0 31 33 33 33 30 30 31 30 30 30 30 37 31 30 3C 2F |13330010000710</|
13B0 50 41 4E 3E 3C 43 61 72 64 53 65 71 4E 62 3E 30 |PAN><CardSeqNb>0|
13C0 30 3C 2F 43 61 72 64 53 65 71 4E 62 3E 3C 46 63 |0</CardSeqNb><Fc|
13D0 74 76 44 74 3E 32 30 31 30 2D 31 32 3C 2F 46 63 |tvDt>2010-12</Fc|
13E0 74 76 44 74 3E 3C 58 70 72 79 44 74 3E 32 30 31 |tvDt><XpryDt>201|
13F0 35 2D 31 32 3C 2F 58 70 72 79 44 74 3E 3C 53 76 |5-12</XpryDt><Sv|
1400 63 43 64 3E 32 30 31 3C 2F 53 76 63 43 64 3E 3C |cCd>201</SvcCd><|
1410 2F 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C |/PlainCardData><|
1420 43 61 72 64 43 74 72 79 43 64 3E 44 45 55 3C 2F |CardCtryCd>DEU</|
1430 43 61 72 64 43 74 72 79 43 64 3E 3C 43 61 72 64 |CardCtryCd><Card|
1440 50 64 63 74 50 72 66 6C 3E 30 30 31 38 3C 2F 43 |PdctPrfl>0018</C|
1450 61 72 64 50 64 63 74 50 72 66 6C 3E 3C 43 61 72 |ardPdctPrfl><Car|
1460 64 42 72 6E 64 3E 43 42 3C 2F 43 61 72 64 42 72 |dBrnd>CB</CardBr|
1470 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 |nd></Card></Envt|
1480 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 |><Cntxt><PmtCntx|
1490 74 3E 3C 43 72 64 68 6C 64 72 50 72 65 73 3E 74 |t><CrdhldrPres>t|
14A0 72 75 65 3C 2F 43 72 64 68 6C 64 72 50 72 65 73 |rue</CrdhldrPres|
14B0 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 74 72 |><OnLineCntxt>tr|
14C0 75 65 3C 2F 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E |ue</OnLineCntxt>|
14D0 3C 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 |<AttndncCntxt>AT|
14E0 54 44 3C 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 |TD</AttndncCntxt|
14F0 3E 3C 43 61 72 64 44 61 74 61 4E 74 72 79 4D 64 |><CardDataNtryMd|
1500 3E 43 49 43 43 3C 2F 43 61 72 64 44 61 74 61 4E |>CICC</CardDataN|
1510 74 72 79 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 |tryMd></PmtCntxt|
1520 3E 3C 53 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C |><SaleCntxt><Sal|
1530 65 52 65 66 4E 62 3E 30 30 30 30 30 30 30 30 31 |eRefNb>000000001|
1540 31 31 31 31 31 31 31 2F 32 30 31 35 31 32 30 33 |1111111/20151203|
1550 31 34 33 33 30 33 3C 2F 53 61 6C 65 52 65 66 4E |143303</SaleRefN|
1560 62 3E 3C 43 73 68 72 49 64 3E 30 30 30 30 30 30 |b><CshrId>000000|

7 Messages Examples - 417 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1570 30 31 3C 2F 43 73 68 72 49 64 3E 3C 2F 53 61 6C |01</CshrId></Sal|
1580 65 43 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C |eCntxt></Cntxt><|
1590 54 78 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 |Tx><TxTp>CRDP</T|
15A0 78 54 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 |xTp><MrchntCtgyC|
15B0 64 3E 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 |d>5999</MrchntCt|
15C0 67 79 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 |gyCd><TxId><TxDt|
15D0 54 6D 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 34 |Tm>2015-12-03T14|
15E0 3A 33 33 3A 30 33 2E 30 30 30 3C 2F 54 78 44 74 |:33:03.000</TxDt|
15F0 54 6D 3E 3C 54 78 52 65 66 3E 31 33 30 32 31 38 |Tm><TxRef>130218|
1600 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C |</TxRef></TxId><|
1610 54 78 53 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 |TxSucss>true</Tx|
1620 53 75 63 73 73 3E 3C 52 76 73 6C 3E 66 61 6C 73 |Sucss><Rvsl>fals|
1630 65 3C 2F 52 76 73 6C 3E 3C 54 78 44 74 6C 73 3E |e</Rvsl><TxDtls>|
1640 3C 43 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 |<Ccy>EUR</Ccy><T|
1650 74 6C 41 6D 74 3E 30 2E 30 31 3C 2F 54 74 6C 41 |tlAmt>0.01</TtlA|
1660 6D 74 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E |mt><ICCRltdData>|
1670 6E 77 49 47 41 41 41 41 41 41 41 42 6E 77 4D 47 |nwIGAAAAAAABnwMG|
1680 41 41 41 41 41 41 41 41 6E 79 59 49 32 6E 74 35 |AAAAAAAAnyYI2nt5|
1690 4D 47 58 6F 71 55 6C 66 4A 51 4D 51 45 67 47 43 |MGXoqUlfJQMQEgGC|
16A0 41 6C 67 41 6E 7A 59 43 45 53 4B 66 43 51 49 41 |AlgAnzYCESKfCQIA|
16B0 41 70 38 6E 41 55 43 66 4E 41 4E 42 41 77 4B 45 |Ap8nAUCfNANBAwKE|
16C0 42 36 41 41 41 41 41 45 45 42 43 66 48 67 67 77 |B6AAAAAEEBCfHggw|
16D0 4D 54 45 79 4D 6A 4D 7A 4E 4A 38 51 45 67 45 51 |MTEyMjMzNJ8QEgEQ|
16E0 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
16F0 41 41 41 41 41 4A 38 7A 41 2B 44 34 79 4A 38 61 |AAAAAJ8zA+D4yJ8a|
1700 41 67 41 51 6E 7A 55 42 49 70 55 46 41 67 41 41 |AgAQnzUBIpUFAgAA|
1710 41 41 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 |AABfKgIJeJoDFRID|
1720 6E 30 45 44 45 77 49 59 6E 41 45 41 6E 7A 63 45 |n0EDEwIYnAEAnzcE|
1730 66 76 43 74 67 73 6F 45 2F 2F 78 51 41 4D 55 42 |fvCtgsoE//xQAMUB|
1740 41 4A 73 43 36 41 41 3D 3C 2F 49 43 43 52 6C 74 |AJsC6AA=</ICCRlt|
1750 64 44 61 74 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C |dData></TxDtls><|
1760 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C 41 75 74 |AuthstnRslt><Aut|
1770 68 73 74 6E 4E 74 74 79 3E 3C 54 70 3E 43 49 53 |hstnNtty><Tp>CIS|
1780 53 3C 2F 54 70 3E 3C 2F 41 75 74 68 73 74 6E 4E |S</Tp></AuthstnN|
1790 74 74 79 3E 3C 52 73 70 6E 54 6F 41 75 74 68 73 |tty><RspnToAuths|
17A0 74 6E 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F 52 |tn><Rspn>APPR</R|
17B0 73 70 6E 3E 3C 2F 52 73 70 6E 54 6F 41 75 74 68 |spn></RspnToAuth|
17C0 73 74 6E 3E 3C 41 75 74 68 73 74 6E 43 64 3E 30 |stn><AuthstnCd>0|
17D0 33 32 39 38 33 3C 2F 41 75 74 68 73 74 6E 43 64 |32983</AuthstnCd|
17E0 3E 3C 2F 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C |></AuthstnRslt><|
17F0 2F 54 78 3E 3C 2F 43 6D 70 6C 74 6E 3E 3C 2F 54 |/Tx></Cmpltn></T|
1800 78 3E 3C 54 78 3E 3C 43 6D 70 6C 74 6E 3E 3C 54 |x><Tx><Cmpltn><T|
1810 78 53 65 71 43 6E 74 72 3E 34 3C 2F 54 78 53 65 |xSeqCntr>4</TxSe|
1820 71 43 6E 74 72 3E 3C 45 6E 76 74 3E 3C 41 63 71 |qCntr><Envt><Acq|
1830 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 30 30 30 30 |rr><Id><Id>00000|
1840 30 30 30 30 31 32 33 3C 2F 49 64 3E 3C 2F 49 64 |0000123</Id></Id|
1850 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 |><ParamsVrsn>201|
1860 31 30 39 31 33 31 32 33 34 35 36 3C 2F 50 61 72 |10913123456</Par|
1870 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 71 72 72 3E |amsVrsn></Acqrr>|
1880 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E |<Mrchnt><Id><Id>|
1890 4D 79 4D 65 72 63 68 61 6E 74 49 44 30 30 30 3C |MyMerchantID000<|
18A0 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D |/Id></Id><CmonNm|
18B0 3E 54 65 73 74 4C 61 62 2C 63 65 72 74 69 66 69 |>TestLab,certifi|
18C0 63 61 74 69 6F 6E 41 56 45 2C 53 45 50 41 3C 2F |cationAVE,SEPA</|
18D0 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 6E 74 3E |CmonNm></Mrchnt>|
18E0 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 3E 38 38 30 |<POI><Id><Id>880|
18F0 30 30 30 30 31 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |00001</Id></Id><|
1900 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 |Cpblties><CardRd|
1910 6E 67 43 70 62 6C 74 69 65 73 3E 50 48 59 53 3C |ngCpblties>PHYS<|
1920 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |/CardRdngCpbltie|
1930 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |s><CardRdngCpblt|
1940 69 65 73 3E 4D 47 53 54 3C 2F 43 61 72 64 52 64 |ies>MGST</CardRd|
1950 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 |ngCpblties><Card|
1960 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 43 49 43 |RdngCpblties>CIC|
1970 43 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |C</CardRdngCpblt|
1980 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 |ies><CardRdngCpb|
1990 6C 74 69 65 73 3E 45 43 54 4C 3C 2F 43 61 72 64 |lties>ECTL</Card|
19A0 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 72 |RdngCpblties><Cr|

7 Messages Examples - 418 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

19B0 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 |dhldrVrfctnCpblt|
19C0 69 65 73 3E 46 43 50 4E 3C 2F 43 72 64 68 6C 64 |ies>FCPN</Crdhld|
19D0 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
19E0 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |<CrdhldrVrfctnCp|
19F0 62 6C 74 69 65 73 3E 4E 50 49 4E 3C 2F 43 72 64 |blties>NPIN</Crd|
1A00 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
1A10 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 |es><CrdhldrVrfct|
1A20 6E 43 70 62 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F |nCpblties>MNSG</|
1A30 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
1A40 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 |lties><CrdhldrVr|
1A50 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 |fctnCpblties>FEP|
1A60 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E |N</CrdhldrVrfctn|
1A70 43 70 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 |Cpblties><OnLine|
1A80 43 70 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F |Cpblties>SMON</O|
1A90 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 3C 4D |nLineCpblties><M|
1AA0 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E |sgCpblties><Dstn|
1AB0 3E 4D 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F |>MDSP</Dstn><NbO|
1AC0 66 4C 69 6E 65 73 3E 38 3C 2F 4E 62 4F 66 4C 69 |fLines>8</NbOfLi|
1AD0 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 31 |nes><LineWidth>1|
1AE0 35 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D |5</LineWidth></M|
1AF0 73 67 43 70 62 6C 74 69 65 73 3E 3C 4D 73 67 43 |sgCpblties><MsgC|
1B00 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E 4D 52 |pblties><Dstn>MR|
1B10 43 50 3C 2F 44 73 74 6E 3E 3C 4C 69 6E 65 57 69 |CP</Dstn><LineWi|
1B20 64 74 68 3E 32 34 3C 2F 4C 69 6E 65 57 69 64 74 |dth>24</LineWidt|
1B30 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E |h></MsgCpblties>|
1B40 3C 2F 43 70 62 6C 74 69 65 73 3E 3C 43 6D 70 6E |</Cpblties><Cmpn|
1B50 74 3E 3C 54 70 3E 54 45 52 4D 3C 2F 54 70 3E 3C |t><Tp>TERM</Tp><|
1B60 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 4E 47 45 |Id><PrvdrId>INGE|
1B70 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 3E 3C 49 |NICO</PrvdrId><I|
1B80 64 3E 49 43 54 32 35 30 3C 2F 49 64 3E 3C 53 72 |d>ICT250</Id><Sr|
1B90 6C 4E 62 3E 31 31 32 32 33 33 34 3C 2F 53 72 6C |lNb>1122334</Srl|
1BA0 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 6D 70 6E 74 3E |Nb></Id></Cmpnt>|
1BB0 3C 43 6D 70 6E 74 3E 3C 54 70 3E 41 50 4C 49 3C |<Cmpnt><Tp>APLI<|
1BC0 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 |/Tp><Id><PrvdrId|
1BD0 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 |>INGENICO</Prvdr|
1BE0 49 64 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 |Id><Id>SEPA-FAST|
1BF0 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C |</Id></Id><Sts><|
1C00 56 72 73 6E 4E 62 3E 30 34 2E 31 30 3C 2F 56 72 |VrsnNb>04.10</Vr|
1C10 73 6E 4E 62 3E 3C 2F 53 74 73 3E 3C 53 74 64 43 |snNb></Sts><StdC|
1C20 6D 70 6C 63 3E 3C 49 64 3E 53 45 50 41 2D 46 41 |mplc><Id>SEPA-FA|
1C30 53 54 3C 2F 49 64 3E 3C 56 72 73 6E 3E 33 2E 31 |ST</Id><Vrsn>3.1|
1C40 3C 2F 56 72 73 6E 3E 3C 49 73 73 72 3E 4F 53 43 |</Vrsn><Issr>OSC|
1C50 41 52 3C 2F 49 73 73 72 3E 3C 2F 53 74 64 43 6D |AR</Issr></StdCm|
1C60 70 6C 63 3E 3C 41 73 73 6D 6E 74 3E 3C 54 70 3E |plc><Assmnt><Tp>|
1C70 43 45 52 54 3C 2F 54 70 3E 3C 41 73 73 67 6E 72 |CERT</Tp><Assgnr|
1C80 3E 4F 53 43 41 52 3C 2F 41 73 73 67 6E 72 3E 3C |>OSCAR</Assgnr><|
1C90 44 6C 76 72 79 44 74 3E 32 30 31 34 2D 30 35 2D |DlvryDt>2014-05-|
1CA0 31 34 54 31 37 3A 31 32 3A 30 35 2E 30 30 30 5A |14T17:12:05.000Z|
1CB0 3C 2F 44 6C 76 72 79 44 74 3E 3C 58 70 72 74 6E |</DlvryDt><Xprtn|
1CC0 44 74 3E 32 30 32 31 2D 30 31 2D 31 32 54 30 39 |Dt>2021-01-12T09|
1CD0 3A 30 37 3A 31 38 2E 30 30 30 5A 3C 2F 58 70 72 |:07:18.000Z</Xpr|
1CE0 74 6E 44 74 3E 3C 4E 62 3E 50 41 59 2E 45 4C 49 |tnDt><Nb>PAY.ELI|
1CF0 2E 49 4E 47 2E 50 4F 49 2E 31 32 30 2E 31 33 30 |.ING.POI.120.130|
1D00 33 30 30 30 32 3C 2F 4E 62 3E 3C 2F 41 73 73 6D |30002</Nb></Assm|
1D10 6E 74 3E 3C 2F 43 6D 70 6E 74 3E 3C 2F 50 4F 49 |nt></Cmpnt></POI|
1D20 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 6E 43 61 72 |><Card><PlainCar|
1D30 64 44 61 74 61 3E 3C 50 41 4E 3E 35 34 31 33 33 |dData><PAN>54133|
1D40 33 30 30 31 30 30 30 30 37 31 30 3C 2F 50 41 4E |30010000710</PAN|
1D50 3E 3C 43 61 72 64 53 65 71 4E 62 3E 30 30 3C 2F |><CardSeqNb>00</|
1D60 43 61 72 64 53 65 71 4E 62 3E 3C 46 63 74 76 44 |CardSeqNb><FctvD|
1D70 74 3E 32 30 31 30 2D 31 32 3C 2F 46 63 74 76 44 |t>2010-12</FctvD|
1D80 74 3E 3C 58 70 72 79 44 74 3E 32 30 31 35 2D 31 |t><XpryDt>2015-1|
1D90 32 3C 2F 58 70 72 79 44 74 3E 3C 53 76 63 43 64 |2</XpryDt><SvcCd|
1DA0 3E 32 30 31 3C 2F 53 76 63 43 64 3E 3C 2F 50 6C |>201</SvcCd></Pl|
1DB0 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 43 61 72 |ainCardData><Car|
1DC0 64 43 74 72 79 43 64 3E 44 45 55 3C 2F 43 61 72 |dCtryCd>DEU</Car|
1DD0 64 43 74 72 79 43 64 3E 3C 43 61 72 64 50 64 63 |dCtryCd><CardPdc|
1DE0 74 50 72 66 6C 3E 30 30 31 38 3C 2F 43 61 72 64 |tPrfl>0018</Card|

7 Messages Examples - 419 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

1DF0 50 64 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 |PdctPrfl><CardBr|
1E00 6E 64 3E 43 42 3C 2F 43 61 72 64 42 72 6E 64 3E |nd>CB</CardBrnd>|
1E10 3C 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 |</Card></Envt><C|
1E20 6E 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C |ntxt><PmtCntxt><|
1E30 43 72 64 68 6C 64 72 50 72 65 73 3E 74 72 75 65 |CrdhldrPres>true|
1E40 3C 2F 43 72 64 68 6C 64 72 50 72 65 73 3E 3C 4F |</CrdhldrPres><O|
1E50 6E 4C 69 6E 65 43 6E 74 78 74 3E 74 72 75 65 3C |nLineCntxt>true<|
1E60 2F 4F 6E 4C 69 6E 65 43 6E 74 78 74 3E 3C 41 74 |/OnLineCntxt><At|
1E70 74 6E 64 6E 63 43 6E 74 78 74 3E 41 54 54 44 3C |tndncCntxt>ATTD<|
1E80 2F 41 74 74 6E 64 6E 63 43 6E 74 78 74 3E 3C 43 |/AttndncCntxt><C|
1E90 61 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 43 49 |ardDataNtryMd>CI|
1EA0 43 43 3C 2F 43 61 72 64 44 61 74 61 4E 74 72 79 |CC</CardDataNtry|
1EB0 4D 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E 3C 53 |Md></PmtCntxt><S|
1EC0 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C 65 52 65 |aleCntxt><SaleRe|
1ED0 66 4E 62 3E 30 30 30 30 30 30 30 30 31 31 31 31 |fNb>000000001111|
1EE0 31 31 31 31 2F 32 30 31 35 31 32 30 33 31 34 33 |1111/20151203143|
1EF0 31 33 34 3C 2F 53 61 6C 65 52 65 66 4E 62 3E 3C |134</SaleRefNb><|
1F00 43 73 68 72 49 64 3E 30 30 30 30 30 30 30 31 3C |CshrId>00000001<|
1F10 2F 43 73 68 72 49 64 3E 3C 2F 53 61 6C 65 43 6E |/CshrId></SaleCn|
1F20 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C 54 78 3E |txt></Cntxt><Tx>|
1F30 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 78 54 70 |<TxTp>CRDP</TxTp|
1F40 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 3E 35 |><MrchntCtgyCd>5|
1F50 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 67 79 43 |999</MrchntCtgyC|
1F60 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D 3E |d><TxId><TxDtTm>|
1F70 32 30 31 35 2D 31 32 2D 30 33 54 31 34 3A 33 31 |2015-12-03T14:31|
1F80 3A 33 34 2E 30 30 30 3C 2F 54 78 44 74 54 6D 3E |:34.000</TxDtTm>|
1F90 3C 54 78 52 65 66 3E 31 33 30 32 31 37 3C 2F 54 |<TxRef>130217</T|
1FA0 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 78 53 |xRef></TxId><TxS|
1FB0 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 75 63 |ucss>true</TxSuc|
1FC0 73 73 3E 3C 52 76 73 6C 3E 66 61 6C 73 65 3C 2F |ss><Rvsl>false</|
1FD0 52 76 73 6C 3E 3C 54 78 44 74 6C 73 3E 3C 43 63 |Rvsl><TxDtls><Cc|
1FE0 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C 41 |y>EUR</Ccy><TtlA|
1FF0 6D 74 3E 31 35 2E 32 31 3C 2F 54 74 6C 41 6D 74 |mt>15.21</TtlAmt|
2000 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E 6E 77 |><ICCRltdData>nw|
2010 49 47 41 41 41 41 41 42 55 68 6E 77 4D 47 41 41 |IGAAAAABUhnwMGAA|
2020 41 41 41 41 41 41 6E 79 59 49 53 64 6F 6B 34 4B |AAAAAAnyYISdok4K|
2030 6D 4E 30 34 6C 66 4A 51 4D 51 45 67 47 43 41 6C |mN04lfJQMQEgGCAl|
2040 67 41 6E 7A 59 43 45 53 4B 66 43 51 49 41 41 70 |gAnzYCESKfCQIAAp|
2050 38 6E 41 55 43 66 4E 41 4E 42 41 77 4B 45 42 36 |8nAUCfNANBAwKEB6|
2060 41 41 41 41 41 45 45 42 43 66 48 67 67 77 4D 54 |AAAAAEEBCfHggwMT|
2070 45 79 4D 6A 4D 7A 4E 4A 38 51 45 67 45 51 41 41 |EyMjMzNJ8QEgEQAA|
2080 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 |AAAAAAAAAAAAAAAA|
2090 41 41 41 4A 38 7A 41 2B 44 34 79 4A 38 61 41 67 |AAAJ8zA+D4yJ8aAg|
20A0 41 51 6E 7A 55 42 49 70 55 46 41 67 41 41 41 41 |AQnzUBIpUFAgAAAA|
20B0 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 6E 30 |BfKgIJeJoDFRIDn0|
20C0 45 44 45 77 49 58 6E 41 45 41 6E 7A 63 45 57 6A |EDEwIXnAEAnzcEWj|
20D0 43 75 78 73 6F 45 2F 2F 78 51 41 4D 55 42 41 4A |CuxsoE//xQAMUBAJ|
20E0 73 43 36 41 41 3D 3C 2F 49 43 43 52 6C 74 64 44 |sC6AA=</ICCRltdD|
20F0 61 74 61 3E 3C 2F 54 78 44 74 6C 73 3E 3C 41 75 |ata></TxDtls><Au|
2100 74 68 73 74 6E 52 73 6C 74 3E 3C 41 75 74 68 73 |thstnRslt><Auths|
2110 74 6E 4E 74 74 79 3E 3C 54 70 3E 43 49 53 53 3C |tnNtty><Tp>CISS<|
2120 2F 54 70 3E 3C 2F 41 75 74 68 73 74 6E 4E 74 74 |/Tp></AuthstnNtt|
2130 79 3E 3C 52 73 70 6E 54 6F 41 75 74 68 73 74 6E |y><RspnToAuthstn|
2140 3E 3C 52 73 70 6E 3E 41 50 50 52 3C 2F 52 73 70 |><Rspn>APPR</Rsp|
2150 6E 3E 3C 2F 52 73 70 6E 54 6F 41 75 74 68 73 74 |n></RspnToAuthst|
2160 6E 3E 3C 41 75 74 68 73 74 6E 43 64 3E 30 33 32 |n><AuthstnCd>032|
2170 39 38 33 3C 2F 41 75 74 68 73 74 6E 43 64 3E 3C |983</AuthstnCd><|
2180 2F 41 75 74 68 73 74 6E 52 73 6C 74 3E 3C 2F 54 |/AuthstnRslt></T|
2190 78 3E 3C 2F 43 6D 70 6C 74 6E 3E 3C 2F 54 78 3E |x></Cmpltn></Tx>|
21A0 3C 54 78 3E 3C 43 6D 70 6C 74 6E 3E 3C 54 78 53 |<Tx><Cmpltn><TxS|
21B0 65 71 43 6E 74 72 3E 35 3C 2F 54 78 53 65 71 43 |eqCntr>5</TxSeqC|
21C0 6E 74 72 3E 3C 45 6E 76 74 3E 3C 41 63 71 72 72 |ntr><Envt><Acqrr|
21D0 3E 3C 49 64 3E 3C 49 64 3E 30 30 30 30 30 30 30 |><Id><Id>0000000|
21E0 30 30 31 32 33 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |00123</Id></Id><|
21F0 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 31 30 |ParamsVrsn>20110|
2200 39 31 33 31 32 33 34 35 36 3C 2F 50 61 72 61 6D |913123456</Param|
2210 73 56 72 73 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D |sVrsn></Acqrr><M|
2220 72 63 68 6E 74 3E 3C 49 64 3E 3C 49 64 3E 4D 79 |rchnt><Id><Id>My|

7 Messages Examples - 420 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2230 4D 65 72 63 68 61 6E 74 49 44 30 30 30 3C 2F 49 |MerchantID000</I|
2240 64 3E 3C 2F 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 54 |d></Id><CmonNm>T|
2250 65 73 74 4C 61 62 2C 63 65 72 74 69 66 69 63 61 |estLab,certifica|
2260 74 69 6F 6E 41 56 45 2C 53 45 50 41 3C 2F 43 6D |tionAVE,SEPA</Cm|
2270 6F 6E 4E 6D 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 |onNm></Mrchnt><P|
2280 4F 49 3E 3C 49 64 3E 3C 49 64 3E 38 38 30 30 30 |OI><Id><Id>88000|
2290 30 30 31 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 70 |001</Id></Id><Cp|
22A0 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 |blties><CardRdng|
22B0 43 70 62 6C 74 69 65 73 3E 50 48 59 53 3C 2F 43 |Cpblties>PHYS</C|
22C0 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
22D0 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |<CardRdngCpbltie|
22E0 73 3E 4D 47 53 54 3C 2F 43 61 72 64 52 64 6E 67 |s>MGST</CardRdng|
22F0 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 |Cpblties><CardRd|
2300 6E 67 43 70 62 6C 74 69 65 73 3E 43 49 43 43 3C |ngCpblties>CICC<|
2310 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 |/CardRdngCpbltie|
2320 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 |s><CardRdngCpblt|
2330 69 65 73 3E 45 43 54 4C 3C 2F 43 61 72 64 52 64 |ies>ECTL</CardRd|
2340 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 |ngCpblties><Crdh|
2350 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 |ldrVrfctnCpbltie|
2360 73 3E 46 43 50 4E 3C 2F 43 72 64 68 6C 64 72 56 |s>FCPN</CrdhldrV|
2370 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 |rfctnCpblties><C|
2380 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C |rdhldrVrfctnCpbl|
2390 74 69 65 73 3E 4E 50 49 4E 3C 2F 43 72 64 68 6C |ties>NPIN</Crdhl|
23A0 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 |drVrfctnCpblties|
23B0 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |><CrdhldrVrfctnC|
23C0 70 62 6C 74 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 |pblties>MNSG</Cr|
23D0 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 |dhldrVrfctnCpblt|
23E0 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 |ies><CrdhldrVrfc|
23F0 74 6E 43 70 62 6C 74 69 65 73 3E 46 45 50 4E 3C |tnCpblties>FEPN<|
2400 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |/CrdhldrVrfctnCp|
2410 62 6C 74 69 65 73 3E 3C 4F 6E 4C 69 6E 65 43 70 |blties><OnLineCp|
2420 62 6C 74 69 65 73 3E 53 4D 4F 4E 3C 2F 4F 6E 4C |blties>SMON</OnL|
2430 69 6E 65 43 70 62 6C 74 69 65 73 3E 3C 4D 73 67 |ineCpblties><Msg|
2440 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 6E 3E 4D |Cpblties><Dstn>M|
2450 44 53 50 3C 2F 44 73 74 6E 3E 3C 4E 62 4F 66 4C |DSP</Dstn><NbOfL|
2460 69 6E 65 73 3E 38 3C 2F 4E 62 4F 66 4C 69 6E 65 |ines>8</NbOfLine|
2470 73 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 31 35 3C |s><LineWidth>15<|
2480 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 67 |/LineWidth></Msg|
2490 43 70 62 6C 74 69 65 73 3E 3C 4D 73 67 43 70 62 |Cpblties><MsgCpb|
24A0 6C 74 69 65 73 3E 3C 44 73 74 6E 3E 4D 52 43 50 |lties><Dstn>MRCP|
24B0 3C 2F 44 73 74 6E 3E 3C 4C 69 6E 65 57 69 64 74 |</Dstn><LineWidt|
24C0 68 3E 32 34 3C 2F 4C 69 6E 65 57 69 64 74 68 3E |h>24</LineWidth>|
24D0 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 2F |</MsgCpblties></|
24E0 43 70 62 6C 74 69 65 73 3E 3C 43 6D 70 6E 74 3E |Cpblties><Cmpnt>|
24F0 3C 54 70 3E 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 |<Tp>TERM</Tp><Id|
2500 3E 3C 50 72 76 64 72 49 64 3E 49 4E 47 45 4E 49 |><PrvdrId>INGENI|
2510 43 4F 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 3E |CO</PrvdrId><Id>|
2520 49 43 54 32 35 30 3C 2F 49 64 3E 3C 53 72 6C 4E |ICT250</Id><SrlN|
2530 62 3E 31 31 32 32 33 33 34 3C 2F 53 72 6C 4E 62 |b>1122334</SrlNb|
2540 3E 3C 2F 49 64 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 |></Id></Cmpnt><C|
2550 6D 70 6E 74 3E 3C 54 70 3E 41 50 4C 49 3C 2F 54 |mpnt><Tp>APLI</T|
2560 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 3E 49 |p><Id><PrvdrId>I|
2570 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 49 64 |NGENICO</PrvdrId|
2580 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F |><Id>SEPA-FAST</|
2590 49 64 3E 3C 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 |Id></Id><Sts><Vr|
25A0 73 6E 4E 62 3E 30 34 2E 31 30 3C 2F 56 72 73 6E |snNb>04.10</Vrsn|
25B0 4E 62 3E 3C 2F 53 74 73 3E 3C 53 74 64 43 6D 70 |Nb></Sts><StdCmp|
25C0 6C 63 3E 3C 49 64 3E 53 45 50 41 2D 46 41 53 54 |lc><Id>SEPA-FAST|
25D0 3C 2F 49 64 3E 3C 56 72 73 6E 3E 33 2E 31 3C 2F |</Id><Vrsn>3.1</|
25E0 56 72 73 6E 3E 3C 49 73 73 72 3E 4F 53 43 41 52 |Vrsn><Issr>OSCAR|
25F0 3C 2F 49 73 73 72 3E 3C 2F 53 74 64 43 6D 70 6C |</Issr></StdCmpl|
2600 63 3E 3C 41 73 73 6D 6E 74 3E 3C 54 70 3E 43 45 |c><Assmnt><Tp>CE|
2610 52 54 3C 2F 54 70 3E 3C 41 73 73 67 6E 72 3E 4F |RT</Tp><Assgnr>O|
2620 53 43 41 52 3C 2F 41 73 73 67 6E 72 3E 3C 44 6C |SCAR</Assgnr><Dl|
2630 76 72 79 44 74 3E 32 30 31 34 2D 30 35 2D 31 34 |vryDt>2014-05-14|
2640 54 31 37 3A 31 32 3A 30 35 2E 30 30 30 5A 3C 2F |T17:12:05.000Z</|
2650 44 6C 76 72 79 44 74 3E 3C 58 70 72 74 6E 44 74 |DlvryDt><XprtnDt|
2660 3E 32 30 32 31 2D 30 31 2D 31 32 54 30 39 3A 30 |>2021-01-12T09:0|

7 Messages Examples - 421 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2670 37 3A 31 38 2E 30 30 30 5A 3C 2F 58 70 72 74 6E |7:18.000Z</Xprtn|
2680 44 74 3E 3C 4E 62 3E 50 41 59 2E 45 4C 49 2E 49 |Dt><Nb>PAY.ELI.I|
2690 4E 47 2E 50 4F 49 2E 31 32 30 2E 31 33 30 33 30 |NG.POI.120.13030|
26A0 30 30 32 3C 2F 4E 62 3E 3C 2F 41 73 73 6D 6E 74 |002</Nb></Assmnt|
26B0 3E 3C 2F 43 6D 70 6E 74 3E 3C 2F 50 4F 49 3E 3C |></Cmpnt></POI><|
26C0 43 61 72 64 3E 3C 50 6C 61 69 6E 43 61 72 64 44 |Card><PlainCardD|
26D0 61 74 61 3E 3C 50 41 4E 3E 35 30 37 31 30 30 39 |ata><PAN>5071009|
26E0 39 39 39 31 30 30 30 31 33 3C 2F 50 41 4E 3E 3C |999100013</PAN><|
26F0 58 70 72 79 44 74 3E 32 30 32 30 2D 31 32 3C 2F |XpryDt>2020-12</|
2700 58 70 72 79 44 74 3E 3C 2F 50 6C 61 69 6E 43 61 |XpryDt></PlainCa|
2710 72 64 44 61 74 61 3E 3C 43 61 72 64 50 64 63 74 |rdData><CardPdct|
2720 50 72 66 6C 3E 30 30 31 37 3C 2F 43 61 72 64 50 |Prfl>0017</CardP|
2730 64 63 74 50 72 66 6C 3E 3C 43 61 72 64 42 72 6E |dctPrfl><CardBrn|
2740 64 3E 43 42 3C 2F 43 61 72 64 42 72 6E 64 3E 3C |d>CB</CardBrnd><|
2750 2F 43 61 72 64 3E 3C 2F 45 6E 76 74 3E 3C 43 6E |/Card></Envt><Cn|
2760 74 78 74 3E 3C 50 6D 74 43 6E 74 78 74 3E 3C 43 |txt><PmtCntxt><C|
2770 61 72 64 50 72 65 73 3E 66 61 6C 73 65 3C 2F 43 |ardPres>false</C|
2780 61 72 64 50 72 65 73 3E 3C 43 72 64 68 6C 64 72 |ardPres><Crdhldr|
2790 50 72 65 73 3E 66 61 6C 73 65 3C 2F 43 72 64 68 |Pres>false</Crdh|
27A0 6C 64 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 |ldrPres><OnLineC|
27B0 6E 74 78 74 3E 74 72 75 65 3C 2F 4F 6E 4C 69 6E |ntxt>true</OnLin|
27C0 65 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 |eCntxt><AttndncC|
27D0 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
27E0 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 |ncCntxt><CardDat|
27F0 61 4E 74 72 79 4D 64 3E 50 48 59 53 3C 2F 43 61 |aNtryMd>PHYS</Ca|
2800 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 |rdDataNtryMd></P|
2810 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 |mtCntxt><SaleCnt|
2820 78 74 3E 3C 53 61 6C 65 52 65 66 4E 62 3E 30 30 |xt><SaleRefNb>00|
2830 30 30 30 30 30 30 31 31 31 31 31 31 31 31 2F 32 |00000011111111/2|
2840 30 31 35 31 32 30 33 31 34 32 38 34 30 3C 2F 53 |0151203142840</S|
2850 61 6C 65 52 65 66 4E 62 3E 3C 43 73 68 72 49 64 |aleRefNb><CshrId|
2860 3E 30 30 30 30 30 30 30 31 3C 2F 43 73 68 72 49 |>00000001</CshrI|
2870 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F |d></SaleCntxt></|
2880 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 54 70 3E |Cntxt><Tx><TxTp>|
2890 43 52 44 50 3C 2F 54 78 54 70 3E 3C 4D 72 63 68 |CRDP</TxTp><Mrch|
28A0 6E 74 43 74 67 79 43 64 3E 35 39 39 39 3C 2F 4D |ntCtgyCd>5999</M|
28B0 72 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 78 49 |rchntCtgyCd><TxI|
28C0 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 |d><TxDtTm>2015-1|
28D0 32 2D 30 33 54 31 34 3A 32 38 3A 34 30 2E 30 30 |2-03T14:28:40.00|
28E0 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 |0</TxDtTm><TxRef|
28F0 3E 31 33 30 32 31 36 3C 2F 54 78 52 65 66 3E 3C |>130216</TxRef><|
2900 2F 54 78 49 64 3E 3C 54 78 53 75 63 73 73 3E 74 |/TxId><TxSucss>t|
2910 72 75 65 3C 2F 54 78 53 75 63 73 73 3E 3C 52 76 |rue</TxSucss><Rv|
2920 73 6C 3E 66 61 6C 73 65 3C 2F 52 76 73 6C 3E 3C |sl>false</Rvsl><|
2930 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 3C |TxDtls><Ccy>EUR<|
2940 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 32 2E 31 |/Ccy><TtlAmt>2.1|
2950 38 3C 2F 54 74 6C 41 6D 74 3E 3C 2F 54 78 44 74 |8</TtlAmt></TxDt|
2960 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 6C 74 3E |ls><AuthstnRslt>|
2970 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C 54 70 |<AuthstnNtty><Tp|
2980 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 74 68 |>CISS</Tp></Auth|
2990 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 6F 41 |stnNtty><RspnToA|
29A0 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 50 50 |uthstn><Rspn>APP|
29B0 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E 54 6F |R</Rspn></RspnTo|
29C0 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 74 6E |Authstn><Authstn|
29D0 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 68 73 |Cd>032983</Auths|
29E0 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 6E 52 73 |tnCd></AuthstnRs|
29F0 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 6C 74 6E |lt></Tx></Cmpltn|
2A00 3E 3C 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 6C 74 |></Tx><Tx><Cmplt|
2A10 6E 3E 3C 54 78 53 65 71 43 6E 74 72 3E 36 3C 2F |n><TxSeqCntr>6</|
2A20 54 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 74 3E |TxSeqCntr><Envt>|
2A30 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 30 |<Acqrr><Id><Id>0|
2A40 30 30 30 30 30 30 30 30 31 32 33 3C 2F 49 64 3E |00000000123</Id>|
2A50 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E |</Id><ParamsVrsn|
2A60 3E 32 30 31 31 30 39 31 33 31 32 33 34 35 36 3C |>20110913123456<|
2A70 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 |/ParamsVrsn></Ac|
2A80 71 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 64 3E |qrr><Mrchnt><Id>|
2A90 3C 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 49 44 |<Id>MyMerchantID|
2AA0 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 43 6D |000</Id></Id><Cm|

7 Messages Examples - 422 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2AB0 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 65 72 |onNm>TestLab,cer|
2AC0 74 69 66 69 63 61 74 69 6F 6E 41 56 45 2C 53 45 |tificationAVE,SE|
2AD0 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D 72 63 |PA</CmonNm></Mrc|
2AE0 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C 49 64 |hnt><POI><Id><Id|
2AF0 3E 38 38 30 30 30 30 30 31 3C 2F 49 64 3E 3C 2F |>88000001</Id></|
2B00 49 64 3E 3C 43 70 62 6C 74 69 65 73 3E 3C 43 61 |Id><Cpblties><Ca|
2B10 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 50 |rdRdngCpblties>P|
2B20 48 59 53 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 |HYS</CardRdngCpb|
2B30 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 |lties><CardRdngC|
2B40 70 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F 43 61 |pblties>MGST</Ca|
2B50 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C |rdRdngCpblties><|
2B60 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
2B70 3E 43 49 43 43 3C 2F 43 61 72 64 52 64 6E 67 43 |>CICC</CardRdngC|
2B80 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E |pblties><CardRdn|
2B90 67 43 70 62 6C 74 69 65 73 3E 45 43 54 4C 3C 2F |gCpblties>ECTL</|
2BA0 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
2BB0 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 |><CrdhldrVrfctnC|
2BC0 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F 43 72 |pblties>FCPN</Cr|
2BD0 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 |dhldrVrfctnCpblt|
2BE0 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 |ies><CrdhldrVrfc|
2BF0 74 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 4E 3C |tnCpblties>NPIN<|
2C00 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |/CrdhldrVrfctnCp|
2C10 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 |blties><CrdhldrV|
2C20 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4D 4E |rfctnCpblties>MN|
2C30 53 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 |SG</CrdhldrVrfct|
2C40 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C |nCpblties><Crdhl|
2C50 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 |drVrfctnCpblties|
2C60 3E 46 45 50 4E 3C 2F 43 72 64 68 6C 64 72 56 72 |>FEPN</CrdhldrVr|
2C70 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 4F 6E |fctnCpblties><On|
2C80 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 53 4D 4F |LineCpblties>SMO|
2C90 4E 3C 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 |N</OnLineCpbltie|
2CA0 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C |s><MsgCpblties><|
2CB0 44 73 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 6E 3E |Dstn>MDSP</Dstn>|
2CC0 3C 4E 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F 4E 62 |<NbOfLines>8</Nb|
2CD0 4F 66 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 69 64 |OfLines><LineWid|
2CE0 74 68 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 74 68 |th>15</LineWidth|
2CF0 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C |></MsgCpblties><|
2D00 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 73 74 |MsgCpblties><Dst|
2D10 6E 3E 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C 4C 69 |n>MRCP</Dstn><Li|
2D20 6E 65 57 69 64 74 68 3E 32 34 3C 2F 4C 69 6E 65 |neWidth>24</Line|
2D30 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 |Width></MsgCpblt|
2D40 69 65 73 3E 3C 2F 43 70 62 6C 74 69 65 73 3E 3C |ies></Cpblties><|
2D50 43 6D 70 6E 74 3E 3C 54 70 3E 54 45 52 4D 3C 2F |Cmpnt><Tp>TERM</|
2D60 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 64 3E |Tp><Id><PrvdrId>|
2D70 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 72 49 |INGENICO</PrvdrI|
2D80 64 3E 3C 49 64 3E 49 43 54 32 35 30 3C 2F 49 64 |d><Id>ICT250</Id|
2D90 3E 3C 53 72 6C 4E 62 3E 31 31 32 32 33 33 34 3C |><SrlNb>1122334<|
2DA0 2F 53 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F 43 6D |/SrlNb></Id></Cm|
2DB0 70 6E 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 41 |pnt><Cmpnt><Tp>A|
2DC0 50 4C 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 |PLI</Tp><Id><Prv|
2DD0 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 |drId>INGENICO</P|
2DE0 72 76 64 72 49 64 3E 3C 49 64 3E 53 45 50 41 2D |rvdrId><Id>SEPA-|
2DF0 46 41 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 53 |FAST</Id></Id><S|
2E00 74 73 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E 31 30 |ts><VrsnNb>04.10|
2E10 3C 2F 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 3E 3C |</VrsnNb></Sts><|
2E20 53 74 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 45 50 |StdCmplc><Id>SEP|
2E30 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 56 72 73 6E |A-FAST</Id><Vrsn|
2E40 3E 33 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 73 72 |>3.1</Vrsn><Issr|
2E50 3E 4F 53 43 41 52 3C 2F 49 73 73 72 3E 3C 2F 53 |>OSCAR</Issr></S|
2E60 74 64 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E 74 3E |tdCmplc><Assmnt>|
2E70 3C 54 70 3E 43 45 52 54 3C 2F 54 70 3E 3C 41 73 |<Tp>CERT</Tp><As|
2E80 73 67 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 73 67 |sgnr>OSCAR</Assg|
2E90 6E 72 3E 3C 44 6C 76 72 79 44 74 3E 32 30 31 34 |nr><DlvryDt>2014|
2EA0 2D 30 35 2D 31 34 54 31 37 3A 31 32 3A 30 35 2E |-05-14T17:12:05.|
2EB0 30 30 30 5A 3C 2F 44 6C 76 72 79 44 74 3E 3C 58 |000Z</DlvryDt><X|
2EC0 70 72 74 6E 44 74 3E 32 30 32 31 2D 30 31 2D 31 |prtnDt>2021-01-1|
2ED0 32 54 30 39 3A 30 37 3A 31 38 2E 30 30 30 5A 3C |2T09:07:18.000Z<|
2EE0 2F 58 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 41 59 |/XprtnDt><Nb>PAY|

7 Messages Examples - 423 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

2EF0 2E 45 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 32 30 |.ELI.ING.POI.120|
2F00 2E 31 33 30 33 30 30 30 32 3C 2F 4E 62 3E 3C 2F |.13030002</Nb></|
2F10 41 73 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 3E 3C |Assmnt></Cmpnt><|
2F20 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C 61 69 |/POI><Card><Plai|
2F30 6E 43 61 72 64 44 61 74 61 3E 3C 50 41 4E 3E 35 |nCardData><PAN>5|
2F40 30 37 31 30 30 39 39 31 31 32 32 37 37 30 34 39 |0710099112277049|
2F50 3C 2F 50 41 4E 3E 3C 58 70 72 79 44 74 3E 32 30 |</PAN><XpryDt>20|
2F60 31 38 2D 30 33 3C 2F 58 70 72 79 44 74 3E 3C 2F |18-03</XpryDt></|
2F70 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 43 |PlainCardData><C|
2F80 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 31 37 |ardPdctPrfl>0017|
2F90 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E 3C |</CardPdctPrfl><|
2FA0 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 61 72 |CardBrnd>CB</Car|
2FB0 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 |dBrnd></Card></E|
2FC0 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 |nvt><Cntxt><PmtC|
2FD0 6E 74 78 74 3E 3C 43 72 64 68 6C 64 72 50 72 65 |ntxt><CrdhldrPre|
2FE0 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C 64 72 50 |s>true</CrdhldrP|
2FF0 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 78 74 |res><OnLineCntxt|
3000 3E 74 72 75 65 3C 2F 4F 6E 4C 69 6E 65 43 6E 74 |>true</OnLineCnt|
3010 78 74 3E 3C 41 74 74 6E 64 6E 63 43 6E 74 78 74 |xt><AttndncCntxt|
3020 3E 41 54 54 44 3C 2F 41 74 74 6E 64 6E 63 43 6E |>ATTD</AttndncCn|
3030 74 78 74 3E 3C 43 61 72 64 44 61 74 61 4E 74 72 |txt><CardDataNtr|
3040 79 4D 64 3E 4D 47 53 54 3C 2F 43 61 72 64 44 61 |yMd>MGST</CardDa|
3050 74 61 4E 74 72 79 4D 64 3E 3C 46 6C 6C 62 63 6B |taNtryMd><Fllbck|
3060 49 6E 64 3E 46 46 4C 42 3C 2F 46 6C 6C 62 63 6B |Ind>FFLB</Fllbck|
3070 49 6E 64 3E 3C 2F 50 6D 74 43 6E 74 78 74 3E 3C |Ind></PmtCntxt><|
3080 53 61 6C 65 43 6E 74 78 74 3E 3C 53 61 6C 65 52 |SaleCntxt><SaleR|
3090 65 66 4E 62 3E 30 30 30 30 30 30 30 30 31 31 31 |efNb>00000000111|
30A0 31 31 31 31 31 2F 32 30 31 35 31 32 30 33 31 34 |11111/2015120314|
30B0 32 33 33 37 3C 2F 53 61 6C 65 52 65 66 4E 62 3E |2337</SaleRefNb>|
30C0 3C 43 73 68 72 49 64 3E 30 30 30 30 30 30 30 31 |<CshrId>00000001|
30D0 3C 2F 43 73 68 72 49 64 3E 3C 2F 53 61 6C 65 43 |</CshrId></SaleC|
30E0 6E 74 78 74 3E 3C 2F 43 6E 74 78 74 3E 3C 54 78 |ntxt></Cntxt><Tx|
30F0 3E 3C 54 78 54 70 3E 43 52 44 50 3C 2F 54 78 54 |><TxTp>CRDP</TxT|
3100 70 3E 3C 4D 72 63 68 6E 74 43 74 67 79 43 64 3E |p><MrchntCtgyCd>|
3110 35 39 39 39 3C 2F 4D 72 63 68 6E 74 43 74 67 79 |5999</MrchntCtgy|
3120 43 64 3E 3C 54 78 49 64 3E 3C 54 78 44 74 54 6D |Cd><TxId><TxDtTm|
3130 3E 32 30 31 35 2D 31 32 2D 30 33 54 31 34 3A 32 |>2015-12-03T14:2|
3140 33 3A 33 37 2E 30 30 30 3C 2F 54 78 44 74 54 6D |3:37.000</TxDtTm|
3150 3E 3C 54 78 52 65 66 3E 31 33 30 32 31 35 3C 2F |><TxRef>130215</|
3160 54 78 52 65 66 3E 3C 2F 54 78 49 64 3E 3C 54 78 |TxRef></TxId><Tx|
3170 53 75 63 73 73 3E 74 72 75 65 3C 2F 54 78 53 75 |Sucss>true</TxSu|
3180 63 73 73 3E 3C 52 76 73 6C 3E 66 61 6C 73 65 3C |css><Rvsl>false<|
3190 2F 52 76 73 6C 3E 3C 54 78 44 74 6C 73 3E 3C 43 |/Rvsl><TxDtls><C|
31A0 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C |cy>EUR</Ccy><Ttl|
31B0 41 6D 74 3E 32 2E 31 37 3C 2F 54 74 6C 41 6D 74 |Amt>2.17</TtlAmt|
31C0 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E 6E 77 |><ICCRltdData>nw|
31D0 49 47 41 41 41 41 41 41 49 58 6E 77 4D 47 41 41 |IGAAAAAAIXnwMGAA|
31E0 41 41 41 41 41 41 6E 77 6B 43 41 41 43 66 4E 41 |AAAAAAnwkCAACfNA|
31F0 4D 2F 41 41 43 66 48 67 67 77 4D 54 45 79 4D 6A |M/AACfHggwMTEyMj|
3200 4D 7A 4E 4A 38 7A 41 2B 44 34 79 4A 38 61 41 67 |MzNJ8zA+D4yJ8aAg|
3210 41 51 6E 7A 55 42 49 70 55 46 42 41 41 41 41 41 |AQnzUBIpUFBAAAAA|
3220 42 66 4B 67 49 4A 65 4A 6F 44 46 52 49 44 6E 30 |BfKgIJeJoDFRIDn0|
3230 45 44 45 77 49 56 6E 41 45 41 79 67 54 66 2B 41 |EDEwIVnAEAygTf+A|
3240 66 67 78 51 45 45 6D 77 4C 49 41 41 3D 3D 3C 2F |fgxQEEmwLIAA==</|
3250 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F 54 78 |ICCRltdData></Tx|
3260 44 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 6C |Dtls><AuthstnRsl|
3270 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E 3C |t><AuthstnNtty><|
3280 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 75 |Tp>CISS</Tp></Au|
3290 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E 54 |thstnNtty><RspnT|
32A0 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E 41 |oAuthstn><Rspn>A|
32B0 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 6E |PPR</Rspn></Rspn|
32C0 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 73 |ToAuthstn><Auths|
32D0 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 74 |tnCd>032983</Aut|
32E0 68 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 6E |hstnCd></Authstn|
32F0 52 73 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 6C |Rslt></Tx></Cmpl|
3300 74 6E 3E 3C 2F 54 78 3E 3C 54 78 3E 3C 43 6D 70 |tn></Tx><Tx><Cmp|
3310 6C 74 6E 3E 3C 54 78 53 65 71 43 6E 74 72 3E 37 |ltn><TxSeqCntr>7|
3320 3C 2F 54 78 53 65 71 43 6E 74 72 3E 3C 45 6E 76 |</TxSeqCntr><Env|

7 Messages Examples - 424 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3330 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
3340 3E 30 30 30 30 30 30 30 30 30 31 32 33 3C 2F 49 |>000000000123</I|
3350 64 3E 3C 2F 49 64 3E 3C 50 61 72 61 6D 73 56 72 |d></Id><ParamsVr|
3360 73 6E 3E 32 30 31 31 30 39 31 33 31 32 33 34 35 |sn>2011091312345|
3370 36 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F |6</ParamsVrsn></|
3380 41 63 71 72 72 3E 3C 4D 72 63 68 6E 74 3E 3C 49 |Acqrr><Mrchnt><I|
3390 64 3E 3C 49 64 3E 4D 79 4D 65 72 63 68 61 6E 74 |d><Id>MyMerchant|
33A0 49 44 30 30 30 3C 2F 49 64 3E 3C 2F 49 64 3E 3C |ID000</Id></Id><|
33B0 43 6D 6F 6E 4E 6D 3E 54 65 73 74 4C 61 62 2C 63 |CmonNm>TestLab,c|
33C0 65 72 74 69 66 69 63 61 74 69 6F 6E 41 56 45 2C |ertificationAVE,|
33D0 53 45 50 41 3C 2F 43 6D 6F 6E 4E 6D 3E 3C 2F 4D |SEPA</CmonNm></M|
33E0 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C 49 64 3E 3C |rchnt><POI><Id><|
33F0 49 64 3E 38 38 30 30 30 30 30 31 3C 2F 49 64 3E |Id>88000001</Id>|
3400 3C 2F 49 64 3E 3C 43 70 62 6C 74 69 65 73 3E 3C |</Id><Cpblties><|
3410 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
3420 3E 50 48 59 53 3C 2F 43 61 72 64 52 64 6E 67 43 |>PHYS</CardRdngC|
3430 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 64 6E |pblties><CardRdn|
3440 67 43 70 62 6C 74 69 65 73 3E 4D 47 53 54 3C 2F |gCpblties>MGST</|
3450 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 |CardRdngCpblties|
3460 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |><CardRdngCpblti|
3470 65 73 3E 43 49 43 43 3C 2F 43 61 72 64 52 64 6E |es>CICC</CardRdn|
3480 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 64 52 |gCpblties><CardR|
3490 64 6E 67 43 70 62 6C 74 69 65 73 3E 45 43 54 4C |dngCpblties>ECTL|
34A0 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C 74 69 |</CardRdngCpblti|
34B0 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 66 63 74 |es><CrdhldrVrfct|
34C0 6E 43 70 62 6C 74 69 65 73 3E 46 43 50 4E 3C 2F |nCpblties>FCPN</|
34D0 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 |CrdhldrVrfctnCpb|
34E0 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 72 |lties><CrdhldrVr|
34F0 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 4E 50 49 |fctnCpblties>NPI|
3500 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 6E |N</CrdhldrVrfctn|
3510 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 |Cpblties><Crdhld|
3520 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
3530 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 72 56 72 66 |MNSG</CrdhldrVrf|
3540 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 |ctnCpblties><Crd|
3550 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
3560 65 73 3E 46 45 50 4E 3C 2F 43 72 64 68 6C 64 72 |es>FEPN</Crdhldr|
3570 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C |VrfctnCpblties><|
3580 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 65 73 3E 53 |OnLineCpblties>S|
3590 4D 4F 4E 3C 2F 4F 6E 4C 69 6E 65 43 70 62 6C 74 |MON</OnLineCpblt|
35A0 69 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 |ies><MsgCpblties|
35B0 3E 3C 44 73 74 6E 3E 4D 44 53 50 3C 2F 44 73 74 |><Dstn>MDSP</Dst|
35C0 6E 3E 3C 4E 62 4F 66 4C 69 6E 65 73 3E 38 3C 2F |n><NbOfLines>8</|
35D0 4E 62 4F 66 4C 69 6E 65 73 3E 3C 4C 69 6E 65 57 |NbOfLines><LineW|
35E0 69 64 74 68 3E 31 35 3C 2F 4C 69 6E 65 57 69 64 |idth>15</LineWid|
35F0 74 68 3E 3C 2F 4D 73 67 43 70 62 6C 74 69 65 73 |th></MsgCpblties|
3600 3E 3C 4D 73 67 43 70 62 6C 74 69 65 73 3E 3C 44 |><MsgCpblties><D|
3610 73 74 6E 3E 4D 52 43 50 3C 2F 44 73 74 6E 3E 3C |stn>MRCP</Dstn><|
3620 4C 69 6E 65 57 69 64 74 68 3E 32 34 3C 2F 4C 69 |LineWidth>24</Li|
3630 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 |neWidth></MsgCpb|
3640 6C 74 69 65 73 3E 3C 2F 43 70 62 6C 74 69 65 73 |lties></Cpblties|
3650 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E 54 45 52 4D |><Cmpnt><Tp>TERM|
3660 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 76 64 72 49 |</Tp><Id><PrvdrI|
3670 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F 50 72 76 64 |d>INGENICO</Prvd|
3680 72 49 64 3E 3C 49 64 3E 49 43 54 32 35 30 3C 2F |rId><Id>ICT250</|
3690 49 64 3E 3C 53 72 6C 4E 62 3E 31 31 32 32 33 33 |Id><SrlNb>112233|
36A0 34 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 64 3E 3C 2F |4</SrlNb></Id></|
36B0 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 3E 3C 54 70 |Cmpnt><Cmpnt><Tp|
36C0 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 64 3E 3C 50 |>APLI</Tp><Id><P|
36D0 72 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C |rvdrId>INGENICO<|
36E0 2F 50 72 76 64 72 49 64 3E 3C 49 64 3E 53 45 50 |/PrvdrId><Id>SEP|
36F0 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 2F 49 64 3E |A-FAST</Id></Id>|
3700 3C 53 74 73 3E 3C 56 72 73 6E 4E 62 3E 30 34 2E |<Sts><VrsnNb>04.|
3710 31 30 3C 2F 56 72 73 6E 4E 62 3E 3C 2F 53 74 73 |10</VrsnNb></Sts|
3720 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C 49 64 3E 53 |><StdCmplc><Id>S|
3730 45 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C 56 72 |EPA-FAST</Id><Vr|
3740 73 6E 3E 33 2E 31 3C 2F 56 72 73 6E 3E 3C 49 73 |sn>3.1</Vrsn><Is|
3750 73 72 3E 4F 53 43 41 52 3C 2F 49 73 73 72 3E 3C |sr>OSCAR</Issr><|
3760 2F 53 74 64 43 6D 70 6C 63 3E 3C 41 73 73 6D 6E |/StdCmplc><Assmn|

7 Messages Examples - 425 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3770 74 3E 3C 54 70 3E 43 45 52 54 3C 2F 54 70 3E 3C |t><Tp>CERT</Tp><|
3780 41 73 73 67 6E 72 3E 4F 53 43 41 52 3C 2F 41 73 |Assgnr>OSCAR</As|
3790 73 67 6E 72 3E 3C 44 6C 76 72 79 44 74 3E 32 30 |sgnr><DlvryDt>20|
37A0 31 34 2D 30 35 2D 31 34 54 31 37 3A 31 32 3A 30 |14-05-14T17:12:0|
37B0 35 2E 30 30 30 5A 3C 2F 44 6C 76 72 79 44 74 3E |5.000Z</DlvryDt>|
37C0 3C 58 70 72 74 6E 44 74 3E 32 30 32 31 2D 30 31 |<XprtnDt>2021-01|
37D0 2D 31 32 54 30 39 3A 30 37 3A 31 38 2E 30 30 30 |-12T09:07:18.000|
37E0 5A 3C 2F 58 70 72 74 6E 44 74 3E 3C 4E 62 3E 50 |Z</XprtnDt><Nb>P|
37F0 41 59 2E 45 4C 49 2E 49 4E 47 2E 50 4F 49 2E 31 |AY.ELI.ING.POI.1|
3800 32 30 2E 31 33 30 33 30 30 30 32 3C 2F 4E 62 3E |20.13030002</Nb>|
3810 3C 2F 41 73 73 6D 6E 74 3E 3C 2F 43 6D 70 6E 74 |</Assmnt></Cmpnt|
3820 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 3E 3C 50 6C |></POI><Card><Pl|
3830 61 69 6E 43 61 72 64 44 61 74 61 3E 3C 50 41 4E |ainCardData><PAN|
3840 3E 35 30 37 31 30 30 39 39 39 39 31 30 30 30 31 |>507100999910001|
3850 33 3C 2F 50 41 4E 3E 3C 43 61 72 64 53 65 71 4E |3</PAN><CardSeqN|
3860 62 3E 30 31 3C 2F 43 61 72 64 53 65 71 4E 62 3E |b>01</CardSeqNb>|
3870 3C 46 63 74 76 44 74 3E 32 30 31 32 2D 30 31 3C |<FctvDt>2012-01<|
3880 2F 46 63 74 76 44 74 3E 3C 58 70 72 79 44 74 3E |/FctvDt><XpryDt>|
3890 32 30 32 30 2D 31 32 3C 2F 58 70 72 79 44 74 3E |2020-12</XpryDt>|
38A0 3C 53 76 63 43 64 3E 39 30 31 3C 2F 53 76 63 43 |<SvcCd>901</SvcC|
38B0 64 3E 3C 2F 50 6C 61 69 6E 43 61 72 64 44 61 74 |d></PlainCardDat|
38C0 61 3E 3C 43 61 72 64 43 74 72 79 43 64 3E 46 52 |a><CardCtryCd>FR|
38D0 41 3C 2F 43 61 72 64 43 74 72 79 43 64 3E 3C 43 |A</CardCtryCd><C|
38E0 61 72 64 50 64 63 74 50 72 66 6C 3E 30 30 31 37 |ardPdctPrfl>0017|
38F0 3C 2F 43 61 72 64 50 64 63 74 50 72 66 6C 3E 3C |</CardPdctPrfl><|
3900 43 61 72 64 42 72 6E 64 3E 43 42 3C 2F 43 61 72 |CardBrnd>CB</Car|
3910 64 42 72 6E 64 3E 3C 2F 43 61 72 64 3E 3C 2F 45 |dBrnd></Card></E|
3920 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C 50 6D 74 43 |nvt><Cntxt><PmtC|
3930 6E 74 78 74 3E 3C 43 72 64 68 6C 64 72 50 72 65 |ntxt><CrdhldrPre|
3940 73 3E 74 72 75 65 3C 2F 43 72 64 68 6C 64 72 50 |s>true</CrdhldrP|
3950 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 6E 74 78 74 |res><OnLineCntxt|
3960 3E 66 61 6C 73 65 3C 2F 4F 6E 4C 69 6E 65 43 6E |>false</OnLineCn|
3970 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 6E 74 78 |txt><AttndncCntx|
3980 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 6E 63 43 |t>ATTD</AttndncC|
3990 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 61 4E 74 |ntxt><CardDataNt|
39A0 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 72 64 44 |ryMd>CICC</CardD|
39B0 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 6D 74 43 |ataNtryMd></PmtC|
39C0 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 78 74 3E |ntxt><SaleCntxt>|
39D0 3C 53 61 6C 65 52 65 66 4E 62 3E 30 30 30 30 30 |<SaleRefNb>00000|
39E0 30 30 30 31 31 31 31 31 31 31 31 2F 32 30 31 35 |00011111111/2015|
39F0 31 32 30 33 31 34 32 32 31 35 3C 2F 53 61 6C 65 |1203142215</Sale|
3A00 52 65 66 4E 62 3E 3C 43 73 68 72 49 64 3E 30 30 |RefNb><CshrId>00|
3A10 30 30 30 30 30 31 3C 2F 43 73 68 72 49 64 3E 3C |000001</CshrId><|
3A20 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F 43 6E 74 |/SaleCntxt></Cnt|
3A30 78 74 3E 3C 54 78 3E 3C 54 78 54 70 3E 52 46 4E |xt><Tx><TxTp>RFN|
3A40 44 3C 2F 54 78 54 70 3E 3C 4D 72 63 68 6E 74 43 |D</TxTp><MrchntC|
3A50 74 67 79 43 64 3E 35 39 39 39 3C 2F 4D 72 63 68 |tgyCd>5999</Mrch|
3A60 6E 74 43 74 67 79 43 64 3E 3C 54 78 49 64 3E 3C |ntCtgyCd><TxId><|
3A70 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 32 2D 30 |TxDtTm>2015-12-0|
3A80 33 54 31 34 3A 32 32 3A 31 35 2E 30 30 30 3C 2F |3T14:22:15.000</|
3A90 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 3E 31 33 |TxDtTm><TxRef>13|
3AA0 30 32 31 34 3C 2F 54 78 52 65 66 3E 3C 2F 54 78 |0214</TxRef></Tx|
3AB0 49 64 3E 3C 54 78 53 75 63 73 73 3E 66 61 6C 73 |Id><TxSucss>fals|
3AC0 65 3C 2F 54 78 53 75 63 73 73 3E 3C 52 76 73 6C |e</TxSucss><Rvsl|
3AD0 3E 66 61 6C 73 65 3C 2F 52 76 73 6C 3E 3C 46 61 |>false</Rvsl><Fa|
3AE0 69 6C 72 52 73 6E 3E 55 43 4D 50 3C 2F 46 61 69 |ilrRsn>UCMP</Fai|
3AF0 6C 72 52 73 6E 3E 3C 54 78 44 74 6C 73 3E 3C 43 |lrRsn><TxDtls><C|
3B00 63 79 3E 45 55 52 3C 2F 43 63 79 3E 3C 54 74 6C |cy>EUR</Ccy><Ttl|
3B10 41 6D 74 3E 32 2E 31 37 3C 2F 54 74 6C 41 6D 74 |Amt>2.17</TtlAmt|
3B20 3E 3C 49 43 43 52 6C 74 64 44 61 74 61 3E 6E 77 |><ICCRltdData>nw|
3B30 49 47 41 41 41 41 41 41 49 58 6E 77 4D 47 41 41 |IGAAAAAAIXnwMGAA|
3B40 41 41 41 41 41 41 58 79 55 44 45 67 45 42 67 67 |AAAAAAXyUDEgEBgg|
3B50 49 39 41 49 63 42 41 5A 38 4A 61 67 41 43 6E 7A |I9AIcBAZ8JagACnz|
3B60 51 44 50 77 41 41 68 41 65 67 41 41 41 41 51 68 |QDPwAAhAegAAAAQh|
3B70 41 51 6E 78 34 49 4D 44 45 78 4D 6A 49 7A 4D 7A |AQnx4IMDExMjIzMz|
3B80 53 66 4D 77 50 67 2B 4D 49 66 47 67 49 41 45 4A |SfMwPg+MIfGgIAEJ|
3B90 38 31 41 53 4B 56 42 51 41 41 41 41 41 41 58 79 |81ASKVBQAAAAAAXy|
3BA0 6F 43 43 58 69 61 41 78 55 53 41 35 39 42 41 78 |oCCXiaAxUSA59BAx|

7 Messages Examples - 426 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3BB0 4D 43 46 4A 77 42 41 4A 38 33 42 4F 50 39 44 63 |MCFJwBAJ83BOP9Dc|
3BC0 62 4B 42 4E 34 49 45 41 44 46 41 51 43 62 41 67 |bKBN4IEADFAQCbAg|
3BD0 41 41 3C 2F 49 43 43 52 6C 74 64 44 61 74 61 3E |AA</ICCRltdData>|
3BE0 3C 2F 54 78 44 74 6C 73 3E 3C 2F 54 78 3E 3C 2F |</TxDtls></Tx></|
3BF0 43 6D 70 6C 74 6E 3E 3C 2F 54 78 3E 3C 54 78 3E |Cmpltn></Tx><Tx>|
3C00 3C 43 6D 70 6C 74 6E 3E 3C 54 78 53 65 71 43 6E |<Cmpltn><TxSeqCn|
3C10 74 72 3E 38 3C 2F 54 78 53 65 71 43 6E 74 72 3E |tr>8</TxSeqCntr>|
3C20 3C 45 6E 76 74 3E 3C 41 63 71 72 72 3E 3C 49 64 |<Envt><Acqrr><Id|
3C30 3E 3C 49 64 3E 30 30 30 30 30 30 30 30 30 31 32 |><Id>00000000012|
3C40 33 3C 2F 49 64 3E 3C 2F 49 64 3E 3C 50 61 72 61 |3</Id></Id><Para|
3C50 6D 73 56 72 73 6E 3E 32 30 31 31 30 39 31 33 31 |msVrsn>201109131|
3C60 32 33 34 35 36 3C 2F 50 61 72 61 6D 73 56 72 73 |23456</ParamsVrs|
3C70 6E 3E 3C 2F 41 63 71 72 72 3E 3C 4D 72 63 68 6E |n></Acqrr><Mrchn|
3C80 74 3E 3C 49 64 3E 3C 49 64 3E 4D 79 4D 65 72 63 |t><Id><Id>MyMerc|
3C90 68 61 6E 74 49 44 30 30 30 3C 2F 49 64 3E 3C 2F |hantID000</Id></|
3CA0 49 64 3E 3C 43 6D 6F 6E 4E 6D 3E 54 65 73 74 4C |Id><CmonNm>TestL|
3CB0 61 62 2C 63 65 72 74 69 66 69 63 61 74 69 6F 6E |ab,certification|
3CC0 41 56 45 2C 53 45 50 41 3C 2F 43 6D 6F 6E 4E 6D |AVE,SEPA</CmonNm|
3CD0 3E 3C 2F 4D 72 63 68 6E 74 3E 3C 50 4F 49 3E 3C |></Mrchnt><POI><|
3CE0 49 64 3E 3C 49 64 3E 38 38 30 30 30 30 30 31 3C |Id><Id>88000001<|
3CF0 2F 49 64 3E 3C 2F 49 64 3E 3C 43 70 62 6C 74 69 |/Id></Id><Cpblti|
3D00 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 62 6C |es><CardRdngCpbl|
3D10 74 69 65 73 3E 50 48 59 53 3C 2F 43 61 72 64 52 |ties>PHYS</CardR|
3D20 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 61 72 |dngCpblties><Car|
3D30 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 4D 47 |dRdngCpblties>MG|
3D40 53 54 3C 2F 43 61 72 64 52 64 6E 67 43 70 62 6C |ST</CardRdngCpbl|
3D50 74 69 65 73 3E 3C 43 61 72 64 52 64 6E 67 43 70 |ties><CardRdngCp|
3D60 62 6C 74 69 65 73 3E 43 49 43 43 3C 2F 43 61 72 |blties>CICC</Car|
3D70 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E 3C 43 |dRdngCpblties><C|
3D80 61 72 64 52 64 6E 67 43 70 62 6C 74 69 65 73 3E |ardRdngCpblties>|
3D90 45 43 54 4C 3C 2F 43 61 72 64 52 64 6E 67 43 70 |ECTL</CardRdngCp|
3DA0 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C 64 72 56 |blties><CrdhldrV|
3DB0 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 46 43 |rfctnCpblties>FC|
3DC0 50 4E 3C 2F 43 72 64 68 6C 64 72 56 72 66 63 74 |PN</CrdhldrVrfct|
3DD0 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 64 68 6C |nCpblties><Crdhl|
3DE0 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 |drVrfctnCpblties|
3DF0 3E 4E 50 49 4E 3C 2F 43 72 64 68 6C 64 72 56 72 |>NPIN</CrdhldrVr|
3E00 66 63 74 6E 43 70 62 6C 74 69 65 73 3E 3C 43 72 |fctnCpblties><Cr|
3E10 64 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 |dhldrVrfctnCpblt|
3E20 69 65 73 3E 4D 4E 53 47 3C 2F 43 72 64 68 6C 64 |ies>MNSG</Crdhld|
3E30 72 56 72 66 63 74 6E 43 70 62 6C 74 69 65 73 3E |rVrfctnCpblties>|
3E40 3C 43 72 64 68 6C 64 72 56 72 66 63 74 6E 43 70 |<CrdhldrVrfctnCp|
3E50 62 6C 74 69 65 73 3E 46 45 50 4E 3C 2F 43 72 64 |blties>FEPN</Crd|
3E60 68 6C 64 72 56 72 66 63 74 6E 43 70 62 6C 74 69 |hldrVrfctnCpblti|
3E70 65 73 3E 3C 4F 6E 4C 69 6E 65 43 70 62 6C 74 69 |es><OnLineCpblti|
3E80 65 73 3E 53 4D 4F 4E 3C 2F 4F 6E 4C 69 6E 65 43 |es>SMON</OnLineC|
3E90 70 62 6C 74 69 65 73 3E 3C 4D 73 67 43 70 62 6C |pblties><MsgCpbl|
3EA0 74 69 65 73 3E 3C 44 73 74 6E 3E 4D 44 53 50 3C |ties><Dstn>MDSP<|
3EB0 2F 44 73 74 6E 3E 3C 4E 62 4F 66 4C 69 6E 65 73 |/Dstn><NbOfLines|
3EC0 3E 38 3C 2F 4E 62 4F 66 4C 69 6E 65 73 3E 3C 4C |>8</NbOfLines><L|
3ED0 69 6E 65 57 69 64 74 68 3E 31 35 3C 2F 4C 69 6E |ineWidth>15</Lin|
3EE0 65 57 69 64 74 68 3E 3C 2F 4D 73 67 43 70 62 6C |eWidth></MsgCpbl|
3EF0 74 69 65 73 3E 3C 4D 73 67 43 70 62 6C 74 69 65 |ties><MsgCpbltie|
3F00 73 3E 3C 44 73 74 6E 3E 4D 52 43 50 3C 2F 44 73 |s><Dstn>MRCP</Ds|
3F10 74 6E 3E 3C 4C 69 6E 65 57 69 64 74 68 3E 32 34 |tn><LineWidth>24|
3F20 3C 2F 4C 69 6E 65 57 69 64 74 68 3E 3C 2F 4D 73 |</LineWidth></Ms|
3F30 67 43 70 62 6C 74 69 65 73 3E 3C 2F 43 70 62 6C |gCpblties></Cpbl|
3F40 74 69 65 73 3E 3C 43 6D 70 6E 74 3E 3C 54 70 3E |ties><Cmpnt><Tp>|
3F50 54 45 52 4D 3C 2F 54 70 3E 3C 49 64 3E 3C 50 72 |TERM</Tp><Id><Pr|
3F60 76 64 72 49 64 3E 49 4E 47 45 4E 49 43 4F 3C 2F |vdrId>INGENICO</|
3F70 50 72 76 64 72 49 64 3E 3C 49 64 3E 49 43 54 32 |PrvdrId><Id>ICT2|
3F80 35 30 3C 2F 49 64 3E 3C 53 72 6C 4E 62 3E 31 31 |50</Id><SrlNb>11|
3F90 32 32 33 33 34 3C 2F 53 72 6C 4E 62 3E 3C 2F 49 |22334</SrlNb></I|
3FA0 64 3E 3C 2F 43 6D 70 6E 74 3E 3C 43 6D 70 6E 74 |d></Cmpnt><Cmpnt|
3FB0 3E 3C 54 70 3E 41 50 4C 49 3C 2F 54 70 3E 3C 49 |><Tp>APLI</Tp><I|
3FC0 64 3E 3C 50 72 76 64 72 49 64 3E 49 4E 47 45 4E |d><PrvdrId>INGEN|
3FD0 49 43 4F 3C 2F 50 72 76 64 72 49 64 3E 3C 49 64 |ICO</PrvdrId><Id|
3FE0 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 3E 3C |>SEPA-FAST</Id><|

7 Messages Examples - 427 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

3FF0 2F 49 64 3E 3C 53 74 73 3E 3C 56 72 73 6E 4E 62 |/Id><Sts><VrsnNb|
4000 3E 30 34 2E 31 30 3C 2F 56 72 73 6E 4E 62 3E 3C |>04.10</VrsnNb><|
4010 2F 53 74 73 3E 3C 53 74 64 43 6D 70 6C 63 3E 3C |/Sts><StdCmplc><|
4020 49 64 3E 53 45 50 41 2D 46 41 53 54 3C 2F 49 64 |Id>SEPA-FAST</Id|
4030 3E 3C 56 72 73 6E 3E 33 2E 31 3C 2F 56 72 73 6E |><Vrsn>3.1</Vrsn|
4040 3E 3C 49 73 73 72 3E 4F 53 43 41 52 3C 2F 49 73 |><Issr>OSCAR</Is|
4050 73 72 3E 3C 2F 53 74 64 43 6D 70 6C 63 3E 3C 41 |sr></StdCmplc><A|
4060 73 73 6D 6E 74 3E 3C 54 70 3E 43 45 52 54 3C 2F |ssmnt><Tp>CERT</|
4070 54 70 3E 3C 41 73 73 67 6E 72 3E 4F 53 43 41 52 |Tp><Assgnr>OSCAR|
4080 3C 2F 41 73 73 67 6E 72 3E 3C 44 6C 76 72 79 44 |</Assgnr><DlvryD|
4090 74 3E 32 30 31 34 2D 30 35 2D 31 34 54 31 37 3A |t>2014-05-14T17:|
40A0 31 32 3A 30 35 2E 30 30 30 5A 3C 2F 44 6C 76 72 |12:05.000Z</Dlvr|
40B0 79 44 74 3E 3C 58 70 72 74 6E 44 74 3E 32 30 32 |yDt><XprtnDt>202|
40C0 31 2D 30 31 2D 31 32 54 30 39 3A 30 37 3A 31 38 |1-01-12T09:07:18|
40D0 2E 30 30 30 5A 3C 2F 58 70 72 74 6E 44 74 3E 3C |.000Z</XprtnDt><|
40E0 4E 62 3E 50 41 59 2E 45 4C 49 2E 49 4E 47 2E 50 |Nb>PAY.ELI.ING.P|
40F0 4F 49 2E 31 32 30 2E 31 33 30 33 30 30 30 32 3C |OI.120.13030002<|
4100 2F 4E 62 3E 3C 2F 41 73 73 6D 6E 74 3E 3C 2F 43 |/Nb></Assmnt></C|
4110 6D 70 6E 74 3E 3C 2F 50 4F 49 3E 3C 43 61 72 64 |mpnt></POI><Card|
4120 3E 3C 50 6C 61 69 6E 43 61 72 64 44 61 74 61 3E |><PlainCardData>|
4130 3C 50 41 4E 3E 35 34 31 33 33 33 30 30 31 30 30 |<PAN>54133300100|
4140 30 30 37 31 30 3C 2F 50 41 4E 3E 3C 43 61 72 64 |00710</PAN><Card|
4150 53 65 71 4E 62 3E 30 30 3C 2F 43 61 72 64 53 65 |SeqNb>00</CardSe|
4160 71 4E 62 3E 3C 46 63 74 76 44 74 3E 32 30 31 30 |qNb><FctvDt>2010|
4170 2D 31 32 3C 2F 46 63 74 76 44 74 3E 3C 58 70 72 |-12</FctvDt><Xpr|
4180 79 44 74 3E 32 30 31 35 2D 31 32 3C 2F 58 70 72 |yDt>2015-12</Xpr|
4190 79 44 74 3E 3C 53 76 63 43 64 3E 32 30 31 3C 2F |yDt><SvcCd>201</|
41A0 53 76 63 43 64 3E 3C 2F 50 6C 61 69 6E 43 61 72 |SvcCd></PlainCar|
41B0 64 44 61 74 61 3E 3C 43 61 72 64 43 74 72 79 43 |dData><CardCtryC|
41C0 64 3E 44 45 55 3C 2F 43 61 72 64 43 74 72 79 43 |d>DEU</CardCtryC|
41D0 64 3E 3C 43 61 72 64 50 64 63 74 50 72 66 6C 3E |d><CardPdctPrfl>|
41E0 30 30 31 38 3C 2F 43 61 72 64 50 64 63 74 50 72 |0018</CardPdctPr|
41F0 66 6C 3E 3C 43 61 72 64 42 72 6E 64 3E 43 42 3C |fl><CardBrnd>CB<|
4200 2F 43 61 72 64 42 72 6E 64 3E 3C 2F 43 61 72 64 |/CardBrnd></Card|
4210 3E 3C 2F 45 6E 76 74 3E 3C 43 6E 74 78 74 3E 3C |></Envt><Cntxt><|
4220 50 6D 74 43 6E 74 78 74 3E 3C 43 72 64 68 6C 64 |PmtCntxt><Crdhld|
4230 72 50 72 65 73 3E 74 72 75 65 3C 2F 43 72 64 68 |rPres>true</Crdh|
4240 6C 64 72 50 72 65 73 3E 3C 4F 6E 4C 69 6E 65 43 |ldrPres><OnLineC|
4250 6E 74 78 74 3E 74 72 75 65 3C 2F 4F 6E 4C 69 6E |ntxt>true</OnLin|
4260 65 43 6E 74 78 74 3E 3C 41 74 74 6E 64 6E 63 43 |eCntxt><AttndncC|
4270 6E 74 78 74 3E 41 54 54 44 3C 2F 41 74 74 6E 64 |ntxt>ATTD</Attnd|
4280 6E 63 43 6E 74 78 74 3E 3C 43 61 72 64 44 61 74 |ncCntxt><CardDat|
4290 61 4E 74 72 79 4D 64 3E 43 49 43 43 3C 2F 43 61 |aNtryMd>CICC</Ca|
42A0 72 64 44 61 74 61 4E 74 72 79 4D 64 3E 3C 2F 50 |rdDataNtryMd></P|
42B0 6D 74 43 6E 74 78 74 3E 3C 53 61 6C 65 43 6E 74 |mtCntxt><SaleCnt|
42C0 78 74 3E 3C 53 61 6C 65 52 65 66 4E 62 3E 30 30 |xt><SaleRefNb>00|
42D0 30 30 30 30 30 30 31 31 31 31 31 31 31 31 2F 32 |00000011111111/2|
42E0 30 31 35 31 32 30 33 31 34 30 37 35 35 3C 2F 53 |0151203140755</S|
42F0 61 6C 65 52 65 66 4E 62 3E 3C 43 73 68 72 49 64 |aleRefNb><CshrId|
4300 3E 30 30 30 30 30 30 30 31 3C 2F 43 73 68 72 49 |>00000001</CshrI|
4310 64 3E 3C 2F 53 61 6C 65 43 6E 74 78 74 3E 3C 2F |d></SaleCntxt></|
4320 43 6E 74 78 74 3E 3C 54 78 3E 3C 54 78 54 70 3E |Cntxt><Tx><TxTp>|
4330 52 46 4E 44 3C 2F 54 78 54 70 3E 3C 4D 72 63 68 |RFND</TxTp><Mrch|
4340 6E 74 43 74 67 79 43 64 3E 35 39 39 39 3C 2F 4D |ntCtgyCd>5999</M|
4350 72 63 68 6E 74 43 74 67 79 43 64 3E 3C 54 78 49 |rchntCtgyCd><TxI|
4360 64 3E 3C 54 78 44 74 54 6D 3E 32 30 31 35 2D 31 |d><TxDtTm>2015-1|
4370 32 2D 30 33 54 31 34 3A 30 37 3A 35 35 2E 30 30 |2-03T14:07:55.00|
4380 30 3C 2F 54 78 44 74 54 6D 3E 3C 54 78 52 65 66 |0</TxDtTm><TxRef|
4390 3E 31 33 30 32 31 33 3C 2F 54 78 52 65 66 3E 3C |>130213</TxRef><|
43A0 2F 54 78 49 64 3E 3C 54 78 53 75 63 73 73 3E 74 |/TxId><TxSucss>t|
43B0 72 75 65 3C 2F 54 78 53 75 63 73 73 3E 3C 52 76 |rue</TxSucss><Rv|
43C0 73 6C 3E 66 61 6C 73 65 3C 2F 52 76 73 6C 3E 3C |sl>false</Rvsl><|
43D0 54 78 44 74 6C 73 3E 3C 43 63 79 3E 45 55 52 3C |TxDtls><Ccy>EUR<|
43E0 2F 43 63 79 3E 3C 54 74 6C 41 6D 74 3E 32 2E 31 |/Ccy><TtlAmt>2.1|
43F0 36 3C 2F 54 74 6C 41 6D 74 3E 3C 49 43 43 52 6C |6</TtlAmt><ICCRl|
4400 74 64 44 61 74 61 3E 6E 77 49 47 41 41 41 41 41 |tdData>nwIGAAAAA|
4410 41 49 57 6E 77 4D 47 41 41 41 41 41 41 41 41 6E |AIWnwMGAAAAAAAAn|
4420 79 59 49 55 63 42 2F 78 33 6A 35 38 2F 42 66 4A |yYIUcB/x3j58/BfJ|

7 Messages Examples - 428 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

4430 51 4D 51 45 67 47 43 41 6C 67 41 6E 7A 59 43 45 |QMQEgGCAlgAnzYCE|
4440 53 4B 66 43 51 49 41 41 70 38 6E 41 51 43 66 4E |SKfCQIAAp8nAQCfN|
4450 41 4D 2F 41 41 43 45 42 36 41 41 41 41 41 45 45 |AM/AACEB6AAAAAEE|
4460 42 43 66 48 67 67 77 4D 54 45 79 4D 6A 4D 7A 4E |BCfHggwMTEyMjMzN|
4470 4A 38 51 45 67 45 51 41 41 41 41 41 41 41 41 41 |J8QEgEQAAAAAAAAA|
4480 41 41 41 41 41 41 41 41 41 41 41 41 4A 38 7A 41 |AAAAAAAAAAAAJ8zA|
4490 2B 44 34 79 4A 38 61 41 67 41 51 6E 7A 55 42 49 |+D4yJ8aAgAQnzUBI|
44A0 70 55 46 41 41 41 41 41 41 42 66 4B 67 49 4A 65 |pUFAAAAAABfKgIJe|
44B0 4A 6F 44 46 52 49 44 6E 30 45 44 45 77 49 54 6E |JoDFRIDn0EDEwITn|
44C0 41 45 41 6E 7A 63 45 4A 6F 31 6A 4D 4D 6F 45 2F |AEAnzcEJo1jMMoE/|
44D0 67 77 51 41 4D 55 42 41 4A 73 43 49 41 41 3D 3C |gwQAMUBAJsCIAA=<|
44E0 2F 49 43 43 52 6C 74 64 44 61 74 61 3E 3C 2F 54 |/ICCRltdData></T|
44F0 78 44 74 6C 73 3E 3C 41 75 74 68 73 74 6E 52 73 |xDtls><AuthstnRs|
4500 6C 74 3E 3C 41 75 74 68 73 74 6E 4E 74 74 79 3E |lt><AuthstnNtty>|
4510 3C 54 70 3E 43 49 53 53 3C 2F 54 70 3E 3C 2F 41 |<Tp>CISS</Tp></A|
4520 75 74 68 73 74 6E 4E 74 74 79 3E 3C 52 73 70 6E |uthstnNtty><Rspn|
4530 54 6F 41 75 74 68 73 74 6E 3E 3C 52 73 70 6E 3E |ToAuthstn><Rspn>|
4540 41 50 50 52 3C 2F 52 73 70 6E 3E 3C 2F 52 73 70 |APPR</Rspn></Rsp|
4550 6E 54 6F 41 75 74 68 73 74 6E 3E 3C 41 75 74 68 |nToAuthstn><Auth|
4560 73 74 6E 43 64 3E 30 33 32 39 38 33 3C 2F 41 75 |stnCd>032983</Au|
4570 74 68 73 74 6E 43 64 3E 3C 2F 41 75 74 68 73 74 |thstnCd></Authst|
4580 6E 52 73 6C 74 3E 3C 2F 54 78 3E 3C 2F 43 6D 70 |nRslt></Tx></Cmp|
4590 6C 74 6E 3E 3C 2F 54 78 3E 3C 2F 44 61 74 61 53 |ltn></Tx></DataS|
45A0 65 74 3E 3C 2F 42 74 63 68 54 72 66 3E 3C 53 63 |et></BtchTrf><Sc|
45B0 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 70 3E 41 |tyTrlr><CnttTp>A|
45C0 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C 41 75 74 |UTH</CnttTp><Aut|
45D0 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 70 74 3E |hntcdData><Rcpt>|
45E0 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B 65 79 |<KEK><KEKId><Key|
45F0 49 64 3E 53 70 65 63 56 31 54 65 73 74 4B 65 79 |Id>SpecV1TestKey|
4600 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 73 6E |</KeyId><KeyVrsn|
4610 3E 32 30 31 30 30 36 30 37 31 35 3C 2F 4B 65 79 |>2010060715</Key|
4620 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 64 3E |Vrsn><DerivtnId>|
4630 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 76 74 |OYclpQE=</Derivt|
4640 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B 65 79 |nId></KEKId><Key|
4650 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F |NcrptnAlgo><Algo|
4660 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F 4B 65 |>DKP9</Algo></Ke|
4670 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 |yNcrptnAlgo><Ncr|
4680 70 74 64 4B 65 79 3E 34 70 41 67 41 42 63 3D 3C |ptdKey>4pAgABc=<|
4690 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B 45 4B |/NcrptdKey></KEK|
46A0 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 6C 67 6F |></Rcpt><MACAlgo|
46B0 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F 41 6C 67 |><Algo>MCCS</Alg|
46C0 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C 4E 63 70 |o></MACAlgo><Ncp|
46D0 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 |sltdCntt><CnttTp|
46E0 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 2F |>DATA</CnttTp></|
46F0 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 4D 41 43 |NcpsltdCntt><MAC|
4700 3E 2B 38 36 7A 47 72 75 45 74 55 55 3D 3C 2F 4D |>+86zGruEtUU=</M|
4710 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 44 61 74 |AC></AuthntcdDat|
4720 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E 3C 2F 41 |a></SctyTrlr></A|
4730 63 63 70 74 72 42 74 63 68 54 72 66 3E 3C 2F 44 |ccptrBtchTrf></D|
4740 6F 63 75 6D 65 6E 74 3E 20 |ocument> |

7 Messages Examples - 429 - 7.6 Batch Transfer messages


Card Payments Message Usage Guide Version 5.0

7.7 Diagnostic Messages

The example below is to test a new DUKPT key that has been downloaded from the Acquirer by
sending a DiagnosticRequest from the POI.

7.7.1 AcceptorDiagnosticRequest

The POI identified by 66000001 from the Merchant identified by EPASMER001 sends the
AcceptorDiagnosticRequest message to the Acquirer host identified by epas-acquirer-1.

The Key Encryption Key is the DUKPT key, named SpecV1TesKey, with the version 2010060715,
which is the test key with the following values:
BDK (Base Derivation Key): 37233E89 0B0104E9 BC943D0E 45EAE5A7
KSN (Key Serial Number): 398725A501 E290200017
TIK (Terminal Initial Key): EE3AE644 1C2EEE18 3F3B4179 2DBCD318
MAC Encryption Key Request: 5E64F1AB F25D3BA1 7F629EC2 B302F8EA
MAC Encryption Key Response: 5E64F1AB 0D5DC4A1 7F629EC2 4C0207EA

7 Messages Examples - 430 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorDiagnosticRequest message contains data presented below.

AcceptorDiagnosticRequest
Header
MessageFunction DiagnosticRequest
ProtocolVersion 5.0
ExchangeIdentifier 378
CreationDateTime 2013-08-08T22:18:35.07+02:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
DiagnosticRequest
Environment
Acquirer
Identification 9287351
ParametersVersion 2013-08-07 08:00:00
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC DC36A17352BDE8F7

7 Messages Examples - 431 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorDiagnosticRequest XML message is presented below.


<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.013.001.05">
<AccptrDgnstcReq>
<Hdr>
<MsgFctn>DGNP</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>378</XchgId>
<CreDtTm>2013-08-08T22:18:35.07+02:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<DgnstcReq>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</POIId>
</Envt>
</DgnstcReq>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>3Dahc1K96Pc=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrDgnstcReq>
</Document>

7 Messages Examples - 432 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body DgnstcReq (without
spaces or line breaks) is dumped below:
0000 3C 44 67 6E 73 74 63 52 65 71 3E 3C 45 6E 76 74 |<DgnstcReq><Envt|
0010 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E |><Acqrr><Id><Id>|
0020 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 2F 49 64 |9287351</Id></Id|
0030 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 |><ParamsVrsn>201|
0040 33 2D 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 |3-08-07 08:00:00|
0050 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 |</ParamsVrsn></A|
0060 63 71 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C |cqrr><MrchntId><|
0070 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 |Id>EPASMER001</I|
0080 64 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F |d></MrchntId><PO|
0090 49 49 64 3E 3C 49 64 3E 36 36 30 30 30 30 30 31 |IId><Id>66000001|
00A0 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F 54 |</Id><Tp>OPOI</T|
00B0 70 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 |p><Issr>ACQR</Is|
00C0 73 72 3E 3C 2F 50 4F 49 49 64 3E 3C 2F 45 6E 76 |sr></POIId></Env|
00D0 74 3E 3C 2F 44 67 6E 73 74 63 52 65 71 3E |t></DgnstcReq> |

The SHA-256 digest of the message body DgnstcReq is:


0000 E9 F8 56 57 FA 8F F8 DD C0 48 2C E0 F4 96 3F 90 |..VW.....H,...?.|
0010 85 19 D2 C6 6B 20 EF 21 FE 56 2E 9E 33 25 D4 F7 |....k .!.V..3%..|

After padding, the digest becomes:


0000 E9 F8 56 57 FA 8F F8 DD C0 48 2C E0 F4 96 3F 90 |..VW.....H,...?.|
0010 85 19 D2 C6 6B 20 EF 21 FE 56 2E 9E 33 25 D4 F7 |....k .!.V..3%..|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (5E64F1AB F25D3BA1 7F629EC2
B302F8EA), we obtain the MAC of the AcceptorDiagnosticRequest DC36A17352BDE8F7 and after
conversion into base64 "3Dahc1K96Pc=".
0000 68 86 0D D2 68 80 B1 1A 85 A3 F5 D8 26 4B 0E FC |h...h.......&K..|
0010 26 6D 33 65 AD 27 B6 42 33 8F B2 F2 B7 CF 00 5F |&m3e.'.B3......_|
0020 DC 36 A1 73 52 BD E8 F7 |.6.sR... |

7 Messages Examples - 433 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

The message sent by the transport protocol is:


0000 00 00 04 26 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |...&<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 31 33 2E 30 30 31 2E 30 35 22 |caaa.013.001.05"|
00A0 3E 3C 41 63 63 70 74 72 44 67 6E 73 74 63 52 65 |><AccptrDgnstcRe|
00B0 71 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E 3E |q><Hdr><MsgFctn>|
00C0 44 47 4E 50 3C 2F 4D 73 67 46 63 74 6E 3E 3C 50 |DGNP</MsgFctn><P|
00D0 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F 50 |rtcolVrsn>5.0</P|
00E0 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 49 |rtcolVrsn><XchgI|
00F0 64 3E 33 37 38 3C 2F 58 63 68 67 49 64 3E 3C 43 |d>378</XchgId><C|
0100 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D 30 |reDtTm>2013-08-0|
0110 38 54 32 32 3A 31 38 3A 33 35 2E 30 37 2B 30 32 |8T22:18:35.07+02|
0120 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 6E |:00</CreDtTm><In|
0130 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 30 |itgPty><Id>66000|
0140 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 |001</Id><Tp>OPOI|
0150 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 3C |</Tp><Issr>ACQR<|
0160 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 79 |/Issr></InitgPty|
0170 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 70 |><RcptPty><Id>ep|
0180 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F 49 |as-acquirer-1</I|
0190 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E 3C |d><Tp>ACQR</Tp><|
01A0 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E 3C |/RcptPty></Hdr><|
01B0 44 67 6E 73 74 63 52 65 71 3E 3C 45 6E 76 74 3E |DgnstcReq><Envt>|
01C0 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 3E 39 |<Acqrr><Id><Id>9|
01D0 32 38 37 33 35 31 3C 2F 49 64 3E 3C 2F 49 64 3E |287351</Id></Id>|
01E0 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 31 33 |<ParamsVrsn>2013|
01F0 2D 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 30 3C |-08-07 08:00:00<|
0200 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F 41 63 |/ParamsVrsn></Ac|
0210 71 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E 3C 49 |qrr><MrchntId><I|
0220 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F 49 64 |d>EPASMER001</Id|
0230 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 4F 49 |></MrchntId><POI|
0240 49 64 3E 3C 49 64 3E 36 36 30 30 30 30 30 31 3C |Id><Id>66000001<|
0250 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F 54 70 |/Id><Tp>OPOI</Tp|
0260 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 |><Issr>ACQR</Iss|
0270 72 3E 3C 2F 50 4F 49 49 64 3E 3C 2F 45 6E 76 74 |r></POIId></Envt|
0280 3E 3C 2F 44 67 6E 73 74 63 52 65 71 3E 3C 53 63 |></DgnstcReq><Sc|
0290 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 70 3E 41 |tyTrlr><CnttTp>A|
02A0 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C 41 75 74 |UTH</CnttTp><Aut|
02B0 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 70 74 3E |hntcdData><Rcpt>|
02C0 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C 4B 65 79 |<KEK><KEKId><Key|
02D0 49 64 3E 53 70 65 63 56 31 54 65 73 74 4B 65 79 |Id>SpecV1TestKey|
02E0 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 72 73 6E |</KeyId><KeyVrsn|
02F0 3E 32 30 31 30 30 36 30 37 31 35 3C 2F 4B 65 79 |>2010060715</Key|
0300 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E 49 64 3E |Vrsn><DerivtnId>|
0310 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 69 76 74 |OYclpQE=</Derivt|
0320 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C 4B 65 79 |nId></KEKId><Key|

7 Messages Examples - 434 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

0330 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 6C 67 6F |NcrptnAlgo><Algo|
0340 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C 2F 4B 65 |>DKP9</Algo></Ke|
0350 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 4E 63 72 |yNcrptnAlgo><Ncr|
0360 70 74 64 4B 65 79 3E 34 70 41 67 41 42 63 3D 3C |ptdKey>4pAgABc=<|
0370 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F 4B 45 4B |/NcrptdKey></KEK|
0380 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 6C 67 6F |></Rcpt><MACAlgo|
0390 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F 41 6C 67 |><Algo>MCCS</Alg|
03A0 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C 4E 63 70 |o></MACAlgo><Ncp|
03B0 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 74 54 70 |sltdCntt><CnttTp|
03C0 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 3E 3C 2F |>DATA</CnttTp></|
03D0 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 4D 41 43 |NcpsltdCntt><MAC|
03E0 3E 33 44 61 68 63 31 4B 39 36 50 63 3D 3C 2F 4D |>3Dahc1K96Pc=</M|
03F0 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 44 61 74 |AC></AuthntcdDat|
0400 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E 3C 2F 41 |a></SctyTrlr></A|
0410 63 63 70 74 72 44 67 6E 73 74 63 52 65 71 3E 3C |ccptrDgnstcReq><|
0420 2F 44 6F 63 75 6D 65 6E 74 3E |/Document> |

7.7.2 AcceptorDiagnosticResponse

The Acquirer epas-acquirer-1 sends the AcceptorDiagnosticResponse message to the POI 66000001
from the Merchant EPASMER001, to prove the validity of the new key used for the MAC of the
diagnostic messages.

AcceptorDiagnosticResponse
Header
MessageFunction DiagnosticResponse
ProtocolVersion 2.0
ExchangeIdentifier 378
CreationDateTime 2013-08-08T22:18:35.08+02:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification epas-acquirer-1
Type Acquirer
DiagnosticResponse
Environment
Acquirer
Identification 9287351
ParametersVersion 2013-08-07 08:00:00
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 66000001
Type OriginatingPOI
Issuer Acquirer

7 Messages Examples - 435 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC 753985C2E0157B4B

7 Messages Examples - 436 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

The AcceptorDiagnosticResponse XML message is presented below.


<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.014.001.05">
<AccptrDgnstcRspn>
<Hdr>
<MsgFctn>DGNQ</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>378</XchgId>
<CreDtTm>2013-08-08T22:18:35.08+02:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id>epas-acquirer-1</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<DgnstcRspn>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</POIId>
</Envt>
</DgnstcRspn>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>dTmFwuAVe0s=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrDgnstcRspn>
</Document>

7 Messages Examples - 437 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

Once unnecessary spaces and carriage returns are removed, the message body DgnstcRspn (without
spaces or line breaks) is dumped below:
0000 3C 44 67 6E 73 74 63 52 73 70 6E 3E 3C 45 6E 76 |<DgnstcRspn><Env|
0010 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
0020 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 2F 49 |>9287351</Id></I|
0030 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 |d><ParamsVrsn>20|
0040 31 33 2D 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 |13-08-07 08:00:0|
0050 30 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F |0</ParamsVrsn></|
0060 41 63 71 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E |Acqrr><MrchntId>|
0070 3C 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F |<Id>EPASMER001</|
0080 49 64 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 |Id></MrchntId><P|
0090 4F 49 49 64 3E 3C 49 64 3E 36 36 30 30 30 30 30 |OIId><Id>6600000|
00A0 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F |1</Id><Tp>OPOI</|
00B0 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 |Tp><Issr>ACQR</I|
00C0 73 73 72 3E 3C 2F 50 4F 49 49 64 3E 3C 2F 45 6E |ssr></POIId></En|
00D0 76 74 3E 3C 2F 44 67 6E 73 74 63 52 73 70 6E 3E |vt></DgnstcRspn>|

The SHA-256 digest of the message body DgnstcRspn is:


0000 27 81 98 1D D3 12 70 20 61 56 CE 50 A2 A4 45 C8 |'.....p aV.P..E.|
0010 4E 71 25 6C 68 E7 36 AC D4 C1 7F 46 99 FF 07 95 |Nq%lh.6....F....|

After padding, the digest becomes:


0000 27 81 98 1D D3 12 70 20 61 56 CE 50 A2 A4 45 C8 |'.....p aV.P..E.|
0010 4E 71 25 6C 68 E7 36 AC D4 C1 7F 46 99 FF 07 95 |Nq%lh.6....F....|
0020 80 00 00 00 00 00 00 00 |........ |

Retail CBC encryption with the MAC Computation test Key (5E64F1AB 0D5DC4A1 7F629EC2
4C0207EA), we obtain the MAC of the AcceptorDiagnosticResponse 753985C2E0157B4B and after
conversion into base64 "dTmFwuAVe0s=".
0000 AB 7F 2D C0 65 90 4C 2D 1A 86 4D DB 37 94 7A 43 |..-.e.L-..M.7.zC|
0010 43 55 E4 77 1E A0 44 7C 02 45 B8 7D 6D 48 56 F9 |CU.w..D|.E.}mHV.|
0020 75 39 85 C2 E0 15 7B 4B |u9....{K |

7 Messages Examples - 438 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

The message sent by the transport protocol is:


0000 00 00 04 2A 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |...*<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 31 34 2E 30 30 31 2E 30 35 22 |caaa.014.001.05"|
00A0 3E 3C 41 63 63 70 74 72 44 67 6E 73 74 63 52 73 |><AccptrDgnstcRs|
00B0 70 6E 3E 3C 48 64 72 3E 3C 4D 73 67 46 63 74 6E |pn><Hdr><MsgFctn|
00C0 3E 44 47 4E 51 3C 2F 4D 73 67 46 63 74 6E 3E 3C |>DGNQ</MsgFctn><|
00D0 50 72 74 63 6F 6C 56 72 73 6E 3E 35 2E 30 3C 2F |PrtcolVrsn>5.0</|
00E0 50 72 74 63 6F 6C 56 72 73 6E 3E 3C 58 63 68 67 |PrtcolVrsn><Xchg|
00F0 49 64 3E 33 37 38 3C 2F 58 63 68 67 49 64 3E 3C |Id>378</XchgId><|
0100 43 72 65 44 74 54 6D 3E 32 30 31 33 2D 30 38 2D |CreDtTm>2013-08-|
0110 30 38 54 32 32 3A 31 38 3A 33 35 2E 30 38 2B 30 |08T22:18:35.08+0|
0120 32 3A 30 30 3C 2F 43 72 65 44 74 54 6D 3E 3C 49 |2:00</CreDtTm><I|
0130 6E 69 74 67 50 74 79 3E 3C 49 64 3E 36 36 30 30 |nitgPty><Id>6600|
0140 30 30 30 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F |0001</Id><Tp>OPO|
0150 49 3C 2F 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 |I</Tp><Issr>ACQR|
0160 3C 2F 49 73 73 72 3E 3C 2F 49 6E 69 74 67 50 74 |</Issr></InitgPt|
0170 79 3E 3C 52 63 70 74 50 74 79 3E 3C 49 64 3E 65 |y><RcptPty><Id>e|
0180 70 61 73 2D 61 63 71 75 69 72 65 72 2D 31 3C 2F |pas-acquirer-1</|
0190 49 64 3E 3C 54 70 3E 41 43 51 52 3C 2F 54 70 3E |Id><Tp>ACQR</Tp>|
01A0 3C 2F 52 63 70 74 50 74 79 3E 3C 2F 48 64 72 3E |</RcptPty></Hdr>|
01B0 3C 44 67 6E 73 74 63 52 73 70 6E 3E 3C 45 6E 76 |<DgnstcRspn><Env|
01C0 74 3E 3C 41 63 71 72 72 3E 3C 49 64 3E 3C 49 64 |t><Acqrr><Id><Id|
01D0 3E 39 32 38 37 33 35 31 3C 2F 49 64 3E 3C 2F 49 |>9287351</Id></I|
01E0 64 3E 3C 50 61 72 61 6D 73 56 72 73 6E 3E 32 30 |d><ParamsVrsn>20|
01F0 31 33 2D 30 38 2D 30 37 20 30 38 3A 30 30 3A 30 |13-08-07 08:00:0|
0200 30 3C 2F 50 61 72 61 6D 73 56 72 73 6E 3E 3C 2F |0</ParamsVrsn></|
0210 41 63 71 72 72 3E 3C 4D 72 63 68 6E 74 49 64 3E |Acqrr><MrchntId>|
0220 3C 49 64 3E 45 50 41 53 4D 45 52 30 30 31 3C 2F |<Id>EPASMER001</|
0230 49 64 3E 3C 2F 4D 72 63 68 6E 74 49 64 3E 3C 50 |Id></MrchntId><P|
0240 4F 49 49 64 3E 3C 49 64 3E 36 36 30 30 30 30 30 |OIId><Id>6600000|
0250 31 3C 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F |1</Id><Tp>OPOI</|
0260 54 70 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 |Tp><Issr>ACQR</I|
0270 73 73 72 3E 3C 2F 50 4F 49 49 64 3E 3C 2F 45 6E |ssr></POIId></En|
0280 76 74 3E 3C 2F 44 67 6E 73 74 63 52 73 70 6E 3E |vt></DgnstcRspn>|
0290 3C 53 63 74 79 54 72 6C 72 3E 3C 43 6E 74 74 54 |<SctyTrlr><CnttT|
02A0 70 3E 41 55 54 48 3C 2F 43 6E 74 74 54 70 3E 3C |p>AUTH</CnttTp><|
02B0 41 75 74 68 6E 74 63 64 44 61 74 61 3E 3C 52 63 |AuthntcdData><Rc|
02C0 70 74 3E 3C 4B 45 4B 3E 3C 4B 45 4B 49 64 3E 3C |pt><KEK><KEKId><|
02D0 4B 65 79 49 64 3E 53 70 65 63 56 31 54 65 73 74 |KeyId>SpecV1Test|
02E0 4B 65 79 3C 2F 4B 65 79 49 64 3E 3C 4B 65 79 56 |Key</KeyId><KeyV|
02F0 72 73 6E 3E 32 30 31 30 30 36 30 37 31 35 3C 2F |rsn>2010060715</|
0300 4B 65 79 56 72 73 6E 3E 3C 44 65 72 69 76 74 6E |KeyVrsn><Derivtn|
0310 49 64 3E 4F 59 63 6C 70 51 45 3D 3C 2F 44 65 72 |Id>OYclpQE=</Der|
0320 69 76 74 6E 49 64 3E 3C 2F 4B 45 4B 49 64 3E 3C |ivtnId></KEKId><|

7 Messages Examples - 439 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

0330 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C 41 |KeyNcrptnAlgo><A|
0340 6C 67 6F 3E 44 4B 50 39 3C 2F 41 6C 67 6F 3E 3C |lgo>DKP9</Algo><|
0350 2F 4B 65 79 4E 63 72 70 74 6E 41 6C 67 6F 3E 3C |/KeyNcrptnAlgo><|
0360 4E 63 72 70 74 64 4B 65 79 3E 34 70 41 67 41 42 |NcrptdKey>4pAgAB|
0370 63 3D 3C 2F 4E 63 72 70 74 64 4B 65 79 3E 3C 2F |c=</NcrptdKey></|
0380 4B 45 4B 3E 3C 2F 52 63 70 74 3E 3C 4D 41 43 41 |KEK></Rcpt><MACA|
0390 6C 67 6F 3E 3C 41 6C 67 6F 3E 4D 43 43 53 3C 2F |lgo><Algo>MCCS</|
03A0 41 6C 67 6F 3E 3C 2F 4D 41 43 41 6C 67 6F 3E 3C |Algo></MACAlgo><|
03B0 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C 43 6E 74 |NcpsltdCntt><Cnt|
03C0 74 54 70 3E 44 41 54 41 3C 2F 43 6E 74 74 54 70 |tTp>DATA</CnttTp|
03D0 3E 3C 2F 4E 63 70 73 6C 74 64 43 6E 74 74 3E 3C |></NcpsltdCntt><|
03E0 4D 41 43 3E 64 54 6D 46 77 75 41 56 65 30 73 3D |MAC>dTmFwuAVe0s=|
03F0 3C 2F 4D 41 43 3E 3C 2F 41 75 74 68 6E 74 63 64 |</MAC></Authntcd|
0400 44 61 74 61 3E 3C 2F 53 63 74 79 54 72 6C 72 3E |Data></SctyTrlr>|
0410 3C 2F 41 63 63 70 74 72 44 67 6E 73 74 63 52 73 |</AccptrDgnstcRs|
0420 70 6E 3E 3C 2F 44 6F 63 75 6D 65 6E 74 3E |pn></Document> |

7 Messages Examples - 440 - 7.7 Diagnostic Messages


Card Payments Message Usage Guide Version 5.0

7.8 Rejection
This example shows the rejection of an AcceptorDiagnosticRequest message because the
identification of the RecipientParty is invalid.

7.8.1 AcceptorDiagnosticRequest

The POI identified by 66000001 from the Merchant identified by EPASMER001 sends the
AcceptorDiagnosticRequest message to the Acquirer host identified by bad-acquirer.

The Key Encryption Key is the DUKPT key, named SpecV1TesKey, with the version 2010060715,
which is the test key with value:
BDK (Base Derivation Key): 37233E89 0B0104E9 BC943D0E 45EAE5A7
KSN (Key Serial Number): 398725A501 E290200017
TIK (Terminal Initial Key): EE3AE644 1C2EEE18 3F3B4179 2DBCD318
MAC Encryption Key Request: 5E64F1AB F25D3BA1 7F629EC2 B302F8EA
MAC Encryption Key Response: 5E64F1AB 0D5DC4A1 7F629EC2 4C0207EA

7 Messages Examples - 441 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

For the 2009 version of ANS X9.24-1:

The AcceptorDiagnosticRequest message contains data presented below.


AcceptorDiagnosticRequest
Header
MessageFunction DiagnosticRequest
ProtocolVersion 5.0
ExchangeIdentifier 378
CreationDateTime 2013-08-09T17:29:37.87+02:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification bad-acquirer
Type Acquirer
DiagnosticRequest
Environment
Acquirer
Identification 9287351
ParametersVersion 2013-08-07 08:00:00
MerchantIdentification
Identification EPASMER001
POIIdentification
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
SecurityTrailer
ContentType AuthenticatedData
AuthenticatedData
Recipient
KEK
KEKIdentification
KeyIdentification SpecV1TestKey
KeyVersion 2011010715
DerivationIdentification 398725A501
KeyEncryptionAlgorithm
Algorithm DUKPT2009
EncryptedKey E290200017
MACAlgorithm
Algorithm RetailSHA256MAC
EncapsulatedContent
ContentType PlainData
MAC DC36A17352BDE8F7

7 Messages Examples - 442 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

The AcceptorDiagnosticRequest XML message is presented below.


<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.013.001.05">
<AccptrDgnstcReq>
<Hdr>
<MsgFctn>DGNP</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>378</XchgId>
<CreDtTm>2013-08-09T17:29:37.87+02:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id> bad-acquirer</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<DgnstcReq>
<Envt>
<Acqrr>
<Id>
<Id>9287351</Id>
</Id>
<ParamsVrsn>2013-08-07 08:00:00</ParamsVrsn>
</Acqrr>
<MrchntId>
<Id>EPASMER001</Id>
</MrchntId>
<POIId>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</POIId>
</Envt>
</DgnstcReq>
<SctyTrlr>
<CnttTp>AUTH</CnttTp>
<AuthntcdData>
<Rcpt>
<KEK>
<KEKId>
<KeyId>SpecV1TestKey</KeyId>
<KeyVrsn>2010060715</KeyVrsn>
<DerivtnId>OYclpQE=</DerivtnId>
</KEKId>
<KeyNcrptnAlgo>
<Algo>DKP9</Algo>
</KeyNcrptnAlgo>
<NcrptdKey>4pAgABc=</NcrptdKey>
</KEK>
</Rcpt>
<MACAlgo>
<Algo>MCCS</Algo>
</MACAlgo>
<NcpsltdCntt>
<CnttTp>DATA</CnttTp>
</NcpsltdCntt>
<MAC>3Dahc1K96Pc=</MAC>
</AuthntcdData>
</SctyTrlr>
</AccptrDgnstcReq>
</Document>

7 Messages Examples - 443 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

7.8.2 AcceptorRejection

The Acquirer host identified by bad-acquirer is invalid. The Acquirer sends an AcceptorRejection
message contains the RejectReason to RecipientParty and details of the error in
AdditionalInformation.

AcceptorDiagnosticRequest
Header
MessageFunction AcceptorResponseReject
ProtocolVersion 5.0
ExchangeIdentifier 378
CreationDateTime 2013-08-09T17:29:37.89+02:00
InitiatingParty
Identification 66000001
Type OriginatingPOI
Issuer Acquirer
RecipientParty
Identification bad-acquirer
Type Acquirer
Reject
RejectReason RecipientParty
AdditionalInformation Invalid Acquirer ID 'bad-acquirer'
MessageInError <?xml version="1.0" encoding="UTF-8"?><Document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.013.001.05"><AccptrDgnstcReq><Hdr>
<MsgFctn>DGNP</MsgFctn><PrtcolVrsn>5.0</PrtcolVrsn><XchgId>378</XchgId>
<CreDtTm>2013-08-
09T17:29:37.87+02:00</CreDtTm><InitgPty><Id>66000001</Id><Tp>OPOI</Tp><I
ssr>ACQR</Issr></InitgPty><RcptPty><Id> bad-
acquirer</Id><Tp>ACQR</Tp></RcptPty></Hdr><DgnstcReq><Envt><Acqrr><Id><
Id>9287351</Id></Id><ParamsVrsn>2013-08-07
08:00:00</ParamsVrsn></Acqrr><MrchntId><Id>EPASMER001</Id></MrchntId><P
OIId><Id>66000001</Id><Tp>OPOI</Tp><Issr>ACQR</Issr></POIId></Envt></Dg
nstcReq><SctyTrlr><CnttTp>AUTH</CnttTp><AuthntcdData><Rcpt><KEK><KEKI
d><KeyId>SpecV1TestKey</KeyId><KeyVrsn>2010060715</KeyVrsn><DerivtnId>
OYclpQE=</DerivtnId></KEKId><KeyNcrptnAlgo><Algo>DKP9</Algo></KeyNcrptn
Algo><NcrptdKey>4pAgABc=</NcrptdKey></KEK></Rcpt><MACAlgo><Algo>MCC
S</Algo></MACAlgo><NcpsltdCntt><CnttTp>DATA</CnttTp></NcpsltdCntt><MAC
>2MAzAzjVWVQ=</MAC></AuthntcdData></SctyTrlr></AccptrDgnstcReq></Docu
ment>

7 Messages Examples - 444 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

The AcceptorRejection XML message is presented below.

<?xml version="1.0" encoding="UTF-8"?>


<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.015.001.05">
<AccptrRjctn>
<Hdr>
<MsgFctn>RJCP</MsgFctn>
<PrtcolVrsn>5.0</PrtcolVrsn>
<XchgId>378</XchgId>
<CreDtTm>2013-08-09T17:29:37.87+02:00</CreDtTm>
<InitgPty>
<Id>66000001</Id>
<Tp>OPOI</Tp>
<Issr>ACQR</Issr>
</InitgPty>
<RcptPty>
<Id> bad-acquirer</Id>
<Tp>ACQR</Tp>
</RcptPty>
</Hdr>
<Rjct>
<RjctRsn>RCPP</RjctRsn>
<AddtlInf>Invalid Acquirer ID 'bad-acquirer'</AddtlInf>
<MsgInErr>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48RG9jdW1lbnQgeG1sbnM6
eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSIgeG1sbnM9
InVybjppc286c3RkOmlzbzoyMDAyMjp0ZWNoOnhzZDpjYWFhLjAxMy4wMDEuMDUiPjxBY2Nw
dHJEZ25zdGNSZXE+PEhkcj48TXNnRmN0bj5ER05QPC9Nc2dGY3RuPjxQcnRjb2xWcnNuPjUu
MDwvUHJ0Y29sVnJzbj48WGNoZ0lkPjM3ODwvWGNoZ0lkPjxDcmVEdFRtPjIwMTMtMDgtMDlU
MTc6Mjk6MzcuODcrMDI6MDA8L0NyZUR0VG0+PEluaXRnUHR5PjxJZD42NjAwMDAwMTwvSWQ+
PFRwPk9QT0k8L1RwPjxJc3NyPkFDUVI8L0lzc3I+PC9Jbml0Z1B0eT48UmNwdFB0eT48SWQ+
IGJhZC1hY3F1aXJlcjwvSWQ+PFRwPkFDUVI8L1RwPjwvUmNwdFB0eT48L0hkcj48RGduc3Rj
UmVxPjxFbnZ0PjxBY3Fycj48SWQ+PElkPjkyODczNTE8L0lkPjwvSWQ+PFBhcmFtc1Zyc24+
MjAxMy0wOC0wNyAwODowMDowMDwvUGFyYW1zVnJzbj48L0FjcXJyPjxNcmNobnRJZD48SWQ+
RVBBU01FUjAwMTwvSWQ+PC9NcmNobnRJZD48UE9JSWQ+PElkPjY2MDAwMDAxPC9JZD48VHA+
T1BPSTwvVHA+PElzc3I+QUNRUjwvSXNzcj48L1BPSUlkPjwvRW52dD48L0RnbnN0Y1JlcT48
U2N0eVRybHI+PENudHRUcD5BVVRIPC9DbnR0VHA+PEF1dGhudGNkRGF0YT48UmNwdD48S0VL
PjxLRUtJZD48S2V5SWQ+U3BlY1YxVGVzdEtleTwvS2V5SWQ+PEtleVZyc24+MjAxMDA2MDcx
NTwvS2V5VnJzbj48RGVyaXZ0bklkPk9ZY2xwUUU9PC9EZXJpdnRuSWQ+PC9LRUtJZD48S2V5
TmNycHRuQWxnbz48QWxnbz5ES1A5PC9BbGdvPjwvS2V5TmNycHRuQWxnbz48TmNycHRkS2V5
PjRwQWdBQmM9PC9OY3JwdGRLZXk+PC9LRUs+PC9SY3B0PjxNQUNBbGdvPjxBbGdvPk1DQ1M8
L0FsZ28+PC9NQUNBbGdvPjxOY3BzbHRkQ250dD48Q250dFRwPkRBVEE8L0NudHRUcD48L05j
cHNsdGRDbnR0PjxNQUM+Mk1BekF6alZXVlE9PC9NQUM+PC9BdXRobnRjZERhdGE+PC9TY3R5
VHJscj48L0FjY3B0ckRnbnN0Y1JlcT48L0RvY3VtZW50Pg==

</MsgInErr>
</Rjct>
</AccptrRjctn>
</Document>

7 Messages Examples - 445 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

The message sent by the transport protocol is:


0000 00 00 07 B6 3C 3F 78 6D 6C 20 76 65 72 73 69 6F |....<?xml versio|
0010 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E 67 |n="1.0" encoding|
0020 3D 22 55 54 46 2D 38 22 3F 3E 3C 44 6F 63 75 6D |="UTF-8"?><Docum|
0030 65 6E 74 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 68 |ent xmlns:xsi="h|
0040 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 67 |ttp://www.w3.org|
0050 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 2D |/2001/XMLSchema-|
0060 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 3D |instance" xmlns=|
0070 22 75 72 6E 3A 69 73 6F 3A 73 74 64 3A 69 73 6F |"urn:iso:std:iso|
0080 3A 32 30 30 32 32 3A 74 65 63 68 3A 78 73 64 3A |:20022:tech:xsd:|
0090 63 61 61 61 2E 30 31 35 2E 30 30 31 2E 30 35 22 |caaa.015.001.05"|
00A0 3E 3C 41 63 63 70 74 72 52 6A 63 74 6E 3E 3C 48 |><AccptrRjctn><H|
00B0 64 72 3E 3C 4D 73 67 46 63 74 6E 3E 52 4A 43 50 |dr><MsgFctn>RJCP|
00C0 3C 2F 4D 73 67 46 63 74 6E 3E 3C 50 72 74 63 6F |</MsgFctn><Prtco|
00D0 6C 56 72 73 6E 3E 35 2E 30 3C 2F 50 72 74 63 6F |lVrsn>5.0</Prtco|
00E0 6C 56 72 73 6E 3E 3C 58 63 68 67 49 64 3E 33 37 |lVrsn><XchgId>37|
00F0 38 3C 2F 58 63 68 67 49 64 3E 3C 43 72 65 44 74 |8</XchgId><CreDt|
0100 54 6D 3E 32 30 31 33 2D 30 38 2D 30 39 54 31 37 |Tm>2013-08-09T17|
0110 3A 32 39 3A 33 37 2E 38 37 2B 30 32 3A 30 30 3C |:29:37.87+02:00<|
0120 2F 43 72 65 44 74 54 6D 3E 3C 49 6E 69 74 67 50 |/CreDtTm><InitgP|
0130 74 79 3E 3C 49 64 3E 36 36 30 30 30 30 30 31 3C |ty><Id>66000001<|
0140 2F 49 64 3E 3C 54 70 3E 4F 50 4F 49 3C 2F 54 70 |/Id><Tp>OPOI</Tp|
0150 3E 3C 49 73 73 72 3E 41 43 51 52 3C 2F 49 73 73 |><Issr>ACQR</Iss|
0160 72 3E 3C 2F 49 6E 69 74 67 50 74 79 3E 3C 52 63 |r></InitgPty><Rc|
0170 70 74 50 74 79 3E 3C 49 64 3E 20 62 61 64 2D 61 |ptPty><Id> bad-a|
0180 63 71 75 69 72 65 72 3C 2F 49 64 3E 3C 54 70 3E |cquirer</Id><Tp>|
0190 41 43 51 52 3C 2F 54 70 3E 3C 2F 52 63 70 74 50 |ACQR</Tp></RcptP|
01A0 74 79 3E 3C 2F 48 64 72 3E 3C 52 6A 63 74 3E 3C |ty></Hdr><Rjct><|
01B0 52 6A 63 74 52 73 6E 3E 52 43 50 50 3C 2F 52 6A |RjctRsn>RCPP</Rj|
01C0 63 74 52 73 6E 3E 3C 41 64 64 74 6C 49 6E 66 3E |ctRsn><AddtlInf>|
01D0 49 6E 76 61 6C 69 64 20 41 63 71 75 69 72 65 72 |Invalid Acquirer|
01E0 20 49 44 20 27 62 61 64 2D 61 63 71 75 69 72 65 | ID 'bad-acquire|
01F0 72 27 3C 2F 41 64 64 74 6C 49 6E 66 3E 3C 4D 73 |r'</AddtlInf><Ms|
0200 67 49 6E 45 72 72 3E 50 44 39 34 62 57 77 67 64 |gInErr>PD94bWwgd|
0210 6D 56 79 63 32 6C 76 62 6A 30 69 4D 53 34 77 49 |mVyc2lvbj0iMS4wI|
0220 69 42 6C 62 6D 4E 76 5A 47 6C 75 5A 7A 30 69 56 |iBlbmNvZGluZz0iV|
0230 56 52 47 4C 54 67 69 50 7A 34 38 52 47 39 6A 64 |VRGLTgiPz48RG9jd|
0240 57 31 6C 62 6E 51 67 65 47 31 73 62 6E 4D 36 65 |W1lbnQgeG1sbnM6e|
0250 48 4E 70 50 53 4A 6F 64 48 52 77 4F 69 38 76 64 |HNpPSJodHRwOi8vd|
0260 33 64 33 4C 6E 63 7A 4C 6D 39 79 5A 79 38 79 4D |3d3LnczLm9yZy8yM|
0270 44 41 78 4C 31 68 4E 54 46 4E 6A 61 47 56 74 59 |DAxL1hNTFNjaGVtY|
0280 53 31 70 62 6E 4E 30 59 57 35 6A 5A 53 49 67 65 |S1pbnN0YW5jZSIge|
0290 47 31 73 62 6E 4D 39 49 6E 56 79 62 6A 70 70 63 |G1sbnM9InVybjppc|
02A0 32 38 36 63 33 52 6B 4F 6D 6C 7A 62 7A 6F 79 4D |286c3RkOmlzbzoyM|
02B0 44 41 79 4D 6A 70 30 5A 57 4E 6F 4F 6E 68 7A 5A |DAyMjp0ZWNoOnhzZ|
02C0 44 70 6A 59 57 46 68 4C 6A 41 78 4D 79 34 77 4D |DpjYWFhLjAxMy4wM|
02D0 44 45 75 4D 44 55 69 50 6A 78 42 59 32 4E 77 64 |DEuMDUiPjxBY2Nwd|
02E0 48 4A 45 5A 32 35 7A 64 47 4E 53 5A 58 45 2B 50 |HJEZ25zdGNSZXE+P|
02F0 45 68 6B 63 6A 34 38 54 58 4E 6E 52 6D 4E 30 62 |Ehkcj48TXNnRmN0b|
0300 6A 35 45 52 30 35 51 50 43 39 4E 63 32 64 47 59 |j5ER05QPC9Nc2dGY|
0310 33 52 75 50 6A 78 51 63 6E 52 6A 62 32 78 57 63 |3RuPjxQcnRjb2xWc|
0320 6E 4E 75 50 6A 55 75 4D 44 77 76 55 48 4A 30 59 |nNuPjUuMDwvUHJ0Y|

7 Messages Examples - 446 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

0330 32 39 73 56 6E 4A 7A 62 6A 34 38 57 47 4E 6F 5A |29sVnJzbj48WGNoZ|
0340 30 6C 6B 50 6A 4D 33 4F 44 77 76 57 47 4E 6F 5A |0lkPjM3ODwvWGNoZ|
0350 30 6C 6B 50 6A 78 44 63 6D 56 45 64 46 52 74 50 |0lkPjxDcmVEdFRtP|
0360 6A 49 77 4D 54 4D 74 4D 44 67 74 4D 44 6C 55 4D |jIwMTMtMDgtMDlUM|
0370 54 63 36 4D 6A 6B 36 4D 7A 63 75 4F 44 63 72 4D |Tc6Mjk6MzcuODcrM|
0380 44 49 36 4D 44 41 38 4C 30 4E 79 5A 55 52 30 56 |DI6MDA8L0NyZUR0V|
0390 47 30 2B 50 45 6C 75 61 58 52 6E 55 48 52 35 50 |G0+PEluaXRnUHR5P|
03A0 6A 78 4A 5A 44 34 32 4E 6A 41 77 4D 44 41 77 4D |jxJZD42NjAwMDAwM|
03B0 54 77 76 53 57 51 2B 50 46 52 77 50 6B 39 51 54 |TwvSWQ+PFRwPk9QT|
03C0 30 6B 38 4C 31 52 77 50 6A 78 4A 63 33 4E 79 50 |0k8L1RwPjxJc3NyP|
03D0 6B 46 44 55 56 49 38 4C 30 6C 7A 63 33 49 2B 50 |kFDUVI8L0lzc3I+P|
03E0 43 39 4A 62 6D 6C 30 5A 31 42 30 65 54 34 38 55 |C9Jbml0Z1B0eT48U|
03F0 6D 4E 77 64 46 42 30 65 54 34 38 53 57 51 2B 49 |mNwdFB0eT48SWQ+I|
0400 47 4A 68 5A 43 31 68 59 33 46 31 61 58 4A 6C 63 |GJhZC1hY3F1aXJlc|
0410 6A 77 76 53 57 51 2B 50 46 52 77 50 6B 46 44 55 |jwvSWQ+PFRwPkFDU|
0420 56 49 38 4C 31 52 77 50 6A 77 76 55 6D 4E 77 64 |VI8L1RwPjwvUmNwd|
0430 46 42 30 65 54 34 38 4C 30 68 6B 63 6A 34 38 52 |FB0eT48L0hkcj48R|
0440 47 64 75 63 33 52 6A 55 6D 56 78 50 6A 78 46 62 |Gduc3RjUmVxPjxFb|
0450 6E 5A 30 50 6A 78 42 59 33 46 79 63 6A 34 38 53 |nZ0PjxBY3Fycj48S|
0460 57 51 2B 50 45 6C 6B 50 6A 6B 79 4F 44 63 7A 4E |WQ+PElkPjkyODczN|
0470 54 45 38 4C 30 6C 6B 50 6A 77 76 53 57 51 2B 50 |TE8L0lkPjwvSWQ+P|
0480 46 42 68 63 6D 46 74 63 31 5A 79 63 32 34 2B 4D |FBhcmFtc1Zyc24+M|
0490 6A 41 78 4D 79 30 77 4F 43 30 77 4E 79 41 77 4F |jAxMy0wOC0wNyAwO|
04A0 44 6F 77 4D 44 6F 77 4D 44 77 76 55 47 46 79 59 |DowMDowMDwvUGFyY|
04B0 57 31 7A 56 6E 4A 7A 62 6A 34 38 4C 30 46 6A 63 |W1zVnJzbj48L0Fjc|
04C0 58 4A 79 50 6A 78 4E 63 6D 4E 6F 62 6E 52 4A 5A |XJyPjxNcmNobnRJZ|
04D0 44 34 38 53 57 51 2B 52 56 42 42 55 30 31 46 55 |D48SWQ+RVBBU01FU|
04E0 6A 41 77 4D 54 77 76 53 57 51 2B 50 43 39 4E 63 |jAwMTwvSWQ+PC9Nc|
04F0 6D 4E 6F 62 6E 52 4A 5A 44 34 38 55 45 39 4A 53 |mNobnRJZD48UE9JS|
0500 57 51 2B 50 45 6C 6B 50 6A 59 32 4D 44 41 77 4D |WQ+PElkPjY2MDAwM|
0510 44 41 78 50 43 39 4A 5A 44 34 38 56 48 41 2B 54 |DAxPC9JZD48VHA+T|
0520 31 42 50 53 54 77 76 56 48 41 2B 50 45 6C 7A 63 |1BPSTwvVHA+PElzc|
0530 33 49 2B 51 55 4E 52 55 6A 77 76 53 58 4E 7A 63 |3I+QUNRUjwvSXNzc|
0540 6A 34 38 4C 31 42 50 53 55 6C 6B 50 6A 77 76 52 |j48L1BPSUlkPjwvR|
0550 57 35 32 64 44 34 38 4C 30 52 6E 62 6E 4E 30 59 |W52dD48L0RnbnN0Y|
0560 31 4A 6C 63 54 34 38 55 32 4E 30 65 56 52 79 62 |1JlcT48U2N0eVRyb|
0570 48 49 2B 50 45 4E 75 64 48 52 55 63 44 35 42 56 |HI+PENudHRUcD5BV|
0580 56 52 49 50 43 39 44 62 6E 52 30 56 48 41 2B 50 |VRIPC9DbnR0VHA+P|
0590 45 46 31 64 47 68 75 64 47 4E 6B 52 47 46 30 59 |EF1dGhudGNkRGF0Y|
05A0 54 34 38 55 6D 4E 77 64 44 34 38 53 30 56 4C 50 |T48UmNwdD48S0VLP|
05B0 6A 78 4C 52 55 74 4A 5A 44 34 38 53 32 56 35 53 |jxLRUtJZD48S2V5S|
05C0 57 51 2B 55 33 42 6C 59 31 59 78 56 47 56 7A 64 |WQ+U3BlY1YxVGVzd|
05D0 45 74 6C 65 54 77 76 53 32 56 35 53 57 51 2B 50 |EtleTwvS2V5SWQ+P|
05E0 45 74 6C 65 56 5A 79 63 32 34 2B 4D 6A 41 78 4D |EtleVZyc24+MjAxM|
05F0 44 41 32 4D 44 63 78 4E 54 77 76 53 32 56 35 56 |DA2MDcxNTwvS2V5V|
0600 6E 4A 7A 62 6A 34 38 52 47 56 79 61 58 5A 30 62 |nJzbj48RGVyaXZ0b|
0610 6B 6C 6B 50 6B 39 5A 59 32 78 77 55 55 55 39 50 |klkPk9ZY2xwUUU9P|
0620 43 39 45 5A 58 4A 70 64 6E 52 75 53 57 51 2B 50 |C9EZXJpdnRuSWQ+P|
0630 43 39 4C 52 55 74 4A 5A 44 34 38 53 32 56 35 54 |C9LRUtJZD48S2V5T|
0640 6D 4E 79 63 48 52 75 51 57 78 6E 62 7A 34 38 51 |mNycHRuQWxnbz48Q|
0650 57 78 6E 62 7A 35 45 53 31 41 35 50 43 39 42 62 |Wxnbz5ES1A5PC9Bb|
0660 47 64 76 50 6A 77 76 53 32 56 35 54 6D 4E 79 63 |GdvPjwvS2V5TmNyc|
0670 48 52 75 51 57 78 6E 62 7A 34 38 54 6D 4E 79 63 |HRuQWxnbz48TmNyc|

7 Messages Examples - 447 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

0680 48 52 6B 53 32 56 35 50 6A 52 77 51 57 64 42 51 |HRkS2V5PjRwQWdBQ|
0690 6D 4D 39 50 43 39 4F 59 33 4A 77 64 47 52 4C 5A |mM9PC9OY3JwdGRLZ|
06A0 58 6B 2B 50 43 39 4C 52 55 73 2B 50 43 39 53 59 |Xk+PC9LRUs+PC9SY|
06B0 33 42 30 50 6A 78 4E 51 55 4E 42 62 47 64 76 50 |3B0PjxNQUNBbGdvP|
06C0 6A 78 42 62 47 64 76 50 6B 31 44 51 31 4D 38 4C |jxBbGdvPk1DQ1M8L|
06D0 30 46 73 5A 32 38 2B 50 43 39 4E 51 55 4E 42 62 |0FsZ28+PC9NQUNBb|
06E0 47 64 76 50 6A 78 4F 59 33 42 7A 62 48 52 6B 51 |GdvPjxOY3BzbHRkQ|
06F0 32 35 30 64 44 34 38 51 32 35 30 64 46 52 77 50 |250dD48Q250dFRwP|
0700 6B 52 42 56 45 45 38 4C 30 4E 75 64 48 52 55 63 |kRBVEE8L0NudHRUc|
0710 44 34 38 4C 30 35 6A 63 48 4E 73 64 47 52 44 62 |D48L05jcHNsdGRDb|
0720 6E 52 30 50 6A 78 4E 51 55 4D 2B 4D 6B 31 42 65 |nR0PjxNQUM+Mk1Be|
0730 6B 46 36 61 6C 5A 58 56 6C 45 39 50 43 39 4E 51 |kF6alZXVlE9PC9NQ|
0740 55 4D 2B 50 43 39 42 64 58 52 6F 62 6E 52 6A 5A |UM+PC9BdXRobnRjZ|
0750 45 52 68 64 47 45 2B 50 43 39 54 59 33 52 35 56 |ERhdGE+PC9TY3R5V|
0760 48 4A 73 63 6A 34 38 4C 30 46 6A 59 33 42 30 63 |HJscj48L0FjY3B0c|
0770 6B 52 6E 62 6E 4E 30 59 31 4A 6C 63 54 34 38 4C |kRnbnN0Y1JlcT48L|
0780 30 52 76 59 33 56 74 5A 57 35 30 50 67 3D 3D 3C |0RvY3VtZW50Pg==<|
0790 2F 4D 73 67 49 6E 45 72 72 3E 3C 2F 52 6A 63 74 |/MsgInErr></Rjct|
07A0 3E 3C 2F 41 63 63 70 74 72 52 6A 63 74 6E 3E 3C |></AccptrRjctn><|
07B0 2F 44 6F 63 75 6D 65 6E 74 3E |/Document> |

7 Messages Examples - 448 - 7.8 Rejection


Card Payments Message Usage Guide Version 5.0

8 Transport Protocols and Services

8.1 Protocols Organisation


Protocol implementation shall follow the general principle of robustness: be strict in what you do, be
tolerant in what you accept from others.
The Acquirer Protocols follows the traditional organisation in five layers of the model defined for the
TCP/IP protocol suite.
The two layers we are interested in are the Application Layer where the Acquirer protocol is located,
and the Transport Layer that the Application protocols interface with the Transport Services.

Initiating Party Recipient Party


Application Application Protocol Application
Layer Layer

Transport Service Transport Service

Transport Transport Protocol Transport


Layer Layer

Figure 67: Protocols Organisation

The Application Protocol is independent of the Transport Protocol, and can be used without
modification with various Transport Protocols, except where the interface to the Transport Services
needs specific information such as the transport addresses.
The Transport Protocol and the Application Protocol are also independent of the communication
infrastructure used below these layers, with the exception of the quality of service of the
communication which may involve tuning of some values of the configuration parameters (e.g. value of
timeout).
The Transport Protocol is a standard protocol allowed by the Application Protocol. Application
Protocol requires the Transport Services which can be used by the Application Protocol, and specifies
the way to use them.
If a standard Transport Protocol used by the Application Protocol does not offer a particular Transport
Service required by the Application Protocol, the Application Protocol specifies this Service through a
Transport Adaptation Layer. This is for instance the case for the application message delimitation,
which is a service not provided by the TCP Transport Protocol, but required for the decoding of a XML
message before delivering it to the Application Layer. It could be also be used to provide a particular
flow control.

Application Acquirer Protocol


Layer (CAPE messages)

Transport Services

message delimitation,
flow control...
Transport AdaptationLayer
Transport
Layer
Standard Transport Layer

Figure 68: Transport Adaptation Layer

8 Transport Protocols and Services - 449 - 8.1 Protocols Organisation


Card Payments Message Usage Guide Version 5.0

As far as transport services and their usage are defined, the definition in future of a new Transport
Protocol compliant to the defined Transport Service, will not impact the specifications of the
Application Protocol.

For the current specification the only selected transport protocol is TCP (Transmission Control
Protocol, specified in the RFC 793).

8 Transport Protocols and Services - 450 - 8.1 Protocols Organisation


Card Payments Message Usage Guide Version 5.0

8.2 TCP Protocol

8.2.1 Typical Use


Because of its widespread availability, the TCP transport protocol remains the favourite transport
protocol. It can be used as:
1. An end-to-end transport protocol between two entities at each extremity of the Application
Protocol.
Initiating Party Recipient Party
Application Application
Protocol Protocol

TCP TCP

Communication
Infrastructure

Figure 69: Peer-to-peer TCP Transport Protocol


2. An interface to a gateway or a driver to make the conversion of transport protocol with the
other side of the Application Protocol. This case is only a transitory solution allowing the
adaptation a legacy system to the Application Protocol, avoiding the specification of all the
existing communication protocols.
Initiating Party Recipient Party

Application Application
Protocol Protocol
Gateway Gateway
TCP TCP
TCP Trp. Trp. TCP

Local Communication Local


Communication Infrastructure Communication

Figure 70: Gateway TCP Transport Protocol

8.2.2 Message Delimitation


The TCP protocol is a stream protocol which does not offer message delimitation or data-unit
delimiting. It uses the general mechanism of message delimitation provided for all the transport
protocols.

8.2.3 Addressing
A transport address for the TCP protocol is composed of:
1. The IP Address or the DNS Name to resolve of the host on which the application protocol
lives.
2. The TCP Port, to dispatch the connections to the application.

8 Transport Protocols and Services - 451 - 8.2 TCP Protocol


Card Payments Message Usage Guide Version 5.0

8.3 Transport Services

8.3.1 Message Delimitation

8.3.1.1 Definition
Message delimitation provides the recognition of the application data (i.e. application message).

8.3.1.2 Specifications
15
Application messages are prefixed by four bytes containing the length, in network order , of the
application message. This length value does not include the the length of this prefix.
length
CAPE message

Figure 71: Header Length


If the four bytes are equal to zero, it is considered as a zero length application message, and these
four bytes are ignored.

8.3.1.3 Typical Example of Implementation


For sending a message:
 The Application Protocol layer requests to send an application message to the interface of the
transport protocol,
 This interface, or transport adaptation layer, adds the length prefix described above and
passes the new message to the transport protocol.
For the receipt of a message, the interface to the transport protocol:
 Waits for the receipt of four bytes to get the length L of the message to receive, and arms the
timeout TC4 to monitor the receipt of the complete application message.
 Waits for the receipt of L bytes to provide a message to the Application Protocol layer,
 On the receipt of the last data unit of this message, stop the TC4 timer, and deliver to the
application layer, the L bytes, content of message.
Timer management is specified in section Connection and Data Management State Diagrams, which
contains message sending and message receiving management.

8.3.1.4 Notes
Use of message delimitation at the transport level:
 Restricts message delimitation to the transport layer interface avoids partial progressive
decoding of the message mixed with receipt of message fragments,
 Separates decoding of the message from its receipt processing.
 Independence of this service from the data coding used by the application, if the data coding
can provide this functionality (e.g. ASN.1/BER data coding).
Use of the message length to delimit a message has the advantage of being able to send any value in
the application message, but prohibits resynchronisation of message after a data loss.

15
Most significant byte first (i.e.; big endian).

8 Transport Protocols and Services - 452 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

Use of a fixed number of bytes to contain the length of the message facilitates implementation of
message receipt.

8 Transport Protocols and Services - 453 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.2 Connection and Data Transfer Management

8.3.2.1 Connection Services


Application protocols use the transport connection services which are organised in three phases:
 The Connection Establishment, to establish an association between the Initiating Party and
the Recipient Party,
 The Transport of Data Units or Data Transfer, to exchange application messages within an
already established connection, and
 The Connection Release service to release a connection established beforehand.
Initiator Party Recipient Party

Connection
Establishment

Data
Transfer

Connection
Release

Figure 72: Connection Services

These services are usually done by transport primitives’ services through various implementations:
 Connection Request: to send an outgoing request in order to establish a transport connection
(done by the Initiating Party).
 Connection Indication: for the receipt an incoming request from the Initiating Party to establish
a transport connection (done by the Recipient Party).
 Connection Response: to send the positive or negative response to the incoming request for
the transport connection establishment (done by the Recipient Party).
 Connection Confirmation: for the receipt an incoming response from the Recipient Party to the
previous outgoing request for the transport connection establishment (done by the Initiating
Party).
 Data Request: to send an outgoing request containing data to deliver to the other peer of a
transport connection (done by the Initiating Party or the Recipient Party).
 Data Acknowledgment: for the receipt an incoming request informing the sender of a Data
Request that the transport layer has sent the related data (done by the Initiating Party or the
Recipient Party).
 Data Indication: for the receipt an incoming request containing data delivered by the other
peer of a transport connection (done by the Initiating Party or the Recipient Party).
 Disconnection Request: to send an outgoing request in order to release a transport connection
(done by the Initiating Party or the Recipient Party).
 Disconnection Indication: for the receipt an incoming request to release a transport connection
(done by the Initiating Party or the Recipient Party).

8 Transport Protocols and Services - 454 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

Initiating Party Recipient Party


Application Trp Layer Adapt. Trp Layer Adapt. Application
connection
request connect req
connection
indication

connection
connect conf response
connection
confirmation

data reques
t
data
data data
ent indication
acknowledgm

data request
data
data data
indication acknowledg
ment

disconnect
ion disc req
request disconnect
ion
indication

Transport Data Units


Transport Primitives (TPDU) Transport Primitives

Figure 73: Transport Connection Management Service Primitives

8.3.2.2 Data Transfer


The real time or interactive exchanges of the Application Protocol are exclusively dialogues of the type
question/answer, involving the related transport primitives:
 The question is a request message sent by the Initiating Party of the message pair to the
Recipient Party of the message pair.
 The answer is a response message sent by the Recipient Party of the message pair to the
Initiating Party of the message pair.
Initiating Party Recipient Party

service request Message Reques


t

processing of
the service
se
Message Respon
service result

Figure 74: Application Protocol Message Flow


This message sequence is used to request a service to the Recipient Party, the response message is
sent to the Initiating Party with the result of the processing. In some case, the request message
notifies a particular event to the Recipient Party, the response message is then an acknowledgement
sent to the Initiating Party.
A pair of request and response messages is identified unambiguously. If a request message is
repeated with the same identifier, (e.g. in case of error, or if the response message have not been
received), depending on the application protocol specification, it may be refused by the Recipient
Party or generate the same response message.

8 Transport Protocols and Services - 455 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.3 Single Message Pair Exchange

8.3.3.1 Definition
Each pair of application messages is enclosed in a unique transport connection that is established for
that purpose by the Initiating Party.

8.3.3.2 Specifications
The sequence flow of a message pair exchange inside a transport connection contains the steps
presented below.
1. The Initiating Party sends a transport connection request to the Recipient Party. The Initiating
Party arms the timeout TC1 to wait for the transport connection response from the Recipient
Party.
2. The Recipient Party receives the transport connection request, accepts it and sends a
transport connection confirmation. At this time the transport connection is established for the
Recipient Party. The Recipient Party arms the timeout TC2 to wait for the application message
request from the Initiating Party.
3. After receipt of the connection confirmation, the transport connection is established for the
Initiating Party, it sends the application message request.
4. The Recipient Party processes the requested service and sends the result within the
application message response to the Initiating Party. The Recipient Party arms the timeout
TC2 to wait for the receipt of a disconnection request from the Initiating Party after it has
received the application message response.
5. The Initiating Party receives the application message response and sends a transport
disconnection request.
6. The Recipient Party receives the transport disconnection request and sends a transport
disconnection request to the Initiating Party. The transport connection is then considered as
released for the Initiating Party which has not to wait for the response of the Recipient Party.
Initiating Party Recipient Party
Connection reque
1 st
TC1:
Connection Accept connection
response Connection resp 2
TC2:
Message
request
Message request
3

Application
time-out Processing

Message response 4
TC2:
Disconnection
request
Disconnection req
5 uest

uest Accept disconnection


Disconnection req 6

Figure 75: Single Message Pair Exchange Sequence Flow

8 Transport Protocols and Services - 456 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

Initiating Party Recipient Party

1 connection connect req


request connection
TC1: indication Accept connection
Connection 2
response connect conf connection
connection response TC2:
confirmation Message
request

3 data
data data
request (Message Request) indication
data
t Processing
Application
time-out
acknowledgmen

data data 4
data request
(Message Response)
indication
data TC2:
acknowledg Disconnection
ment
request
disconnection disc req
5 disconnection
request
indication
Accept disconnection
disc req disconnection 6
confirmation

Figure 76: Single Message Pair Exchange Transport Primitives Sequence Flow

8.3.3.3 Notes
Each peer of the transport connection has to activate timeout to avoid loss of resources in case of
event not received by one peer. These timeout control the management of the transport connection,
establishment, release, sending and receipt of data.
The application has to manage its own timeout to supervise the processing of the service by the
Recipient Party. This is not the role of the transport service to specify the behaviour of the application
layer, but on the other hand the application layer might send disconnection request for this reason or
others to release the transport connection at any time.
A best practice for the connection release is that the receiver of the last message has the
responsibility to release the connection.
The value of the timeout TC2 has to be large enough to take into account the management of
connections by the Initiating Party. Its purpose is rather to avoid a forgotten transport connection that
remains open forever.

8 Transport Protocols and Services - 457 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.4 Multiple Message Pair Exchange

8.3.4.1 Definition
Multiple Message Pair Exchange in the same connection is the option to keep a transport connection
open (or alive) in order to send the next application message pair on the same transport connection.
It allows the exchange of a sequence of message pairs on the same connection, avoiding the
overhead of the connection establishment.

8.3.4.2 Specifications
Sequence flow of a message pair exchange inside a transport connection contains the steps below.
1. The Initiating Party and the Recipient Party establish the transport connection. The Initiating
Party sends the application message request number 1.
2. When the Initiating Party receives the application message response number 1, it arms the
timeout TC3 to wait for another message request to send from the application layer.
3. The Initiating Party sends the application message request number 2 before the expiration of
the timeout TC3.
4. The Initiating Party receives the application message response number 2 and arms again the
timeout TC3 to wait for the message response from the Recipient Party.
5. In the absence of new application message to send, the TC3 timer timed out. The Requester
sends then the transport disconnection request to release the connection because of
inactivity.
Initiating Party Recipient Party
Connection reque
1 st

Connection resp

Message request
1
Processing request 1
2 Message response
1
TC3:
Inactivity
Message request
3 2
Processing request 2
Arms inactivity TC3 4 Message response
2

no activity
on the connection

TC3 has timed out Disconnection req


5 uest

uest
Disconnection req

Figure 77: Multiple Message Pair Exchange Sequence Flow

8 Transport Protocols and Services - 458 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

Initiating Party Recipient Party

1 connection connect req


request connection
indication

connect conf connection


connection response
confirmation

data
data data
request
(Message Request 1) indication
data
t Processing request 1
acknowledgmen
data data
data request
2 (Message Response 1)
Arms inactivity TC3 indication
data
acknowledgmen
t

3 data data
Desarms inactivity TC3 data
request
(Message Request 2) indication
data
t Processing request 2
acknowledgmen
data data
data request
Arms inactivity TC3 4 (Message Response 2)
indication
data
no activity acknowledgmen
on the connection
t

TC3 has timed out disconnection


5 disc req disconnection
request
indication

disc req disconnection


confirmation

Figure 78: Multiple Message Pair Exchange Transport Primitives Sequence Flow

8 Transport Protocols and Services - 459 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.4.3 Notes
The transport is based upon a connectionless network protocol like IP that does not reserve any
resource on the network except at the of extremities of the transport connection. In this case the
overhead of a connection establishment is the exchange of two packets, and the resource
consumption of an established connection context entry in the protocol stack.
This mechanism has several advantages to manage significant volume of messages:
 To avoid the use of a header carrying application-only information, and provide a better
separation between transport and application layers.
 The simplicity of the message management by the transport service layer and the application
layer, for the Initiating Party and the Recipient Party.
 To be able to verify of the response on both transport layer (the transport connection) and
application layer (application data in the header of the message), with a clear separation
between these two layers.
 The adaptability of the communication resources to the traffic of messages.
 The ability to isolate the processing and resolution of problems in the various message pairs.

8 Transport Protocols and Services - 460 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.5 Addressing

8.3.5.1 Definition
A peer (Recipient and Initiating Parties) is identified by its transport address; it is this address which is
used when connecting to a peer.
The form of the transport address depends on the type of transport protocol being used (e.g. an IP
address or a DNS name of the node together with a TCP port would form a TCP transport address).

Initiating Party Recipient Party


Application Application Protocol Application
Layer Layer
Transport Transport
address address

Transport Service Transport Service


Transport Transport
address address
Transport Protocol
Transport Layer Transport Layer

Figure 79: Transport Address

8.3.5.2 Specifications
The transport address of the Recipient Party is a parameter used at the application level by the
Initiating Party as a destination address to establish a connection.
Application protocol may define assignment of the Recipient Party’s transport address at any level:
globally for the whole application protocol, per class of message, or per service.

8 Transport Protocols and Services - 461 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.6 Flow Control

8.3.6.1 Definition
Flow control is the service which allows the control of the flow of data between the application layer
and the transport layer, or between the Initiating Party and the Recipient Party.

8.3.6.2 Specifications
Flow control of the transport protocol may be not available in the transport service. The Application
and Transport layers have to put in place a data acknowledgment mechanism to avoid resource
saturation of a layer in the event that a large volume of data is to be sent to the other peer.
Application protocols have to design a flow control between the Initiating Party and the Recipient
Party. This flow control is completely transparent to the transport service layer.
The transport service used is the Data Acknowledgment primitive, sent to the application when the
transport service layer is able to take into account new data.

8 Transport Protocols and Services - 462 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.7 Error Cases


This section defines errors detected by the transport protocol and transmitted to the application layer.
The responsibility and the choice of error resolution are left to the application layer, unless the
transport service layer needs to perform some action to continue to work.
The Application Layer Protocols must define the actions to be taken in the event of these errors as the
actions will vary according to the message exchange (eg actions in the event of Authorisation failure
are different to those to be taken when performing a Completion exchange).
The errors are generic; the transport layer is not always able to report a specific reason for the errors.

8.3.7.1 Unable to Establish a Transport Connection (ERTR01)

Definition
The transport layer is unable to establish the transport connection that the application layer has
requested to open, because:
 The lower protocol layer has notified an “out of service” communication state as permanent or
in response to the attempt to open the connection.
 The TC1 timer has expired, and the connection in progress is considered as broken (the
connection establishment as a failure).
 The Recipient Party has denied the connection request.
 The transport layer has reached the maximum number of concurrent connections it can
manage.

Transport Service Behaviour


The transport service layer considers the establishment of the transport connection as a failure, and
notifies the result to the application layer.

8.3.7.2 Transport Connection Broken (ERTR02)

Definition
The transport layer realises that an open connection is broken. Several reasons may cause this error:
 The transport layer receives an unexpected disconnection request.
 An error occurred at a lower level while the transport layer waits for the end of a message
after the receipt of the length prefix and incomplete data units.
 The lower level notifies the transport layer that a defect occurs (e.g. on the physical interface),
and the transport connection is broken.
 The remote peer has not respected the state diagram of the connection management. The
Initiating Party has sent data after sending the message request but before the Recipient
Party has finished sending the message response. The Recipient Party sends data before the
Initiating Party has finished sending the message request.
 The remote peer has released the transport connection.
 A connection deemed to be inactive when TC2 expires. The connection seems to be forgotten
by the Initiating Party, and the Recipient Party closes the transport connection at the
expiration of the TC2.

Transport Service Behaviour


The transport service layer notifies the closing of the transport connection to the application layer.
Partial messages are deleted and not sent to the application layer.

8 Transport Protocols and Services - 463 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.7.3 Unable to Send a Message (ERTR03)

Definition
The transport layer cannot send an application message. Several reasons may cause this error:
 An error occurred at a lower level when the transport layer sends an application message at
the request of the application layer.
 The connection was broken just before the sending of the message, and the application layer
did not receive the disconnection notification before the request to the transport layer to send
a message.
 The remote peer is not ready to receive data. The Recipient Party has not yet received the
message request. The Initiating Party has not received the connection confirmation or has not
yet received the message response.

Transport Service Behaviour


The transport service layer notifies the error to the application layer.
Note that the transport service layer is not always able to report error to the application layer. In
particular when a connection is broken, the transport service has removed the connection context, and
might have some difficulty to identify the context of the error.

8.3.7.4 Message Too Big (ERTR04)

Definition
The transport layer cannot receive an application message, because the prefix contains a message
length above the limit of the transport layer memory.

Transport Service Behaviour


The transport service layer has an internal parameter containing the size limit of a message, or a
global limit for the set of message buffers. When the limit is reached, the transport layer:
 Releases the connection on which the message has to be received.
 Notifies the error to the application layer.
As the transport layer cannot receive the message, it has to release the transport connection. Most of
the time error of this class happens when there is a desynchronisation of message delimitation
between the two peers.

8 Transport Protocols and Services - 464 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.7.5 Late Arrival (ERTR05)

Definition
The transport service layer receives a data unit for the application after a timeout has expired and
before the request for a disconnection.
The application layer must also handle this error.
The drawing below shows such error example, when the application timeout on the message
response expires.
Initiating Party Recipient Party

Arms application data


timer data data
request
(Message Request) indication
-
data acknow
ledgement Processing request 1

data data
di se) request
Application timer
re scon at a (Message Respon data acknow
expires q ne d ind ledgement
-
cti
on
disc req
disconnectio
n
indication
n
disc req disconnectio
confirmation

Figure 80: Late Arrival Error Example

Transport Service Behaviour


The transport service layer ignores the message or data units .
The transport layer may have removed the connection context, and may not be able to identify the
context of the error. In addition, the application layer will have already started the error handling and
cannot process the late response.
The implementation of the Transport Protocol has to ensure that any data unit is not assigned to the
wrong connection.

8.3.7.6 Max Number of Connections (ERTR06)

Definition
If, on the arrival of an incoming connection request,the transport service layer cannot open a new
transport connection this error will be returned to the Application Layer. This could occur, for example,
when the Application or Transport Layer has reached the maximum number of concurrent transport
connections it can handle.

Transport Service Behaviour


The behaviour is implementation dependant. For instance, the transport service layer may have an
internal parameter containing the limit number of open connections. When the limit is reached, the
transport layer must :
 decline the incoming connection request,
 notify the error to the application layer.

8 Transport Protocols and Services - 465 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.7.7 Incomplete Application Message (ERTR07)

Definition
After the receipt of an application message header, the transport layer arms the timeout TC4 to
monitor the receipt of the complete application message.
This error will be triggered if the TC4 timer expires before the end of the application message is
received, and might happen:
 When a serious error occurs on a lower communication level or on the communication
infrastructure between the 2 peers.
 The remote transport or application layer encounters a serious error, or is out of order.

Transport Service Behaviour


The transport service layer must carry out the following actions:
1. discard the incomplete application message,
2. close the transport connection to avoid further problems of data synchronisation (the next data
unit may be the start of the next application message, or part of the previous application
message),
3. notify the error to the application layer.

8.3.7.8 Other Errors


All other errors are detected or resolved at the application layer, as:
 Non-understandable message: all decoding of message are made by the application layer, so
this error is detected and resolved at the application layer.
 Busy situation: when the application layer has not enough resources to process all the
messages received, it can answer that it is busy at the application level to the other peer.

8 Transport Protocols and Services - 466 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.8 Transport Service Parameters

This section summarises the set of configuration parameters required by the transport service
management. These parameters are configurable and may be downloaded using the EPAS TMS
protocol or another proprietary means. These values depends first upon the communication
infrastructure.

Name TC1
Definition Transport connection establishment timer
Owner Initiating Party of a transport connection establishment
Usage After the sending of a transport connection request, the Initiating Party arms the TC1 timer to wait for
the response from the Recipient Party. TC1 is reset on the transport connection confirmation being
received..
Specification 8.3.3 Single Message Pair Exchange

Name TC2
Definition Transport connection idle timer
Owner Recipient Party of a transport connection
Usage Keeping open transport connections which are not being used by the Initiating Party.
After the receipt of a message request or sending of a message response, the Recipient Party arms
the TC2 timer to wait for the use of this transport connection. TC2 must be disarmed when a new
message is sent across this connection.
This timer has to be long enough to not interfere with the TC3 timer
Specification 8.3.3 Single Message Pair Exchange

Name TC3
Definition Transport connection activity timer
Owner Initiating Party on a transport connection
Usage This timer is armed by the Initiating Party before the release of a transport connection, to wait for a
new message request to send. It is armed when a response message is received and disarmed
when a new request is sent. Expiry of the timer triggers a request to close the idle connection.
It avoids the management of permanent transport connections between remote peers, the
multiplexing of message exchanges, and the re-connection for every message exchange.
Specification 0
Multiple Message Pair Exchange

Name TC4
Definition Application message receipt timer
Owner Initiating Party or Recipient Party on a transport connection
Usage This timer is armed by the Initiating Party or Recipient Party at the receipt of the application
message prefix to supervise the receipt of the complete application message. It is armed at the
receipt of a message header and disarmed when the message is complete.
It allows the detection of an incomplete application message.
Specification 8.3.7.7 Incomplete Application Message

8 Transport Protocols and Services - 467 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

Name Recipient Party Address


Definition Transport address of the Recipient Party
Owner Initiating Party of a transport connection
Usage This (or these) transport address is used by the Initiating Party to establish a transport connection
with the Recipient Party.
Specification 8.3.5 Addressing

8 Transport Protocols and Services - 468 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.9 Connection and Data Management State Diagrams


This section presents the state diagrams of the transport connection management on both Initiating
Party and Recipient Party side.
These state diagrams are valid for both Single and Multiple messages pair exchanges.
The transitions between states have the syntax: Event [Condition to Activate]/Action

8.3.9.1 Recipient Party Diagram

States
The Recipient Party may have the following states:
 Await Request: The Recipient Party has received a connection request, and sent the
connection confirmation. The connection is established. No message pair exchange is in
progress. The Recipient Party waits for the beginning of a message request, or a disconnect
request.
 Receiving: The Recipient Party has received the beginning of a message request, which is not
complete yet.
 Responding: The Recipient Party has received a complete message request. The transport
adaptation layer waits for application layer to send the message response.

Events
The Recipient Party may receive the following events:
 CON_IND: The Recipient Party receives a connection indication from the network.
 DATA_IND: The Recipient Party receives data.
 DATA_REQ: The Recipient Party application layer wants to send data.
 TC2, TC4: The timer TC2 (respectively TC4) has expired.
 Error: There is an error situation, such as receiving a disconnection request from the network
or the application layer, a message that is too big, or other errors.

Diagram
CON_IND / DATA_IND [complete msg] /
Await
CON_RES, start TC2 DATA_IND, restart TC2 Responding
Request DATA_REQ /
DATA_REQ, restart TC2
TC2, DATA_IND DATA_IND,
Error / [uncomplete msg] TC2,
DISC_REQ / stop TC2, DATA_IND Error /
start TC4 [uncomplete msg] DATA_IND DISC_REQ
[complete msg]
/ DATA_IND,
start TC2
Receiving

TC4,
Error /
DISC_REQ

Figure 81: Recipient Party Connection Management State Diagram

8 Transport Protocols and Services - 469 - 8.3 Transport Services


Card Payments Message Usage Guide Version 5.0

8.3.9.2 Initiating Party Diagram

States
The Initiating Party may have the following states:
 Connecting: The Initiating Party has sent a connection request, and waits the positive or
negative answer to that request.
 Connected: The Initiating Party has received a connection confirmation, positive response,
and the transport connection is established. No message pair exchange is in progress. The
transport adaptation layer waits for application layer to send a message request.
 Await Response: The Initiating Party has sent the message request, and has not received any
part of the response message.
 Receiving: The Initiating Party has sent the message request, and has received the beginning
of the response message which is not complete yet.

Events
The Initiating Party may receive the following events:
 CON_REQ: The Initiating Party application layer wants to send a connection request.
 CON_CNF: The Initiating Party receives a connection confirmation.
 DATA_REQ: The Initiating Party application layer wants to send data.
 DATA_IND: The Initiating Party receives data.
 TC1, TC4: The timer TC1 (resp. TC4) has expired.
 Error: There is an error situation, such as receiving a disconnection request from the network
or the application layer, a message that is too big, or other errors.

Diagram

CON_REQ / start TC1

DATA_REQ /
stop TC3, DATA_REQ
CON_CNF / Await
Connecting Connected
stop TC1 DATA_IND [complete msg, mult msg Response
pair] / DATA_IND, start TC3
TC1, DATA_IND, DATA_IND
TC3, Error / Error /
Error / [uncomplete msg] DISC_REQ
DISC_REQ DISC_REQ DATA_IND / start TC4
DATA_IND [uncomplete msg]
[complete msg,
mult msg pair]
/ stop TC4
DATA_IND Receiving
start TC3

DATA_IND
[complete msg, TC4,
single msg pair] Error /
/ DISC_REQ, DISC_REQ
DATA_IND

Figure 82: Initiating Party Connection Management State Diagram

8 Transport Protocols and Services - 470 - 8.3 Transport Services

You might also like