Tap & Pay Functionality on Note 3 Running KitKat?

[iN8ter]

Re: Tap & Pay Functionality on Note 3 Running Kit Kat?

My point exactly! As I've been saying all along, it is not a hardware issue, it is T-Mobile, thanks for the conformation, good day

I didn't confirm anything other than your reference and quote is completely out of place in this thread.

The NFC is still used in HCE. How else is the NFC connection made. The reason Wallet was blocked before is cause it accessed the SE. With HCE they don't block Wallet.

That would be like blocking the Starbucks app cause you can buy coffee with it. The carriers were only concerned with owning the Secure element on the phone, which resides on the SIM card. Want Google to hold your info, have at it! HCE removes one of the big benefits of the SE setup - you own your info and can destroy it by destroying the SIM card.

The S4 allows Wallet. The One allows it. Why would they block the Note and allow the others.

[inappropriate content deleted by moderator]

Sent from my Galaxy Note 3 using Tapatalk

 

[rusty502]

Re: Tap & Pay Functionality on Note 3 Running Kit Kat?

I didn't confirm anything other than your reference and quote is completely out of place in this thread.

The NFC is still used in HCE. How else is the NFC connection made. The reason Waller was blocked before is cause it accessed the SE. With HCE they don't block Wallet.

The S4 allows Wallet. The One allows it. why would they block the Note and allow the others.

[inappropriate content deleted by moderator]

Sent from my Galaxy Note 3 using Tapatalk

I'm not whining at all, wallet works fine for me, I see no point in continuing, we obviously disagree, or are doing a poor job of communicating, anyway, nice meeting you, maybe we will cross paths again on something we do agree on, take care

 

[NotJustAPhone]

Keep the discussion civil and on-topic. I suggest that those involved take the opportunity to review the forum rules. Personal attacks and insults will not be tolerated.

Thread has been cleaned up.

Sent from my Galaxy Note II

 

[apraetor]

Re: Tap & Pay Functionality on Note 3 Running Kit Kat?

Wrong, it is CARRIER blocked on the T-mobile note 3, kitkat enabled it on the Sprint note 3, it was blocked by Sprint when running JB, kitkat simply changes security, it no longer requires a secure SIM, so it may be easier to bypass the carrier lock, but the carriers DO have the ability to block it, and I would bet Verizon will also, they want you to use Isis

Actually, the reason the Google Wallet app doesn't support the AT&T or T-Mobile models of the Note 3 is because of the NFC chip. The chip doesn't support Host Card Emulation, which is the "unblockable" method Google uses for Tap and Pay. The NFC chip in the Sprint phones is from a different manufacturer and DOES support HCE, so the Wallet app works.

 

[apraetor]

Re: Tap & Pay Functionality on Note 3 Running Kit Kat?

Okay. You should read up on the issue especially as it pertains to this phone. The info exists. Calm down and seek it out.

This is like saying it's okay if your browser connects to your bank on a non encrypted connection because their servers are secure. Developer would pull an update if it resulted in such a scenario. That's just an example to get the point across.

Also. It still makes no sense as every other 4.4 device supports Google Wallet in Tap to Pay.

The evidence does not line up with your conspiracy theory.

Have a great day.

Sent from my Galaxy Note 3 using Tapatalk

That browser comparison is a false analogy. With the SE the Wallet app would store privileged information on the SIM card, which would (and could ONLY) be retrieved by the Wallet app when it was time to make a payment. This allowed the carriers to block the Tap and Pay feature by disabling access to the Secure Element for any app other than ISIS. Google's response was to switch to using Host Card Emulation. Each time you make an NFC payment the Wallet app sends a unique string to the payment terminal, which the terminal sends to Google for authentication & processing of the transaction. No secure element is required nor used, because the authentication is done via the cloud. When the Wallet app detects the cash register's reader it uses the phone's data connection to contact Google and is issued a unique, one-time-use key. The phone then passes this key to the reader on the cash register, which sends this key or to Google via the store's transaction processing system.

This method has some strong advantages. No SE is needed, and the payment info is always secure because even if someone managed to intercept the key during NFC transmission it would be invalidated as soon as the cash register transaction finishes. This is the reason Tap and Pay only works if you have phone service or a wifi signal -- the authentication is being performed out-of-band, not via the NFC interface. This is also the reason only Kitkat phones can use Tap and Pay now; Host Card Emulation wasn't available pre-Kitkat. Additionally, HCE isn't supported by some phones. Notably, the Sprint Note 3 DOES offer HCE, while the AT&T, Verizon and T-Mobile models all use an NFC chip from a different manufacturer which doesn't have HCE capability.

If you want to compare this to banking try this: you get a phone call from someone claiming to work for your bank, saying they need to talk to you about... whatever. You, wanting to verify they are legit, look up the bank's phone number via an independent source, like the phone book or the bank's website. You call that number and ask to speak to whomever it was calling you, and are put through to them. Congratulations, you've just used out-of-band authentication to verify the identity of the caller without any need for cryptography involving pre-shared keys. The system works so long as the phone book (or Google, in the case of Tap and Pay) can be considered a trusted source of information.