thanks a lot, unfortunately this is the only info I have been able to acquire about it. But I think assuming I can clone the uid and they aren’t doing anyhting else it should work?
While true you can’t clone the whole card, the question is, do you need the whole javacard part of it or just the mifare emulation part of it? I think you are seeing that just because TagInfo is asking for it and the javacard is simply choosing to send what TagInfo is asking for by emulating the mifare classic. I could see the possibility (No idea if its true) of being able to clone mifare classic data to an xM1. Could totally be off but worth a try.
Pretty sure I will need the Java card part also, but like you say worth a try…
UPDATE
Tried and followed through this Proxmark guide , the proxmark doesn’t see it as a NXP MIFARE CLASSIC 1k
unfortunately, it is seen as TYPE : JC0P31 or JC0P41 v2.3.1
Assuming the JC is Java Card
I could change the UID of my test card to match, but don’t think that will do anything.
Thanks for the info @turbo2ltr and @bepiswriter
Thanks for that, and yes the read info does look very much like a Flex One.
It’s actually a prepay credit card, I got it as test.
It’s a “sticker card” with no expiry, so I was hoping it could get cloned or converted into an implant
Just to clarify what others have said - the answer is yes and no. What you have there is a secure element (smart card chip) that is emulating a Mifare classic 1k. What this means is that the chip is responding to iso14443a selection and scan commands as a classic 1k but also at the same time all the AIDs (applets) on the chip are accessible via apdu commands. So, you could easily clone the Mifare Classic 1k emulated data to an xM1 for example, but chances are really really high that this emulation is not what’s being used by whatever application you use this card with. It’s probably accessing an applet on the card and ignoring the Mifare Classic 1k emulation all together.
So in this case it absolutely will do nothing for you to clone the mifare emulated card to another chip… payment applications are not tied to this functionality what so ever.