apdu

I have an ACR122U NFC reader/writer connected to my Windows machine with ACR122 driver installed. I try to use javax.smartcardio API to send an SELECT (by AID) ADPU to my Android device (which should be in HCE mode). This is my code: TerminalFactory factory = TerminalFactory.getDefault(); List<CardTerminal> terminals = factory.terminals().list(); CardTerminal terminal = terminals.get(0); System.out.println(terminal.getName()); Card card = terminal.connect("*"); CardChannel channel = card.getBasicChannel(); execute(channel, new byte[] { (byte) 0xFF, 0x00, 0x51, (byte) 195, 0x00}, card); execute

Preface: I have a dual interface smart card reader that has some extended capabilities (other than sending APDU commands to card and receiving APDU responses). For example in its document it is mentioned that you can get firmware version of your reader using following command: GET_FIRMWARE_VERSION: FF 69 44 42 05 68 92 00 05 00 In its tool, there is a button for this function and it works fine: I even sniffed USB port to see what exactly exchanged in the connection between my PC and my reader for this function: Command: Response: Problem: I want to get my reader version (and maybe send other

I understand that this is a "discussion" topic that has no definite answer, but I would really like some feedback on what to expect when developing NFC APPs for Android, in particular using IsoDep to communicate with DESFire cards using APDU frames. Can I expect that the same APDU frames sent to a particular DESFire card responds identically across Android Devices and versions? What Android versions and devices should I test on as a minimum to be reasonably well covered? Is it common with bugs or regressions in the Android drivers or can I expect that these are rooted out a long time ago? What

I need to read account number from Maestro/Mastercard with smart card reader. I am using Java 1.6 and its javax.smartcardio package. I need to send APDU command which will ask EMV application stored on card's chip for PAN number. Problem is, I cannot find regular byte array to construct APDU command which will return needed data anywhere... You shouldn't need to wrap the APDU further. The API layer should take care of that. It looks like the 0x6D00 response just means that the application did not support the INS. Just troubleshooting now, but you did start out by selecting the MasterCard