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:

...

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):

...

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

...

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

...

1
04
00A404000E325041592E5359532E444446303100
6F3D840E325041592E5359532E4444463031A52BBF0C28610C4F07A0000000041010870101610C4F07A0000000043060870103610A4F05B0123456788701099000
00A4040007A000000004101000
6F358407A0000000041010A52A870101500A4D6173746572436172645F2D06656E646566729F1101019F380B9F02069F33039C019F03069000
80A800001283100000000017500000080000000000025000
770A820200809404100101009000
00B2011400
70485F24034912315A0854133390000015138C0E95059F02069F34039F33039F37048E0A000000000000000000009F0D0500000000009F0E0500000000009F0F0500000000009F4A01829000
80AE40001580000000010000000017503F0000006000E1F29BE500
77299F2701809F360200029F2608AC123456789ABCDE9F10120110000000020000DAC000000000000000009000

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>

...

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

...

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

...

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

...

2.2. Sample ICC Solution Log Python Scripts

Exemple for Interac:

...