WEBVTT - Tap Versus Swipe

0:00:04.240 --> 0:00:07.560
<v Speaker 1>Get in techt with Technology with text Stuff from stuff

0:00:07.560 --> 0:00:14.600
<v Speaker 1>works dot com. Hey everyone, and welcome to text Stuff.

0:00:14.640 --> 0:00:18.200
<v Speaker 1>I'm Jonathan Strickland and I'm Lauren, and today we're going

0:00:18.280 --> 0:00:20.760
<v Speaker 1>to talk about some more money matters. We had our

0:00:20.840 --> 0:00:23.360
<v Speaker 1>discussion about all of our currency, which was a lot

0:00:23.400 --> 0:00:26.600
<v Speaker 1>of fun, but it's not the only thing about money

0:00:26.600 --> 0:00:29.440
<v Speaker 1>in tech that really is an interesting subject that's come

0:00:29.520 --> 0:00:32.760
<v Speaker 1>up in discussion a lot, particularly in the United States recently. Oh,

0:00:33.000 --> 0:00:36.280
<v Speaker 1>certainly not. In fact, many ways that we exchange money

0:00:36.320 --> 0:00:40.479
<v Speaker 1>these days are really really technological. Yeah. In fact, uh,

0:00:40.560 --> 0:00:43.600
<v Speaker 1>the vast majority of the way money changes hands has

0:00:43.640 --> 0:00:46.920
<v Speaker 1>nothing to do with any sort of physical currency whatsoever. Yeah,

0:00:46.960 --> 0:00:50.960
<v Speaker 1>I never actually carry cash on me. But we've never

0:00:51.360 --> 0:00:54.800
<v Speaker 1>really talked on this show about how credit cards work. Yeah,

0:00:54.880 --> 0:00:57.680
<v Speaker 1>that's true. And uh, and so we actually put forth

0:00:57.720 --> 0:01:01.160
<v Speaker 1>that we're going to do an episode about smart cards

0:01:01.240 --> 0:01:05.119
<v Speaker 1>and smart technology and NFC and credit cards and asked

0:01:05.120 --> 0:01:08.199
<v Speaker 1>if anyone had any other questions. We did have response Chase,

0:01:08.240 --> 0:01:10.720
<v Speaker 1>our buddy, Chase said, be sure to talk about coin.

0:01:11.120 --> 0:01:14.240
<v Speaker 1>Don't worry, Chase, we got you covered. And you you

0:01:14.280 --> 0:01:17.480
<v Speaker 1>may be thinking, but what about traditional magnetic stripe cards?

0:01:17.520 --> 0:01:20.319
<v Speaker 1>And we are totally not talking about those today. Now, well, well,

0:01:20.360 --> 0:01:22.720
<v Speaker 1>well here, here's all you need to know. Okay, there's

0:01:22.760 --> 0:01:26.520
<v Speaker 1>information that's related to the credit card account you have

0:01:26.680 --> 0:01:29.679
<v Speaker 1>that's located on that magnetic stripe. You can have a

0:01:29.720 --> 0:01:32.720
<v Speaker 1>reader that reads that information when the stripe is pushed

0:01:32.760 --> 0:01:35.480
<v Speaker 1>past it that that actually has that little magnetic field

0:01:35.480 --> 0:01:39.039
<v Speaker 1>that can generate the information necessary for the processing of

0:01:39.080 --> 0:01:42.800
<v Speaker 1>the payment. But really we wanted to talk about some

0:01:42.920 --> 0:01:45.839
<v Speaker 1>of the more advanced technologies will probably at some point

0:01:45.880 --> 0:01:48.160
<v Speaker 1>go back and actually talk about the development of that

0:01:48.280 --> 0:01:51.560
<v Speaker 1>magnetic stripe tech because we were so dependent upon it

0:01:51.640 --> 0:01:53.520
<v Speaker 1>for so long. In fact, in the United States we're

0:01:53.520 --> 0:01:56.440
<v Speaker 1>still very heavily dependent upon it. And actually that's why

0:01:56.480 --> 0:01:59.600
<v Speaker 1>we wanted to do this episode about NFC technology because

0:01:59.640 --> 0:02:03.880
<v Speaker 1>in j Nuary of some forty million US Target customers

0:02:04.760 --> 0:02:07.920
<v Speaker 1>Target the brand the store, the store um had their

0:02:07.920 --> 0:02:11.520
<v Speaker 1>credit card information stolen during a hack. And in February

0:02:11.639 --> 0:02:14.000
<v Speaker 1>the news broke that Congress and the major credit card

0:02:14.040 --> 0:02:17.040
<v Speaker 1>companies here in the States are are finally in agreement

0:02:17.160 --> 0:02:20.440
<v Speaker 1>that America should move to these smart credit cards, which

0:02:20.560 --> 0:02:23.040
<v Speaker 1>I'm sure has the rest of the world just snickering

0:02:23.040 --> 0:02:26.919
<v Speaker 1>at us, because this is technology that exists in other

0:02:27.000 --> 0:02:30.480
<v Speaker 1>places and has existed in other places for decades. Yeah,

0:02:30.520 --> 0:02:34.120
<v Speaker 1>in fact, so much so that it's become part of

0:02:34.120 --> 0:02:38.800
<v Speaker 1>of just like the general UH language. I remember watching

0:02:38.840 --> 0:02:41.680
<v Speaker 1>this little tangent here, but I remember watching an episode

0:02:42.200 --> 0:02:44.919
<v Speaker 1>of that Mitchell and web Look, which is a comedy

0:02:44.919 --> 0:02:48.520
<v Speaker 1>sketch series from the over in the UK, and at

0:02:48.560 --> 0:02:52.680
<v Speaker 1>one point there is a comedy duo vaudeville team called

0:02:52.800 --> 0:02:56.200
<v Speaker 1>uh Fish and Chip and they're breaking up. That that's

0:02:56.240 --> 0:02:58.800
<v Speaker 1>their last names are Fish and Chip. That's adorable. But

0:02:58.919 --> 0:03:00.880
<v Speaker 1>Chip breaks up to go and join up with a

0:03:00.919 --> 0:03:03.880
<v Speaker 1>guy whose last name is Pen, so it's Chip and Pen.

0:03:04.680 --> 0:03:06.519
<v Speaker 1>I had no idea that that was a thing when

0:03:06.520 --> 0:03:08.960
<v Speaker 1>I saw this pen are. Yeah, I didn't know that

0:03:09.040 --> 0:03:12.120
<v Speaker 1>Chip and pen was. That was just that's the shorthand

0:03:12.160 --> 0:03:15.560
<v Speaker 1>for this technology of a chip that's inside a credit

0:03:15.560 --> 0:03:19.160
<v Speaker 1>card and a pen a personal identification number that you

0:03:19.280 --> 0:03:23.280
<v Speaker 1>used to fully fulfill a transaction. I didn't know that.

0:03:23.400 --> 0:03:25.120
<v Speaker 1>I just was like, oh, so you're going from an

0:03:25.240 --> 0:03:28.920
<v Speaker 1>established pairing of things to something unusual, And then as

0:03:28.960 --> 0:03:31.359
<v Speaker 1>the joke continue, like no, this must be a thing.

0:03:32.320 --> 0:03:34.320
<v Speaker 1>And again it just shows how in the United States

0:03:34.520 --> 0:03:38.160
<v Speaker 1>we're way behind on this technology. Yeah, so master Card

0:03:38.200 --> 0:03:40.920
<v Speaker 1>and Visa have both set themselves a deadline of October

0:03:42.360 --> 0:03:45.000
<v Speaker 1>to roll this technology out to their customers in the US.

0:03:45.360 --> 0:03:47.560
<v Speaker 1>But but, but let's let's go back a little bit.

0:03:47.640 --> 0:03:51.000
<v Speaker 1>What exactly are smart cards? Where does this NFC? What

0:03:51.000 --> 0:03:53.360
<v Speaker 1>what is NFC? Where does all this technology come from?

0:03:53.400 --> 0:03:57.280
<v Speaker 1>An excellent question. NFC stands for near field communication, which

0:03:57.280 --> 0:03:59.760
<v Speaker 1>we've talked about on this podcast before. But you know,

0:03:59.800 --> 0:04:03.080
<v Speaker 1>it's good to have a refresher. And near field communication

0:04:03.160 --> 0:04:06.440
<v Speaker 1>is just a type of short range radio transmission. It's

0:04:06.520 --> 0:04:10.360
<v Speaker 1>it's not in itself some sort of brand new technology

0:04:10.360 --> 0:04:12.960
<v Speaker 1>that we had never thought of. It's just a very

0:04:13.000 --> 0:04:17.479
<v Speaker 1>specific implementation of radio waves. Right, It's not like not

0:04:17.600 --> 0:04:20.839
<v Speaker 1>like some brand new weird energy that glows orange in

0:04:20.839 --> 0:04:24.120
<v Speaker 1>the dark or something. Right, And what's actually special about

0:04:24.160 --> 0:04:26.680
<v Speaker 1>it is that it's extremely short range, like like ten

0:04:26.720 --> 0:04:29.719
<v Speaker 1>centimeters or less. Yeah. Yeah, ten centimeters tends to be

0:04:29.839 --> 0:04:34.400
<v Speaker 1>what people say is the maximum transmission distance for most implementations.

0:04:34.440 --> 0:04:37.200
<v Speaker 1>I think technically it can go up to around twenty

0:04:37.240 --> 0:04:40.720
<v Speaker 1>centimeters depending upon how you build it into your technology.

0:04:40.760 --> 0:04:43.800
<v Speaker 1>But for the for the applications we're thinking about, ten

0:04:43.800 --> 0:04:46.839
<v Speaker 1>centimeters makes the most sense, because you're actually talking about

0:04:47.160 --> 0:04:51.520
<v Speaker 1>exchanging information between two very small devices that can be

0:04:51.560 --> 0:04:54.159
<v Speaker 1>brought into proximity with one another. So it's not the

0:04:54.160 --> 0:04:56.240
<v Speaker 1>sort of thing you want to be able to broadcast

0:04:56.279 --> 0:04:59.880
<v Speaker 1>across a country, let alone a room, certainly, which you

0:05:00.160 --> 0:05:02.919
<v Speaker 1>is why usually we don't talk about very short distances

0:05:02.920 --> 0:05:05.400
<v Speaker 1>being special in technology, but but this is, this is

0:05:05.400 --> 0:05:08.280
<v Speaker 1>one of those rare occasions. And uh, it's it's also

0:05:08.360 --> 0:05:12.200
<v Speaker 1>good for transmitting small amounts of information. Yeah, it's not

0:05:12.279 --> 0:05:15.560
<v Speaker 1>designed to move lots of data very quickly. In fact,

0:05:15.680 --> 0:05:19.960
<v Speaker 1>the maximum speed, depending again upon the implementation, is around

0:05:20.000 --> 0:05:23.120
<v Speaker 1>a hundred six kilabits per second up to four four

0:05:23.200 --> 0:05:26.360
<v Speaker 1>killa bits per second. The killa bits per second, that's

0:05:26.800 --> 0:05:29.800
<v Speaker 1>that's not a lot right in the grand scheme of things.

0:05:30.000 --> 0:05:31.680
<v Speaker 1>If you had taught me back in the Apple two

0:05:31.720 --> 0:05:34.800
<v Speaker 1>E days, I would have thought, wow, that was fat.

0:05:34.920 --> 0:05:37.240
<v Speaker 1>You can move everything I've ever written in just a

0:05:37.279 --> 0:05:40.920
<v Speaker 1>couple of seconds. But these days, that's that's super slow.

0:05:40.960 --> 0:05:43.560
<v Speaker 1>I mean, we're talking now about people getting fiber where

0:05:43.600 --> 0:05:46.279
<v Speaker 1>they get a gigabit per second download. That's I don't

0:05:46.279 --> 0:05:49.279
<v Speaker 1>even understand what that means right now. Right now, that

0:05:49.360 --> 0:05:52.000
<v Speaker 1>just seems like a dream, although Google Fiber possibly coming

0:05:52.040 --> 0:05:56.000
<v Speaker 1>to Atlanta, uh and totally different podcasts. But anyway, Yes,

0:05:56.040 --> 0:06:00.400
<v Speaker 1>so NFC really suited for this the small amount of data,

0:06:00.480 --> 0:06:04.920
<v Speaker 1>small number of packets going between chips and uh there

0:06:04.960 --> 0:06:08.400
<v Speaker 1>are lots of different implementations of that as well. Right. Okay,

0:06:08.440 --> 0:06:10.520
<v Speaker 1>So so we mentioned that this is all sent via

0:06:10.600 --> 0:06:14.200
<v Speaker 1>a radio frequency. What frequency is that? Thirteen point fifty

0:06:14.279 --> 0:06:18.320
<v Speaker 1>six mega hurts Okay. Um. It was chosen specifically for

0:06:18.360 --> 0:06:22.200
<v Speaker 1>its suitability for for inductive coupling, which we'll get into

0:06:22.240 --> 0:06:24.320
<v Speaker 1>in a second here. But it's basically the technology that

0:06:24.360 --> 0:06:27.520
<v Speaker 1>makes all of this work. Um. And it's also pretty

0:06:27.520 --> 0:06:32.000
<v Speaker 1>resistant to environmental interference and human tissue does not readily

0:06:32.040 --> 0:06:34.120
<v Speaker 1>absorb it. Yeah, these are all very important things if

0:06:34.120 --> 0:06:37.720
<v Speaker 1>you're talking about a technology that's going to be around people. Yeah,

0:06:37.760 --> 0:06:39.640
<v Speaker 1>Like we're talking about stuff that could be either that

0:06:39.680 --> 0:06:42.200
<v Speaker 1>credit card that we're going to talk about eventually, or

0:06:42.839 --> 0:06:45.360
<v Speaker 1>even a smartphone where you have a virtual credit card

0:06:45.440 --> 0:06:49.880
<v Speaker 1>stored on another device. Plus, this idea of the resistance

0:06:49.920 --> 0:06:53.239
<v Speaker 1>to environmental interference really important. If you're talking again about

0:06:53.240 --> 0:06:55.840
<v Speaker 1>something that's going to be used frequently. You don't want,

0:06:56.000 --> 0:06:58.680
<v Speaker 1>you know, if there's some sort of weird stormy weather

0:06:58.720 --> 0:07:02.080
<v Speaker 1>outside and suddenly you can't process payments. If you're an

0:07:02.120 --> 0:07:06.520
<v Speaker 1>umbrella store, that's bad news. That's very bad news. That's

0:07:06.520 --> 0:07:09.120
<v Speaker 1>a terrible business model. Yes, you should have gone with

0:07:09.160 --> 0:07:13.640
<v Speaker 1>some other payment plan. Okay. So so technically this is

0:07:13.680 --> 0:07:16.680
<v Speaker 1>an extension of r f I D technology, which is

0:07:16.680 --> 0:07:19.200
<v Speaker 1>why you might have sometimes heard uh, n f C

0:07:19.520 --> 0:07:22.600
<v Speaker 1>and r f I D being kind of equated colloquially. Yeah,

0:07:22.680 --> 0:07:25.360
<v Speaker 1>it's it's similar in r f I D stands for

0:07:25.440 --> 0:07:29.120
<v Speaker 1>radio frequency identification, So it's it's kind of like if

0:07:29.160 --> 0:07:32.360
<v Speaker 1>you've ever had one of those um those security badges

0:07:32.520 --> 0:07:36.080
<v Speaker 1>that you then hold up to a reader that when

0:07:36.080 --> 0:07:38.600
<v Speaker 1>it detects the security badge, it will unlock the door

0:07:38.640 --> 0:07:40.760
<v Speaker 1>for you so you can continue in. Most of those

0:07:40.760 --> 0:07:44.840
<v Speaker 1>badges are using r f I D rather than NFC technology,

0:07:44.840 --> 0:07:47.440
<v Speaker 1>although technically they could use either. I mean, some of

0:07:47.480 --> 0:07:49.920
<v Speaker 1>them probably do use n f C. It depends on

0:07:50.000 --> 0:07:52.560
<v Speaker 1>it depends on how much money and what exactly you

0:07:52.600 --> 0:07:54.800
<v Speaker 1>want to do with this kind of thing. But but

0:07:54.920 --> 0:07:57.160
<v Speaker 1>both of these technologies when you really get down to it.

0:07:57.280 --> 0:08:00.440
<v Speaker 1>Our applications of that inductive coupling stuff that we were

0:08:00.480 --> 0:08:03.280
<v Speaker 1>talking about just a minute ago um. And that's the

0:08:03.520 --> 0:08:06.840
<v Speaker 1>property of flowing electrons and magnetic fields to influence each

0:08:06.840 --> 0:08:11.040
<v Speaker 1>other um, meaning that when electrons flow through a conductive material,

0:08:11.080 --> 0:08:15.000
<v Speaker 1>they create a magnetic field. And conversely, and existing magnetic

0:08:15.040 --> 0:08:17.680
<v Speaker 1>field can create a flow of electrons in a conductive

0:08:17.680 --> 0:08:21.040
<v Speaker 1>material exactly as long as you've got a fluctuating magnetic field,

0:08:21.080 --> 0:08:23.720
<v Speaker 1>because otherwise, if you or or in this case, you're

0:08:23.720 --> 0:08:26.640
<v Speaker 1>talking about bringing something within the proximity of a magnetic

0:08:26.720 --> 0:08:30.000
<v Speaker 1>field that will cause electrons to flow. The important thing

0:08:30.040 --> 0:08:33.160
<v Speaker 1>is if you want to make that last like you

0:08:33.200 --> 0:08:35.320
<v Speaker 1>want to, and it's something that's going to be a

0:08:35.360 --> 0:08:39.199
<v Speaker 1>magnetic field that continues to induce electricity, it has to

0:08:39.240 --> 0:08:43.040
<v Speaker 1>be a fluctuating magnetic field, otherwise it'll just it will

0:08:43.080 --> 0:08:45.880
<v Speaker 1>induce electricity originally at first, and then everything kind of

0:08:45.880 --> 0:08:49.000
<v Speaker 1>balances out. So the same sort of thing with alternating current.

0:08:49.040 --> 0:08:52.040
<v Speaker 1>Actually alternating current is necessary to create that magnetic field

0:08:52.040 --> 0:08:56.040
<v Speaker 1>because or at least a fluctuating one, because otherwise balances

0:08:56.280 --> 0:08:58.760
<v Speaker 1>And yeah, you just get something that's equivalent to a

0:08:58.760 --> 0:09:02.200
<v Speaker 1>bar magnet, which would be useful for a moment and

0:09:02.200 --> 0:09:05.079
<v Speaker 1>then not useful anymore. Right, we know all of this

0:09:05.240 --> 0:09:08.480
<v Speaker 1>thanks to Michael Faraday's work way back in the eighteen thirties.

0:09:08.480 --> 0:09:12.160
<v Speaker 1>So this is not new technology technically, no, But I

0:09:12.200 --> 0:09:14.360
<v Speaker 1>should point out that Michael Faraday made all of his

0:09:14.400 --> 0:09:20.680
<v Speaker 1>purchases in cash, so just made that up alright, So yeah,

0:09:20.800 --> 0:09:23.959
<v Speaker 1>r F I D. Originally we're talking about a passive system, right,

0:09:24.000 --> 0:09:27.880
<v Speaker 1>It's not something that's actively communicating between two entities. So

0:09:27.920 --> 0:09:30.400
<v Speaker 1>in other words, you really had something that was kind

0:09:30.440 --> 0:09:33.559
<v Speaker 1>of like a detector, and then if the right sort

0:09:33.600 --> 0:09:37.840
<v Speaker 1>of chip came into the the field of the detector,

0:09:38.160 --> 0:09:41.880
<v Speaker 1>everything's cool. But you're not getting like an exchange of information, right,

0:09:41.960 --> 0:09:44.080
<v Speaker 1>And what's going on there is that if you've got

0:09:44.120 --> 0:09:47.440
<v Speaker 1>a chip in something um and by by passing that's

0:09:47.440 --> 0:09:50.400
<v Speaker 1>something near a reader that generates a magnetic field, you're

0:09:50.640 --> 0:09:54.000
<v Speaker 1>inducing the flow of electricity in the chip, thus creating

0:09:54.000 --> 0:09:57.559
<v Speaker 1>a pneumatic magnetic field which the reader can then pick up. Right.

0:09:57.640 --> 0:09:59.720
<v Speaker 1>So this is pretty simple stuff. I mean, it's not

0:09:59.800 --> 0:10:02.440
<v Speaker 1>like the chip inside whatever it is, whether it's a

0:10:02.520 --> 0:10:06.240
<v Speaker 1>key fob or a card or whatever, it's not itself,

0:10:06.360 --> 0:10:09.199
<v Speaker 1>uh connected to any sort of battery. It only gets

0:10:09.200 --> 0:10:12.280
<v Speaker 1>that electricity when it comes into contact with that magnetic

0:10:12.320 --> 0:10:16.040
<v Speaker 1>field of the reader. So, uh that you know that's passive.

0:10:16.080 --> 0:10:18.559
<v Speaker 1>It means that there's not an active amount of electricity

0:10:18.600 --> 0:10:21.320
<v Speaker 1>going through that chip. However, there are also active versions

0:10:21.360 --> 0:10:24.200
<v Speaker 1>of r F I D. Yeah, if you power that chip,

0:10:24.280 --> 0:10:26.600
<v Speaker 1>it will allow you to to a to extend the

0:10:26.640 --> 0:10:29.440
<v Speaker 1>chip to reader distance and also to store some information

0:10:29.480 --> 0:10:31.400
<v Speaker 1>on the chip for the reader to find. Right, So

0:10:31.440 --> 0:10:34.160
<v Speaker 1>in this case we're talking about something more advanced than

0:10:34.240 --> 0:10:37.360
<v Speaker 1>just a key in a lock. Now we've got something

0:10:37.360 --> 0:10:41.000
<v Speaker 1>where you could theoretically have information stored on that r

0:10:41.080 --> 0:10:44.720
<v Speaker 1>F I D chip. That is very important to allow

0:10:44.800 --> 0:10:47.840
<v Speaker 1>you to do some form of transaction, whether it's monetary

0:10:47.920 --> 0:10:52.040
<v Speaker 1>or otherwise. Right. NFC uses this same technology, but it

0:10:52.040 --> 0:10:56.200
<v Speaker 1>allows for for data transfer both ways, and basically does

0:10:56.240 --> 0:10:59.000
<v Speaker 1>this by letting the chip and the reader both have

0:10:59.120 --> 0:11:02.360
<v Speaker 1>the capacity to act as the active or the passive

0:11:02.400 --> 0:11:05.280
<v Speaker 1>partner in the transaction and they kind of switch roles

0:11:05.400 --> 0:11:08.320
<v Speaker 1>or flip flop back and forth in order to complete

0:11:08.320 --> 0:11:11.280
<v Speaker 1>any given transaction. And this is what really makes that

0:11:11.520 --> 0:11:14.720
<v Speaker 1>NFC ability. Like using it in the in the sense

0:11:14.800 --> 0:11:18.120
<v Speaker 1>of a payment makes it really useful because not only

0:11:18.240 --> 0:11:21.679
<v Speaker 1>can it allow you to pay for something, you can

0:11:21.720 --> 0:11:25.440
<v Speaker 1>have this ongoing relationship between an app on either a

0:11:25.480 --> 0:11:29.160
<v Speaker 1>credit card or in your phone or whatever whatever implementation,

0:11:29.559 --> 0:11:32.440
<v Speaker 1>there can be this ongoing communication that allows you to

0:11:32.440 --> 0:11:35.440
<v Speaker 1>do other things besides just make a payment, like apply

0:11:35.880 --> 0:11:38.760
<v Speaker 1>bonuses that you may have accrued by being a frequent

0:11:38.760 --> 0:11:41.560
<v Speaker 1>shopper at a particular place you know, or really carefully

0:11:41.679 --> 0:11:45.080
<v Speaker 1>encrypt a payment. Yes, and that will be really important

0:11:45.080 --> 0:11:47.080
<v Speaker 1>for us to talk about when we get into the

0:11:47.600 --> 0:11:52.439
<v Speaker 1>at least the perceived drawbacks of NFC. So we're talking

0:11:52.480 --> 0:11:54.719
<v Speaker 1>about lots you know this. This is just kind of

0:11:54.760 --> 0:11:59.080
<v Speaker 1>a platform, right, This is just a way of transmitting information. Again,

0:11:59.120 --> 0:12:02.000
<v Speaker 1>it doesn't necessary early mean that it's just paying. It

0:12:02.000 --> 0:12:04.280
<v Speaker 1>can be practically anything. And in fact, one of the

0:12:04.320 --> 0:12:07.360
<v Speaker 1>examples that I would hear all the time when I

0:12:07.400 --> 0:12:10.880
<v Speaker 1>was first hearing about NFC being incorporated into cell phones,

0:12:11.200 --> 0:12:12.960
<v Speaker 1>so that you would have an NFC chip in a

0:12:13.000 --> 0:12:15.600
<v Speaker 1>cell phone that you could bring to cell phones together

0:12:15.880 --> 0:12:19.120
<v Speaker 1>and exchange an electronic business card. So that way, if

0:12:19.120 --> 0:12:21.640
<v Speaker 1>I'm at a conference and everyone happens to have these phones,

0:12:21.960 --> 0:12:25.000
<v Speaker 1>we can meet with one another and do this quick exchange,

0:12:25.080 --> 0:12:27.320
<v Speaker 1>so I now have their contact information. I don't have

0:12:27.360 --> 0:12:31.559
<v Speaker 1>to keep up with lots of physical paper cards that ultimately,

0:12:31.640 --> 0:12:34.240
<v Speaker 1>you know, you're going to the washers or they're going

0:12:34.280 --> 0:12:37.280
<v Speaker 1>to go into a dusk drawer or into the garbage.

0:12:37.320 --> 0:12:39.680
<v Speaker 1>I mean, it's just you know, that's that's the thing.

0:12:39.800 --> 0:12:42.280
<v Speaker 1>So that was one example, but there are a lot

0:12:42.280 --> 0:12:44.800
<v Speaker 1>of other ones too, Like, for example, maybe maybe Lauren

0:12:44.840 --> 0:12:48.560
<v Speaker 1>and I both have UH music players electronic music players

0:12:48.559 --> 0:12:51.400
<v Speaker 1>that have these this NFC technology in it, I might

0:12:51.440 --> 0:12:54.200
<v Speaker 1>be able to do. You know, Lauren's listening to some

0:12:54.280 --> 0:12:56.600
<v Speaker 1>music that I think sounds interesting, but I'm not familiar

0:12:56.640 --> 0:12:58.520
<v Speaker 1>with it, and then just by tapping the phones, she

0:12:58.559 --> 0:13:01.040
<v Speaker 1>can give me the information where I have access to

0:13:01.080 --> 0:13:03.560
<v Speaker 1>that same sort of music. This would never actually happen

0:13:04.080 --> 0:13:08.120
<v Speaker 1>because also the fact that Lauren and I listened to

0:13:08.120 --> 0:13:11.560
<v Speaker 1>totally different types of music, and so I would never

0:13:11.600 --> 0:13:16.640
<v Speaker 1>ever think anything she listened to was interesting and vice versa. Clearly. Yeah,

0:13:16.880 --> 0:13:20.040
<v Speaker 1>you know, I mean, come on, I like Tibetan throat

0:13:20.160 --> 0:13:23.080
<v Speaker 1>screen singing. It's just it's that's my thing. I've never

0:13:23.160 --> 0:13:26.760
<v Speaker 1>listened to Tibetan thrash metal, but that's that's interesting, okay, Um,

0:13:26.800 --> 0:13:29.520
<v Speaker 1>all right, And so if you're thinking that all of

0:13:29.559 --> 0:13:32.800
<v Speaker 1>this UH near field communications r F I D stuff

0:13:32.840 --> 0:13:36.240
<v Speaker 1>sounds a lot like that Bluetooth low energy beacon stuff

0:13:36.280 --> 0:13:39.320
<v Speaker 1>that we were talking about in a recent episode. It's

0:13:39.360 --> 0:13:41.920
<v Speaker 1>it's kind of similar, but it's different in a couple

0:13:41.960 --> 0:13:44.439
<v Speaker 1>of ways. First of all, NFC and r F I

0:13:44.559 --> 0:13:48.040
<v Speaker 1>d uh with with those things, the device that contains

0:13:48.080 --> 0:13:49.800
<v Speaker 1>the chip has to be a lot closer to the

0:13:49.800 --> 0:13:52.920
<v Speaker 1>reader than with Bluetooth low energy. Right, Bluetooth you've got

0:13:52.960 --> 0:13:56.240
<v Speaker 1>like a maximum range of fifty meters, which, if you

0:13:56.280 --> 0:14:00.520
<v Speaker 1>do the math, is significantly greater than ten centimeters. It's

0:14:00.520 --> 0:14:05.520
<v Speaker 1>significantly You're indeed correct. And secondly, each chip and reader

0:14:05.679 --> 0:14:09.280
<v Speaker 1>can only interact with one thing at a time. That is,

0:14:09.559 --> 0:14:12.440
<v Speaker 1>once a transaction is started with a chip, the reader

0:14:12.440 --> 0:14:15.440
<v Speaker 1>will communicate only with that chip, and the chip only

0:14:15.440 --> 0:14:18.760
<v Speaker 1>with that reader until the transaction is complete. So NFC

0:14:18.880 --> 0:14:22.200
<v Speaker 1>isn't good for broadcasting to multiple multiple devices the way

0:14:22.200 --> 0:14:25.360
<v Speaker 1>that Bluetooth blow energy is. But this actually, in my opinion,

0:14:25.400 --> 0:14:27.600
<v Speaker 1>makes it more ideal for the kind of things like

0:14:28.000 --> 0:14:31.320
<v Speaker 1>payment process. It's more secure. Yeah, you know that you're

0:14:31.360 --> 0:14:35.120
<v Speaker 1>not accidentally paying for someone else's purchase, or you know

0:14:35.160 --> 0:14:37.600
<v Speaker 1>there's that things aren't getting yeah, if everything is set

0:14:37.640 --> 0:14:40.160
<v Speaker 1>up correctly, right, right, like First of all, the range

0:14:40.240 --> 0:14:42.800
<v Speaker 1>is so short that it's not likely that some let's

0:14:42.800 --> 0:14:46.280
<v Speaker 1>say it's a store that has multiple cash registers, unless

0:14:46.280 --> 0:14:49.160
<v Speaker 1>those cash registers are really close together and and those

0:14:49.400 --> 0:14:51.840
<v Speaker 1>reading devices are you know, practically next to each other,

0:14:51.880 --> 0:14:55.160
<v Speaker 1>which can create problems of multiplying the field and getting

0:14:55.200 --> 0:14:57.800
<v Speaker 1>everything kind of confused. Yeah, that that would be a problem,

0:14:57.800 --> 0:15:00.920
<v Speaker 1>but you know, it's fairly easy to solve. For one thing,

0:15:01.200 --> 0:15:04.160
<v Speaker 1>it's not likely that you're gonna have two devices within uh,

0:15:04.400 --> 0:15:08.240
<v Speaker 1>you know, having that ten centimeter overlap radius overlap. But

0:15:08.320 --> 0:15:11.760
<v Speaker 1>for another, because it has this one on one communication

0:15:11.920 --> 0:15:14.880
<v Speaker 1>and blocks everything else out, you don't have to necessarily

0:15:14.920 --> 0:15:17.720
<v Speaker 1>worry about their being interference from other ways either, like

0:15:17.800 --> 0:15:22.240
<v Speaker 1>someone taking out their their smartphone that has the same

0:15:22.240 --> 0:15:24.280
<v Speaker 1>sort of technology to make their purchase in their next

0:15:24.320 --> 0:15:26.880
<v Speaker 1>to you, but because of the arc of their hand

0:15:27.520 --> 0:15:30.720
<v Speaker 1>it comes into contact with that field. It really reduces

0:15:30.800 --> 0:15:34.960
<v Speaker 1>those those, um, those worst case scenarios quite a bit.

0:15:36.280 --> 0:15:41.240
<v Speaker 1>So let's talk about actual NFC credit cards. Now, again,

0:15:41.280 --> 0:15:43.320
<v Speaker 1>this is one of those things where in some countries

0:15:43.440 --> 0:15:46.080
<v Speaker 1>this is ah, this has been looked into for a while,

0:15:46.200 --> 0:15:50.280
<v Speaker 1>But let's let's talk about specifically the United States because one,

0:15:50.360 --> 0:15:53.200
<v Speaker 1>we lived there, and too, there's this new initiative for

0:15:53.280 --> 0:15:55.560
<v Speaker 1>the US to kind of move to this smart credit

0:15:55.600 --> 0:15:58.760
<v Speaker 1>card technology and to explain to our our U S

0:15:58.800 --> 0:16:01.640
<v Speaker 1>listeners what the big deal, while again all of our

0:16:01.680 --> 0:16:05.720
<v Speaker 1>friends over in Europe and Asia chuckle to themselves. Sure,

0:16:05.840 --> 0:16:08.360
<v Speaker 1>because France was really the first country to adopt the

0:16:08.400 --> 0:16:11.760
<v Speaker 1>technology for for payment related purposes. That was like what

0:16:11.960 --> 0:16:18.200
<v Speaker 1>like to three years ago in Night four? Whoa, okay, alright,

0:16:18.280 --> 0:16:20.720
<v Speaker 1>nineteen eighty four, the year after Return of the Jedi

0:16:20.800 --> 0:16:23.760
<v Speaker 1>came out, and they furthermore, are you sure that wasn't

0:16:24.360 --> 0:16:29.880
<v Speaker 1>two eighty three? They all came out three years apart. Sorry,

0:16:29.920 --> 0:16:33.840
<v Speaker 1>I didn't mean to question you. Um. Furthermore, France had

0:16:33.840 --> 0:16:37.920
<v Speaker 1>widespread chip based credit and debit systems by nineteen two,

0:16:38.360 --> 0:16:41.880
<v Speaker 1>So so we're we're technically really only fourteen or known.

0:16:42.040 --> 0:16:44.920
<v Speaker 1>That's twenty four years behind, not thirty something years. But

0:16:45.040 --> 0:16:50.160
<v Speaker 1>well that's that's something right. So again, it's it's it's

0:16:50.200 --> 0:16:52.680
<v Speaker 1>not that the United States hasn't tried this kind of

0:16:52.720 --> 0:16:57.320
<v Speaker 1>stuff out, or that we don't have companies that are

0:16:57.320 --> 0:17:00.880
<v Speaker 1>working on building this technology into their credit cards. It's

0:17:00.920 --> 0:17:04.080
<v Speaker 1>just that we don't necessarily see it spread out widely

0:17:04.119 --> 0:17:08.120
<v Speaker 1>across our entire infrastructure. Right. Uh sure. Side note, I'm

0:17:08.119 --> 0:17:10.320
<v Speaker 1>not sure if I actually said numbers correctly. I really

0:17:10.320 --> 0:17:12.880
<v Speaker 1>can't subtract on the fly, so if if you need

0:17:12.920 --> 0:17:14.720
<v Speaker 1>to write it and correct me on that one. But

0:17:14.720 --> 0:17:18.760
<v Speaker 1>but okay, So anyway, the US has indeed seen applications

0:17:18.760 --> 0:17:21.360
<v Speaker 1>of this technology before. It's not completely new, like Jonathan

0:17:21.400 --> 0:17:27.119
<v Speaker 1>was just saying, circa seven mobile, the the Gasoline Petroleum Company,

0:17:27.960 --> 0:17:30.920
<v Speaker 1>debuted a station credit card system that used an r

0:17:31.000 --> 0:17:33.400
<v Speaker 1>F I D key chain to access the user's account,

0:17:33.520 --> 0:17:36.400
<v Speaker 1>and then in two thousand five, JP Morgan Chase introduced

0:17:36.400 --> 0:17:40.040
<v Speaker 1>a card a credit card UH with a proprietary r

0:17:40.160 --> 0:17:43.600
<v Speaker 1>F I D system called blink right, and then Visa

0:17:43.720 --> 0:17:46.560
<v Speaker 1>and master Card have both been looking into it as well.

0:17:47.000 --> 0:17:50.080
<v Speaker 1>Moving into the two thousand's, we've seen that technology come up,

0:17:50.640 --> 0:17:54.959
<v Speaker 1>but again, not so useful if if you were kind

0:17:55.000 --> 0:17:58.240
<v Speaker 1>of a homebody. Right. Well, the problem is that this

0:17:58.320 --> 0:18:01.479
<v Speaker 1>technology is terrific, but it only works if stores are

0:18:01.480 --> 0:18:04.040
<v Speaker 1>set up with the infrastructure to allow you to use it.

0:18:04.240 --> 0:18:07.040
<v Speaker 1>So although they were pretty great for Americans who traveled

0:18:07.040 --> 0:18:09.680
<v Speaker 1>to other countries, there weren't that many places that you

0:18:09.680 --> 0:18:11.639
<v Speaker 1>could use them in the US, and in fact, I

0:18:12.080 --> 0:18:14.760
<v Speaker 1>know that there are tourists who come to the United

0:18:14.800 --> 0:18:17.639
<v Speaker 1>States who are used to this system and back in

0:18:17.680 --> 0:18:21.200
<v Speaker 1>Europe or back in Asia who then I wonder why

0:18:21.240 --> 0:18:23.639
<v Speaker 1>you have to take their credit card in order to

0:18:24.240 --> 0:18:26.919
<v Speaker 1>make a payment at say a restaurant or you know,

0:18:27.000 --> 0:18:29.199
<v Speaker 1>they the whole swiping thing is one of those things

0:18:29.240 --> 0:18:33.120
<v Speaker 1>that oh, how how how quaint and insecure. But we'll

0:18:33.119 --> 0:18:35.479
<v Speaker 1>get into that too, but yeah, it was. It's one

0:18:35.520 --> 0:18:37.159
<v Speaker 1>of those things where I know there are people who

0:18:37.240 --> 0:18:39.320
<v Speaker 1>come over to the United States are kind of I mean,

0:18:39.359 --> 0:18:43.719
<v Speaker 1>the US has this this at least this reputation of

0:18:43.760 --> 0:18:47.359
<v Speaker 1>being really technologically advanced and forward thinking and all of

0:18:47.400 --> 0:18:50.919
<v Speaker 1>those kind of things, but when you get to certain industries,

0:18:51.320 --> 0:18:53.840
<v Speaker 1>we really lag behind. In fact, we lag behind in

0:18:53.840 --> 0:18:57.160
<v Speaker 1>a lot of ways. But but you know, within within

0:18:57.200 --> 0:18:59.600
<v Speaker 1>the United States, we don't we don't tend to think

0:18:59.640 --> 0:19:01.840
<v Speaker 1>that way because we're kind of insulated and we aren't

0:19:01.840 --> 0:19:04.199
<v Speaker 1>living in this own little tech tech bubble where we

0:19:04.200 --> 0:19:07.480
<v Speaker 1>think we've got all the best stuff. Guys, we don't

0:19:07.520 --> 0:19:09.840
<v Speaker 1>have the best stuff. We do not we had the

0:19:09.880 --> 0:19:13.640
<v Speaker 1>best stuff in a long time. Merchants and credit card

0:19:13.640 --> 0:19:17.159
<v Speaker 1>companies both have cited the cost of the infrastructure, and

0:19:17.240 --> 0:19:20.359
<v Speaker 1>also the public's lack of understanding of the technology as

0:19:20.720 --> 0:19:24.040
<v Speaker 1>barriers to making all of this widespread. Yeah, ignorance and

0:19:24.119 --> 0:19:28.639
<v Speaker 1>expense the two big barriers, and in fact that ignorance problem.

0:19:28.680 --> 0:19:30.720
<v Speaker 1>I mean, it sounds like it's something simple that you

0:19:30.800 --> 0:19:32.440
<v Speaker 1>just do a couple of little p s A s

0:19:32.440 --> 0:19:36.720
<v Speaker 1>and people understand how the technology works, but never underestimate

0:19:37.240 --> 0:19:40.359
<v Speaker 1>how we will allow ignorance to play into our major

0:19:40.400 --> 0:19:43.719
<v Speaker 1>policy decisions. If you want an example of that, just

0:19:43.840 --> 0:19:45.840
<v Speaker 1>take a look at how well the metric system was

0:19:45.880 --> 0:19:49.920
<v Speaker 1>implemented in the United States. It's it's understandable, and maybe

0:19:49.920 --> 0:19:52.200
<v Speaker 1>not about the metric systems, but it's it's understandable about

0:19:52.240 --> 0:19:55.240
<v Speaker 1>about business decisions that are going to potentially cost you

0:19:55.280 --> 0:19:57.200
<v Speaker 1>a lot of money. Like I can see why why

0:19:57.240 --> 0:19:59.840
<v Speaker 1>companies would be a little bit shy about enacting some

0:20:00.080 --> 0:20:02.639
<v Speaker 1>thing that they don't think is going to make them money.

0:20:02.760 --> 0:20:05.760
<v Speaker 1>And in fact, now we'll get into why one of

0:20:05.760 --> 0:20:09.560
<v Speaker 1>the big reasons why why merchants in particular might be reluctant,

0:20:09.600 --> 0:20:11.960
<v Speaker 1>and part of that is that although NFC itself is

0:20:12.000 --> 0:20:15.600
<v Speaker 1>a standard right, that's a standard form of radio transmission.

0:20:15.960 --> 0:20:19.800
<v Speaker 1>So the basic technology upon which information is flowing is

0:20:19.840 --> 0:20:23.520
<v Speaker 1>going to remain the same from one implementing one implementation

0:20:23.600 --> 0:20:28.600
<v Speaker 1>to another. The actual uh software that's being used to

0:20:28.680 --> 0:20:32.680
<v Speaker 1>transmit that data depends upon who it is that's creating

0:20:32.800 --> 0:20:36.439
<v Speaker 1>the program or the proprietary right and there they have

0:20:36.560 --> 0:20:41.400
<v Speaker 1>not classically made these systems to to work across each other. Right.

0:20:41.440 --> 0:20:44.320
<v Speaker 1>So if you have one credit card company that's using

0:20:44.400 --> 0:20:47.960
<v Speaker 1>one of these implementations of software and a different credit

0:20:48.000 --> 0:20:51.440
<v Speaker 1>card company that uses a completely different implementation, and those

0:20:51.440 --> 0:20:55.359
<v Speaker 1>two programs cannot communicate with each other, then as a vendor,

0:20:55.800 --> 0:20:58.960
<v Speaker 1>you may have to choose either between two different credit

0:20:59.000 --> 0:21:02.160
<v Speaker 1>card companies or you have to spend twice as much

0:21:02.240 --> 0:21:04.800
<v Speaker 1>to get as many to be able to support both

0:21:04.840 --> 0:21:07.840
<v Speaker 1>of them. So, because there's no standard, okay, but so

0:21:07.960 --> 0:21:11.600
<v Speaker 1>there are a few different proprietary ways of using this

0:21:11.720 --> 0:21:13.919
<v Speaker 1>in the States right now. Exactly. Yeah. One of the

0:21:13.960 --> 0:21:15.359
<v Speaker 1>big ones are at least one of the ones that

0:21:15.480 --> 0:21:19.080
<v Speaker 1>probably has the most high profile of all of them.

0:21:19.119 --> 0:21:21.320
<v Speaker 1>I mean, it's not the oldest implementation, but it's one

0:21:21.359 --> 0:21:23.040
<v Speaker 1>that a lot of people have heard about is Google.

0:21:23.760 --> 0:21:26.680
<v Speaker 1>Google has really been behind NFC technology for a while now,

0:21:26.680 --> 0:21:29.040
<v Speaker 1>a couple of years and they also have their app

0:21:29.119 --> 0:21:33.360
<v Speaker 1>called Google Wallet, which is meant for both payment well

0:21:33.400 --> 0:21:36.280
<v Speaker 1>not just both. It's meant for payment transfers, so that

0:21:36.320 --> 0:21:39.320
<v Speaker 1>if you're buying something from a merchant that supports Google Wallet.

0:21:39.440 --> 0:21:41.960
<v Speaker 1>It's also meant to be able to give you access

0:21:42.040 --> 0:21:44.600
<v Speaker 1>to special deals, like if someone's got a sale. It

0:21:44.640 --> 0:21:47.600
<v Speaker 1>can give you a notification. If it's some vendor that

0:21:47.680 --> 0:21:50.240
<v Speaker 1>you've gone to several times, it might let you know

0:21:50.240 --> 0:21:53.119
<v Speaker 1>about any specials that are running. Uh. It can also

0:21:53.160 --> 0:21:57.760
<v Speaker 1>incorporate things like customer loyalty programs. So let's say that

0:21:58.040 --> 0:22:00.159
<v Speaker 1>I use it for my local coffee shop and the

0:22:00.200 --> 0:22:02.080
<v Speaker 1>tenth cup of coffee I get a freak cup. I

0:22:02.080 --> 0:22:03.800
<v Speaker 1>don't have to keep track of a card that has

0:22:03.840 --> 0:22:07.119
<v Speaker 1>to be punched. It's all. It's all. Yeah, it's tracked

0:22:07.160 --> 0:22:10.439
<v Speaker 1>on the app itself. UM So that's a that's a

0:22:10.440 --> 0:22:13.199
<v Speaker 1>big one that's got a lot of press recently. And

0:22:13.280 --> 0:22:16.120
<v Speaker 1>you know, I have a smartphone that has an NFC chip,

0:22:16.280 --> 0:22:19.439
<v Speaker 1>I have a Google Wallet account. I have never used

0:22:19.960 --> 0:22:23.720
<v Speaker 1>that to make I've never seen a vendor nearby that

0:22:24.040 --> 0:22:25.639
<v Speaker 1>used it. I know there are some because if I

0:22:25.640 --> 0:22:27.760
<v Speaker 1>go on their website and I do a search, a

0:22:27.800 --> 0:22:30.240
<v Speaker 1>few of them are in this area, this area being

0:22:30.280 --> 0:22:33.199
<v Speaker 1>Buckhead in Atlanta, that's where our office is, and I

0:22:33.240 --> 0:22:35.119
<v Speaker 1>know there are a few that accept it. I have

0:22:35.280 --> 0:22:37.280
<v Speaker 1>never gone to any of them to try it out,

0:22:37.600 --> 0:22:40.160
<v Speaker 1>So I mean it's not that I'm afraid of technology.

0:22:40.160 --> 0:22:42.160
<v Speaker 1>I just don't have access to it. Yeah, I haven't either.

0:22:42.640 --> 0:22:45.920
<v Speaker 1>So then we've got MasterCard. They have a a app

0:22:45.960 --> 0:22:48.840
<v Speaker 1>called UH, or at least a technology called pay Pass,

0:22:48.880 --> 0:22:51.400
<v Speaker 1>which is a tap to pay method where you use

0:22:51.400 --> 0:22:54.400
<v Speaker 1>a physical card that has a passive n FC chip

0:22:54.440 --> 0:22:56.280
<v Speaker 1>in it. So it's kind of similar to those passive

0:22:56.400 --> 0:22:58.280
<v Speaker 1>r F I D chips we talked about earlier. It

0:22:58.280 --> 0:23:00.879
<v Speaker 1>doesn't require a power supply, right, which is important. I mean,

0:23:00.880 --> 0:23:03.199
<v Speaker 1>you've got a physical credit card, you don't have a

0:23:03.240 --> 0:23:06.600
<v Speaker 1>lot of space to put a battery there, so UH

0:23:06.760 --> 0:23:09.040
<v Speaker 1>you end up using the inductive coupling to get this

0:23:09.119 --> 0:23:12.560
<v Speaker 1>payment terminal to process the information UM and you can

0:23:12.600 --> 0:23:15.439
<v Speaker 1>also have an electronic version of it that's stored as

0:23:15.480 --> 0:23:17.960
<v Speaker 1>an app on a smartphone that has enough C chip

0:23:18.080 --> 0:23:21.480
<v Speaker 1>and that one is compatible with Google Wallet, which, as

0:23:21.520 --> 0:23:24.320
<v Speaker 1>we said before, is maybe not actually useful. Yeah, yeah,

0:23:24.520 --> 0:23:26.679
<v Speaker 1>I mean it all depends on you, Like if you

0:23:26.680 --> 0:23:29.879
<v Speaker 1>live in San Francisco. There's probably every single place around

0:23:29.920 --> 0:23:33.639
<v Speaker 1>you that's that supports it, but here in Atlanta, you know. So. Um.

0:23:33.880 --> 0:23:36.800
<v Speaker 1>Another one is one that's done by American Express, a

0:23:36.920 --> 0:23:39.920
<v Speaker 1>T and T, T Mobile and Verizon. Uh. This one,

0:23:40.000 --> 0:23:44.640
<v Speaker 1>for all you archer fans is uh isis UH. That's

0:23:44.640 --> 0:23:46.919
<v Speaker 1>actually the name of it, isis I s I S.

0:23:47.000 --> 0:23:50.760
<v Speaker 1>It promotes itself as the industry's most widely accepted mobile wallet,

0:23:51.160 --> 0:23:53.480
<v Speaker 1>So it's very similar to Google Wallet, has those same

0:23:53.560 --> 0:23:57.000
<v Speaker 1>kind of features, but it's a different proprietary approach. So

0:23:57.080 --> 0:24:00.680
<v Speaker 1>again ISIS and Google Wallet. If it's like a Google

0:24:00.680 --> 0:24:04.399
<v Speaker 1>Wallet using that MasterCard pay pass, they don't necessarily work

0:24:04.400 --> 0:24:07.479
<v Speaker 1>on the same system. So if you have a receiver

0:24:07.600 --> 0:24:09.640
<v Speaker 1>as a vendor, you may only be able to accept

0:24:09.680 --> 0:24:12.720
<v Speaker 1>one but not the other, which we'll talk a little

0:24:12.720 --> 0:24:15.399
<v Speaker 1>bit more about in our our problems with n f

0:24:15.520 --> 0:24:18.560
<v Speaker 1>C section. And then of these companies that we've talked about,

0:24:18.560 --> 0:24:20.719
<v Speaker 1>it seems like Samsung and Visa have been left out

0:24:20.720 --> 0:24:23.960
<v Speaker 1>in the cold. Yeah, you got Samsung Wallet, which is

0:24:23.960 --> 0:24:27.199
<v Speaker 1>a partnership between Samsung and Visa, But this one was

0:24:27.600 --> 0:24:31.200
<v Speaker 1>kind of a a head scratcher because they announced this

0:24:31.400 --> 0:24:34.560
<v Speaker 1>partnership in two thousand thirteen at the Mobile the World

0:24:34.680 --> 0:24:38.280
<v Speaker 1>Mobile Congress, which the two fourteen one is happening as

0:24:38.320 --> 0:24:42.159
<v Speaker 1>we're recording this podcast. But the two thirteen one they

0:24:42.200 --> 0:24:44.480
<v Speaker 1>announced this partnership. They said, Oh, here's what we're gonna do.

0:24:44.520 --> 0:24:45.919
<v Speaker 1>It's gonna be this big thing. It's going to be

0:24:45.960 --> 0:24:49.600
<v Speaker 1>our approach to this NFC payment processing and all the

0:24:49.640 --> 0:24:52.199
<v Speaker 1>sort of wallet features you would expect. And then they

0:24:52.200 --> 0:24:56.120
<v Speaker 1>started announcing the upcoming Samsung phones which did not support

0:24:56.200 --> 0:24:59.480
<v Speaker 1>Samsung Wallet. So you had this partnership in this technology,

0:24:59.520 --> 0:25:02.480
<v Speaker 1>but you didn't have the actual implementation available for anyone

0:25:02.520 --> 0:25:05.440
<v Speaker 1>to purchase in the in the flagship products that were

0:25:05.440 --> 0:25:07.120
<v Speaker 1>coming out. I'm sure it was a it was a

0:25:07.200 --> 0:25:10.600
<v Speaker 1>just missed dovetail kind of situation wherein they couldn't quite

0:25:10.640 --> 0:25:13.200
<v Speaker 1>make it go. Yeah. I mean, it might have even

0:25:13.280 --> 0:25:15.359
<v Speaker 1>been one of those things where you try and factor

0:25:15.400 --> 0:25:18.400
<v Speaker 1>in the price of including another chip in your phone

0:25:18.440 --> 0:25:20.320
<v Speaker 1>because that's going to make it more. Sung is always

0:25:20.400 --> 0:25:23.240
<v Speaker 1>very priced Savage, Oh yeah, yeah, Well, for one thing,

0:25:23.359 --> 0:25:26.600
<v Speaker 1>they're the company that makes a product for every price

0:25:26.640 --> 0:25:29.159
<v Speaker 1>point and every use case. I mean, I watched a

0:25:29.320 --> 0:25:32.960
<v Speaker 1>video recently that showed a lineup of all the different

0:25:33.040 --> 0:25:36.080
<v Speaker 1>Samsung products, and at one point they they joked that

0:25:36.119 --> 0:25:39.000
<v Speaker 1>the video editor had died trying to put it together

0:25:39.080 --> 0:25:40.880
<v Speaker 1>because it was just too many. That was a scene

0:25:40.880 --> 0:25:44.440
<v Speaker 1>Net video by the way, Tales of Adventure or something

0:25:44.440 --> 0:25:46.320
<v Speaker 1>along those lines. Great series. You should check it out.

0:25:46.680 --> 0:25:49.159
<v Speaker 1>But we've got a lot more to talk about with

0:25:49.200 --> 0:25:52.919
<v Speaker 1>this technology, including those pros and cons, and before we

0:25:52.960 --> 0:25:55.000
<v Speaker 1>get to that, I think we should take a quick

0:25:55.040 --> 0:25:59.720
<v Speaker 1>break to thank our sponsor. Alright, so we've kind of

0:25:59.800 --> 0:26:02.800
<v Speaker 1>hit tod that some of the challenges of this whole

0:26:02.920 --> 0:26:06.520
<v Speaker 1>NFC approach, particularly here in the United States. Obviously it's

0:26:06.520 --> 0:26:09.480
<v Speaker 1>already implemented in other parts of the world, so why

0:26:09.520 --> 0:26:12.000
<v Speaker 1>aren't we seeing it everywhere? One of the big reasons,

0:26:12.080 --> 0:26:14.640
<v Speaker 1>Lauren you brought it up it is the fact that

0:26:14.920 --> 0:26:20.040
<v Speaker 1>to build up infrastructure means investing. It's it costs money,

0:26:20.119 --> 0:26:22.280
<v Speaker 1>and especially when you've still got all of these competing

0:26:22.280 --> 0:26:25.960
<v Speaker 1>technologies working, it's it's it doesn't make any sense for

0:26:26.000 --> 0:26:28.360
<v Speaker 1>anyone to build that infrastructure, right if there were one

0:26:28.400 --> 0:26:30.879
<v Speaker 1>of these that came out as the dominant one, and

0:26:30.920 --> 0:26:33.719
<v Speaker 1>therefore it kind of just gravitates to that becoming a

0:26:33.760 --> 0:26:37.240
<v Speaker 1>standard that would be a lot easier on the merchant's

0:26:37.480 --> 0:26:40.160
<v Speaker 1>end of things, because you would just invest in whatever

0:26:40.320 --> 0:26:44.320
<v Speaker 1>technology one out. But in these early days, it's really

0:26:44.400 --> 0:26:46.320
<v Speaker 1>hard to say which one is going to be the

0:26:46.320 --> 0:26:49.000
<v Speaker 1>most important, and in fact, it may change from vendor

0:26:49.040 --> 0:26:53.040
<v Speaker 1>to vendor. You might do some market research of your own,

0:26:53.200 --> 0:26:56.280
<v Speaker 1>just look at past transactions that you have that you've

0:26:56.320 --> 0:26:59.119
<v Speaker 1>managed over the time that you've been a merchant, and

0:26:59.160 --> 0:27:02.720
<v Speaker 1>you might see perhaps your business, for some reason or another,

0:27:03.080 --> 0:27:06.600
<v Speaker 1>you just process more payments through American Express, which means

0:27:06.640 --> 0:27:08.439
<v Speaker 1>you would want to go with that isis approach, right,

0:27:08.720 --> 0:27:11.560
<v Speaker 1>So it makes more sense to you just because the

0:27:11.680 --> 0:27:13.640
<v Speaker 1>vast majority of the people who come into your store

0:27:13.680 --> 0:27:16.720
<v Speaker 1>are using American Express cards. But if they're all using

0:27:17.080 --> 0:27:20.119
<v Speaker 1>Visa cards, or they're all using MasterCard, or there's a

0:27:20.240 --> 0:27:23.760
<v Speaker 1>real strong mix in there, your decisions start getting really

0:27:23.840 --> 0:27:27.679
<v Speaker 1>murky and complicated, and you may end up investing in

0:27:27.680 --> 0:27:31.359
<v Speaker 1>an infrastructure that ultimately fails to take off because some

0:27:31.560 --> 0:27:35.040
<v Speaker 1>other technology becomes dominant. Well, then you've got a real

0:27:35.160 --> 0:27:38.200
<v Speaker 1>problem on your hands, right, You've spent all this money

0:27:38.240 --> 0:27:41.400
<v Speaker 1>with no payoff, absolutely, and and that's that's even assuming

0:27:41.440 --> 0:27:44.320
<v Speaker 1>that people are using these NFC cards a lot of

0:27:44.320 --> 0:27:48.320
<v Speaker 1>people still have meganetic stripes, and so therefore it's it's

0:27:48.320 --> 0:27:50.320
<v Speaker 1>a dual problem. You know, if if you can't get

0:27:50.320 --> 0:27:52.959
<v Speaker 1>customers onto these new cards, then they can't use your

0:27:53.000 --> 0:27:56.280
<v Speaker 1>system and no one it's just yeah, it's it's kind

0:27:56.280 --> 0:27:59.320
<v Speaker 1>of us catch twenty two's right. So you know, you

0:27:59.320 --> 0:28:02.560
<v Speaker 1>you want there to be an existing base of customers

0:28:02.560 --> 0:28:05.120
<v Speaker 1>out there who have this technology so that your investment

0:28:05.160 --> 0:28:09.720
<v Speaker 1>makes sense. But the customers don't really want this technology

0:28:09.800 --> 0:28:13.120
<v Speaker 1>unless there's ways to use it. So yeah, it's this

0:28:13.119 --> 0:28:15.640
<v Speaker 1>this weird problem where you have to have the solution

0:28:15.720 --> 0:28:17.840
<v Speaker 1>to have the problem in order to solve the other half,

0:28:17.960 --> 0:28:21.000
<v Speaker 1>and it's ways. Yeah, And one of those barriers to

0:28:21.040 --> 0:28:23.840
<v Speaker 1>getting customers to sign up for these for these NFC

0:28:23.880 --> 0:28:27.600
<v Speaker 1>cards is the security question, right, because if you're talking

0:28:27.640 --> 0:28:32.719
<v Speaker 1>about transmitting information by radio already you have people wondering

0:28:32.720 --> 0:28:36.119
<v Speaker 1>about the possibility of eavesdroppers, someone carrying some sort of

0:28:36.160 --> 0:28:39.600
<v Speaker 1>device that can read off the information on a chip.

0:28:40.200 --> 0:28:42.360
<v Speaker 1>A couple of different things to keep in mind here. One,

0:28:43.240 --> 0:28:45.720
<v Speaker 1>if you're talking about an active NFC chip, something that's

0:28:45.720 --> 0:28:49.520
<v Speaker 1>actually drawing power from something like a smartphone, it's really

0:28:49.520 --> 0:28:51.640
<v Speaker 1>only gonna be broadcasting when you tell it to broadcast,

0:28:52.080 --> 0:28:55.760
<v Speaker 1>so when you're using the app to actually make a purchase, unless,

0:28:55.760 --> 0:28:58.400
<v Speaker 1>of course, your smartphone itself has been hacked in some way,

0:28:58.480 --> 0:29:03.600
<v Speaker 1>in which case you've got multiple problems, not just NFC absolutely, uh.

0:29:03.720 --> 0:29:06.560
<v Speaker 1>But you know, since it is a radio communication, once

0:29:06.600 --> 0:29:09.560
<v Speaker 1>that once that transmission is active, it can technically be

0:29:09.640 --> 0:29:11.680
<v Speaker 1>picked up from up to like ten meters that's about

0:29:11.720 --> 0:29:15.400
<v Speaker 1>thirty three ft away, right, Yeah, so there is that concern. However,

0:29:15.800 --> 0:29:17.960
<v Speaker 1>one way to get around this concern is to use

0:29:18.160 --> 0:29:22.840
<v Speaker 1>our beloved friend encryption and encryption. I mean, this is

0:29:23.160 --> 0:29:25.640
<v Speaker 1>it's obviously going to be important for any company that

0:29:25.680 --> 0:29:31.080
<v Speaker 1>wants to utilize NFC transmissions because if you don't show

0:29:31.120 --> 0:29:34.680
<v Speaker 1>that you value the safety the financial safety of your customers,

0:29:34.680 --> 0:29:37.760
<v Speaker 1>you're not going to have customers for very long. So

0:29:38.240 --> 0:29:42.400
<v Speaker 1>this is actually pretty sophisticated stuff, and there's encryption along

0:29:42.480 --> 0:29:45.920
<v Speaker 1>multiple steps, so it's not like it's just a simple

0:29:46.200 --> 0:29:48.880
<v Speaker 1>it's not like a transposition cipher where A is B

0:29:49.080 --> 0:29:51.160
<v Speaker 1>and B A C and C s D. They'll never

0:29:51.280 --> 0:29:55.160
<v Speaker 1>figure that out, right, right, When when an NFC card

0:29:55.160 --> 0:29:57.479
<v Speaker 1>and a card reader come into contact with each other,

0:29:57.520 --> 0:30:00.680
<v Speaker 1>and there's encryption levels involved. There's there's this whole series

0:30:00.680 --> 0:30:03.680
<v Speaker 1>of sign countersign kind of exchanges that are going to

0:30:03.800 --> 0:30:08.600
<v Speaker 1>verify that that each bit is dealing with a verified bit. Right,

0:30:08.680 --> 0:30:10.720
<v Speaker 1>So if you were to eavesdrop on that, all you

0:30:10.720 --> 0:30:14.640
<v Speaker 1>would get is the pop product of this conversation, which

0:30:14.640 --> 0:30:17.200
<v Speaker 1>would just be gobbledegook from your perspective. You wouldn't have

0:30:17.240 --> 0:30:20.240
<v Speaker 1>the description key exactly, and nobody has the key in

0:30:20.280 --> 0:30:22.920
<v Speaker 1>this situation. I mean, it's it's a it's a temporary,

0:30:23.040 --> 0:30:27.040
<v Speaker 1>one time use kind of thing. And again, this technology

0:30:27.080 --> 0:30:29.440
<v Speaker 1>is primed to only talk to one device at a

0:30:29.480 --> 0:30:33.120
<v Speaker 1>single time, so that cuts that down quite significantly. Also,

0:30:33.640 --> 0:30:36.040
<v Speaker 1>when you look at it, you know, even though you think, well,

0:30:36.080 --> 0:30:39.480
<v Speaker 1>this sounds like there's some security issues, it's actually safer

0:30:40.000 --> 0:30:44.120
<v Speaker 1>than our old magnetic stripe technology. Right, So even if

0:30:44.160 --> 0:30:47.080
<v Speaker 1>you feel like this has got its own kind of drawbacks,

0:30:47.680 --> 0:30:50.200
<v Speaker 1>it has fewer drawbacks than the stuff we're depending on

0:30:50.320 --> 0:30:52.840
<v Speaker 1>right now. Oh. Absolutely, the data on a on a

0:30:52.880 --> 0:30:56.200
<v Speaker 1>magnetic stripe can be read, written, deleted, or changed with

0:30:56.400 --> 0:30:59.840
<v Speaker 1>pretty common equipment. Yea. This is a reason why, uh,

0:31:00.040 --> 0:31:02.920
<v Speaker 1>when I stay at a hotel that uses a magnetic

0:31:02.960 --> 0:31:06.040
<v Speaker 1>stripe key, I tend to keep the key because you

0:31:06.040 --> 0:31:09.000
<v Speaker 1>never know what's actually been encoded on that key. There

0:31:09.000 --> 0:31:11.440
<v Speaker 1>could be I mean some places use the key as

0:31:11.520 --> 0:31:13.920
<v Speaker 1>also a form of payment, where you can buy stuff

0:31:13.960 --> 0:31:16.960
<v Speaker 1>at a restaurant that's in the hotel, or or a

0:31:17.040 --> 0:31:19.840
<v Speaker 1>shop in the hotel. It's a general identification tool. Share. Yeah,

0:31:19.880 --> 0:31:22.360
<v Speaker 1>so I'll keep those keys and then shread them at home.

0:31:23.040 --> 0:31:27.080
<v Speaker 1>I really do. That's smarter than I am. So and

0:31:27.240 --> 0:31:30.120
<v Speaker 1>I'm not known as a privacy nut. I mean, I'm

0:31:30.160 --> 0:31:32.600
<v Speaker 1>an advocate, but I don't. I don't get like super

0:31:32.640 --> 0:31:35.160
<v Speaker 1>paranoid unless I happen to be around someone like Darren Kitchen,

0:31:35.200 --> 0:31:38.560
<v Speaker 1>because the dude is a brilliant hacker, nice guy. I

0:31:38.600 --> 0:31:41.080
<v Speaker 1>just I just feel like everything I ever said on

0:31:41.120 --> 0:31:43.600
<v Speaker 1>the Internet is in his hand anytime I happened to

0:31:43.600 --> 0:31:46.600
<v Speaker 1>be near him. But other than that, I'm pretty easy going.

0:31:46.680 --> 0:31:49.040
<v Speaker 1>But this is one of those steps I actually do take.

0:31:49.240 --> 0:31:53.360
<v Speaker 1>That's that's not paranoia. That's intelligent different. It's not paranoid

0:31:53.440 --> 0:31:56.360
<v Speaker 1>if they're really out to get you. Uh. And so, Also,

0:31:56.440 --> 0:32:00.120
<v Speaker 1>like we said, these transactions, in every implementation I I've

0:32:00.120 --> 0:32:02.240
<v Speaker 1>seen where you're using it to make a payment, it

0:32:02.320 --> 0:32:06.200
<v Speaker 1>requires that you enter a pin as well. A personal identification,

0:32:06.480 --> 0:32:09.440
<v Speaker 1>right instead of a signature. Right. So when I would

0:32:09.480 --> 0:32:11.840
<v Speaker 1>make a payment at that coffee shop, in order for

0:32:11.880 --> 0:32:13.320
<v Speaker 1>that payment to go through, I would first have to

0:32:13.440 --> 0:32:15.760
<v Speaker 1>input whatever the PIN is, you know, however long that

0:32:15.840 --> 0:32:17.840
<v Speaker 1>might be. It's usually a four digit number, that's what

0:32:17.880 --> 0:32:20.920
<v Speaker 1>we're used to in the United States. Then that would

0:32:21.000 --> 0:32:24.000
<v Speaker 1>allow the transaction to continue. So in other words, if

0:32:24.000 --> 0:32:26.560
<v Speaker 1>you lost your smartphone and someone picked it up, you

0:32:26.560 --> 0:32:29.600
<v Speaker 1>wouldn't have to worry about them automatically being able to

0:32:29.760 --> 0:32:32.840
<v Speaker 1>use that smartphone to go on a spending spree, right right.

0:32:33.080 --> 0:32:36.640
<v Speaker 1>I honestly, magnetic stripes kind of terrify me. They. I recently,

0:32:36.720 --> 0:32:38.440
<v Speaker 1>when I was out to dinner with a friend, we

0:32:38.440 --> 0:32:41.600
<v Speaker 1>we accidentally exchanged credit cards. When we got the bill back,

0:32:42.000 --> 0:32:45.959
<v Speaker 1>and I used his card for two days before I

0:32:46.000 --> 0:32:49.840
<v Speaker 1>noticed that it was his card with no problems. Yeah,

0:32:49.920 --> 0:32:53.000
<v Speaker 1>the security measures in the United States are a little

0:32:53.080 --> 0:32:55.080
<v Speaker 1>on the lax side, depending upon where you go. Some

0:32:55.120 --> 0:32:57.680
<v Speaker 1>places are really good about it, like, for inst instance,

0:32:57.720 --> 0:33:00.360
<v Speaker 1>I have on my card ask for I D written

0:33:00.360 --> 0:33:02.400
<v Speaker 1>on the back rather than my signature, which is a

0:33:02.480 --> 0:33:05.520
<v Speaker 1>terrific way of cutting down at least on that kind

0:33:05.520 --> 0:33:08.920
<v Speaker 1>of kind of problem. So whenever anyone apologizes but asks

0:33:09.000 --> 0:33:12.200
<v Speaker 1>for my idea, I tell them, do not apologize. That's

0:33:12.280 --> 0:33:15.360
<v Speaker 1>what I want. I want that extra level. The problem

0:33:15.360 --> 0:33:17.560
<v Speaker 1>is it just doesn't happen as frequently is should but

0:33:17.600 --> 0:33:20.000
<v Speaker 1>at any rate. So now that kind of brings us

0:33:20.080 --> 0:33:22.440
<v Speaker 1>Chase one of us to talk about coin. So we

0:33:22.440 --> 0:33:26.480
<v Speaker 1>we covered the NFC thing. Coin is not and NFC

0:33:26.680 --> 0:33:31.240
<v Speaker 1>enabled credit card. It's actually a different implementation of electronic

0:33:31.280 --> 0:33:35.760
<v Speaker 1>credit cards, and it's a really nifty idea and the

0:33:35.800 --> 0:33:39.480
<v Speaker 1>implementation is something that I've never seen before, and I

0:33:39.520 --> 0:33:41.560
<v Speaker 1>find it kind of exciting and I like the I

0:33:41.640 --> 0:33:43.360
<v Speaker 1>like the notion of it. But it also has some

0:33:43.440 --> 0:33:46.080
<v Speaker 1>drawbacks that we're going to talk about. Sure, But but

0:33:46.120 --> 0:33:48.080
<v Speaker 1>it is but it is really cool. I got so

0:33:48.120 --> 0:33:50.040
<v Speaker 1>excited when I saw it. So it's it's the same

0:33:50.400 --> 0:33:53.440
<v Speaker 1>size and shape as a standard credit card, and it's

0:33:53.480 --> 0:33:56.960
<v Speaker 1>a it's it's a crowd funded effort. This is this

0:33:57.000 --> 0:33:59.200
<v Speaker 1>was a startup that got some of its funding at

0:33:59.280 --> 0:34:04.880
<v Speaker 1>least by asking people to make contributions to their company.

0:34:04.920 --> 0:34:07.640
<v Speaker 1>So what exactly is it? Well, it's build as a

0:34:07.640 --> 0:34:11.640
<v Speaker 1>device that can replace every type of credit card, loyalty card,

0:34:11.800 --> 0:34:15.200
<v Speaker 1>gift card, and membership card all in one go. So

0:34:15.200 --> 0:34:18.279
<v Speaker 1>in other words, instead of having to carry ten or

0:34:18.320 --> 0:34:21.360
<v Speaker 1>fifteen different types of cards, depending upon the kind of

0:34:21.400 --> 0:34:23.879
<v Speaker 1>person you are, you would only have to have one.

0:34:24.680 --> 0:34:27.440
<v Speaker 1>And it works like this because it's it's actually a

0:34:27.480 --> 0:34:30.680
<v Speaker 1>computer in a card. Um that magnetic stripe on it

0:34:30.760 --> 0:34:33.680
<v Speaker 1>is readwriteable, right, So not it's not. You know, a

0:34:33.719 --> 0:34:37.719
<v Speaker 1>typical magnetic stripe on a credit card is read only you.

0:34:37.960 --> 0:34:42.799
<v Speaker 1>You aren't. Hypothetically, you're not supposed to overwrite it. Uh,

0:34:43.080 --> 0:34:45.839
<v Speaker 1>there's nothing that's given to you in the credit card

0:34:45.880 --> 0:34:48.239
<v Speaker 1>that allows you to overwrite it. There are technologies that

0:34:48.400 --> 0:34:51.600
<v Speaker 1>where you could overwrite the information on your magnetic strip,

0:34:51.719 --> 0:34:54.160
<v Speaker 1>but it's meant to be read, right, Yeah, don't do that.

0:34:54.200 --> 0:34:57.399
<v Speaker 1>By the way, it's almost certainly illegal where you are.

0:34:57.840 --> 0:35:00.480
<v Speaker 1>But then you rate. This is designed so that it

0:35:00.520 --> 0:35:04.840
<v Speaker 1>can on the fly change that magnetic strip to mimic

0:35:05.280 --> 0:35:08.359
<v Speaker 1>whatever card you would be using. So, for one thing,

0:35:08.480 --> 0:35:10.920
<v Speaker 1>whatever card you're using would need to have a magnetic

0:35:10.960 --> 0:35:14.920
<v Speaker 1>stripe as part of its way of being read by

0:35:15.000 --> 0:35:17.160
<v Speaker 1>whatever vendor. So if you have a loyalty card that's

0:35:17.200 --> 0:35:20.160
<v Speaker 1>punched card, that's not necessarily gonna you don't want to

0:35:20.160 --> 0:35:23.080
<v Speaker 1>punch a hole in your coin smart card, that would be.

0:35:24.840 --> 0:35:28.160
<v Speaker 1>But if it has some sort of counterpart where there's

0:35:28.200 --> 0:35:31.760
<v Speaker 1>a magnetic strip or that they just implement that into

0:35:31.880 --> 0:35:34.920
<v Speaker 1>their their vendor system, then you could use it as

0:35:34.920 --> 0:35:38.319
<v Speaker 1>a loyalty card or whatever. U. So yeah, this this

0:35:38.400 --> 0:35:42.600
<v Speaker 1>little computer on the fly can change the programming on

0:35:42.640 --> 0:35:46.600
<v Speaker 1>that magnetic stripe to be whichever card you need. So

0:35:46.840 --> 0:35:50.040
<v Speaker 1>the big advantage from the merchant's side of this is

0:35:50.080 --> 0:35:52.560
<v Speaker 1>that they don't have to install one of those crazy

0:35:52.600 --> 0:35:56.080
<v Speaker 1>readers that NFC or r F I D would need, right,

0:35:56.160 --> 0:36:00.400
<v Speaker 1>They could just use their their established credit card reading

0:36:01.200 --> 0:36:04.560
<v Speaker 1>equipment to do this. Because that magnetic strikes the same

0:36:04.600 --> 0:36:07.680
<v Speaker 1>thing on the coin card as it would be if

0:36:07.719 --> 0:36:10.560
<v Speaker 1>you were using the actual credit card that it's mimicking.

0:36:10.920 --> 0:36:13.279
<v Speaker 1>So when you you swipe it, it's just going to

0:36:13.400 --> 0:36:17.080
<v Speaker 1>read as if it were your Visa or MasterCard or whatever. Right,

0:36:17.120 --> 0:36:19.279
<v Speaker 1>And the advantage to you is that you can you

0:36:19.320 --> 0:36:22.960
<v Speaker 1>can enter all of your systems of payment and loyalty

0:36:23.040 --> 0:36:27.279
<v Speaker 1>that use these magnetic stripes into into the app. Yeah. Yeah,

0:36:27.320 --> 0:36:29.160
<v Speaker 1>So the way this would work is you pair the

0:36:29.520 --> 0:36:33.080
<v Speaker 1>coin smart card with something like a smart phone that

0:36:33.080 --> 0:36:35.960
<v Speaker 1>that's running this coin app on it and you also

0:36:36.040 --> 0:36:40.080
<v Speaker 1>get a little a little um uh peripheral that plugs

0:36:40.080 --> 0:36:41.720
<v Speaker 1>into your phone. It's kind of like one of those

0:36:41.719 --> 0:36:45.959
<v Speaker 1>square card readers that you've seen that that merchants often

0:36:45.960 --> 0:36:48.200
<v Speaker 1>will use, where it's hooked up to an iPhone. You

0:36:48.280 --> 0:36:51.680
<v Speaker 1>just swipe a card through the square things. Yeah, because

0:36:51.719 --> 0:36:54.920
<v Speaker 1>it turns anyone, it's like anyone into a mobile payment

0:36:54.960 --> 0:36:57.560
<v Speaker 1>processing system and you can have I mean for people

0:36:57.560 --> 0:37:00.200
<v Speaker 1>who run things like they go to a convinced and

0:37:00.640 --> 0:37:02.759
<v Speaker 1>they have a booth set up at a convention for

0:37:02.800 --> 0:37:06.200
<v Speaker 1>them to sell merchandise to people. This is great because

0:37:06.360 --> 0:37:09.640
<v Speaker 1>it has such a low barrier of entry. The cost

0:37:09.719 --> 0:37:12.600
<v Speaker 1>is really low. Yeah, it's it's essentially free, and then

0:37:12.640 --> 0:37:17.160
<v Speaker 1>you pay a certain percentage of each of each swipe

0:37:16.080 --> 0:37:20.440
<v Speaker 1>of transaction. So so it's great anyway. But this technology

0:37:20.520 --> 0:37:22.600
<v Speaker 1>works very much the same way. It's got a little

0:37:22.640 --> 0:37:27.440
<v Speaker 1>swipe reader that you connect to your phone, and as

0:37:27.480 --> 0:37:30.279
<v Speaker 1>you swipe a card, it stores all that information that's

0:37:30.320 --> 0:37:33.719
<v Speaker 1>in that magnetic stripe onto the app and then relays

0:37:33.760 --> 0:37:36.520
<v Speaker 1>that to the coin smart card, so that the coin

0:37:36.560 --> 0:37:40.160
<v Speaker 1>smart card is able to mimic that particular credit card

0:37:40.239 --> 0:37:42.959
<v Speaker 1>or loyalty card or whatever it is. Uh. You're also

0:37:43.000 --> 0:37:45.319
<v Speaker 1>supposed to take a picture of that card, so that

0:37:45.360 --> 0:37:47.680
<v Speaker 1>way you will be able to cycle through the cards

0:37:47.680 --> 0:37:50.120
<v Speaker 1>properly when you're using it and remember which is which. Yeah,

0:37:50.160 --> 0:37:51.600
<v Speaker 1>because if you know, if you have been to have

0:37:51.600 --> 0:37:55.200
<v Speaker 1>a check card and a credit card, and it's really

0:37:55.239 --> 0:37:58.960
<v Speaker 1>important for you to use the right one. Yeah, I've

0:37:59.000 --> 0:38:01.960
<v Speaker 1>known some people who remember as entire credit card numbers

0:38:02.000 --> 0:38:04.680
<v Speaker 1>of their own. But I know, yeah, I know folks

0:38:04.719 --> 0:38:07.840
<v Speaker 1>who make enough purchases online where they've committed all of

0:38:07.880 --> 0:38:10.760
<v Speaker 1>the cards they have to memory. I don't do that frequently.

0:38:10.880 --> 0:38:13.560
<v Speaker 1>I have a hard time with like my phone number

0:38:13.680 --> 0:38:17.080
<v Speaker 1>and my social Security number. I had a hard time

0:38:17.239 --> 0:38:20.080
<v Speaker 1>with the three digit security code that's on the back

0:38:20.080 --> 0:38:23.480
<v Speaker 1>of your card, which every single card I've owned, that

0:38:23.560 --> 0:38:26.360
<v Speaker 1>number has worn off within like three weeks of getting

0:38:26.360 --> 0:38:29.840
<v Speaker 1>the card. So I have to commit this three digit

0:38:29.920 --> 0:38:33.920
<v Speaker 1>number to memory, which shouldn't be a problem, but I

0:38:34.000 --> 0:38:35.960
<v Speaker 1>got a lot of brain cells that are dedicated to

0:38:36.400 --> 0:38:40.200
<v Speaker 1>firefly trivia, so apparently a three digit number is a

0:38:40.360 --> 0:38:44.200
<v Speaker 1>herculean task for me to remember at any rate. So

0:38:44.280 --> 0:38:46.759
<v Speaker 1>you swipe all your cards, you differentiate them. Your coin

0:38:46.840 --> 0:38:49.719
<v Speaker 1>smart card can then represent any of those cards, so

0:38:49.760 --> 0:38:54.120
<v Speaker 1>you can then put those those physical cards simply safe. Um,

0:38:54.200 --> 0:38:57.160
<v Speaker 1>keeping in mind that there are some some instances where

0:38:57.600 --> 0:38:59.360
<v Speaker 1>you might run into some trouble. I'll get into that

0:38:59.400 --> 0:39:02.000
<v Speaker 1>when we get into some of the cons sure, but

0:39:02.080 --> 0:39:04.720
<v Speaker 1>so okay, So so coin interacts with your cell phone

0:39:04.800 --> 0:39:08.600
<v Speaker 1>through Bluetooth low energy. It's so good that we already

0:39:08.600 --> 0:39:10.359
<v Speaker 1>did that podcast, so we don't have to go into

0:39:10.400 --> 0:39:13.400
<v Speaker 1>what this is. But it does mean that the smart

0:39:13.440 --> 0:39:15.880
<v Speaker 1>card and your app can communicate up to a fifty

0:39:15.960 --> 0:39:18.400
<v Speaker 1>meters away from each other or or thereabouts. That's like

0:39:18.440 --> 0:39:22.200
<v Speaker 1>the ideal maximum range. Uh So this actually allows you

0:39:22.239 --> 0:39:24.799
<v Speaker 1>to have some cool features built into that smart card

0:39:24.960 --> 0:39:27.799
<v Speaker 1>a right. One of its security features is that if

0:39:27.960 --> 0:39:30.719
<v Speaker 1>your your coin card gets out of range, out of

0:39:30.760 --> 0:39:34.000
<v Speaker 1>that fifty ish meter Bluetooth loow energy range of your phone,

0:39:34.040 --> 0:39:36.040
<v Speaker 1>your phone will send you a little alert saying like, hey,

0:39:36.040 --> 0:39:38.360
<v Speaker 1>you might have left your card somewhere. Yeah, which I

0:39:38.400 --> 0:39:43.040
<v Speaker 1>have done a few times at restaurants. So this would

0:39:43.080 --> 0:39:46.000
<v Speaker 1>actually be that little bit of security where if someone

0:39:46.120 --> 0:39:48.920
<v Speaker 1>took your wallet but you still had your phone, then

0:39:48.920 --> 0:39:50.640
<v Speaker 1>you would get an alert. So you knew that you

0:39:50.640 --> 0:39:54.200
<v Speaker 1>would know, maybe faster than normal, that you've been pickpocketed

0:39:54.600 --> 0:39:57.799
<v Speaker 1>or if you're just happen to be careless occasionally, you know,

0:39:57.840 --> 0:40:00.160
<v Speaker 1>once in a blue moon, then it would all to you.

0:40:00.280 --> 0:40:02.080
<v Speaker 1>If you had left your card behind, you can immediately

0:40:02.120 --> 0:40:05.319
<v Speaker 1>go back and reclaim your card, which was pretty cool.

0:40:05.680 --> 0:40:09.120
<v Speaker 1>It's designed to be really energy efficient. That bluetooth low

0:40:09.160 --> 0:40:11.640
<v Speaker 1>energy stuff is pretty cool. So the battery in the

0:40:11.719 --> 0:40:14.200
<v Speaker 1>card should last a good couple of years, and then

0:40:14.239 --> 0:40:16.560
<v Speaker 1>after it's out, you just replace it the way that

0:40:16.600 --> 0:40:19.960
<v Speaker 1>you would replace any other magnetic stripe card exactly. And

0:40:20.000 --> 0:40:22.520
<v Speaker 1>that's another thing is that you know that magnetic stripe stuff,

0:40:22.560 --> 0:40:25.920
<v Speaker 1>that that material can wear down after lots, especially if

0:40:25.920 --> 0:40:29.359
<v Speaker 1>you happen to be a frequent shopper. Um So in

0:40:29.400 --> 0:40:31.800
<v Speaker 1>that sense, you would need to replace the card anyway

0:40:31.800 --> 0:40:35.040
<v Speaker 1>because it would actually physically wear down. But the battery itself,

0:40:35.080 --> 0:40:37.560
<v Speaker 1>you don't recharge it, right, there's no you don't plug

0:40:37.600 --> 0:40:39.439
<v Speaker 1>your smart card in at the end of the day.

0:40:39.520 --> 0:40:41.799
<v Speaker 1>It will actually hold that charge for two years. Okay,

0:40:41.840 --> 0:40:44.360
<v Speaker 1>But so this is all really cool, but it sounds

0:40:44.360 --> 0:40:46.640
<v Speaker 1>to me like it's not going to solve this problem

0:40:46.640 --> 0:40:52.680
<v Speaker 1>of magnetic stripe card information being pretty insecure compared with NFC. Yeah, yeah, exactly,

0:40:52.719 --> 0:40:55.200
<v Speaker 1>if you happen to have a device that can read

0:40:55.239 --> 0:40:59.520
<v Speaker 1>a magnetic stripe. Well, worst case scenario, let's say that

0:40:59.640 --> 0:41:04.359
<v Speaker 1>some on some um person working at a a any

0:41:04.400 --> 0:41:08.200
<v Speaker 1>kind of merchant, who has decided they're going to set

0:41:08.239 --> 0:41:11.440
<v Speaker 1>out on a life of crime, and they have invested

0:41:11.520 --> 0:41:15.520
<v Speaker 1>in a magnetic card reader where they can swipe and

0:41:15.560 --> 0:41:17.960
<v Speaker 1>store information. Let's say that they've got ahold of that,

0:41:18.320 --> 0:41:21.040
<v Speaker 1>and they get ahold of your card. Maybe you've handed

0:41:21.080 --> 0:41:23.120
<v Speaker 1>it over for a purchase and you think you're just

0:41:23.160 --> 0:41:26.040
<v Speaker 1>making a regular purchase. Meanwhile they are cycling through every

0:41:26.040 --> 0:41:28.640
<v Speaker 1>single card you have and reading it. Not only would

0:41:28.640 --> 0:41:30.839
<v Speaker 1>they have access to whatever card you were using at

0:41:30.840 --> 0:41:35.640
<v Speaker 1>the time, they might theoretically be able to access everything.

0:41:36.560 --> 0:41:38.640
<v Speaker 1>Now they're they're ways of getting around this with the app,

0:41:38.719 --> 0:41:41.160
<v Speaker 1>so that if you cycle from one card to the next,

0:41:41.239 --> 0:41:44.520
<v Speaker 1>you have to agree to it. So in that case,

0:41:44.920 --> 0:41:46.800
<v Speaker 1>the worst case scenario is they just get access to

0:41:46.840 --> 0:41:49.080
<v Speaker 1>whatever card you're using at the time for that transaction,

0:41:49.120 --> 0:41:53.200
<v Speaker 1>as opposed to every card you own. So better, Yeah,

0:41:53.239 --> 0:41:56.120
<v Speaker 1>it's better. It's better. It's way better than suddenly saying, oh,

0:41:56.200 --> 0:41:59.120
<v Speaker 1>my Visa card was lifted and my Master card, my

0:41:59.200 --> 0:42:01.800
<v Speaker 1>American Express card and I no longer have nine cups

0:42:01.800 --> 0:42:04.880
<v Speaker 1>of coffee at my favorite local coffee right. Apparently I

0:42:05.000 --> 0:42:07.880
<v Speaker 1>made a purchase of fifty seven cups of coffee today,

0:42:08.200 --> 0:42:10.160
<v Speaker 1>don't have any memory of that, possibly because of the

0:42:10.160 --> 0:42:13.640
<v Speaker 1>caffeine affecting my brain, or more likely I have been hacked.

0:42:14.000 --> 0:42:18.759
<v Speaker 1>So yeah, there's that issue. Also, um, you know, they

0:42:18.800 --> 0:42:22.000
<v Speaker 1>could store a lot more information on them than a

0:42:22.160 --> 0:42:25.280
<v Speaker 1>credit card would typically have on it. So in theory,

0:42:25.320 --> 0:42:28.520
<v Speaker 1>if someone were able to get access to maybe the

0:42:28.560 --> 0:42:30.880
<v Speaker 1>worst case, they get access to both your phone or

0:42:30.880 --> 0:42:32.960
<v Speaker 1>whatever device you happen to have paired with your card

0:42:33.040 --> 0:42:35.400
<v Speaker 1>and the card itself, they get to get access to

0:42:35.760 --> 0:42:39.240
<v Speaker 1>lots of personal data, so that would be an issue too. Also,

0:42:39.440 --> 0:42:42.560
<v Speaker 1>I do want to put in that magnetic stripe cards

0:42:42.760 --> 0:42:45.840
<v Speaker 1>and and computerized magnetic magnetic stripe cards. I'm going to

0:42:46.080 --> 0:42:47.400
<v Speaker 1>figure out how to say that by the end of

0:42:47.440 --> 0:42:51.320
<v Speaker 1>this podcast. I swear like coin are not the only

0:42:51.360 --> 0:42:53.080
<v Speaker 1>things that you can put a whole bunch of different

0:42:53.080 --> 0:42:56.440
<v Speaker 1>information on. NFC chips are capable of holding multiple kinds

0:42:56.480 --> 0:42:59.520
<v Speaker 1>of all kinds of info. Yeah, yeah, yeah, exactly. It

0:42:59.560 --> 0:43:02.879
<v Speaker 1>doesn't have to just be uh financial oriented or even

0:43:03.040 --> 0:43:05.479
<v Speaker 1>how many times you've bought that cup of coffee. Yeah,

0:43:05.480 --> 0:43:07.680
<v Speaker 1>in Europe they're they're used as patient I D cards

0:43:07.719 --> 0:43:11.160
<v Speaker 1>that store a certain amount of medical information on them. Right. Yeah,

0:43:11.200 --> 0:43:15.080
<v Speaker 1>So I mean the convenience feature I totally understand, right,

0:43:15.239 --> 0:43:17.800
<v Speaker 1>Especially if you are someone who has lots of different cards,

0:43:17.880 --> 0:43:21.960
<v Speaker 1>the coin approach makes a lot of sense from that respect. Personally,

0:43:22.040 --> 0:43:24.800
<v Speaker 1>I don't actually carry a lot of different credit cards,

0:43:24.800 --> 0:43:27.120
<v Speaker 1>so for this, I would think it was a really

0:43:27.160 --> 0:43:30.239
<v Speaker 1>cool technology, but it wouldn't be terribly useful for me.

0:43:30.840 --> 0:43:33.239
<v Speaker 1>The cards that I do carry I want to keep

0:43:33.400 --> 0:43:36.399
<v Speaker 1>very very separate and not have any chance that would

0:43:36.440 --> 0:43:39.200
<v Speaker 1>excellently use one that rather than the other. Um. But

0:43:40.200 --> 0:43:42.120
<v Speaker 1>I could see how this could be really important for

0:43:42.120 --> 0:43:45.240
<v Speaker 1>someone who has multiple cards that they're constantly magic, particularly

0:43:45.239 --> 0:43:47.680
<v Speaker 1>if you're one of those people who have that that

0:43:47.719 --> 0:43:50.080
<v Speaker 1>you know, guys, you know what I'm talking about where

0:43:50.200 --> 0:43:53.759
<v Speaker 1>you can't sit upright because your wallet is so thick

0:43:53.840 --> 0:43:57.359
<v Speaker 1>that you're always kilted at an angle. Um. You know,

0:43:57.520 --> 0:43:59.880
<v Speaker 1>I feel you. I used to be you, but I

0:44:00.120 --> 0:44:02.759
<v Speaker 1>I've managed to I did. I got rid of a

0:44:02.800 --> 0:44:06.160
<v Speaker 1>lot of loyalty guards. I said, you know what, my loyalty.

0:44:06.239 --> 0:44:08.600
<v Speaker 1>You can't put a price on it. I'm a free agent.

0:44:08.800 --> 0:44:11.439
<v Speaker 1>I go where I want to. But yeah, so that's

0:44:11.600 --> 0:44:14.319
<v Speaker 1>you know, things to keep in mind. You are you're

0:44:14.400 --> 0:44:17.640
<v Speaker 1>you are a coffee rebel, Jonathan, I am. Yeah. Look,

0:44:18.600 --> 0:44:20.919
<v Speaker 1>just because I went into Starbucks, you know, twelve times

0:44:20.960 --> 0:44:22.640
<v Speaker 1>last week, doesn't mean I'm going to go to that

0:44:22.640 --> 0:44:25.359
<v Speaker 1>one today, despite the fact that's the most convenient because

0:44:25.360 --> 0:44:29.239
<v Speaker 1>it's right across the street. Anyway. Yeah, it's interesting technology.

0:44:29.280 --> 0:44:32.280
<v Speaker 1>I love the idea that it's a read write magnetic strip.

0:44:32.400 --> 0:44:34.359
<v Speaker 1>That to me is just cool that it's oh yeah,

0:44:34.400 --> 0:44:35.680
<v Speaker 1>you know, it's kind of like it it makes me

0:44:35.719 --> 0:44:37.480
<v Speaker 1>think of something that you would see in a science

0:44:37.480 --> 0:44:39.960
<v Speaker 1>fiction movie, like you know, Blade Runner being one of

0:44:39.960 --> 0:44:42.759
<v Speaker 1>the favorites around here in the office. But it's right

0:44:42.800 --> 0:44:45.319
<v Speaker 1>here right now. So yeah, so thank you Chase for

0:44:45.320 --> 0:44:47.680
<v Speaker 1>for asking us about that, because although although it is

0:44:47.560 --> 0:44:50.680
<v Speaker 1>it is a technically kind of separate conversation from the

0:44:50.920 --> 0:44:54.760
<v Speaker 1>NFC technology one, it's still related and I'm excited about

0:44:54.800 --> 0:44:58.200
<v Speaker 1>both of these technologies upcoming. Yeah. Yeah, yeah, especially uh,

0:44:58.400 --> 0:45:01.839
<v Speaker 1>you know, we're seeing, like, like we said, deadlines here

0:45:01.960 --> 0:45:05.000
<v Speaker 1>October two thousand fifteen for these smart cards coming up

0:45:05.000 --> 0:45:07.759
<v Speaker 1>from the major credit card companies and hopefully that will

0:45:07.840 --> 0:45:10.120
<v Speaker 1>also mean that we'll have an agreed upon standard at

0:45:10.200 --> 0:45:14.160
<v Speaker 1>that point. And also the coin Um smart card I

0:45:14.200 --> 0:45:17.120
<v Speaker 1>think they're launching sometime in the summer of two thousand

0:45:17.120 --> 0:45:19.720
<v Speaker 1>fourteen is when they should start seeing the actual products

0:45:19.719 --> 0:45:22.560
<v Speaker 1>start getting into Backer's hands. I'm I'm wondering how this

0:45:22.760 --> 0:45:25.919
<v Speaker 1>NFC decision is going to start affecting coin and whether

0:45:26.040 --> 0:45:28.359
<v Speaker 1>or not Coin is running a little bit scared right now. Yeah,

0:45:28.520 --> 0:45:30.400
<v Speaker 1>it could be that's one of those great ideas that

0:45:30.480 --> 0:45:33.359
<v Speaker 1>launched too late. Uh you know, I'm sure we're going

0:45:33.400 --> 0:45:36.880
<v Speaker 1>to see support from magnetic stripe sticking around for a

0:45:36.880 --> 0:45:40.240
<v Speaker 1>little while. Anyway, I mean, merchants are going to probably

0:45:40.239 --> 0:45:43.040
<v Speaker 1>have multiple things that will have to rely upon, so

0:45:43.080 --> 0:45:45.279
<v Speaker 1>if you if I can't imagine anyone just throwing the

0:45:45.280 --> 0:45:47.560
<v Speaker 1>system out the window, and unless they decided to do

0:45:47.560 --> 0:45:49.920
<v Speaker 1>it like office space style, which is fair. That also

0:45:50.160 --> 0:45:52.920
<v Speaker 1>was did bring up one other issue I thought of

0:45:53.160 --> 0:45:56.080
<v Speaker 1>with the possibility of using coin as a payment. I

0:45:56.400 --> 0:45:58.279
<v Speaker 1>totally it's slipped my mind, but now it's come back

0:45:58.320 --> 0:46:02.480
<v Speaker 1>to me. If our is lost to the facility you're in,

0:46:02.960 --> 0:46:07.359
<v Speaker 1>so some places still have those old carbon copy uh

0:46:07.520 --> 0:46:09.520
<v Speaker 1>devices where you put your card down, it makes a

0:46:09.560 --> 0:46:12.080
<v Speaker 1>hard carbon copy of whatever is. And this is also

0:46:12.120 --> 0:46:14.120
<v Speaker 1>something you'll see if you go to like conventions or

0:46:14.160 --> 0:46:16.239
<v Speaker 1>things like that where people aren't able to afford the

0:46:16.280 --> 0:46:20.880
<v Speaker 1>electronic versions um or perhaps there's a a malfunction of

0:46:20.920 --> 0:46:23.520
<v Speaker 1>some sort, or if you're in the basement of a

0:46:23.600 --> 0:46:26.200
<v Speaker 1>large hotel, for example, and you cannot use a card

0:46:26.200 --> 0:46:31.239
<v Speaker 1>swiper that's to be transmitting via three G. Yeah, yeah,

0:46:31.280 --> 0:46:34.399
<v Speaker 1>you can't get a signal, the WiFi is completely worked. Yeah,

0:46:34.480 --> 0:46:37.000
<v Speaker 1>you've gotta You've gotta figure something else out. Well, a

0:46:37.040 --> 0:46:39.040
<v Speaker 1>coin card won't help you in that sense because it's

0:46:39.080 --> 0:46:41.640
<v Speaker 1>not going to have the physical numbers on the card

0:46:41.760 --> 0:46:45.359
<v Speaker 1>for them to copy using this old method. So if

0:46:45.400 --> 0:46:47.640
<v Speaker 1>there ever is a situation where you have to make

0:46:47.640 --> 0:46:50.359
<v Speaker 1>a purchase through a merchant who doesn't have access to

0:46:50.600 --> 0:46:54.200
<v Speaker 1>WiFi or three G or anything like that, or a

0:46:54.200 --> 0:46:57.520
<v Speaker 1>telephone line, then I mean, granted, that's you know, one

0:46:58.120 --> 0:47:00.400
<v Speaker 1>one case out of you know, a hundred that you

0:47:00.440 --> 0:47:03.399
<v Speaker 1>would be encountering on a normal basis, but still something

0:47:03.440 --> 0:47:05.720
<v Speaker 1>to think about. It's something where the coin method would

0:47:05.719 --> 0:47:08.640
<v Speaker 1>not work. Every time it rains. My favorite tie restaurant

0:47:08.640 --> 0:47:10.759
<v Speaker 1>is off limits because I don't have cash on me.

0:47:10.920 --> 0:47:14.759
<v Speaker 1>Oh wow. That's well, whenever I go shopping at at

0:47:14.760 --> 0:47:17.040
<v Speaker 1>any sort of convention or conference, like if I'm looking

0:47:17.120 --> 0:47:19.600
<v Speaker 1>at gift shops or you know, Dragon Con here in

0:47:19.600 --> 0:47:23.239
<v Speaker 1>in in Atlanta has an enormous actually sometimes more than

0:47:23.320 --> 0:47:27.400
<v Speaker 1>one enormous dealer room that has all these different vendors

0:47:27.440 --> 0:47:29.120
<v Speaker 1>with cool stuff in it, but a lot of them.

0:47:29.200 --> 0:47:32.520
<v Speaker 1>You know, the one booth might be really technologically savvy

0:47:32.560 --> 0:47:35.120
<v Speaker 1>and ready to deal with anything, and the next booth

0:47:35.200 --> 0:47:37.680
<v Speaker 1>might be, you know, you need to you need to

0:47:37.760 --> 0:47:41.000
<v Speaker 1>barter with chickens. It's just it's they run the whole gamut,

0:47:41.280 --> 0:47:44.279
<v Speaker 1>really they do. And I'm personally sick to death of

0:47:44.360 --> 0:47:47.080
<v Speaker 1>carrying chickens with me to Dragon Con. I'm not happy

0:47:47.120 --> 0:47:51.399
<v Speaker 1>about either. It's just it's not convenient. So anyway, thank

0:47:51.440 --> 0:47:53.440
<v Speaker 1>you so much Chase for asking about coin. It was

0:47:53.480 --> 0:47:55.680
<v Speaker 1>fun to get into that. And I hope that this

0:47:55.880 --> 0:47:58.400
<v Speaker 1>kind of gives some of our our u S listeners

0:47:58.440 --> 0:48:00.480
<v Speaker 1>and a better idea of what enough See is all

0:48:00.520 --> 0:48:03.520
<v Speaker 1>about and what they can expect to see over the

0:48:03.520 --> 0:48:06.160
<v Speaker 1>next couple of years. And uh, for those of you

0:48:06.280 --> 0:48:08.799
<v Speaker 1>in other places where you've been using NFC for a while,

0:48:08.880 --> 0:48:11.680
<v Speaker 1>maybe you learned exactly what's going on behind the scenes

0:48:11.719 --> 0:48:14.400
<v Speaker 1>of that technology you depend upon frequently. I hope that

0:48:14.440 --> 0:48:16.960
<v Speaker 1>this was helpful for you guys too, And if you

0:48:17.040 --> 0:48:19.800
<v Speaker 1>have any suggestions for future topics that we can tackle

0:48:19.920 --> 0:48:22.400
<v Speaker 1>here at tech Stuff, here's what I want you to do.

0:48:22.480 --> 0:48:25.080
<v Speaker 1>I want you to send us an email. That address

0:48:25.200 --> 0:48:28.960
<v Speaker 1>is tech stuff at Discovery dot com. Or if you

0:48:29.000 --> 0:48:31.280
<v Speaker 1>want to just be really succinct you think an email

0:48:31.320 --> 0:48:34.640
<v Speaker 1>is just that's too formal, let's know on social media

0:48:34.680 --> 0:48:37.840
<v Speaker 1>you can find us at Twitter, at Facebook, and at tumbler.

0:48:37.920 --> 0:48:41.439
<v Speaker 1>We use the handle tech Stuff hs W at all

0:48:41.520 --> 0:48:44.720
<v Speaker 1>three locations, and we will talk to you again really

0:48:44.760 --> 0:48:50.640
<v Speaker 1>soon for more on this and thousands of other topics.

0:48:50.800 --> 0:48:57.920
<v Speaker 1>Does it staff works dot com.