The CR100 is a compact mobile wireless EMV NFC POS terminal designed for businesses, payment solution providers, fintech companies, system integrators, and software developers. It combines EMV chip card reading, EMV contactless payment support, Bluetooth connectivity, and USB communication in a portable payment reader.
Designed to work with smartphones, tablets, computers, and other compatible smart devices, the CR100 can be integrated into mobile POS applications and custom payment solutions. Its compact 66 × 66 × 9.8 mm design makes it suitable for portable checkout, field payment, retail, hospitality, and other card-present applications.
The CR100 supports EMV/PBOC chip cards, ISO 7816 Class A/B/C, EMV contactless, and ISO 14443A/B. It also provides payment-oriented security functions including DUKPT, Fixed Key, and MK/SK key management, together with DES, 3DES, AES, RSA, and SHA-256 cryptographic algorithms.
- CR100, you can accept payments wherever you go.
- Powerfully and flexibly accepts EMV and NFC payments
- Connects with smart devices via BLE or USB
- Easily to be integrated into apps on iOS, Android, Windows, and Linux
Specification
| EMV Card Reader | EMV/PBOC Chip Card Reader, ISO 7816 Compliant Class A, B, C |
| NFC Reader | EMV contactless, ISO 14443A/B |
| Communication | Bluetooth v3.0, Bluetooth v4.0 and USB |
| Indicator | LED Status indicator & Buzzer |
| Key Management | DUKPT |
| Fixed Key | |
| MK/SK | |
| Encryption Algorithm | DES |
| 3DES | |
| AES | |
| RSA | |
| SHA-256 | |
| Supported Operating System | Android 2.1 or above |
| iOS 6.0 or above | |
| Windows Phone 8 | |
| MS Windows | |
| Certifications | EMV L1&L2 |
| EMV contactless L1 | |
| PBOC L1&L2 | |
| MasterCard PayPass | |
| Visa PayWave | |
| VISA Ready | |
| PCI-PTS 5.x with SRED | |
| MasterCard TQM | |
| AMEX Pay | |
| Bluetooth BQB | |
| FCC | |
| CE | |
| Charging Method | Micro USB |
| Battery | Lithium polymer rechargeable battery 3.7V, greater than 250mAh |
| Dimensions | 66 x 66 x 9.8 mm(WxHxD) |
Bluetooth and USB Connectivity
The CR100 can communicate with a host device through Bluetooth or USB. Bluetooth provides a convenient wireless connection for mobile POS applications, while USB can be used where a wired connection is preferred.
A typical mobile payment architecture can be structured as:
Payment Card → CR100 → Bluetooth/USB → Mobile Application → Payment Platform
In this configuration, the CR100 provides the card-reading interface while the application running on the host device provides the user interface and connects to the appropriate payment infrastructure.
| Connection | Typical Use |
|---|---|
| Bluetooth | Wireless mobile POS applications |
| USB | Wired integration and development |
| Smartphone | Mobile payment applications |
| Tablet | Portable retail and service POS |
| Computer | Desktop or integrated POS applications |
The best connection method depends on the host hardware, application architecture, operating system, and deployment environment.
Compact Design for Portable Payment
One of the main advantages of the CR100 is its compact form factor. Measuring only 66 × 66 × 9.8 mm, the reader is designed for applications where portability and space efficiency are important.
The device uses a rechargeable 3.7V lithium polymer battery with a capacity greater than 250mAh and can be charged through Micro USB.
| Physical Specification | Value |
|---|---|
| Width | 66 mm |
| Height | 66 mm |
| Depth | 9.8 mm |
| Battery type | Rechargeable lithium polymer |
| Battery voltage | 3.7V |
| Battery capacity | >250mAh |
| Charging interface | Micro USB |
Its small footprint allows the reader to be carried alongside a smartphone or tablet without adding significant bulk to a mobile POS setup.
Security and Payment Data Protection
Security is a critical requirement for payment hardware. The CR100 specification includes multiple key management methods and cryptographic algorithms for payment-oriented applications.
Supported key management options include:
- DUKPT
- Fixed Key
- MK/SK
The listed cryptographic algorithms include:
- DES
- 3DES
- AES
- RSA
- SHA-256
These technologies provide security-related building blocks for payment solution development. The actual security architecture of a commercial deployment depends on the complete system, including the payment application, host device, processor, acquiring institution, transaction flow, and key-injection process.
For production payment projects, customers should confirm the exact security configuration, certification scope, and key-management requirements with the manufacturer and relevant payment partners.
EMV and Payment Certifications
The CR100 product specification lists several payment and regulatory certifications and qualifications.
| Certification or Qualification | Listed Support |
|---|---|
| EMV | L1 & L2 |
| EMV Contactless | L1 |
| PBOC | L1 & L2 |
| MasterCard | PayPass |
| Visa | PayWave |
| Visa | VISA Ready |
| PCI | PCI-PTS 5.x with SRED |
| MasterCard | TQM |
| American Express | AMEX Pay |
| Bluetooth | BQB |
| Regulatory | FCC / CE |
These qualifications can be important when evaluating payment hardware for commercial deployment.
However, certification requirements vary according to country, payment scheme, processor, transaction architecture, and final software configuration. Certification information should therefore be verified against the exact production configuration required for the target market.
CR100 Mobile POS Terminal vs. Traditional POS Terminal
The CR100 follows a different design approach from a conventional countertop POS terminal. Instead of combining the payment reader, display, operating system, and payment application into one large device, the CR100 can work as a compact payment peripheral connected to another smart device.
| Comparison | CR100 Mobile POS Reader | Traditional Countertop POS |
|---|---|---|
| Portability | High | Low to medium |
| Host device | Smartphone, tablet, computer | Integrated terminal |
| Wireless connection | Bluetooth | Model dependent |
| USB connection | Yes | Model dependent |
| EMV chip reading | Yes | Usually available |
| EMV contactless | Yes | Usually available |
| Mobile deployment | Excellent | Limited |
| Form factor | 66 × 66 × 9.8 mm | Generally larger |
| Custom application integration | Designed for integration | Platform dependent |
| Best use | Mobile and integrated POS | Fixed checkout |
The CR100 is particularly suitable when the software interface already exists on a smartphone, tablet, computer, or embedded host and a compact payment reader is required.
CR100 vs. NFC-Only Reader
An NFC-only reader may be sufficient for applications that only need contactless communication. However, payment projects may require both contact and contactless card interfaces.
| Capability | NFC-Only Reader | CR100 |
|---|---|---|
| NFC/contactless | Yes | Yes |
| EMV chip card | Usually not | Yes |
| ISO 14443A/B | Model dependent | Yes |
| ISO 7816 | Usually not | Yes |
| Bluetooth | Model dependent | Yes |
| USB | Model dependent | Yes |
| Mobile POS integration | Possible | Designed for this use |
| Payment security functions | Varies | DUKPT, Fixed Key, MK/SK |
For a project that needs both EMV chip card and contactless payment capabilities, a combined reader can simplify the hardware architecture.
Operating System and Application Integration
The product specification lists Android, iOS, Windows Phone 8, and Microsoft Windows compatibility, while the product description states that the device can be integrated into applications on iOS, Android, Windows, and Linux.
Because operating systems and mobile development requirements change over time, developers should confirm the current SDK, API, drivers, libraries, and supported OS versions before beginning a production integration.
| Platform | Product Information |
|---|---|
| Android | Listed support |
| iOS | Listed support |
| Windows | Listed support |
| Linux | Application integration stated |
| Windows Phone | Windows Phone 8 listed |
The most important consideration for developers is not only operating system compatibility, but also the availability of the appropriate SDK and communication protocol for the intended application.
How the CR100 Works in a Mobile POS System
The CR100 is designed to operate as part of a larger payment solution rather than as a standalone payment-processing service.
A typical workflow can include the following steps:
1. Connect the Reader
The CR100 connects to a smartphone, tablet, computer, or other compatible host device using Bluetooth or USB.
2. Launch the Payment Application
The merchant opens a compatible POS or payment application on the host device.
3. Enter the Transaction
The application sends the transaction amount and required instructions to the payment workflow.
4. Present the Card
The customer inserts an EMV chip card or presents a compatible contactless card or NFC payment device.
5. Process the Transaction
The reader communicates the required card information to the host application according to the implemented payment architecture.
6. Complete the Payment
The payment application communicates with the appropriate payment infrastructure and completes the transaction.
This architecture allows the CR100 to serve as a compact payment interface while the software platform controls the broader customer and transaction experience.
Applications of the CR100
The CR100 can be considered for a variety of mobile and integrated payment applications.
Mobile Retail POS
Retail employees can use a smartphone or tablet together with the CR100 to support payment acceptance without relying on a fixed checkout terminal.
Restaurant and Hospitality Payments
Portable payment hardware can be useful in restaurants, hotels, events, and hospitality environments where transactions may take place away from a fixed counter.
Field Service Payments
Service companies can integrate a mobile payment reader into applications used by technicians, delivery personnel, installers, and other field workers.
Portable Checkout
The compact form factor is suitable for businesses that need to accept payments at markets, events, temporary locations, exhibitions, or mobile sales points.
Payment Software Development
Fintech companies, payment providers, software developers, and system integrators can evaluate the CR100 as payment-reader hardware for custom applications.
POS System Integration
The Bluetooth and USB interfaces allow the reader to be considered for integration with custom POS systems, tablets, computers, and embedded payment solutions.
| Application | Why CR100 Can Fit |
|---|---|
| Retail | Portable card acceptance |
| Hospitality | Mobile checkout |
| Restaurants | Payment away from fixed counters |
| Field service | Compact and wireless |
| Events | Temporary/mobile payment stations |
| Fintech | Custom payment application development |
| System integration | Bluetooth and USB connectivity |
Benefits of a Compact EMV NFC Payment Reader
Choosing a compact payment reader can provide several advantages when designing a mobile payment solution.
Flexible Deployment
The reader can be paired with different host devices rather than requiring a dedicated all-in-one POS terminal.
Reduced Hardware Footprint
The compact 66 × 66 × 9.8 mm design can help minimize the physical size of a mobile checkout solution.
Contact and Contactless Payment
Supporting both EMV chip cards and EMV contactless transactions allows a payment application to accommodate different card-present scenarios.
Wireless Operation
Bluetooth connectivity provides flexibility for mobile payment environments where a cable between the reader and host device is inconvenient.
Integration Potential
The CR100 is designed around communication with external smart devices, making it suitable for software-driven payment solutions.

Important Considerations Before Integration
Selecting payment hardware requires more than comparing physical specifications. Developers and purchasing teams should evaluate the complete payment architecture before placing a production order.
Consider the following questions:
- Is the required SDK available for the target operating system?
- What Bluetooth and USB communication APIs are provided?
- Which EMV kernels and transaction functions are supported?
- What payment processors or acquiring partners can be used?
- How are encryption keys generated, injected, and managed?
- Which certifications apply to the intended market?
- Does the certification scope match the final hardware and software configuration?
- What documentation and technical support are available?
- Which current iOS, Android, Windows, and Linux versions are supported?
- Is OEM or ODM customization required?
These questions can help prevent compatibility problems during development and commercial deployment.
Why Choose CR100 for a Mobile Payment Project?
The CR100 brings several core payment interfaces into one compact device:
EMV Chip + EMV Contactless + NFC + Bluetooth + USB
This combination makes it suitable for companies that want to build a mobile POS solution around their own software or host device.
Instead of purchasing a large standalone POS terminal, businesses can design a payment experience around a smartphone, tablet, computer, or custom application and use the CR100 as the card-reading component.
Its combination of payment interfaces, compact construction, wireless connectivity, and security-related features makes it a practical option for mobile and integrated payment projects.

Frequently Asked Questions
Is the CR100 an EMV card reader?
Yes. The CR100 is specified as an EMV/PBOC chip card reader and supports ISO 7816 Class A, B, and C.
Does the CR100 support contactless payments?
Yes. The product specification lists EMV Contactless and ISO 14443A/B support.
Is the CR100 a general-purpose RFID reader?
It should not automatically be considered a general-purpose RFID reader. Its documented contactless functions focus on EMV Contactless and ISO 14443A/B. If your project requires a particular RFID frequency, tag type, protocol, read range, or read/write function, confirm compatibility before ordering.
Can the CR100 connect to a smartphone?
Yes. The device is designed to connect to smart devices through Bluetooth and can also communicate through USB.
Does the CR100 support Bluetooth?
Yes. Bluetooth 3.0 and Bluetooth 4.0 are listed in the product specification.
Does the CR100 support USB?
Yes. USB is listed as a communication interface and Micro USB is used for charging.
What encryption algorithms are supported?
The listed algorithms include DES, 3DES, AES, RSA, and SHA-256.
What key-management methods are supported?
The specification lists DUKPT, Fixed Key, and MK/SK key management.
Is the CR100 a standalone POS machine?
No. The CR100 is better understood as a mobile payment reader that works with a host device and payment application. A complete payment solution also requires appropriate software and payment-processing infrastructure.
What businesses can use the CR100?
Potential applications include retail, restaurants, hospitality, field service, events, mobile commerce, fintech, payment software, and custom POS integration.
Can the CR100 be integrated into a custom application?
The product description states that it can be integrated into applications on iOS, Android, Windows, and Linux. Developers should confirm the currently available SDK, API, development documentation, and supported operating-system versions for their project.
Build Your Mobile POS Solution with CR100
The CR100 is a compact EMV NFC payment reader designed for mobile and integrated POS applications. With EMV chip card support, EMV Contactless, ISO 14443A/B, Bluetooth, USB, and payment-oriented security features, it provides a flexible hardware platform for businesses and developers building custom payment solutions.
Whether you are developing a mobile POS application, integrating payment hardware into an existing system, or evaluating an EMV NFC reader for a new commercial project, the CR100 can be configured as part of a broader payment architecture.
For OEM, ODM, bulk purchasing, SDK integration, certification documentation, or custom payment projects, contact our team to discuss your requirements, target market, host platform, application architecture, and deployment plans.


