-
Notifications
You must be signed in to change notification settings - Fork 13
Home
Welcome to the FEITIAN_MOBILE_READERS wiki!
Feitian mobile reader SDK support all Feitian smart card reader, the reader developed based on different platform, on Windows/Linux/macOS, we using USB and Bluetooth interface. and on mobile platform(Android, iOS) we choose lightning connector and Bluetooth as communication interface.
The mobile SDK support all of those interfaces.
All Feitian readers are accordance with CCID Standard, which is industry standard. on linux and macOS, there have open source driver: https://github.com/LudovicRousseau/CCID. windows system already integrated CCID driver inside windows system, so which means the reader is plug in and play with USB interface, not for Bluetooth interface(need install driver on Windows if you plan using bluetooth as communication interface).
Our SDK implement the CCID protocol and envelop API as PC/SC API, user can call PC/SC API directly. and in the low level, it calls ExternalAccessoryFramework for lightning interface, and call CoreBluetooth Framework as Bluetooth interface.
To using the ExternalAcessoryFramework, make sure you have add protocol string in your Info.plist
Specify protocol names that match the target device. The UISupportedExternalAccessoryProtocols key in your app’s Info.plist must contain one or more protocol names that match protocol names declared by the device.Your app must identify correct protocol names when enumerating connected devices using the External Accessory framework.
App developers must meet all iOS Developer Program requirements. The following steps are required for apps that communicate with devices.
- Specify protocol names that match the target device. The UISupportedExternalAccessoryProtocols key in your app’s Info.plist must contain one or more protocol names that match protocol names declared by the device. Your app must identify correct protocol names when enumerating connected devices using the External Accessory framework.
- Confirm that the target device has completed MFi certification. All steps up to and including production certification must be complete before you submit your iOS app for review.
- Provide the unique MFI PPID for the target device in iTunes Connect. When you submit your app using iTunes Connect, you must enter the device’s unique MFI PPID in your app metadata Review Notes field. The device’s unique MFI PPID is a ten digit number that is assigned when the device’s Product Plan is created. If you are not the device developer, you will need to obtain the MFI PPID from the device developer.
The Android SDK doing the same layer as iOS, in the high level API, we provide PC/SC API and private API, allow user through basic API to operate the reader. and in the middleware, the SDK implement the CCID protocol, and call USB Core framework, Bluetooth framework in android system, and send/receive data from reader.