Showing results for 
Search instead for 
Did you mean: 

Getting E00061 - How do I format device information for encrypted mobile card reader track data?

Hello all,


How do I format the <DeviceInfo> element within an <EncryptedTrackData> element?

I'm trying to integrate an encrypted card reader from ID Tech with an iPhone application using AIM. I'm using the information found in


In appendix B it instructs to add an <EncryptedTrackData> element to the <payment> element, and shows an example. I have integrated the example into my code, and I'm getting the following error :


E00061 Device information is not formatted correctly(1).


The device information element <DeviceInfo> in the example contains the following, Hex encoded:




At best that looks incomplete. I've tried many different variations on that format and can't get past it. Do I need to have a specific FID? If I take the FID portion out, it complains of a missing FID value, so I think I'm on the right track, but cannot find any documentation on how to format the DeviceInfo section.


Here is my request:


<?xml version="1.0" encoding="utf-8"?>
<createTransactionRequest xmlns:xsi="" xmlns:xsd="" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">


And here's the response I'm getting:


<?xml version="1.0" encoding="utf-8"?>
<createTransactionResponse xmlns:xsi="" xmlns:xsd="" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
      <text>Device information is not formatted correctly(1).</text>

Thanks for your help!




My apologies, I realize we're talking about different things. Please disregard my previous reply.

Let's back up a bit. Which make and model of card reader are you using? And where did you acquire it?

With that information I can provide a better answer.

"Move fast and break things," out. "Move carefully and fix what you break," in.

It's an IDTECH SecureMag USB KB reader - it spits out the encrypted data like a keyboard would.


The data contains unencrypted information like the last 4 digits of the card of the card holder's name.


I also don't know which parts of that information needs to be submitted to - once I know that, I can hopefully find out how to extract it from the code. I have the source code of a program that does it - I just don't know what exactly is required.


But before I can get there, I still have the E00061 error to contend with - unless that error shows up because the data cannot be decrypted correctly in which case the error message is misleading.

@rlund Where did you buy the card reader?

"Move fast and break things," out. "Move carefully and fix what you break," in.

I don't know that answer - I'm just the developer who is supposed to make it work.


As far as I know, one of our business partners who uses a different card reader from the same company organized the whole thing. As far as I know, the card readers were pre-programmed with the correct settings and key to work with


Still hoping on an answer here since I can't even test any data submissions until I know what Device Information should be sent to avoid this error...


Can I get a final ruling on whether or not the Device Info is the same for every reader (as referenced earlier in this thread) or if a key has to be attached?

If I need to attach a key to the Device Info, which key is that? The KSN, the Input Derivation Key, or ... ?


The Demo software for this reader outputs a some kind of key in Hex, but doesn't say what key that is.