Today is Samstag, 23rd März 2019

Posts Tagged ‘google’

Google Debitcard for the Wallet App

As announce earlier, Google is looking into the card business. Now it is official: there is a Google Debit Card. This allows customers to use an ordinary plastic card in order to pay at MasterCard enabled terminals as well as withdraw money at an ATM from their Google Wallet Balance.

Final NFC hits the consumer market

Today Google announced its NFC based mobile wallet for the Nexus S in New York. Therefore Google developed new applications using the embedded NFC hardware in the Nexus S, the PN65 from NXP. In the future, customers can use Google Wallet to pay (eg using a contactless creditcard) or redeem a coupon using Google Offers. The offer currently is limited to Sprint customers in the US. The trial will start in New York and San Francisco and will continuously be extended till fall 2011.

In order to make this project happen Google partners with FirstData who provides the TSM (Trusted Service Management) Infrastructure. The first player offering a service in the wallet it Citi-Bank, which has a contactless credit card (Mastercard paypass) in the wallet that allows customers to pay in less than a second at the POS. Additionally Google will provide a prepaid stored value account in the Wallet, which can be topped up with a credit card.

There are already a number of merchant that will accept this special wallet from Google such as Macy’s, Guess or Subways. Of course, the contactless credit card can be used at any store which has been acquired to accept Mastercard paypass. Currently there are around 300.000 Mastercard Paypass terminals in the field in the US.

This is actually the first time, that Google opens the secure element in its mobile device for contactless applications. So far the APIs to access the secure element are not available to developers. The main feature, sending APDUs from an Android App to the secure element was not possible so far, as the Radio Interface Layer (RLI) blocked this kind of communication. Thru modifications in the firmware it is already possible to access the embedded secure element through the contactless interface as well as enable Single Wire Protocol (SWP) support to use the SIM card as a secure element. Although the API will allow other service providers to access the secure element, without an application on the embedded secure element there is not much benefit. FirstData is responsible to up apps into the secure smartcard chip in the phone.

In order to enable the NFC card emulation functionality of the mobile phone, the screen of the Android device needs to be unlocked and a PIN code is required as well. Of course the contactless communication is encrypted.

Videos and Pictures from Engadget

SMS NDEF on Android.

Since Android 2.3 (Gingerbread) Google phones are able to use the embedded NFC chip to read external tags. Such tags contain a data format called NDEF (Near Field Communication Data Exchange Format). This data format acts as a container for different data types such as SMS, URLs or Connection-Pairing Information. Up to now Android is not able to interpret the format of SMS stored on the tags correct. Also the most current version 2.3.4 does not fix the issue, although the bug has been reported through multiple channels.

When reading a tag with an NDEF SMS record, the tag is detected correctly.

But when opening the SMS application the content is not interpreted correctly. The message payload is attached to the MSISDN and therefore the SMS cannot be sent.

Countries and companies which have a tag infrastructure with SMS records in the field cannot casino pa natet be used with the Google phones. This is also true for the tags that are used for the service in Austria, but with a major difference: It seams that the NDEF data on tag itself was customized for Nokia phones that were available in the last years (which are able to decode the tags corretly) and therefore the Android phone is not able to read the information correctly. Thus the Android phone only indicates a „unknown tag type“.


Google-Code Bug Report (12142)

Google-Code Bug Report (15866)


Welcome at