Terminal Profile used to answer PDOL
Closed this issue · 2 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Access a card with PDOL
2. EMVTerminalProfile does not contains the expected settings
3. GET PROCESSING OPTIONS command fails
What is the expected output? What do you see instead?
It would be great to set the terminal profile using ressource files (as AID or
ATR).
Would need to change the static declarations of EMVTerminalProfile.
What version of the product are you using? On what operating system?
Last one
Please provide any additional information below.
Original issue reported on code.google.com by tho...@souvignet.net on 15 Apr 2012 at 4:53
GoogleCodeExporter commented
I'll handle this one.
Original comment by sasc...@gmail.com on 11 May 2012 at 5:42
- Changed state: Accepted
GoogleCodeExporter commented
Terminal resident data can now be specified in an external properties file. The
values is this file overrides any default values specified in the code.
-Dterminal.properties=[path.to.properties.file]
The format of the file is:
tagAndLengthInHex=Value
Eg:
9f1a=0826
The key should be lower case hex without spaces
Original comment by sasc...@gmail.com on 11 May 2012 at 5:49
- Changed state: Fixed
- Added labels: Type-Enhancement
- Removed labels: Type-Defect