1. How can I get the SDK for the UniPay?
A: ID TECH has a UniPay evaluation kit available for purchasing. This evaluation kit includes a mobile reader and SDK password to download from our website. The SDK contains app libraries, demo, and source code to operate the UniPay reader. UPDATE SDKs are now offered free of charge on the Knowledge Base
2. How can I get the password for downloading the SDK for the UniPay?
A: The SDK downloading from ID TECH website is for customers who have purchased the evaluation kit from ID TECH. Please contact the salesperson if you didn't receive it when you received the evaluation kit. If the reader is purchased through a reseller or a distributor, please contact them for the SDK.
3. What platforms is the UniPay compatible with?
A. There are currently three UniPay SDK's: an iOS SDK, an Android audio jack SDK, and an Android USB SDK for interfacing with the UniPay via the micro USB port with converter cables.
4. Is there a general code to parse the credit card data in Java?
A: Check out Parsomatic - Home
5. How is the UniPay powered?
A: Unlike the UniMag and Shuttle, the UniPay is powered from an internal battery that recharges from the micro USB port. Make sure the device has sufficient power before attempting operation.
6. What is the battery life for the UniPay?
A: One time full charge can perform 250 times smart card reading and MSR card reading with 7 days standby mode.
7. Can the mobile reader output the card data into a web page directly?
A: No. ID TECH mobile readers are 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.
8. How do I got about to have the mobile reader injected with the key for it to output the encrypted data?
A: The UniPay is not encrypted by default. You need to order it with key injection from sales or send your unit in to be key injected in our or a similar key injection facility. Please contact sales for pricing and details.
9. My Android device is not currently supported, what should I do?
A: Android devices must be individually tested to be supported by the UniPay reader. If yours is not currently on our list from the product page, you must either send us the device for in house testing or use the autoconfig to attempt to create a profile. If successful, please email us the logs and we should be able to update our list with the new profile.
10. How do I know if my phone is supported or not?
A: The supported list is on the UniPay product page at the following link: http://www.idtechproducts.com/products/mobile-readers/176.html
11. My UniPay is timing out on my iOS device, what is the cause?
A: iOS has a few potential settings which can cause the UniPay not to work. When a device fails to connect or read, please check the following settings to make sure they are correct.
1. Privacy: Please go to the privacy menu in the settings and check for microphone.
Ensure that any app which uses the UniMag reader is set to green.
2. Mono Audio: Please go to settings, general, accessibility to check the mono audio setting.
This should be turned off and is in the hearing section of this list. Also, check the left right balance just below this to make sure it is in the center.
3. Volume limit: The iOS device can be set to limit volume from the music app. To check this, please go to settings and scroll down until you find the music app (picture of a red music note).
In this menu, check the Equalizer and Volume Limit settings to make sure they are both turned off.
4. Restrictions. If this is turned on, you need to make sure microphone access or audio settings are not incorrectly set with access denied.
If all of these settings are correct and the reader still does not work, please make sure you have checked function in the ID TECH demo. It can be found on the app store under the terms "ID TECH UniMag". You may also try the same reader with a different device, just to be sure that the problem is not specific to that mobile device.
12. I'm a developer upgrading my existing UniMag/UniMag II/Shuttle application on iOS to also support the UniPay, how can I use both in the same app?
A: Our latest release of the UniPay SDK includes support for both devices using our Universal Library. Please contact sales for more information on how to obtain and work with the library. We are working to make the update for our UniMag SDK as well. Steps below.
Steps:
1.Remove UniMag SDK from project (uniMag.h and IDTECH_UniMag.a)
2.Add IDTech.framework to project
3.Add IDTech.bundle to project
4.In the project, replace all occurrences of
#import “uniMag.h”
with
#import
13. The demo app does not compile on the simulator with x64 architecture. It is set up to try to be a Mac app and not an iOS app if its x64. So I can not run my app on the simulator if I have your framework in it. How do I correct this?
A: The framework will not compile in iOS 64-bit simulators. This is because the framework also supports OS X, so XCode attempts to load the OS X code when using 64-bit iOS simulator (same CPU architecture). The solution is to remove arm64 from the Architectures and Valid Architectures for the simulator build settings. (64-bit works fine on iOS device).
14. All of the documentation is for UniPay. I have UniMag also and the framework SDK is the same one, but UniMag does not have all of the same method names as UniPay. So I need documentation for using the new universal framework with UniMag.
A: Documentation is still a few weeks out. But implementation is straight forward:
1. Use UniPay manual/tutorials to understand how to implement the UniPay. This is by using [IDT_UniPay sharedController] for commands, and using IDT_UniPay_Delegate methods for capturing data.
2. Setup support for UniMag the exact same was as UniPay using IDT_UniMag class. This means following UniPay manual, substitute “IDT_UniMag” for everywhere there are examples showing “IDT_UniPay”. So, for instance, when the UniPay manual says to start a swipe you execute [[IDT_UniPay sharedController] mrs_startMSRSwipe], for the UniMag it would be [[IDT_UniMag sharedController] msr_startMSRSwipe].
3. The IDT_UniPay and IDT_UniMag use the same delegates.This means that once you established the delegates for IDT_UniPay, IDT_UniMag will use those same delegates to return information. As the manual tells you to make the IDT_UniPay class a delegate (put IDT_UniPay_Delegate in class header and then [[IDT_UniPay sharedController] setDelegate:self]), you do the same thing for UniMag (IDT_UniMag_Delegate in class header and [[IDT_UniMag sharedController] setDelegate:self].
4. Refer to the IDT_UniMag.h file for all available methods. Then in your code, when you want to access UniPay you use [IDT_UniPay sharedController] and when you want to access UniMag, you use [IDT_UniMag sharedController].
See also:
