Host card emulation

The term "host card emulation" (HCE) was coined in 2012 by Doug Yeager and Ted Fifelski, the founders of SimplyTapp, Inc., to describe the ability to open a communication channel between a contactless payment terminal and a remotely hosted secure element that contains financial payment card data, to pay at the point-of-sale.^[2] They implemented this new technology on Android. At that time, RIM had similar functionality, called "virtual target emulation", which was supposed to be available on the BlackBerry Bold 9900 under the BB7 operating system. Prior to HCE, card emulation existed in hardware only: a card could be replicated with a multiple-purpose secure element, housed inside a smartphone.^[1]

By including HCE in Android, Google hoped to accelerate adoption of Android payments and to increase adoption of Google Wallet by mobile network operators. At the time, Android's share of the mobile operating system market was 80%.^[3] However, even with the inclusion of HCE in Android 4.4, the banks still needed the major card networks to support HCE. Four months later, at Mobile World Congress 2014, Visa and MasterCard announced their intent to support HCE.^[4][5] On December 18, 2014, less than ten months after Visa and MasterCard announced their support for HCE, Royal Bank of Canada (RBC) became the first North American financial institution to launch a commercial implementation of mobile payments using the HCE technology.^[6]

As a result of widespread adoption of HCE, some companies offer modified implementations that usually focus on providing additional security for the HCE's communication channel. One such implementation is termed HCE+.

The new HCE architecture supports payments, loyalty programs, card access, and transit passes.

Before HCE, adoption of NFC in payment systems was low, due to lack of infrastructure (terminals), due to the high capital cost of deploying secure elements, and due to the need for complex partner relationships.

By supporting HCE in Android 4.4, Google enabled companies to adopt NFC at a relatively low cost.^{[citation needed]}

Host card emulation enables near field communication (NFC) information transfer between a terminal configured to exchange NFC radio information with an NFC card and a mobile device application configured to act or pretend to emulate the functional responses of an NFC card. HCE requires that the NFC protocol be routed to the main operating system of the mobile device instead of being routed to a local hardware-based secure element (SE) chip configured to respond only as a card, with no other functionality.^[7]

Since the release of Android 4.4, Google has implemented HCE within the Android operating system.^[1] Google introduced platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments, loyalty programs, card access, transit passes, and other custom services.^[7] With HCE, any app on an Android 4.4 device can emulate an NFC smart card, letting users tap to initiate transactions with an app of their choice. Apps can also use a new Reader Mode so as to act as readers for HCE cards and other NFC-based transactions.

The first known mobile handset to support anything like HCE outside of the Android family was the BlackBerry bold 9900 that was first available in Thailand. released together with BlackBerry 7 OS.^[8]

CyanogenMod operating system was the next known mobile device operating system to support HCE ^[8] through the effort of modifying the NXP NFC stack known as libnfc-nxp, the NFC service manager, and operating system APIs by Doug Yeager. The OS APIs were adapted to include two new tag types that were called ISO_PCDA and ISO_PCDB which are also known terminal or PCD standards. This would imply that you could "read" a tag in the same manner that you could read a terminal.

Microsoft has announced new support for HCE NFC payments in Windows 10. This will allow improved payment integration flows and enable coexistence of HCE with UICC-based secure elements in Windows 10 and Windows 10 Mobile.^[9]

HCE is used to allow transactions between mobile devices and other credential acquiring devices. Those devices may include other mobile devices, contactless point-of-sale terminals, transit turnstiles, or a variety of access control touch pads. For example, Android developers can leverage HCE to create specific payment experiences, such as using HCE to enable a mobile application as a transit card.^[10]