AMEX has an official ICS word document. That document needs to be filled according to the terminal specifications and needs. Should you use EVAL as the test tool to qualify your system, they are little discrepancies between AMEX’S ICS and EVAL ICS form.

Here are the steps needed to fill the ICS and run the test cases for different profiles under EVAL:

1st Step:

AMEX Official winword document needs to filled according to the terminal`s specifications. The ICS configuration is strictly dependent on the kernel functionality and it may differ from customer to customer according to purchased kernel and device capabilities.

2nd Step:

After the ICS configuration is ready the winword document needs to be imported into the EVAL tool.

Open

After importing the ICS winword document the imported ICS flags should be checked. The word document may fail to fill some configurations:

Open

Since the configuration is different for each terminal the attached image is an example.

Each configuration flag has 2 columns: 1) Value 2) Configuration

Value: It can be assigned value of Y or N. The value used here is the default value of the terminal.

Configuration: It can be assigned value of Y or N. It states whether that option of the terminal can be toggled.

After the import is completed “Inconsistency Check” needs to be done.

The inconsistency check finds the conflicts in the ICS file. If there is any inconsistency in any of the profiles it needs to be fixed before starting the tests.

After the checks are completed save a copy of the ICS. That will be useful when the EVAL tool is restarted. When a .tre file is already available there will be no need to import the winword document again.

Last operation is to click on Start Tests Selection. This will generate the tests list per profile for all profiles.

3rd Step:

At that point configuration EVAL tool is complete.

EVAL tool has 2 libraries for AMEX kernel testing. One is for EXPRESSPAY and one is for COMMON library.

We suggest you save different test result database for each library. The naming convention we use is:

CustomerNameDeviceNameDateAmex4_0LibraryName.mdb

Keeping these databases are very useful since we want to trace the tests` results.

4th Step:

Now the tests need to be run for different profiles.

4.1: Then for each configuration profiles using the Switch Profile button:

4.2. An EVAL popup appears indicating what are the configuration or settings to apply to the reader, as for example:

Then for each EVAL configuration part of the current Profile:

4.3.a Check the Use Default (Overload tags value with …)

4.3.b Enter the value for tag 9F35, 9F33 …

4.3.b.1 Overload tag 9F33 in ENTRY POINT for these options:

(leave Byte 2, bit 8 to 0, set No CVM required option to 1 Byte 2 bit 4)

Other interface: byte 1, bit 6 ICC with Contact, bit 7 for magnetic Strip

Online Pin: Byte 2 bit 7

Signature: Byte 2 bit 6

SDA: Byte 2 bit 8

DDA: Byte 2, bit 7

CDA: Byte 2, bit 4

 Note: For profiles requesting no explicit values for SDA and CDA, set these 2 values to 1.

4.3.b.2 Overload tag 9F35 in ENTRYPOINT for these values (Offline Only/Online Only):

Merchant Controlled:

21 – Attended, Online only

22 – Attended, Online with offline capability

23 – Attended, Offline only

24 – Unattended, Online only

25 – Unattended, Online with offline capability

26 – Unattended, Offline only

4.3.c in ACE Client in the CONFIGURATION/ENTRYPOINT once you have loaded the ACE Server Configuration:

4.3.c.1: Use tag DF1B in ENTRY POINT for these options:

Mobile CVM: Byte 5, bit 3

Terminal Exempt Of No CVM Checks: No CVM Check exempt: Byte 5, bit 2

Delay Authorization: Byte 2, bit 2

Transit Terminal: Byte 5, bit 1

Only EMV Mode: Byte 6, bit 7

4.3.c.2: Use tag DF30 in ENTRY POINT for these options:

Zero Amount Checking Flag: Byte 1, bit 7

Status Check: Byte 1, bit 8

4.3.c.3: Use tag 9F40 in ENTRY POINT for these options:

Goods: Byte 1, bit 7

Services: Byte 1, bit 6

5th Step:

Send the ENTRY POINT configuration to the device

5.1: Execute the tests for a specific configuration.

5.2: Check if another configuration is expected in this Profile. If there is one, change the configuration and execute the test.

• If end of all configs or per config, change the library to make the profile tests for both library.

• If there is not any test left in that config change go back to step 4.1