WEBVTT

00:00:00.716 --> 00:00:05.120
So 3.1 is all about not keeping it if you don't need it; 3.2 is

00:00:05.120 --> 00:00:06.774
a weird one because now it's saying well,

00:00:06.774 --> 00:00:09.379
don't keep sensitive authentication data.

00:00:09.379 --> 00:00:10.688
Right.

00:00:10.688 --> 00:00:12.868
And that's pretty self-explanatory, isn't it?

00:00:12.868 --> 00:00:13.779
Right.

00:00:13.779 --> 00:00:15.818
Do you have merchants or clients where that's a

00:00:15.818 --> 00:00:19.569
problem for you where they think oh, I'll keep this or I'll keep that?

00:00:19.569 --> 00:00:25.705
Well, at the risk of sort of tip-toeing over the brink of call recordings,

00:00:25.705 --> 00:00:29.819
that's the most obvious case, right?

00:00:29.819 --> 00:00:33.276
Where you've recorded the CVV2 as part of the MOTO transaction?

00:00:33.276 --> 00:00:34.068
Right.

00:00:34.068 --> 00:00:38.025
That's the most obvious case.

00:00:38.025 --> 00:00:40.833
Other cases, at least for merchants, any longer,

00:00:40.833 --> 00:00:42.951
I don't find that to be particularly common,

00:00:42.951 --> 00:00:44.431
and even for service providers,

00:00:44.431 --> 00:00:48.515
I don't find that to be particularly common unless the

00:00:48.515 --> 00:00:50.262
entity is involved in card issuing,

00:00:50.262 --> 00:00:52.326
in which case there's kind of a pass for that.

00:00:52.326 --> 00:00:53.876
Yeah, there is a pass for that.

00:00:53.876 --> 00:00:54.229
But you know,

00:00:54.229 --> 00:00:56.002
I used to see that a lot in e-commerce where people would

00:00:56.002 --> 00:00:58.859
keep the PAN and the CVV2 together.

00:00:58.859 --> 00:01:00.013
Yes, once upon a time.

00:01:00.013 --> 00:01:00.993
I think that's gone now, really.

00:01:00.993 --> 00:01:04.993
By and large, yes.
