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!






I am working on integrating the encrypted card reader with ios. Can you please guide on how to generate the values for DeviceInfo and encrypted value? I have been scrambling for so many days without any luck and it is nothing in documentaiton about it.


Please help.




Hello @riteshmitra 


The iOS SDK now resides on GitHub and that there is documentation on how to use it as part of the download.


Are you using an encrypted reader injected with the Authorize.Net key?  For a list of supported secure card readers devices please go to 


Please note that  the sandbox and live production environments use a different key, and they cannot be used interchangeably.   You must use a reader injected with the sandbox key when testing in the sandbox, and a reader injected with the production key with the live payment gateway.




Hi Richard,


I am using encrypted card reader using iOS SDK on production environment.


Hope this answers your questions.


Please guide on how to do this.




Which encrypted card reader are you using?



IDTECH Shuttle



Reviving an old thread because I can't find a solution for this anywhere.


I get the exact same error, even when I substitute the DeviceInfo/Description as suggested by Lilith.


I am using the reference page to test this so far:


Is it possible that running a transaction request on this page does not work with encrypted data, or am I missing anything?





@rlund, are you using a card reader that has been injected with the key for our Sandbox environment?

If it's using the Production key, that would explain the error, as the API Reference Page plugs into the Sandbox environment.

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

Thanks for the reply.


To be sure: are you saying that the error message not only shows up with the Device Information is incorrect but also if the decryption of the data fails?


As far as I know, the reader I have has a key built-in that works for the live environment, so I didn't expect the decryption to work, but I was confused on the error message talking about the Device Information being incorrect...


@rlund Bear in mind that the DeviceInfo element should include the key in its contents:




Since the API Reference is meant to be used without needing a Production account, it uses the Sandbox environment, and needs the Sandbox key.

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

Is this documented anywhere at all? I thought earlier in this thread it was announced that the hex string can be the same generic text for everyone ...


Also, how does this information get encrypted into the hex string that shows up in the documentation?


And isn't it counterproductive to security to include the key in the submitted code?


I was under the impression that the code needed to be kept as secret as possible - I don't even have the code that was used to setup the card reader I have, and I was told that I would not be given the code for security reasons...


I'm sorry, but now I'm utterly confused...