emv

问题 I'm working on a C platform and I want to read the AFL of a card. If the previous command, select of the AID, don't give me a PDOL tag, it's ok: I can read the AFL without issues. But I need to write a method that can generate a GET PROCESSING OPTION regardless the PDOL. So the questions are: How can I write an universal method that work despite the PDOL? Have I to map every single possible TAG? How can I format the GPO command with the correct data? Look the following example: SELECT AID

问题 If card support SDA + DDA , At what condition POS will not perform SDA/DDA operation?? Is ODA performed by POS decided on basis of tag 82 only? or other tags/values check by the terminal to decide - ODA need to perform or not... For me - DDA check card is genuine or not and no data altered inside it so it must be performed by any terminal. Also I believe CA pubic key require to decrypt the certificate and here RID + Tag 8F used to get the correct key from key repository. Is it correct? 回答1:

问题 I'm working with a mobile payment terminal and a testing tool for testing EMV transactions. Part of the setup of the terminal involves loading a number of CAP keys into the terminal for use with different types of cards. I'm curious, how does the terminal go about selecting an appropriate CAP key? Is there any information I could obtain from the APDU logs that would indicate to me which CAP key will be used? The specific problem I'm running into is I have a demo project that is processing

问题 I am working on an NFC-based payment device. I am using MIFARE DESFire EV1 chip. My question is: How to enable a full EMV compliant payment transaction with this chip hardware? I found this Visa Ring which does payment transactions. It uses NFC Ring® design of McLear & Co with NTAG IC. 回答1: How to enable a EMV payment transaction with MIFARE DESFire EV1? Simple answer: You can't. MIFARE DESFire is a proprieatry contactless smartcard system that implements a filesystem for data storage and an

问题 I have a terminal that has its own API to stablish and send commands between chip and terminal, there is a function that transmits the APDU command and returns the answer in a byte array. For example, if a want to read the tag 5A (Application PAN), I send the following command: byte[] byteArrayAPDU = new byte[]{(byte)0x00, (byte)0xCA, (byte)0x00, (byte)0x5A}; int nResult = SmartCardInterface.transmit(nCardHandle, byteArrayAPDU, byteArrayResponse); The variable byteArrayResponse gets the

问题 i have some issues with reading the IBAN number from the german CashCards (also known as Geldkarte). I can communicate with my card, and i get some informations from it. but i don`t know which commandApdu i must send to the card, to get the IBAN number... The application runs on Java 7 and i use the java.smartcardio api Protocoll is T=1 my commandApdu to get the date looks like this: byte[] commandBytes = new byte[]{0x00, (byte)0xa4, 0x04, 0x00, 0x07, (byte)0xa0, 0x00, 0x00, 0x00,0x04, 0x30,

问题 I have succesfully retrieved the CVM List from EMV card. 0000 0000 0000 0000 4103 4203 1E03 1F02 From the EMV specification book 3, the first 4 bytes and second 4 bytes are amount and rest is CV rules. Making these the CV Rule 4103 4203 1E03 1F02 The book also shows how to parse the CV rules, as shown below: I am assuming that I need to convert the first two bytes in a CV rule to binary and match with the table above? But why does the table above have empty cells? Also can someone explain in

问题 I am trying to generate AC manually, I have a tool to generate AC but I want to generate it by my own to understand the algorithm for the same. My calculation is fine for Discover card but it is failing for MasterCard. As per my understanding, data used to generate AC is depend on Tag 8C - CDOL1 which we provide to card with Gen AC command + AIP + ATC. AIP and ATC - accessed internally by ICC. Data used to generate AC is:- data part of Gen AC command + value of tag 82 + value of tag 9f36 + 80

问题 I am trying to generate AC manually, I have a tool to generate AC but I want to generate it by my own to understand the algorithm for the same. My calculation is fine for Discover card but it is failing for MasterCard. As per my understanding, data used to generate AC is depend on Tag 8C - CDOL1 which we provide to card with Gen AC command + AIP + ATC. AIP and ATC - accessed internally by ICC. Data used to generate AC is:- data part of Gen AC command + value of tag 82 + value of tag 9f36 + 80

问题 I am trying to build a correctly formatted GET PROCESSING OPTIONS command to be sent to a contactless EMV card. This post has been very helpful but I just need to know a little more detail. When parsing the PDOL, is it safe to assume that each tag is 2 bytes in length, followed by the size of the data expected in return? For example, the PDOL 9F66049F02069F37049F1A02 is broken into 9F66 04 , 9F02 06 , etc. each with 2 byte tags and 1 byte for the expected length of the data value. Is it safe