I am currently implementing an EMV transaction and have encountered an issue where my Second Generate AC command is returning a "6A86" response code when called immediately after a successful First Generate AC command.
My First Generate AC command returns a successful response of "77299F2701809F360201699F2608CA3559C737FD8E6A9F10120110A00003220000000000000000142800FF9000". Here's the APDU command for the First Generate AC command:
"80AE800042000000000002000000000000056604800008000566230425001CB0FCE92200000000000000000000410300100545000000000000000000000000000000000000000000"
Following the successful response from the First Generate AC command, I immediately send the Second Generate AC command, which returns a "6A86" response code. Here's the APDU command for the Second Generate AC command:
"80AE4001106D0000000000000000000000000000FF303004800008001CB0FCE9000000000000000000"
I have tried checking for possible errors in the data elements used in the Second Generate AC command, but I cannot seem to identify any issues. I am wondering what could be causing the "6A86" response code and how I can resolve this issue to continue with the EMV transaction.
Any suggestions or insights would be greatly appreciated. Thank you in advance.