BankThink

Host Card Emulation needs simpler ID tech to calm mobile security fears

Complimentary Access Pill
Enjoy complimentary access to top ideas and insights — selected by our editors.

Security concerns are one reason that we haven't seen mass adoption of Host Card Emulation (HCE), but there is emerging technology that can address the problem.

While using the cloud via HCE appears to offer a solution that is ideal for service providers, as it is carrier- and OEM-independent (except for iPhone, which is a closed solution), there remains a perception that HCE might not be secure enough.

This is where trusted execution environment (TEE) technology comes into its own. The TEE has reached a significant level of maturity, offering GlobalPlatform compliance and delivering scale across the Android base, but importantly it delivers hardware-level protection to secure HCE.

p19ga8vj2d1763t0uf11pdc7usc.jpg
A model of the Android operating system logo stands on display at the company's booth at the Mobile World Congress in Barcelona, Spain, on Monday, Feb. 27, 2012. The Mobile World Congress, operated by the GSMA, expects 60,000 visitors and 1400 companies to attend the four-day technology industry event which runs Feb. 27 through March 1. Photographer: Chris Ratcliffe/Bloomberg
Chris Ratcliffe/Bloomberg

This increased level of security opens up opportunities to deliver simpler (yet more secure) authentication. On top of this, the TEE’s Trusted User Interface can securely deliver value-added services such as high value payments, secure messaging and other transaction-based services.

Many banks are seeing the combination of HCE and TEE as the technologies to enable mobile payment integration with existing bank apps, satisfying the needs of the service provider and the consumer. We may now have a mobile payments solution that can finally reach scale!

The world of mobile payments is not unlike the political systems we see in many countries around the world. Three or more groups arguing; sometimes working together and at other times pulling in totally different directions.

Consumers typically have strong relationships with their bank, their carrier and possibly also their smartphone vendor, all of whom are vying to push their own brand of mobile wallet. However, consumers usually wish to pay with their preferred card, from their preferred bank and don’t necessarily want multiple wallets cluttering their phone’s home screen.

Banks wish to reach the widest possible audience, irrespective of which phone is being used on which network. Quite understandably, they view their brand as being of the utmost importance and want consumers to use a single, bank-owned wallet.

The smartphone vendors are offering banks and consumers a secure payments environment and a global presence, but dressed up inside their own vendor-branded wallet (e.g, Apple Pay, Samsung Pay). Some banks see this as a dilution of their brand and consumers are faced with yet another app (distinct from their mobile banking app) and potential issues when switching between phones. This is not an ideal situation, for consumers or banks.

For reprint and licensing requests for this article, click here.
Mobile payments Identity verification ISO and agent
MORE FROM AMERICAN BANKER