WEBVTT - What's in Google Wallet?

0:00:00.280 --> 0:00:02.960
<v Speaker 1>Brought to you by the reinvented two thousand twelve Camray.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.000 --> 0:00:17.960
<v Speaker 1>tech Stuff from how stuff works dot com. Hello again, everyone,

0:00:18.000 --> 0:00:20.560
<v Speaker 1>Welcome to tech stuff. My name is Chris Poulette and

0:00:20.560 --> 0:00:23.000
<v Speaker 1>I'm an editor at how stuff works dot com. Sitting

0:00:23.040 --> 0:00:27.040
<v Speaker 1>across from me, as always senior writer Jonathan Strickland. It

0:00:27.040 --> 0:00:30.000
<v Speaker 1>ain't fair how we scrounged for three or four bucks

0:00:30.080 --> 0:00:35.960
<v Speaker 1>while she gets warbucks. The little brat as always excellent.

0:00:36.159 --> 0:00:41.280
<v Speaker 1>Thank you. So we're gonna talk about Google Wallet today, indeed,

0:00:41.360 --> 0:00:44.480
<v Speaker 1>and Google Wallet was a project that was announced back

0:00:44.680 --> 0:00:48.440
<v Speaker 1>in I think May of eleven. It is now late

0:00:48.680 --> 0:00:51.600
<v Speaker 1>June twenty eleven when we're recording this podcast, but we

0:00:51.640 --> 0:00:54.400
<v Speaker 1>wanted to kind of talk about it and kind of

0:00:54.640 --> 0:00:58.200
<v Speaker 1>go over what the implications of the the product is.

0:00:58.400 --> 0:01:01.480
<v Speaker 1>Our gosh, I'm so tired. I've just got back from

0:01:01.520 --> 0:01:05.000
<v Speaker 1>vacation and my my ability to speak in coherent sentences

0:01:05.000 --> 0:01:10.680
<v Speaker 1>with proper grammar is sorely depleted. Yes, yes, so Google

0:01:10.680 --> 0:01:15.800
<v Speaker 1>wallet fire bad. Um. Anyway, so we wanted to talk

0:01:15.800 --> 0:01:18.080
<v Speaker 1>about what Google walle it is, how it works in

0:01:18.120 --> 0:01:21.880
<v Speaker 1>a kind of bird's eye view level and what it

0:01:21.959 --> 0:01:26.319
<v Speaker 1>might mean to the future of making purchases. Yeah, it's

0:01:26.360 --> 0:01:29.039
<v Speaker 1>funny because this is not really a new topic at all,

0:01:29.080 --> 0:01:32.200
<v Speaker 1>but it's new to many people here in the United

0:01:32.240 --> 0:01:33.960
<v Speaker 1>States because I mean, this is the kind of thing

0:01:34.000 --> 0:01:37.320
<v Speaker 1>that's been going on for many years over in Asia. Yeah,

0:01:37.440 --> 0:01:41.399
<v Speaker 1>Japan in particular, Japan in particular. Um, basically the idea

0:01:41.400 --> 0:01:45.720
<v Speaker 1>of being that you could uh store payment information in

0:01:45.920 --> 0:01:51.880
<v Speaker 1>your cell phone or smartphone and uh use that information

0:01:52.000 --> 0:01:55.880
<v Speaker 1>to make a payment when you go to a store. Yes,

0:01:56.000 --> 0:01:59.120
<v Speaker 1>so instead of scanning a you know, swiping your credit

0:01:59.160 --> 0:02:02.720
<v Speaker 1>card and signing a little digital thing, or or having

0:02:02.760 --> 0:02:04.200
<v Speaker 1>to put in your pin number if you're using a

0:02:04.200 --> 0:02:06.720
<v Speaker 1>debit card, or even using a credit card that has

0:02:06.720 --> 0:02:08.720
<v Speaker 1>an r F I D chip in it where you

0:02:08.760 --> 0:02:12.400
<v Speaker 1>know you'll you'll see those consoles at certain vendors where

0:02:12.840 --> 0:02:17.200
<v Speaker 1>you can tap the card and that registers as a payment. Uh,

0:02:17.240 --> 0:02:19.240
<v Speaker 1>instead of using a card at all, it would be

0:02:19.280 --> 0:02:21.760
<v Speaker 1>stored on your phone. And you might ask, well, why

0:02:21.760 --> 0:02:24.079
<v Speaker 1>would you even bother to do that, Like, why why

0:02:24.240 --> 0:02:26.120
<v Speaker 1>have it on your phone? As opposed to if you

0:02:26.240 --> 0:02:29.560
<v Speaker 1>if it's replacing tapping a card, how does that make

0:02:29.600 --> 0:02:31.760
<v Speaker 1>it easier? If you put it on a phone, and

0:02:31.800 --> 0:02:34.440
<v Speaker 1>that's a that's a legitimate question. I mean, one answer

0:02:34.480 --> 0:02:38.000
<v Speaker 1>you could arguably give is that, well, you cut down

0:02:38.000 --> 0:02:39.840
<v Speaker 1>on the things you need to carry. But when you're

0:02:39.840 --> 0:02:43.080
<v Speaker 1>talking about a credit card, it's not like that's a huge,

0:02:43.160 --> 0:02:45.600
<v Speaker 1>bulky thing that's really weighing it down. In fact, it's

0:02:45.720 --> 0:02:48.360
<v Speaker 1>much smaller form factor than a cell phone or smartphone.

0:02:49.040 --> 0:02:53.280
<v Speaker 1>So really the value in the proposition is that Google

0:02:53.360 --> 0:02:59.440
<v Speaker 1>has has grouped this ability to pay through a a

0:02:59.480 --> 0:03:03.200
<v Speaker 1>smartphone own with other services that kind of make it

0:03:03.600 --> 0:03:07.320
<v Speaker 1>more of an attractive service. It's not it's not just

0:03:07.480 --> 0:03:09.280
<v Speaker 1>that you can pay with a smartphone. There are other

0:03:09.720 --> 0:03:12.440
<v Speaker 1>features that are involved that are pretty cool. Yeah. And

0:03:12.480 --> 0:03:16.440
<v Speaker 1>in addition to that, Google says that it doesn't intend

0:03:16.600 --> 0:03:20.959
<v Speaker 1>to replace a credit card. It intends to replace all

0:03:20.960 --> 0:03:24.040
<v Speaker 1>of your credit cards and your loyalty cards. Does the

0:03:24.480 --> 0:03:27.400
<v Speaker 1>cards that you carry around with you to UM. You know,

0:03:27.440 --> 0:03:29.760
<v Speaker 1>if you you're at your grocery store and you get,

0:03:29.800 --> 0:03:32.840
<v Speaker 1>you know, fifty cents off a can of tomatoes if

0:03:32.880 --> 0:03:36.560
<v Speaker 1>you have the card, UM, basically you're selling them your

0:03:36.600 --> 0:03:38.920
<v Speaker 1>information so they can market to you. But you also

0:03:38.920 --> 0:03:41.520
<v Speaker 1>exchange they'll give you a discount, and you also get yeah,

0:03:41.720 --> 0:03:45.400
<v Speaker 1>so not just loyalty cards, but also coupons, like electronic coupons.

0:03:45.920 --> 0:03:48.760
<v Speaker 1>So so there might be a loyalty program. For example,

0:03:49.320 --> 0:03:53.600
<v Speaker 1>here's an easy one. My wife really likes coffee, right,

0:03:53.640 --> 0:03:58.320
<v Speaker 1>so she has loyalty cards with practically every coffee shop

0:03:58.520 --> 0:04:02.960
<v Speaker 1>that is in a ten mile radius of our home. Yeah.

0:04:03.200 --> 0:04:05.800
<v Speaker 1>Her loyalty to coffee as legendary, Yes, to the point

0:04:05.800 --> 0:04:07.880
<v Speaker 1>where you know, she has to sort through her loyalty

0:04:07.920 --> 0:04:10.080
<v Speaker 1>cards when she goes into a coffee shop to determine

0:04:10.120 --> 0:04:13.320
<v Speaker 1>which one of her cards applies at that shop. And

0:04:13.400 --> 0:04:15.440
<v Speaker 1>so you know, it's one of those things where you know,

0:04:15.600 --> 0:04:17.760
<v Speaker 1>you buy nine coffees and the tenth one is free,

0:04:18.400 --> 0:04:21.080
<v Speaker 1>same sort of thing, except it stored electronically on your phone,

0:04:21.120 --> 0:04:24.920
<v Speaker 1>and so it the the application of Google Wallet keeps

0:04:24.960 --> 0:04:27.719
<v Speaker 1>track of how many times you've been to this particular

0:04:27.839 --> 0:04:31.400
<v Speaker 1>place and bought a particular thing, and then automatically registers

0:04:31.400 --> 0:04:33.520
<v Speaker 1>when you hit ten, and so when you go to

0:04:33.560 --> 0:04:37.520
<v Speaker 1>pay it registered, it files that information for you. It's

0:04:37.560 --> 0:04:39.800
<v Speaker 1>the same as if your card had been stamped a

0:04:39.880 --> 0:04:42.440
<v Speaker 1>tenth time, and then you don't have to uh and

0:04:42.480 --> 0:04:46.000
<v Speaker 1>want you don't get the price of the coffee deducted

0:04:46.040 --> 0:04:50.400
<v Speaker 1>from your account or charged to your card. Um. And

0:04:50.440 --> 0:04:52.559
<v Speaker 1>before we get too far into this, just before we

0:04:53.240 --> 0:04:55.839
<v Speaker 1>launch into it, I wanted to mention UH that we

0:04:55.880 --> 0:05:00.480
<v Speaker 1>do have an article about paying UH with a cell phone.

0:05:00.480 --> 0:05:02.520
<v Speaker 1>In fact, it's called can you use a cell Phone

0:05:02.560 --> 0:05:05.320
<v Speaker 1>as a credit Card? And Julia Layton wrote that article

0:05:05.360 --> 0:05:07.799
<v Speaker 1>and it's a UM. If you go and read the article,

0:05:07.800 --> 0:05:10.920
<v Speaker 1>you'll actually notice that there's some mention of of this

0:05:11.080 --> 0:05:13.880
<v Speaker 1>debuting in the United States back in two thousand seven,

0:05:14.240 --> 0:05:17.239
<v Speaker 1>and not Google Wallet, but the ability to pay using

0:05:17.480 --> 0:05:20.239
<v Speaker 1>using a phone as a credit card. Now, keep in mind,

0:05:20.400 --> 0:05:23.320
<v Speaker 1>even two thousand seven is late to the game compared

0:05:23.360 --> 0:05:26.440
<v Speaker 1>to Japan. That's that's true. That's true. UM. I just

0:05:26.480 --> 0:05:29.520
<v Speaker 1>wanted to go before we go any further to UM.

0:05:29.560 --> 0:05:33.520
<v Speaker 1>Google is also saying that in addition to loyalty cards

0:05:34.040 --> 0:05:37.559
<v Speaker 1>and credit cards, Google says that it that Google Wallet

0:05:37.560 --> 0:05:40.760
<v Speaker 1>will eventually allow you to use gift cards, receipts, boarding passes,

0:05:41.520 --> 0:05:47.560
<v Speaker 1>UM and and possibly your keys UM available through Google Wallet.

0:05:47.640 --> 0:05:51.920
<v Speaker 1>So UM it would in fact, in theory be able

0:05:51.960 --> 0:05:53.839
<v Speaker 1>to reduce the amount of stuff you would need to

0:05:53.839 --> 0:05:56.279
<v Speaker 1>carry in your wallet. Now, I noticed there's no driver's

0:05:56.360 --> 0:06:00.440
<v Speaker 1>license mentioned in their passport. That would be interesting to see.

0:06:00.440 --> 0:06:04.200
<v Speaker 1>Although passports in the United States do have a radio

0:06:04.240 --> 0:06:07.520
<v Speaker 1>frequency identification chip, Yes they do. So I have a

0:06:07.520 --> 0:06:11.840
<v Speaker 1>little little wallet that blocks that. Yes, mine. We'll talk

0:06:11.880 --> 0:06:14.320
<v Speaker 1>about that later too, because that's gonna come up. But

0:06:14.360 --> 0:06:17.359
<v Speaker 1>we should probably talk about the you know, how it

0:06:17.400 --> 0:06:20.000
<v Speaker 1>works and the benefits of using it. Sure now, when

0:06:20.040 --> 0:06:22.479
<v Speaker 1>they were when Google was launching this, they were talking

0:06:22.480 --> 0:06:28.960
<v Speaker 1>about two specific other partners with this. Yes, there are

0:06:28.960 --> 0:06:32.480
<v Speaker 1>also thousands of vendors that are going to support this,

0:06:32.600 --> 0:06:36.040
<v Speaker 1>but the two partners specifically that I wanted to talk

0:06:36.080 --> 0:06:41.320
<v Speaker 1>about where Sprint because the phone that they're debuting the

0:06:41.440 --> 0:06:45.000
<v Speaker 1>Google Wallet service on is the Nexus S four G,

0:06:45.240 --> 0:06:48.320
<v Speaker 1>which is only on Sprint, Yes, all right. And then

0:06:48.640 --> 0:06:51.839
<v Speaker 1>City MasterCard, which is that you know, that's where that's

0:06:51.880 --> 0:06:54.360
<v Speaker 1>got the financial backing. That's so if you want to

0:06:54.400 --> 0:06:58.479
<v Speaker 1>have Google Wallet, you have really two choices as far

0:06:58.600 --> 0:07:02.320
<v Speaker 1>as what kind of payment option you go with. You

0:07:02.320 --> 0:07:06.680
<v Speaker 1>can either apply to get a City MasterCard account, or

0:07:06.760 --> 0:07:08.799
<v Speaker 1>if you already have one, you can enter that information

0:07:08.839 --> 0:07:13.000
<v Speaker 1>into Google Wallet and that will become your Google Wallet account.

0:07:14.000 --> 0:07:18.480
<v Speaker 1>Or you can get a Google Prepaid card and Google

0:07:18.480 --> 0:07:21.240
<v Speaker 1>Prepaid Card is you know, it's essentially what sounds like,

0:07:21.280 --> 0:07:24.200
<v Speaker 1>you can you can put money into your Google Prepaid

0:07:24.240 --> 0:07:26.800
<v Speaker 1>card and use that for payments, kind of like you know,

0:07:26.960 --> 0:07:30.040
<v Speaker 1>like pay Pal or any other sort of gift card

0:07:30.160 --> 0:07:32.840
<v Speaker 1>kind of approach. Um, And what's kind of interesting is

0:07:32.880 --> 0:07:37.400
<v Speaker 1>that if you do the Google prepay approach, they will

0:07:37.440 --> 0:07:41.160
<v Speaker 1>actually credit you ten dollars in your account, so you'll

0:07:41.200 --> 0:07:43.880
<v Speaker 1>get ten bucks for free. Yeah, I thought that was

0:07:44.240 --> 0:07:49.280
<v Speaker 1>pretty funny. Actually, and at least until um the end

0:07:49.360 --> 0:07:52.760
<v Speaker 1>of twenty eleven, you will not have to pay any

0:07:53.000 --> 0:07:56.920
<v Speaker 1>fees to add money to your Google Prepaid card. So,

0:07:56.960 --> 0:07:58.880
<v Speaker 1>in other words, it's not like you get a service

0:07:58.920 --> 0:08:01.520
<v Speaker 1>feed up added on top of you know, you want

0:08:01.520 --> 0:08:04.120
<v Speaker 1>to add say a hundred dollars to your Google Prepaid card,

0:08:04.360 --> 0:08:06.000
<v Speaker 1>You're not going to get a service fee of five

0:08:06.080 --> 0:08:08.720
<v Speaker 1>bucks on top of that, at least until the end

0:08:08.760 --> 0:08:11.680
<v Speaker 1>of twenty eleven. Now, uh, what does that mean that

0:08:11.720 --> 0:08:15.120
<v Speaker 1>in they'll start adding in a service fee. Maybe we

0:08:15.200 --> 0:08:19.160
<v Speaker 1>don't know. But the wording is specifically about till the

0:08:19.320 --> 0:08:22.320
<v Speaker 1>end of or at least until the end of twenty eleven,

0:08:22.360 --> 0:08:25.600
<v Speaker 1>is how they put it. So, um, yeah, you've got

0:08:25.720 --> 0:08:27.920
<v Speaker 1>so you've got the that's the backing as far as

0:08:27.920 --> 0:08:32.080
<v Speaker 1>payment goes, so it's either City MasterCard or the prepaid card,

0:08:32.840 --> 0:08:37.640
<v Speaker 1>which you can use any credit card to purchase money

0:08:37.679 --> 0:08:40.400
<v Speaker 1>to go toward the prepaid card. You don't have to

0:08:40.400 --> 0:08:44.200
<v Speaker 1>have a City master Card for that one. Uh. Well,

0:08:44.240 --> 0:08:47.840
<v Speaker 1>what about the actual payment process, like, how does this

0:08:48.040 --> 0:08:51.959
<v Speaker 1>transfer happen? Well, it happens through UM something called an

0:08:52.080 --> 0:08:56.959
<v Speaker 1>NFC chip. Yes, that's near field communication. UM. This is

0:08:57.000 --> 0:08:59.520
<v Speaker 1>a little different from the r F I D chip

0:09:00.000 --> 0:09:03.040
<v Speaker 1>that you find in your UH and some of your

0:09:03.080 --> 0:09:06.040
<v Speaker 1>credit cards, which is if you if you have one,

0:09:06.080 --> 0:09:09.440
<v Speaker 1>you'll know it. It's that that little uh usually gold

0:09:09.480 --> 0:09:13.680
<v Speaker 1>color or silver colored UM piece of metal embedded in

0:09:13.679 --> 0:09:17.840
<v Speaker 1>the chip. Basically that has your your information UH in

0:09:17.920 --> 0:09:21.760
<v Speaker 1>it so that when you UH take it near one

0:09:21.760 --> 0:09:24.960
<v Speaker 1>of those paid UH pads and you touch it to

0:09:25.080 --> 0:09:28.880
<v Speaker 1>that the pad can read that of course. UM. You know,

0:09:29.160 --> 0:09:32.600
<v Speaker 1>basically it's as far as you know, it's not electronic

0:09:32.760 --> 0:09:35.160
<v Speaker 1>or anything like that. It doesn't have you know, need

0:09:35.160 --> 0:09:38.920
<v Speaker 1>a battery or anything to operate. UM. So it's it,

0:09:39.080 --> 0:09:42.800
<v Speaker 1>but it's essentially always on. There's nothing keeping it from

0:09:42.880 --> 0:09:44.880
<v Speaker 1>being read at any time, which is one of the

0:09:45.400 --> 0:09:49.160
<v Speaker 1>criticisms people have of R f i D chips, and

0:09:49.400 --> 0:09:52.200
<v Speaker 1>as Jonathan was saying, he's got apparently he carries a

0:09:52.240 --> 0:09:55.720
<v Speaker 1>Faraday cage in his wallet. It's a it's it's a

0:09:55.760 --> 0:09:59.480
<v Speaker 1>special case that has r f i D blocking material,

0:10:00.240 --> 0:10:03.000
<v Speaker 1>or not r f i D blocking material, but blocks

0:10:03.080 --> 0:10:06.360
<v Speaker 1>radio frequencies. Right, So if somebody had something that could

0:10:06.800 --> 0:10:09.880
<v Speaker 1>if he weren't carrying that, and somebody had something that

0:10:09.920 --> 0:10:13.000
<v Speaker 1>could pick up an r f i D chip near enough,

0:10:13.520 --> 0:10:15.960
<v Speaker 1>and they just you know, bumped into him in public,

0:10:16.000 --> 0:10:19.360
<v Speaker 1>say like a pickpocket might, except without having to pick

0:10:19.400 --> 0:10:22.520
<v Speaker 1>his pocket, they could read the number off of the card. Um.

0:10:22.559 --> 0:10:25.600
<v Speaker 1>I also find that having r f i D chips,

0:10:25.679 --> 0:10:28.560
<v Speaker 1>multiple r f i D chips in my wallet will

0:10:28.679 --> 0:10:34.840
<v Speaker 1>interfere with things like the UH rapid transit system in Atlanta.

0:10:34.920 --> 0:10:37.000
<v Speaker 1>If you have another r f i D chip, it

0:10:37.080 --> 0:10:40.160
<v Speaker 1>will you know, they'll the two signals will cancel each

0:10:40.160 --> 0:10:44.240
<v Speaker 1>other out and say I can't read that the wallet. Um,

0:10:44.280 --> 0:10:46.960
<v Speaker 1>that's annoying. It's so irritating having to go all the

0:10:47.000 --> 0:10:48.760
<v Speaker 1>way to taking a card out of your wallet to

0:10:48.800 --> 0:10:50.800
<v Speaker 1>tap against the little circle so that you can go

0:10:50.840 --> 0:10:55.079
<v Speaker 1>in and ride public transportation. Such an inconvenience, But in goodness,

0:10:55.080 --> 0:11:00.000
<v Speaker 1>we got rid of that token system. But in contrast, UM,

0:11:00.080 --> 0:11:03.040
<v Speaker 1>the near field communication system can be turned on and off,

0:11:03.200 --> 0:11:07.520
<v Speaker 1>and there is a transceiver built into UH the NFC

0:11:07.679 --> 0:11:10.760
<v Speaker 1>enabled phones in this case the nexus S that will

0:11:10.760 --> 0:11:14.199
<v Speaker 1>allow you to transmit that information, so it can be

0:11:14.360 --> 0:11:17.959
<v Speaker 1>you can turn it off essentially. UM, now you can

0:11:18.000 --> 0:11:21.640
<v Speaker 1>have and you can have a passive NFC system where

0:11:21.840 --> 0:11:24.160
<v Speaker 1>where one element is just like with r F I D,

0:11:24.280 --> 0:11:26.760
<v Speaker 1>where one element is is active and then the other

0:11:26.800 --> 0:11:30.040
<v Speaker 1>one is passive. But in the case of smartphones we're

0:11:30.040 --> 0:11:32.880
<v Speaker 1>talking about and both both parts are active. And then

0:11:32.880 --> 0:11:35.199
<v Speaker 1>you say, all right, well enough about this, how does

0:11:35.200 --> 0:11:40.200
<v Speaker 1>it actually work? All right? Well, uses inductive coupling. Really, yeah,

0:11:40.360 --> 0:11:43.480
<v Speaker 1>so we're talking inducing electricity. And if you guys have

0:11:43.520 --> 0:11:45.240
<v Speaker 1>been listening to tech stuff for a while, you know

0:11:45.280 --> 0:11:48.280
<v Speaker 1>we've talked about this in multiple episodes and including some

0:11:48.320 --> 0:11:52.719
<v Speaker 1>of our Basic Electronics episodes and others. So induction, we're

0:11:52.760 --> 0:11:58.600
<v Speaker 1>talking about that wonderful relationship between electric electricity and magnetic fields.

0:11:58.840 --> 0:12:02.640
<v Speaker 1>So electric fields and the magnetic fields, and so what's

0:12:02.679 --> 0:12:06.960
<v Speaker 1>happening with U NFC is that it's you have at

0:12:07.040 --> 0:12:10.560
<v Speaker 1>least one element that's producing magnetic field and then you

0:12:10.600 --> 0:12:13.559
<v Speaker 1>have another element that has a coil of wire in it.

0:12:14.040 --> 0:12:17.400
<v Speaker 1>And when you pass that that chip that has the

0:12:17.440 --> 0:12:21.120
<v Speaker 1>coil of wire in it next or through that magnetic field,

0:12:21.800 --> 0:12:24.920
<v Speaker 1>it alters the magnetic field, all right, and it alters

0:12:24.920 --> 0:12:26.880
<v Speaker 1>it in such a way depending upon the coil of

0:12:26.880 --> 0:12:30.439
<v Speaker 1>wire that's in that chip and other elements. It manipulates

0:12:30.440 --> 0:12:32.880
<v Speaker 1>that magnetic field in such a way that something that

0:12:33.160 --> 0:12:37.240
<v Speaker 1>electricity flows through that active element and then whatever is

0:12:37.280 --> 0:12:41.760
<v Speaker 1>supposed to happen theoretically happens. So yeah, exactly. So example,

0:12:41.760 --> 0:12:44.719
<v Speaker 1>for example, if it's a locked door and it has

0:12:44.800 --> 0:12:48.360
<v Speaker 1>an electric lock that is producing this, it's using near

0:12:48.400 --> 0:12:51.720
<v Speaker 1>field communication. UM. You have the little pad on the

0:12:51.720 --> 0:12:55.000
<v Speaker 1>door that is actively generating this magnetic field. You pass

0:12:55.080 --> 0:12:58.600
<v Speaker 1>your key fob through that magnetic field. It registers that

0:12:58.720 --> 0:13:03.280
<v Speaker 1>as the correct uh kind of alteration of that mannetic

0:13:03.320 --> 0:13:05.960
<v Speaker 1>field that corresponds to this person has a key to

0:13:06.080 --> 0:13:09.920
<v Speaker 1>this office and it will unlock. Now with the smartphones,

0:13:09.920 --> 0:13:13.320
<v Speaker 1>you've got the two different magnetic fields that are being generated,

0:13:13.720 --> 0:13:16.640
<v Speaker 1>and that's where you can have this communication passed between

0:13:16.679 --> 0:13:21.000
<v Speaker 1>the two where essentially you have one asking for identification

0:13:21.040 --> 0:13:24.640
<v Speaker 1>and the other one UM making sure that registers that

0:13:24.800 --> 0:13:27.240
<v Speaker 1>it's an actual payment. You know, you have to have

0:13:27.280 --> 0:13:30.120
<v Speaker 1>this work on both sides for this to to take place.

0:13:30.520 --> 0:13:33.559
<v Speaker 1>So um and just in case you're curious, the data

0:13:33.679 --> 0:13:39.440
<v Speaker 1>rates that can transfer between two devices in an NFC system, Uh,

0:13:39.640 --> 0:13:43.200
<v Speaker 1>there are three different data rates that are possible. And

0:13:43.240 --> 0:13:45.640
<v Speaker 1>when you hear how what the speeds are, you gonna think, wow,

0:13:45.679 --> 0:13:49.240
<v Speaker 1>that's pretty slow compared to like an Internet connection, like

0:13:49.280 --> 0:13:52.640
<v Speaker 1>a broadband Internet connection a hundred six killabits per second,

0:13:52.920 --> 0:13:56.400
<v Speaker 1>two twelve kilabits per second, and four four killa bits

0:13:56.440 --> 0:13:58.120
<v Speaker 1>per second. But you gotta keep in mind that the

0:13:58.120 --> 0:14:01.680
<v Speaker 1>amount of information that's being transferred here minuscule. Yes, you know,

0:14:01.720 --> 0:14:06.760
<v Speaker 1>you're talking about some sort of identification, credit card information, um,

0:14:06.800 --> 0:14:09.679
<v Speaker 1>and that's it really and well, purchase price or whatever.

0:14:10.559 --> 0:14:13.240
<v Speaker 1>But it's tiny in comparison to the amount of data

0:14:13.280 --> 0:14:15.560
<v Speaker 1>you get even just loading up a basic web page.

0:14:15.840 --> 0:14:18.960
<v Speaker 1>So you don't really need a super fast data transfer

0:14:19.080 --> 0:14:24.239
<v Speaker 1>rate in order for this to work. So the smartphones

0:14:24.280 --> 0:14:27.760
<v Speaker 1>are using this NFC technology, and the the vendors have

0:14:27.880 --> 0:14:29.880
<v Speaker 1>to use it as well. I mean, obviously, even if

0:14:29.920 --> 0:14:31.960
<v Speaker 1>you've got Google Wallet and you walk into a store,

0:14:31.960 --> 0:14:33.920
<v Speaker 1>there's no guarantee you can use your phone to pay

0:14:33.960 --> 0:14:36.720
<v Speaker 1>for whatever you're buying, the vendor has to also have

0:14:37.440 --> 0:14:40.720
<v Speaker 1>their half of the system in place, right, So yeah,

0:14:40.760 --> 0:14:42.480
<v Speaker 1>you can't just walk up to a cashier and wave

0:14:42.520 --> 0:14:44.800
<v Speaker 1>your phone around and it will pay for it. You

0:14:44.880 --> 0:14:48.320
<v Speaker 1>might get some funny looks or be politely asked to leave,

0:14:48.440 --> 0:14:52.240
<v Speaker 1>or maybe not politely asked to leave. Well, um it does.

0:14:52.320 --> 0:14:58.520
<v Speaker 1>If you've seen the MasterCard pay pass system, UM, then

0:14:58.880 --> 0:15:01.040
<v Speaker 1>there there are actually play says. There's a on the

0:15:01.080 --> 0:15:05.960
<v Speaker 1>Google Wallet UM information site. There is a way to

0:15:06.040 --> 0:15:09.480
<v Speaker 1>look up whether or not they're Google Wallet merchants in

0:15:09.480 --> 0:15:12.880
<v Speaker 1>your area. And basically any place that has that system

0:15:13.040 --> 0:15:17.400
<v Speaker 1>already in place, that system will interact with Google Wallet

0:15:17.480 --> 0:15:20.520
<v Speaker 1>or is this it's supposed to? Um? Plus, there are

0:15:20.560 --> 0:15:22.280
<v Speaker 1>other places to a lot of the stores that you

0:15:22.320 --> 0:15:25.480
<v Speaker 1>might find the malls here UM in the United States,

0:15:25.520 --> 0:15:29.080
<v Speaker 1>and some restaurants UM. You know, places like blooming Gale's

0:15:29.680 --> 0:15:34.960
<v Speaker 1>or American Eagle, Macy's, um Arby's. Yeah, that's true because

0:15:35.000 --> 0:15:38.120
<v Speaker 1>I actually went. Uh. If you go to to Google's

0:15:38.160 --> 0:15:40.920
<v Speaker 1>pages on this, they have a little section where you

0:15:40.920 --> 0:15:43.000
<v Speaker 1>can type in your zip code and see what what

0:15:43.160 --> 0:15:48.760
<v Speaker 1>stores nearby are. UM have that that option and so

0:15:48.800 --> 0:15:51.520
<v Speaker 1>I checked for our office just out of curiosity and

0:15:51.560 --> 0:15:54.400
<v Speaker 1>saw that there was an Arby's. And uh, it's interesting

0:15:54.400 --> 0:15:56.960
<v Speaker 1>because we actually have a couple of really large malls

0:15:57.560 --> 0:16:00.440
<v Speaker 1>near our office, and I didn't see a lot of

0:16:00.480 --> 0:16:03.800
<v Speaker 1>stores in those malls that had adopted us. Now. Granted,

0:16:04.600 --> 0:16:07.760
<v Speaker 1>even though this technology, again the technology itself is not new,

0:16:08.120 --> 0:16:11.640
<v Speaker 1>the product and the service are very new. Uh so

0:16:11.680 --> 0:16:13.920
<v Speaker 1>it's not a huge surprise that there's not a widespread

0:16:13.960 --> 0:16:17.520
<v Speaker 1>adoption yet. But what is interesting to me his Eric

0:16:17.560 --> 0:16:22.600
<v Speaker 1>Schmidt has said that he believes within a year there

0:16:22.600 --> 0:16:25.480
<v Speaker 1>will be widespread adoption. So, based upon the recording of

0:16:25.480 --> 0:16:29.400
<v Speaker 1>this podcast within by June two thousand and twelve, Schmidt

0:16:29.480 --> 0:16:34.120
<v Speaker 1>expects that this NFC approach to paying for goods and

0:16:34.200 --> 0:16:38.520
<v Speaker 1>services will be widespread. I'm holding him to that. It

0:16:38.560 --> 0:16:43.120
<v Speaker 1>would be nice. I mean, especially again we'll get back

0:16:43.160 --> 0:16:45.760
<v Speaker 1>to the offers and everything with Google Wallet to talk

0:16:45.800 --> 0:16:50.600
<v Speaker 1>about how you know that adds value to their their service. Um,

0:16:50.640 --> 0:16:54.360
<v Speaker 1>but uh, I mean it would be nice to know

0:16:54.440 --> 0:16:57.240
<v Speaker 1>that we are no longer kind of in the the

0:16:57.280 --> 0:17:02.200
<v Speaker 1>relatively dark agents technologically speaking, compared to like Japan. I

0:17:02.240 --> 0:17:04.000
<v Speaker 1>know I keep bringing that up, but I mean Japan

0:17:04.119 --> 0:17:06.399
<v Speaker 1>is light years ahead of us as far as the

0:17:06.480 --> 0:17:10.879
<v Speaker 1>mobile technology goes, you know, I mean they're we're catching

0:17:10.960 --> 0:17:14.000
<v Speaker 1>up definitely. And I know that the iPhone is has

0:17:14.320 --> 0:17:17.920
<v Speaker 1>become popular in Japan as well, So it's not like, uh,

0:17:18.000 --> 0:17:20.080
<v Speaker 1>you know they look at our our brand new toys

0:17:20.119 --> 0:17:27.800
<v Speaker 1>and say, man, that was cool five years ago. Well, um, well,

0:17:27.840 --> 0:17:29.600
<v Speaker 1>that's something I want to talk about in a minute.

0:17:29.600 --> 0:17:31.359
<v Speaker 1>There I wanted to bring up before we got away

0:17:31.359 --> 0:17:35.399
<v Speaker 1>from too far away from how it works. I feel

0:17:35.400 --> 0:17:38.000
<v Speaker 1>compelled to point out that there is another step. You

0:17:38.000 --> 0:17:41.879
<v Speaker 1>don't just tap your phone to the pad and you know,

0:17:41.960 --> 0:17:44.560
<v Speaker 1>say thank you very much, here's your receipt. There is

0:17:44.560 --> 0:17:48.040
<v Speaker 1>another step. Now you you might be wondering, uh, you know,

0:17:48.119 --> 0:17:50.480
<v Speaker 1>how does it know it's me? You have to enter

0:17:50.520 --> 0:17:53.840
<v Speaker 1>a pin on your phone. Your phone has to be

0:17:53.960 --> 0:17:56.320
<v Speaker 1>on if it if it is off, if you've run

0:17:56.320 --> 0:17:59.200
<v Speaker 1>out of battery, you've run out of cash or not cash.

0:17:59.240 --> 0:18:01.760
<v Speaker 1>But you know, um yeah, you can't usually can't use

0:18:01.800 --> 0:18:04.800
<v Speaker 1>it anymore because it's got to be able to receive

0:18:04.800 --> 0:18:07.560
<v Speaker 1>a signal. Now you don't have to have a a

0:18:07.640 --> 0:18:10.640
<v Speaker 1>phone signal where you are. So you're in a really

0:18:10.680 --> 0:18:14.400
<v Speaker 1>giant mall um away from a tower, and you're way

0:18:14.400 --> 0:18:16.240
<v Speaker 1>from a tower and you can't get a signal. Why,

0:18:16.240 --> 0:18:18.200
<v Speaker 1>I can't imagine the mall that wouldn't have its self.

0:18:19.040 --> 0:18:22.359
<v Speaker 1>But there's there are places. There are places near where

0:18:22.359 --> 0:18:24.480
<v Speaker 1>I live that are right around the corner where I live,

0:18:24.560 --> 0:18:27.159
<v Speaker 1>and there are certain stores that if you go into it,

0:18:27.160 --> 0:18:29.320
<v Speaker 1>it's like they've built a fair day cage around that

0:18:29.359 --> 0:18:32.399
<v Speaker 1>store because you can't your signal drops like a like

0:18:32.400 --> 0:18:34.879
<v Speaker 1>like a like a stone, like like something that drops

0:18:34.960 --> 0:18:37.399
<v Speaker 1>very like something that it hung in the air, the

0:18:37.440 --> 0:18:42.000
<v Speaker 1>same way bricks. Don't I love that? Um? But yeah,

0:18:42.280 --> 0:18:44.399
<v Speaker 1>you have to you have to be able to identify yourself.

0:18:44.480 --> 0:18:46.400
<v Speaker 1>The phone has to be on for you to complete

0:18:46.440 --> 0:18:50.280
<v Speaker 1>the transaction. UM. As a matter of fact, the uh,

0:18:50.320 --> 0:18:53.000
<v Speaker 1>the information is stored in something that Google is calling

0:18:53.160 --> 0:18:56.920
<v Speaker 1>the Secure Elements. Yes, it's not. It's not connected directly

0:18:56.960 --> 0:19:00.000
<v Speaker 1>to the Android processing chip. That was a very important

0:19:00.440 --> 0:19:03.040
<v Speaker 1>part of Google's presentation. They wanted to make sure that

0:19:03.160 --> 0:19:06.200
<v Speaker 1>everyone understood the what measures they had taken to ensure

0:19:06.280 --> 0:19:08.920
<v Speaker 1>security of this, because you know you could you could

0:19:09.600 --> 0:19:14.280
<v Speaker 1>clearly any time you're talking about transmitting data wirelessly. There's

0:19:14.280 --> 0:19:17.280
<v Speaker 1>this whole fear that there's a way that that data

0:19:17.320 --> 0:19:20.360
<v Speaker 1>could get leaked and compromised. And of course we all

0:19:20.400 --> 0:19:24.840
<v Speaker 1>know that you don't have to transmit data wirelessly in

0:19:24.960 --> 0:19:27.800
<v Speaker 1>order for your information to be compromised. I know this

0:19:27.960 --> 0:19:33.520
<v Speaker 1>from recent personal experience. But um, but any time that

0:19:33.840 --> 0:19:38.760
<v Speaker 1>you see that that medium of exchange, that's one of

0:19:38.760 --> 0:19:41.359
<v Speaker 1>the concerns you have, right. So, yeah, the secure element

0:19:41.520 --> 0:19:47.800
<v Speaker 1>is is completely separate from the Android processor and the

0:19:47.920 --> 0:19:53.400
<v Speaker 1>apps that Google walad app does not directly um access

0:19:53.480 --> 0:19:56.560
<v Speaker 1>the secure element. So, in other words, they wanted to

0:19:56.560 --> 0:19:59.040
<v Speaker 1>make sure that if you were to, say, lose your phone,

0:19:59.400 --> 0:20:02.600
<v Speaker 1>that getting hold of your credit card information would not

0:20:02.760 --> 0:20:05.320
<v Speaker 1>be an easy thing to do. Now, that's not to

0:20:05.359 --> 0:20:09.440
<v Speaker 1>say that some enterprising hacker couldn't figure out a way

0:20:09.440 --> 0:20:11.680
<v Speaker 1>to do it. So even if you were to lose

0:20:11.720 --> 0:20:16.200
<v Speaker 1>your phone, the Google stresses that you should immediately contact

0:20:16.240 --> 0:20:18.960
<v Speaker 1>your your bank or other financial institution, or to change

0:20:18.960 --> 0:20:21.440
<v Speaker 1>your credit cards, canceled them out and get new ones,

0:20:21.520 --> 0:20:24.840
<v Speaker 1>because you know, you never want to just entrust and

0:20:25.080 --> 0:20:28.720
<v Speaker 1>say that something is completely secure from all possible attacks.

0:20:28.960 --> 0:20:33.280
<v Speaker 1>Because we all learned a lesson from Titanic, well, Uly

0:20:33.400 --> 0:20:39.320
<v Speaker 1>Leonardo DiCaprio is dreamy well, and in the case of

0:20:39.600 --> 0:20:43.480
<v Speaker 1>the uh nexus s the secure element is an n

0:20:43.600 --> 0:20:46.960
<v Speaker 1>x p p N six K chip. I'll sure give

0:20:47.000 --> 0:20:50.159
<v Speaker 1>it away now everyone knows. According to Clinton Bolton from

0:20:50.280 --> 0:20:55.040
<v Speaker 1>E Week, UM and yeah, lest you think, as I

0:20:55.080 --> 0:20:59.400
<v Speaker 1>saw in comments on his article, UM, that we are

0:20:59.600 --> 0:21:05.240
<v Speaker 1>necessary early spreading fear, uncertainly, uncertainty and doubt, all otherwise

0:21:05.240 --> 0:21:08.720
<v Speaker 1>known as fud UM. I just I feel compelled to

0:21:08.760 --> 0:21:12.680
<v Speaker 1>report um as other people did. I saw this person

0:21:12.800 --> 0:21:17.840
<v Speaker 1>quoted a couple of times UM McAfee security expert UM

0:21:17.960 --> 0:21:23.040
<v Speaker 1>Jimmy Shaw, who basically was saying that based on what

0:21:23.119 --> 0:21:26.040
<v Speaker 1>he knows the system, it's not that the system isn't

0:21:26.080 --> 0:21:29.800
<v Speaker 1>designed with security in place, he you know, so much

0:21:29.840 --> 0:21:33.520
<v Speaker 1>as he thinks that it might be possible to take

0:21:33.600 --> 0:21:38.280
<v Speaker 1>the authentication key from the Google Wallet application itself and

0:21:39.240 --> 0:21:43.720
<v Speaker 1>uh rite an application that will allow somebody to fool

0:21:43.760 --> 0:21:47.080
<v Speaker 1>the secure element into giving up what it has. It's

0:21:47.080 --> 0:21:50.600
<v Speaker 1>not the secure element that he sees as the weak

0:21:50.840 --> 0:21:56.080
<v Speaker 1>link the app as being reverse engineer able to get

0:21:56.160 --> 0:21:59.520
<v Speaker 1>at whatever the you know your PIN number and just

0:22:00.000 --> 0:22:05.159
<v Speaker 1>it yes, sorry, you know pin? Actually the end of

0:22:05.160 --> 0:22:09.840
<v Speaker 1>the personal number, the personal identification number number, UH your

0:22:09.880 --> 0:22:14.600
<v Speaker 1>Windows phone. Now we're talking to Android I'm sorry. Yes, yeah,

0:22:14.840 --> 0:22:20.120
<v Speaker 1>they basically they feel that it's possible to do that. Now, um, yes,

0:22:20.200 --> 0:22:22.760
<v Speaker 1>you could say that Google has gone to a lot

0:22:22.760 --> 0:22:25.639
<v Speaker 1>of trouble to ensure that it's not going to be

0:22:25.720 --> 0:22:28.800
<v Speaker 1>easy to make this happen. Um and and and people

0:22:29.720 --> 0:22:34.040
<v Speaker 1>uh who like this idea are probably saying no, you're

0:22:34.080 --> 0:22:37.480
<v Speaker 1>just saying this, and it's it's very unlikely. Yes, it's unlikely,

0:22:38.240 --> 0:22:41.199
<v Speaker 1>but it's possible. It's a good idea to keep that

0:22:41.240 --> 0:22:45.520
<v Speaker 1>in mind. Just like any bank, it's possible that it

0:22:45.520 --> 0:22:49.600
<v Speaker 1>could get robbed. It's likely, but it's possible, and it's

0:22:49.640 --> 0:22:52.359
<v Speaker 1>possible you could have your card skimmed when you go

0:22:52.480 --> 0:22:56.359
<v Speaker 1>to a machine or that it is very possible, and

0:22:56.600 --> 0:22:58.560
<v Speaker 1>you know that there might be a very tiny camera

0:22:58.680 --> 0:23:05.320
<v Speaker 1>recording your movements that you so anyway the but but

0:23:05.480 --> 0:23:07.719
<v Speaker 1>also we should keep in mind that Android phones have

0:23:08.200 --> 0:23:12.720
<v Speaker 1>um have optional or locking systems on them as well.

0:23:12.800 --> 0:23:15.359
<v Speaker 1>So that's as a second level of security, which is

0:23:15.600 --> 0:23:17.960
<v Speaker 1>separate from the Google wallet. Like that's just so that

0:23:18.000 --> 0:23:19.600
<v Speaker 1>you can use your phone. So for example, if you

0:23:19.640 --> 0:23:21.720
<v Speaker 1>were to pick up my phone, you would find out

0:23:21.760 --> 0:23:25.199
<v Speaker 1>that there is a security code that you would need

0:23:25.240 --> 0:23:27.600
<v Speaker 1>to enter in order to access my phone. Now, yes,

0:23:27.880 --> 0:23:29.840
<v Speaker 1>there are ways of getting around that if you know

0:23:29.880 --> 0:23:33.040
<v Speaker 1>how to hack the phone properly. But again it's that

0:23:33.280 --> 0:23:38.280
<v Speaker 1>level of security that discourages you know, a major percentage

0:23:38.280 --> 0:23:40.639
<v Speaker 1>of the people who would otherwise try and take advantage

0:23:40.760 --> 0:23:45.680
<v Speaker 1>of finding your phone. So you know, no security system

0:23:45.720 --> 0:23:47.520
<v Speaker 1>is gonna be perfect, but you try and make it

0:23:47.520 --> 0:23:52.600
<v Speaker 1>strong enough so that the cases are our failures. And

0:23:52.640 --> 0:23:55.359
<v Speaker 1>then again, as I said before, Google does stress that

0:23:55.440 --> 0:23:58.679
<v Speaker 1>you have to let your financial institutions know so that

0:23:58.720 --> 0:24:00.399
<v Speaker 1>you can you can make sure that no one can

0:24:00.480 --> 0:24:04.320
<v Speaker 1>use that card against you. Um. And also they have

0:24:04.359 --> 0:24:07.240
<v Speaker 1>an element in place where it prevents you from creating

0:24:07.240 --> 0:24:10.479
<v Speaker 1>a week password or a weak pen. Yeah, so if

0:24:10.480 --> 0:24:12.680
<v Speaker 1>you were to try doing one one one one as

0:24:12.720 --> 0:24:14.560
<v Speaker 1>your pen so that you wouldn't have to remember it

0:24:14.600 --> 0:24:18.479
<v Speaker 1>whenever you're using Google Wallet, it will reject that and

0:24:18.520 --> 0:24:20.359
<v Speaker 1>make you choose something that's not going to be the

0:24:20.400 --> 0:24:24.600
<v Speaker 1>same digit four times or four sequential digits either up

0:24:24.680 --> 0:24:30.160
<v Speaker 1>or down. That kind of thing. Tony Bradley is sorry,

0:24:30.200 --> 0:24:33.199
<v Speaker 1>Tony Tony Bradley of PC World, Um, it sounds like

0:24:33.240 --> 0:24:36.119
<v Speaker 1>you may have read the same article because it's um

0:24:36.160 --> 0:24:40.479
<v Speaker 1>this one also quoted Jimmy Shaw, uh but um he

0:24:40.560 --> 0:24:45.000
<v Speaker 1>had Bradley spoken with Google specifically about some of these things,

0:24:45.200 --> 0:24:48.640
<v Speaker 1>and Google said that Google Wallet itself does not have

0:24:48.880 --> 0:24:53.479
<v Speaker 1>access to the credit card information uh in the secure element.

0:24:54.440 --> 0:24:58.120
<v Speaker 1>Um so you know, basically they you know, they're they're

0:24:58.160 --> 0:25:00.679
<v Speaker 1>stressing that it really is a secure way of doing this.

0:25:00.760 --> 0:25:04.520
<v Speaker 1>Plus the uh uh. They added that the transceiver is

0:25:04.560 --> 0:25:08.439
<v Speaker 1>off if your your phone screen is off. So as

0:25:08.480 --> 0:25:10.160
<v Speaker 1>long as your screen is off, it is not there's

0:25:10.200 --> 0:25:13.760
<v Speaker 1>no way that it's supposed to be able to transmit information.

0:25:13.760 --> 0:25:17.680
<v Speaker 1>And near field communication works over very short distances. We're

0:25:17.720 --> 0:25:23.720
<v Speaker 1>talking like centimeters so um so, so intercepting that would

0:25:23.720 --> 0:25:28.040
<v Speaker 1>be difficult unless you know everyone's really buddy buddy in

0:25:28.080 --> 0:25:32.760
<v Speaker 1>the stores you're shopping right right. So I do think, um,

0:25:32.800 --> 0:25:36.280
<v Speaker 1>I do think they've put some some good security measures

0:25:36.320 --> 0:25:40.000
<v Speaker 1>in place. I like any kind of electronic transaction, I

0:25:40.040 --> 0:25:44.520
<v Speaker 1>think there's probably some risk involved. There's there's no fail

0:25:44.640 --> 0:25:48.080
<v Speaker 1>proof system out there. But I would say that again

0:25:48.240 --> 0:25:51.520
<v Speaker 1>it I would say that just because yes, there's an

0:25:51.560 --> 0:25:55.399
<v Speaker 1>element where there's a element of risk there, but it's tiny,

0:25:55.840 --> 0:25:58.120
<v Speaker 1>just like there's an element of risk in every kind

0:25:58.160 --> 0:26:01.360
<v Speaker 1>of transaction. You can do yeah, and you know, keep

0:26:01.400 --> 0:26:05.880
<v Speaker 1>in mind that anything that isn't an electronic transfer has

0:26:05.920 --> 0:26:08.200
<v Speaker 1>its own element of risk to it. It may be

0:26:08.400 --> 0:26:12.520
<v Speaker 1>different from the electronic version, but it's still there. So

0:26:12.960 --> 0:26:16.160
<v Speaker 1>no no system is perfect. Even we we found out

0:26:16.760 --> 0:26:20.920
<v Speaker 1>just this week that topic that we recently talked about bitcoin,

0:26:21.520 --> 0:26:23.760
<v Speaker 1>people have been stealing bitcoin. Yeah. I actually did an

0:26:23.840 --> 0:26:27.199
<v Speaker 1>update for our bitcoin podcast because of that. Yes, so

0:26:27.240 --> 0:26:30.400
<v Speaker 1>you'll be hearing. Actually you've already heard that. So when

0:26:30.400 --> 0:26:33.880
<v Speaker 1>you when you unless something has gone terribly wrong, you've

0:26:33.880 --> 0:26:36.560
<v Speaker 1>heard our bitcoin episode and so you will have heard

0:26:36.600 --> 0:26:39.600
<v Speaker 1>the update that I gave at the end of it. Um,

0:26:39.640 --> 0:26:43.600
<v Speaker 1>So did you want to talk about the offers? Yeah,

0:26:43.640 --> 0:26:46.000
<v Speaker 1>I want to talk with very briefly about Google Offers.

0:26:46.000 --> 0:26:50.359
<v Speaker 1>So Google Offers is kind of Google's answer to things

0:26:50.400 --> 0:26:54.480
<v Speaker 1>like group on, scout Mob. There are other lots of

0:26:54.600 --> 0:26:57.720
<v Speaker 1>living social, There are a lot of other services out

0:26:57.720 --> 0:27:02.439
<v Speaker 1>there that offer deals or cop ponds for specific goods

0:27:02.440 --> 0:27:05.840
<v Speaker 1>and services. And these are awesome, right, you know, you

0:27:05.880 --> 0:27:08.879
<v Speaker 1>get this this deal and maybe it's uh, you know,

0:27:08.920 --> 0:27:11.280
<v Speaker 1>it's maybe it's a place that you've never been before

0:27:11.280 --> 0:27:13.000
<v Speaker 1>and you want to check it out. Maybe it's a

0:27:13.040 --> 0:27:15.520
<v Speaker 1>place you go to all the time, and you want

0:27:15.560 --> 0:27:18.040
<v Speaker 1>to be able to use the offer towards some sort

0:27:18.080 --> 0:27:22.360
<v Speaker 1>of goods or service um or maybe you never would

0:27:22.359 --> 0:27:24.320
<v Speaker 1>have thought to go there at all, but this has

0:27:24.359 --> 0:27:28.920
<v Speaker 1>convinced you too, because the deal is just so darn good. Um. Well,

0:27:29.400 --> 0:27:31.800
<v Speaker 1>in most cases with this kind of thing, you you,

0:27:32.040 --> 0:27:34.960
<v Speaker 1>especially if it's a mobile app, you get some sort

0:27:35.119 --> 0:27:39.359
<v Speaker 1>of deal that you have to show at whatever the

0:27:39.440 --> 0:27:42.240
<v Speaker 1>vendor is, you know, whoever is, whoever is offering the

0:27:42.280 --> 0:27:46.520
<v Speaker 1>goods or services. So let's say, for example, I can

0:27:46.560 --> 0:27:50.320
<v Speaker 1>give a specific example. I used a a h an

0:27:50.320 --> 0:27:55.280
<v Speaker 1>app to get discount tickets to a local theater, and

0:27:55.400 --> 0:27:58.800
<v Speaker 1>the stage theater, not a movie theater, And so I

0:27:58.840 --> 0:28:00.840
<v Speaker 1>went to the theater and then I had to pull

0:28:00.920 --> 0:28:03.720
<v Speaker 1>up the app and show that I had activated that

0:28:03.760 --> 0:28:06.639
<v Speaker 1>particular offer, and I showed it at the door and

0:28:06.680 --> 0:28:10.480
<v Speaker 1>they applied the discount and then I got my tickets. Well,

0:28:11.000 --> 0:28:15.080
<v Speaker 1>with Google offers partnered with Google Wallet, it's not always

0:28:15.080 --> 0:28:16.199
<v Speaker 1>going to be the case, because you know, you have

0:28:16.280 --> 0:28:18.760
<v Speaker 1>to have the vendor using the system too. But let's

0:28:18.760 --> 0:28:21.280
<v Speaker 1>say that you have a Google offer for that particular place,

0:28:21.560 --> 0:28:24.960
<v Speaker 1>and you're using Google Wallet to pay for your whatever.

0:28:25.200 --> 0:28:26.800
<v Speaker 1>So let's say I'm going to the theater and they

0:28:26.800 --> 0:28:29.240
<v Speaker 1>have the system there. I could tap my phone to

0:28:29.320 --> 0:28:32.560
<v Speaker 1>that and it would automatically apply that coupon to the

0:28:32.600 --> 0:28:35.439
<v Speaker 1>purchase without me having to do a separate step of

0:28:35.480 --> 0:28:38.440
<v Speaker 1>showing the offer to someone else. And the same is

0:28:38.480 --> 0:28:42.000
<v Speaker 1>true again with the loyalty cards. So you might have

0:28:42.440 --> 0:28:45.600
<v Speaker 1>a particular place you go to a lot and uh,

0:28:45.840 --> 0:28:49.240
<v Speaker 1>you have your loyalty benefits, you have a coupon, and

0:28:49.280 --> 0:28:52.840
<v Speaker 1>you've got this uh, this Google Wallet system. All you

0:28:52.880 --> 0:28:55.680
<v Speaker 1>do is with one tap, you make your purchase and

0:28:55.720 --> 0:28:59.760
<v Speaker 1>everything is applied to that one uh, that one transaction.

0:29:00.280 --> 0:29:05.640
<v Speaker 1>And this is really a compelling service to me because

0:29:05.880 --> 0:29:09.360
<v Speaker 1>it simplifies everything, and you might even get to the

0:29:09.360 --> 0:29:12.560
<v Speaker 1>point where you're not even fully aware of all the

0:29:12.720 --> 0:29:17.000
<v Speaker 1>things that are looped in offers. So, for example, let's

0:29:17.000 --> 0:29:19.160
<v Speaker 1>say there are a lot of grocery stores that have

0:29:19.440 --> 0:29:24.280
<v Speaker 1>the loyalty cards, right, and you get certain deals when

0:29:24.320 --> 0:29:27.440
<v Speaker 1>you go shopping that other people who do who are

0:29:27.440 --> 0:29:29.520
<v Speaker 1>not part of the loyalty program, they don't have access

0:29:29.560 --> 0:29:32.080
<v Speaker 1>to those deals. And let's just say you're going on

0:29:32.160 --> 0:29:34.680
<v Speaker 1>a normal shopping trip and you're not even really paying

0:29:34.720 --> 0:29:37.280
<v Speaker 1>attention as you're purchasing your stuff. You know, you're getting

0:29:37.320 --> 0:29:39.760
<v Speaker 1>the brands you like, and you're getting whatever products you want,

0:29:39.960 --> 0:29:41.520
<v Speaker 1>and you go to check out and you tap your

0:29:41.560 --> 0:29:44.960
<v Speaker 1>phone and if there were any offers, that automatically gets

0:29:45.680 --> 0:29:49.400
<v Speaker 1>applied to whatever it was you were purchasing, and uh

0:29:49.480 --> 0:29:51.600
<v Speaker 1>and again it cuts down on the stuff you have

0:29:51.720 --> 0:29:54.920
<v Speaker 1>to remember to carry with you. So, for example, I

0:29:55.040 --> 0:29:59.800
<v Speaker 1>used my loyalty uh key fob things so much at

0:29:59.800 --> 0:30:03.040
<v Speaker 1>our grocery store that it eventually wore through and broke

0:30:03.080 --> 0:30:05.720
<v Speaker 1>off my key chain. And now I don't have it

0:30:05.760 --> 0:30:07.360
<v Speaker 1>with me all the time because I never bothered to

0:30:07.400 --> 0:30:09.200
<v Speaker 1>replace it because I was like, well, you know, it's

0:30:10.960 --> 0:30:15.520
<v Speaker 1>more walking. Yeah. I actually uh got an app from

0:30:15.520 --> 0:30:19.880
<v Speaker 1>my smartphone that has the ability to put the barcodes

0:30:19.920 --> 0:30:22.840
<v Speaker 1>on the screen. So theoretically you're supposed to just uh

0:30:22.840 --> 0:30:26.360
<v Speaker 1>scan your your phone screen in front of the thing

0:30:26.400 --> 0:30:28.479
<v Speaker 1>and it will read your loyalty card number. I can

0:30:28.480 --> 0:30:32.440
<v Speaker 1>tell you I think probably because of the screen protector

0:30:32.520 --> 0:30:35.960
<v Speaker 1>on my phone, I could never get it to read properly,

0:30:36.640 --> 0:30:39.040
<v Speaker 1>especially on the well on the youth scan lanes that

0:30:39.080 --> 0:30:41.440
<v Speaker 1>you know, I kind of nervous given your phone to

0:30:41.480 --> 0:30:44.200
<v Speaker 1>the cashier. But you know, on the youth scan thing. Well,

0:30:44.240 --> 0:30:46.160
<v Speaker 1>it's just me. I'm gonna get it, you know, right,

0:30:46.560 --> 0:30:49.360
<v Speaker 1>you know, I sat there for ten minutes. The people

0:30:49.400 --> 0:30:52.360
<v Speaker 1>were hitting me behind from behind with oranges and that

0:30:52.560 --> 0:30:54.920
<v Speaker 1>like the old the old days when they first got

0:30:54.960 --> 0:30:58.200
<v Speaker 1>the scanners, and the person would the cashier would scan something.

0:30:58.200 --> 0:31:00.800
<v Speaker 1>Nothing would happen. Scan it, nothing would happened. Scan it,

0:31:00.840 --> 0:31:03.560
<v Speaker 1>nothing would happen. Stop, look at the sticker, put it

0:31:03.600 --> 0:31:07.360
<v Speaker 1>back down, scan it, nothing would happen. Yeah, it's like that, um,

0:31:07.400 --> 0:31:13.320
<v Speaker 1>But a near field communication system would completely scanning, scanning, needing,

0:31:13.400 --> 0:31:15.680
<v Speaker 1>just need to get it close enough to and for vendors,

0:31:15.800 --> 0:31:18.280
<v Speaker 1>for vendors that are participating with Google Offers but are

0:31:18.320 --> 0:31:20.960
<v Speaker 1>not participating with Google Wallet, you would still do the

0:31:21.000 --> 0:31:23.440
<v Speaker 1>scanning thing, right. You would have to open up your

0:31:23.440 --> 0:31:27.640
<v Speaker 1>Google Offers part of your Google Wallet and show off, hey,

0:31:27.760 --> 0:31:31.280
<v Speaker 1>I've got this coupon. So you would still do it

0:31:31.360 --> 0:31:34.760
<v Speaker 1>the older way through that method. But if they are

0:31:34.960 --> 0:31:37.080
<v Speaker 1>working with the Google Wallet system, then again it's just

0:31:37.160 --> 0:31:39.800
<v Speaker 1>one tap and you go, I think it's a sorry

0:31:39.840 --> 0:31:41.640
<v Speaker 1>you were going to say something, Well, you can go

0:31:41.640 --> 0:31:43.480
<v Speaker 1>ahead and say that. I think it's all I was

0:31:43.520 --> 0:31:46.360
<v Speaker 1>just gonna say. I think it's an interesting product and

0:31:46.440 --> 0:31:49.480
<v Speaker 1>I think I think it has a lot of potential. Um,

0:31:49.520 --> 0:31:51.680
<v Speaker 1>I know that there are a lot of other companies

0:31:52.120 --> 0:31:56.600
<v Speaker 1>that are looking into similar ways of doing payments. You've

0:31:56.640 --> 0:31:59.360
<v Speaker 1>also got the other services like group on, You've got

0:31:59.360 --> 0:32:03.320
<v Speaker 1>services like Living Social. They're they're handling the offers side

0:32:03.320 --> 0:32:06.160
<v Speaker 1>of it. They're not necessarily partnered with the payment side

0:32:06.280 --> 0:32:09.840
<v Speaker 1>of it yet, although that may change. Yeah, that's exactly

0:32:09.880 --> 0:32:13.200
<v Speaker 1>where I was gonna go because American Express and UH

0:32:13.280 --> 0:32:17.000
<v Speaker 1>four square are currently working together. UM. Now these are

0:32:17.000 --> 0:32:20.080
<v Speaker 1>with the plastic card not you know, there's not an

0:32:20.080 --> 0:32:24.360
<v Speaker 1>electronic wallet, but you figure with American expresses clout UH,

0:32:24.400 --> 0:32:27.160
<v Speaker 1>they would easily be able to do this. And yeah,

0:32:27.200 --> 0:32:29.680
<v Speaker 1>I mean you it is the similar situation, just not

0:32:29.760 --> 0:32:32.360
<v Speaker 1>with your phone. If you go with you find the

0:32:32.440 --> 0:32:34.520
<v Speaker 1>deal on four square. When you're out someplace where you

0:32:34.640 --> 0:32:38.280
<v Speaker 1>check in UH and you have your American Express card

0:32:38.360 --> 0:32:42.320
<v Speaker 1>with you and you pay with it, it should automatically, um,

0:32:42.360 --> 0:32:44.320
<v Speaker 1>you know, give you the discount. And that's that's the

0:32:45.080 --> 0:32:47.400
<v Speaker 1>trial they ran out of south By Southwest. And there's

0:32:47.440 --> 0:32:50.160
<v Speaker 1>also a group on now, which is something they're doing

0:32:50.160 --> 0:32:52.080
<v Speaker 1>where it's trying to give you an instant offer rather

0:32:52.080 --> 0:32:55.320
<v Speaker 1>than something that you redeem later, which is traditionally how

0:32:55.480 --> 0:32:58.520
<v Speaker 1>a lot of these deals have worked. Um. And then

0:32:58.560 --> 0:33:00.880
<v Speaker 1>you've got you know, like we of the Nexus S

0:33:00.920 --> 0:33:03.520
<v Speaker 1>four G is on Sprint, and that's the only carrier

0:33:03.640 --> 0:33:07.240
<v Speaker 1>right now that is supporting this whole endeavor. Um. There

0:33:07.240 --> 0:33:09.920
<v Speaker 1>there's also talk that the other major carriers in the

0:33:10.000 --> 0:33:11.760
<v Speaker 1>United States, which of course our A, T and T,

0:33:11.920 --> 0:33:14.760
<v Speaker 1>T Mobile and Verizon, are all working on their own

0:33:15.000 --> 0:33:19.360
<v Speaker 1>NFC proprietary approach to payments, which means that we could

0:33:19.360 --> 0:33:25.320
<v Speaker 1>have a another sort of standards war to determine which

0:33:25.440 --> 0:33:30.400
<v Speaker 1>if any of the four come into uh prominence. And

0:33:30.760 --> 0:33:32.880
<v Speaker 1>you know, so it may be that it's it's a

0:33:32.960 --> 0:33:37.640
<v Speaker 1>divided market where it all depends upon which carrier is

0:33:38.520 --> 0:33:42.560
<v Speaker 1>in charge of your your cell phone plan. So yeah,

0:33:42.640 --> 0:33:45.400
<v Speaker 1>we're still gonna be kind of keeping an eye on this,

0:33:45.480 --> 0:33:48.800
<v Speaker 1>and you know, hopefully we're gonna have systems that will

0:33:48.800 --> 0:33:51.640
<v Speaker 1>go across all carriers so that it makes it simpler

0:33:51.680 --> 0:33:59.520
<v Speaker 1>for everybody. Right because assuming that the the scanning platforms,

0:33:59.640 --> 0:34:03.280
<v Speaker 1>the FC consoles where you tap the phone against it,

0:34:03.360 --> 0:34:08.040
<v Speaker 1>assuming they can read all the different variations of this, well,

0:34:08.040 --> 0:34:10.560
<v Speaker 1>then that would be fine, right because then it wouldn't matter,

0:34:10.719 --> 0:34:15.000
<v Speaker 1>like if the if the vendor end is agnostic toward

0:34:15.080 --> 0:34:17.880
<v Speaker 1>which platform you're using, that would be best. But if

0:34:17.920 --> 0:34:19.600
<v Speaker 1>you go there and you're like, I've got this on

0:34:19.640 --> 0:34:21.640
<v Speaker 1>my phone and you tap it. Oh wait, you're a

0:34:21.640 --> 0:34:24.719
<v Speaker 1>T Mobile customer. Sorry, we only we only use this

0:34:24.800 --> 0:34:29.720
<v Speaker 1>for Sprint, that would be very frustrating from a consumer standpoint,

0:34:29.880 --> 0:34:34.200
<v Speaker 1>to the point where you're like, what's the point of this. So, um,

0:34:34.239 --> 0:34:37.120
<v Speaker 1>it's early days yet, We'll have to see and and uh,

0:34:37.360 --> 0:34:40.560
<v Speaker 1>it's not that I hope that Google is triumphant and

0:34:40.680 --> 0:34:44.120
<v Speaker 1>gets that the total market share for this. Um. I

0:34:44.160 --> 0:34:46.200
<v Speaker 1>think the competition is a great thing. I just want

0:34:46.200 --> 0:34:48.719
<v Speaker 1>to make sure that the competition is such that it

0:34:48.760 --> 0:34:52.680
<v Speaker 1>doesn't hurt the consumer experience. So I want to make

0:34:52.719 --> 0:34:55.520
<v Speaker 1>that clear though, that I'm not trumpeting Google and saying

0:34:55.520 --> 0:34:58.719
<v Speaker 1>I hope that they crush everyone under the heel of

0:34:58.760 --> 0:35:03.840
<v Speaker 1>their enormous school colplex boot. Yeah it's uh, these boots

0:35:03.840 --> 0:35:07.840
<v Speaker 1>were made for Google. It's convenient enough, and people are

0:35:07.880 --> 0:35:11.640
<v Speaker 1>there certainly enough smartphones out there where I think the

0:35:12.040 --> 0:35:14.520
<v Speaker 1>market may be more ripe than it has been in

0:35:14.520 --> 0:35:18.000
<v Speaker 1>the past. Um, but I still think it will will

0:35:18.040 --> 0:35:22.360
<v Speaker 1>take some time. To catch on Bolton, who I mentioned

0:35:22.400 --> 0:35:27.280
<v Speaker 1>earlier from the week. Also, Uh in his article mentioned

0:35:27.320 --> 0:35:31.960
<v Speaker 1>that Uh, in addition to security concerns, he thinks that

0:35:32.080 --> 0:35:37.719
<v Speaker 1>it's possible that basically apathy consumer apathy will win out

0:35:37.840 --> 0:35:40.920
<v Speaker 1>and that none of the you know, Google wallet just

0:35:40.960 --> 0:35:44.399
<v Speaker 1>won't succeed in the long run. Um, I'm not so

0:35:44.440 --> 0:35:48.799
<v Speaker 1>sure that security or apathy are are gonna beat UM

0:35:48.880 --> 0:35:54.480
<v Speaker 1>the convenience of NFC unless there are just some horrific problems.

0:35:54.520 --> 0:35:56.440
<v Speaker 1>I mean, you know, with all of it, the hacking

0:35:56.480 --> 0:36:00.880
<v Speaker 1>that's been going on lately, with UM, everybody, with every buddy,

0:36:01.560 --> 0:36:04.200
<v Speaker 1>I just don't know that it's it's going to register.

0:36:04.680 --> 0:36:07.200
<v Speaker 1>You know, at this point, it may ultimately not matter

0:36:07.239 --> 0:36:11.000
<v Speaker 1>if you if you demonstrate that the financial systems aren't

0:36:11.160 --> 0:36:14.040
<v Speaker 1>secure on their end, that doesn't matter what you're carrying

0:36:14.040 --> 0:36:17.240
<v Speaker 1>in your wallet. Yeah, that's whether it's virtual or physical.

0:36:17.360 --> 0:36:19.640
<v Speaker 1>And I mean that's a scary thought. But we've already

0:36:19.680 --> 0:36:22.600
<v Speaker 1>seen it happen. You know, we've seen credit card companies

0:36:22.640 --> 0:36:25.879
<v Speaker 1>get attacked by hackers, and we've seen you know, other

0:36:25.920 --> 0:36:29.719
<v Speaker 1>companies that are not directly connected to financial institutions but

0:36:29.760 --> 0:36:33.000
<v Speaker 1>are indirectly connected. And that's the way in and so yeah,

0:36:33.080 --> 0:36:36.279
<v Speaker 1>it's a scary thing. But I mean and people who

0:36:36.320 --> 0:36:40.239
<v Speaker 1>have been able to decrypt a pin block um that

0:36:40.320 --> 0:36:43.360
<v Speaker 1>they've hacked, which which was at one time considered you know,

0:36:43.440 --> 0:36:46.360
<v Speaker 1>highly secure because you have the credit card number encrypt

0:36:46.440 --> 0:36:48.600
<v Speaker 1>or the debit card number encrypted plus the pin block

0:36:48.800 --> 0:36:52.440
<v Speaker 1>encrypted different separately, and they said, oh, yeah, well with

0:36:52.520 --> 0:36:55.279
<v Speaker 1>that level of security, you're not going to get it. Yeah,

0:36:55.400 --> 0:36:58.160
<v Speaker 1>they've found ways to get that. Ever, say that your

0:36:58.160 --> 0:37:01.320
<v Speaker 1>ship is unsinkable, so you can also get mugged on

0:37:01.360 --> 0:37:04.360
<v Speaker 1>the way to the have your cash taken from you.

0:37:04.440 --> 0:37:07.080
<v Speaker 1>So the message you should take from this episode is

0:37:07.120 --> 0:37:09.480
<v Speaker 1>the world is dangerous and they're all out to get you. So,

0:37:09.520 --> 0:37:11.520
<v Speaker 1>if you guys have any other topics you would like

0:37:11.600 --> 0:37:13.879
<v Speaker 1>us to talk about on tech Stuff, you can let

0:37:13.960 --> 0:37:16.520
<v Speaker 1>us know on Facebook or Twitter or handled there as

0:37:16.600 --> 0:37:19.319
<v Speaker 1>tech Stuff h s W, or you can send us

0:37:19.360 --> 0:37:22.800
<v Speaker 1>an email That address is tech stuff at how stuff

0:37:22.800 --> 0:37:24.960
<v Speaker 1>Works dot com and Chris and I will frighten you

0:37:25.000 --> 0:37:29.920
<v Speaker 1>again really soon. Be sure to check out our new

0:37:30.000 --> 0:37:33.359
<v Speaker 1>video podcast, Stuff from the Future. Join how Stuff Work

0:37:33.400 --> 0:37:36.960
<v Speaker 1>staff as we explore the most promising and perplexing possibilities

0:37:37.000 --> 0:37:40.880
<v Speaker 1>of tomorrow. The house Stuff Works iPhone app has arrived.

0:37:41.000 --> 0:37:48.120
<v Speaker 1>Download it today on iTunes, Brought to you by the

0:37:48.160 --> 0:37:51.520
<v Speaker 1>reinvented two thousand twelve camera. It's ready, are you