A: ID TECH has a mobile reader, evaluation kit, available for purchase. This evaluation kit includes a mobile reader, a CD with the SDK for Apple, Android & Blackberry devices, manuals and other technical documents.
A: The SDK downloading from ID TECH website is for customers who have purchased evaluation kit from ID TECH. Please contact the salesperson if you didn't receive it when you receive the evaluation kit. If the reader is purchased through a reseller or a distribution, please contact them for the SDK.
A. You may download "ID TECH UniMag Reader Demo" from the App Store to verify the performance of the reader.
A: Please download "ID TECH UniMag Reader Demo" from App Store and test it on the Apple device or on another Apple device if possible to see if the same problem happens there. If so, contact ID TECH to get the hardware checked. If not, please contact software support.
A: Yes. Customers can download "ID TECH UniMag Demo" from Google Play. Another testing aplication called "UniMag Utility" can also be used for testing and sending out log files to ID TECH for further troubleshooting.
ID TECH UniMag Utility:
A: You can download the UniMag Utility (see FAQ #5 above) and follow the steps below to test the UniMag with your phone.
1. Remove bumper or case if there is any.
A: After a card swipe is captured, the application usually jumps to another view which shows summarized transaction information. Before switched to the next view, the application should remove all observers, call closeConnection function and then release UniMag instance. Customers can reference to the demo source code included in the SDK package.
A. There isn't one from ID TECH but a sample code (for card data in plain text) from one of our customers is available on request. It can be used as reference only which we are not able to support or answer any questions about it.
A: Our lab testing result shows the battery lifetime is at least 80,000 operations.
A: No. ID TECH mobile reader is not keyboard emulated; therefore, the data will not automatically populate onto a text field on a webpage. An application is required to capture the card data from the SDK and then submit the data to certain text fields on the web page.
A: Customers can download “UniMag Utility” from Google Play to obtain the model number and OS version of the Android device. Log files can be sent to ID TECH through [Email] button.
A: We expect the reader to work with later OS versions if there is no significant change made to the OS. Customers can download “UniMag Utility” from Google Play and send out log files to ID TECH if any error message is occurred.e suggest you to try it. If there is no significant change made to the OS, we expect the reader will work with later OS version.
A: Following the following steps:
1. Download “ID TECH UniMag Demo” from Google Play.
Note: To avoid the new XML file to be reloaded each time the app is started, you can rename the xml file name to “IDT_uniMagCfgx.xx.xml” (e.g. IDT_uniMagCfg1.15.xml), so the demo can locate this profile setting file in the tablet internal memory. The xml file with the same file name may already exist in the internal memory. If that’s the case, just replace that file with your new xml file.
A: Without sending the devices in for our development team to analyze the wave form and tune up a profile for that particular Android device, customers may try to modify the configuration file by themselves and see if a profile of similar model would work on the unsupported one. For example, customers may try to apply the profile of Sprint HTC EVO 3D (PG86100) to the PG86310. However, we are not able to guarantee it would work.
Here’s how to make the changes to add a profile for an unsupported model.
1. Copy the profile of PG86100, from start node <pg86100> to end node </pg86100>
A: ID TECH mobile readers are not encrypted by default, but they all have the capability of being encrypted. If they are to be encrypted, the key is determined by your processor or gateway. They can specify an AES key or a TDES key needed. In both cases the key management is DUKPT. If that key is already in the key library at our facility, you only need to specify the name of it and we can inject it into your units upon request when ordering the readers. If we don’t have it, you will need to request that your processor send it to us as several parts in the required secure manner. We also have the capability of generating a private encryption key for your use only and this involves sending the several key parts we have generated to your processor. The units must be injected in a PCI certified Key Injection Facility, they cannot be injected remotely.
17. I have a Samsung Galaxy Nexus and would like to use it with the Unimag Pro for building a prototype. I received the SDK v2.6 with config file 126.96.36.199 and tried it. Even though the idt_unimagcfg_default.xml contains a section<galaxynexus>, I get a timeout when the dongle is plugged in. Why is this?
A: The Samsung Galaxy Nexus (GALAXYNEXUS) is not supported by UniMag Pro (ID-80110004-XXX). However, it is supported by UniMag II (ID-80110008-XXX) and Shuttle (ID-80110010-XXX). The configuration file (.xml) is shared among different UniMag family readers. There might be some supported model included for the testing purpose of the development team. Therefore, please always reference to the supported phone list on ID TECH website.
A: An extension cable might affect the wave signal of audio jack readers; therefore, we don’t suggest customers using it since we are not able to guarantee the reading performance.
A: The Key Value shown in the demo is the current transaction key which is used for encryption / decryption. This key changes every time when the KSN counter increases.
A: UniMag (ID-80110001-XXX) is our first generation audio jack reader, and UniMag Pro (ID-80110004-XXX) is the next generation after UniMag. Both readers read 3 track data, but there are couple differences between the two. First, UniMag Pro supports more phones than UniMag. Please find supported phone list on the link below. Second, UniMag Pro includes embedded batteries in the hardware design, which is mainly used to ensure sufficient power is given on certain phones for the reader to work properly. However, it doesn’t mean there is a performance concern without the embedded batteries. If the application focuses on Apple devise or any phone that on the UniMag supported list, UniMag can still be a good choice. Finally, UniMag Pro is the only solution out of these two choices if Blackberry platform will be one of the target markets.
Since we are trying to keep improving our products, customers may also want to consider UniMag II (ID-80110008-XXX) or Shuttle if the application needs first 2 track data only. UniMag II (ID-80110008-XXX) and Shuttle support more phones than UniMag and UniMag Pro, while Shuttle has better feasibility to support even more phone in the future due to the hardware design.
A: For supported phone list of mobile readers, please reference to the link on ID TECH website under [Products] à [Mobile Readers]. A list of device common name, OS version (which was tested by ID TECH), and carrier will be available.
A: ID TECH provides SDK for both UniMag family readers (UniMag, UniMag Pro, UniMag II and Shuttle) and iMag family readers (iMag and iMag Pro).
iMag and iMag Pro share the same SDK which is written in Objective-C and present with static library format. Readers in UniMag family share the same SDKs. ID TECH currently provides SDKs for three platforms: iOS (Objective-C with .a static library file), Android (Java with Jar file) and Blackberry (Java with Jar file).
A: To integrate your application with our mobile readers, you will need the SDK, which will make development process much easier. The SDK provides necessary APIs for an application to detect reader connection, get card data from the reader, or power up reader (if UniMag family readers are used). The SDK package also includes a piece of demo application for customers to verify the functionality of the reader.
Please note that the SDK does not include a feature to decrypt card data. The whole encrypted data block (from STX 0x02 to ETX 0x03) will be passed to the application. Therefore, customer’s application will be responsible for parsing designated fields (such as encrypted track 1 data, encrypted track 2 data and KSN) and handling decryption process.
A: The SDK will output complete card data in either clear text or encrypted format depending whether or not the reader is encrypted with a secure key. ID TECH currently doesn’t provide APIs for an application to extract a specific field such as card number and expiration date. An application will need to parse the data by itself.
iOS SDK also embedded a format filter to ensure data integrity. Start and end sentinels will be verified for non-encrypted data; while checksum and LRC will be verified for encrypted data. When the card data doesn’t match either format, a bad swipe message will show.
A: There are two ways to power up the reader. One is by power up string and the other is through command. ID TECH UniMag Demo is set to power up the reader through command by default. Therefore, UniMag (ID-80110001) and UniMag Pro (ID-80110004) will receive timeout error if [Settings] à [Command to Connect] is enabled because the two models do not support bi-directional communication.
It is not required to enable “Command to Connect” when testing UniMag II (ID-80110008) and Shuttle (ID-80110010) in ID TECH UniMag Demo since they support commands.
A: The encrypted output formats of the two sets (UniMag/UniMag Pro vs. UniMag II/Shuttle) of reader are different. Customers may reference to the manuals of the two sets of reader for more details.
1. UniMag II/Shuttle does not support hashed data; while UniMag Pro does. à The status is determined by Field 9.
2. UniMag II/Shuttle supports outputting serial number; while UniMag Pro does not. à The status is determined by Field 8.
3. Session ID is supported by UniMag Pro when security level is 4. à The status is determined by Field 9.
A: UniMag reader requires the mobile device to output stereo audio in order to function. Please make sure the [Mono Audio] setting under [Settings] à [General] à [Accessibility] à Mono Audio is disabled.