Mastercard Test Environment Interface (TEI) module drives ACE-Client automatically:
It sends PROCESSING and ENTRY POINT configurations
Transactions are started on acceptance device
Signals are updated during the transactions
Mastercard Test Environment Interface (TEI) module does not change:
the TERMINAL configuration
the CAKeys or Revocated keys from CAKEYS, EFL, and CRL
Activation
STEP #1 Intialization on Device
Before starting a TEI session, Mastercard CAKeys and the TERMINAL configuration must be sent manually:
CaKeys file is C:\Amadis\ACE-Client\Data\MASTERCARD\CAKeys CL MASTERCARD
TERMINAL configuration must be configured for Mastercard Contactless
The “Prepare” button is sending the same CAKeys and current TERMINAL configuration.
During the execution of automated tests, it is better to not manipulate ACE-Client. Between the tests, ACE-Client is fully available. Please use the File > Export mechanism to send the information about the last transaction for support request.
The Revocated keys C:\Amadis\ACE-Client\Data\MASTERCARD\REVOK CL MASTERCARD are needed for some of the tests and must be sent manually:
3M25-7340(A_01_RID1-IssCert-revoc)
3M25-7340(A_02_RID2-IssCert-revoc)
3M25-7340(B_01_RID1-IssCert-revoc)
3M25-7340(B_02_RID2-IssCert-revoc)
3M25-7340(C_01_RID1-IssCert-revoc)
3M25-7340(C_02_RID2-IssCert-revoc)
STEP #2: Check DLL Presence
The TEI dll for ACE-Client is not included in the setup. If you have libMasterCardAutomation.dll please copy it into C:\Amadis\ACE-Client\plugins.
Once the dll is in plugins directory, a new section appears at the bottom of Setup page with the title Mastercard Automation.
STEP #3: ACE Client Settings
Field | Comment | Value |
---|---|---|
Port | Listening Port | The value should match the port from Test Environment Interface Tool (10172 by default) |
Automatic Start | Activate/Deactivate the TEI server start when ACE-Client is started | 0 or 1 |
Configuration Version | Select the version of TEI library |
|
Select Directory | Local directory to use locally defined configurations. Should be left empty. |
As for example ACE Client side:
STEP #4: Start Automation On Ace Client:
Then click on Automatic Start for starting the TEI as for example:
STEP #5 Check the TEI parameters
Once the TEI Server is started in ACE-Client, TEI tool can connect to ACE-Client.
EVAL side using Tools->Start TEI:
When clicking on Start TEI, this menu is displayed in EVAL tool:
Note that:
ACT is supported
CLEAN is supported
TEST_INFO is supported
STOP_ACK is supported
TEST_DATA is NOT supported
Config is supported
PCD Bypass is NOT supported
By clicking on Start TEI, this menu appears:
TEI tool should connect to ACE-Client (driving the Reader) in the Reader connection side, so we use a localhost or 127.0.0.1 address with the 10172 communication port
On ACE side nothing has to be changed. Follow this:
Test the connection with this button:
FAQ
Is TEI module started ?
If the button Start/Stop at the right of button 'Update Port' displays 'Stop', TEI module is up. If it displays 'Start', the module is down.
APDU Received at unexpected moment:
If after a while EVAL stops and you see this:
Eval probe may be disconnected:
And even if you reconnect the probe, the test is still failing, then you have 2 options:
close EVAL and restart it
Stop TEI tool first, reconnect Probe, then restart TEI tool (EVAL->Tools->Start TEI)
How to change the listening port in ACE Client
change the value in the field
click on Update Port button
click on Stop button
click on Start button (same as Stop)
FIME’s EVAL and TEI
Amadis does not provide EVAL or Test Environment Interface tool. If you have any questions on them, please contact the provider of theses tools.