1. Replay Mode

To enable the Replay Mode is activated in FMK 3.5, from the menu ‘TMS’->’Administrative…’ in ACE-Client, ensure the ‘Replay (Yes/No)’ Option is Enabled

NOTE: This feature needs to be enabled through the Compilation Options _CAD_INTERFACE_SUPPORT_ and _REPLAY_MODE_SUPPORT_

1.1. Location of Card.txt

The Replay Mode requires the file ‘Card.txt’ to be present in the execution folder.

1.1.1. Windows Command Line

Put the Card.txt file in the same folder than the executable, as for example:

/OpenKizis/WIN32_Debug_Static/Card.txt

1.1.2. Eclipse Debug Session

When starting a debug session from Eclipse then Card.txt must be located under OpenKizis folder as for example:

/OpenKizis/Card.txt

NOTE: It is possible to change the ‘Working Directory’ from the ‘Arguments’ Tab in the Debug Configuration Dialog

1.2. Format

The format of Card.txt is (see replay.7z for sample Card.txt files):

Open

Line 1: Number of Card Detection (i.e. Reset)

Line 2: Simulated Technology Detected (04: Contactless, 40: Contact) [' ' and a 4 byte Unpredictable Number]

Line 3: APDU 1 Command (not used, displayed as expected APDU Command in Console Logs)

Line 4: APDU 1 Response

Line 5: APDU 2 Command

Line 6: APDU 2 Response

…

IMPORTANT: Card.txt shall always end with an empty line

1.2.1. Card Mute Simulation

Leaving a Blank Line for an APDU Response simulates a Card Mute

1.2.2. setting the Unpredictable Number ‘9F37’

Line 2 now offers an Optional Feature where it is possible to force the Unpredictable Number (tag ‘9F37’) for each Card Detection

The can be achieved by adding a space character ' ' after the Card Technology Code followed by the value of the Unpredictable Number (4 bytes)

For Example:
Line 2 containing ‘04 12345678’ means: ‘04’ = Contactless Card - ‘12345678’ = Value of Unpredictable Number ‘9F37’
The Section https://teamamadis.atlassian.net/wiki/spaces/AGF/pages/1178304556/Replay+Mode+in+FWK+3+5#1.3.3.-Two-Presentments-Scenario-(See-Phone-or-Double-Tap) shows how to set the Unpredictable Numbers ‘9F37’ for multiple Card Detections

1.3. Replay Scenarios

the Replay Mode allows to reproduce different scenarios such as Torn Transaction, Two Presentments,… by specifying the Number of Card Detection (first line)

The Technology must be specified after each Card Detection, the same Card.txt can simulate detection of multiple technologies in the same Script

1.3.1. Normal Replay Scenario

Most scenarios involve a single Card Detection

For example the following APDU Exchanges:

Will require the following Card.txt:

1.3.2. Card Mute Replay Scenario (Torn Transaction)

Some scenario imply a Card is Mute, i.e. Card not sending back a Response (RSP, SW1/SW2), this situation occurs during Torn Transactions Testing
NOTE: The [Card Mute] is simulated with an <Empty Line>

For example, the following APDU Exchanges (with a CMD without RSP and/or SW1/SW2):

Will require the following Card.txt:

NOTE: Absence of APDU Response in the first GenAC Command is simulating a ‘Card Mute’ situation

1.3.3. Two Presentments Scenario (See Phone or Double Tap)

Some scenarios require a Double Tap (TRY AGAIN Outcome with Start-B), this occurs when a SEE PHONE is requested or execution of Issuer Scripts following an ONLINE REQUEST Outcome

For example, the following APDU Exchanges (PURE with 2nd Tap after 1st GenAC):

Will require the following Card.txt:

NOTE: in this example, the Unpredictable Number used in the Generate AC of the 1st Transaction (Line 15) is ‘9F37’ = ‘A69314EC’ therefore the first Card Detection in Line 2 specifies the Contactless Card Technology ‘04’ followed by the value of the Unpredictable Number: 04-A69314EC

The Unpredictable Number used in the Generate AC of the 2nd Transaction (Line 26) is ‘9F37’ = ‘CD12AA59’ therefore the second Card Detection in Line 17 specifies the Contactless Card Technology ‘04’ followed by the new value of Unpredictable Number: ‘04 CD12AA59’

2. Python Scripts

Some Python Scripts were made for generating Card.txt from Log Files

The Python Scripts may require some modifications due to inconsistencies with Log Files generated from different Kernels and different Tool Versions

For exemple, PayPass Logs generated by EVAL are slightly different from ExpressPay Logs

Also new Versions of EVAL may generate slightly different Logs from older Versions even for the same Kernel

IMPORTANT: Some Card.txt still requires manual modifications after their generation for Card Mute and Double Tap Scenarios (see Card Mute Replay Scenario and Two Presentments Scenario )

2.1. Sample EVAL Log Python Scripts

Sample Python Script for generating Card.txt file from EVAL Logs

Example for PURE:

Open

2.2. Sample ICC Solution Log Python Scripts

Exemple for Interac:

Open