WEBVTT

00:00:01.140 --> 00:00:03.390
[Autogenerated] Let's go back to the retail stores network of wide

00:00:03.390 --> 00:00:07.090
brain coffee and see how scope could be reduced by outsourcing

00:00:07.090 --> 00:00:08.750
some of the payment card processing.

00:00:09.540 --> 00:00:12.520
A very common technique now in the retail environment is to

00:00:12.520 --> 00:00:16.880
take all cardholder data out scope by using validated point

00:00:16.880 --> 00:00:18.450
to point encryption solutions.

00:00:19.640 --> 00:00:20.700
Envy solutions.

00:00:20.710 --> 00:00:24.720
The cardholder data is strongly encrypted in secure module

00:00:24.730 --> 00:00:28.460
inside the permit terminal and then transmitted to a point to

00:00:28.460 --> 00:00:32.950
point encryption solution provider, who then passes it to the acquiring bank.

00:00:34.140 --> 00:00:37.350
The solution provider will also look after the clearing file.

00:00:37.740 --> 00:00:42.740
They can provide the necessary reconciliation information to an organizations of

00:00:42.740 --> 00:00:46.330
carrying system on with point to point encryption in place.

00:00:46.590 --> 00:00:47.740
There's no storage,

00:00:47.870 --> 00:00:51.260
processing or transmission of cardholder data anywhere

00:00:51.320 --> 00:00:54.780
in the wired brain coffee systems, and it's PC idea,

00:00:54.780 --> 00:00:55.650
says compliance.

00:00:56.140 --> 00:00:59.100
But this channel will be restricted to the number of

00:00:59.100 --> 00:01:02.650
requirements listed in S a Q P two p A, which is quite small.

00:01:03.290 --> 00:01:05.510
If the point of sale system requires something that

00:01:05.510 --> 00:01:07.810
looks like a 16 digit panto operate,

00:01:08.000 --> 00:01:11.280
the payment terminal can also just generate a truncated power,

00:01:11.280 --> 00:01:12.450
a token to send to it.

00:01:12.940 --> 00:01:13.680
And yes,

00:01:13.860 --> 00:01:17.170
I completely understand that this requires replacing every

00:01:17.170 --> 00:01:19.150
single payment terminal in the organization.

00:01:19.540 --> 00:01:22.350
But that's something that has been them every few years, anyway.

00:01:23.210 --> 00:01:25.690
And with the drive to accepting contact list transactions,

00:01:25.790 --> 00:01:28.370
many organizations are taking advantage of the fact that they

00:01:28.370 --> 00:01:30.220
have to upgrade their terminals anyway.

00:01:30.530 --> 00:01:34.050
And they're deploying point to point encryption solutions at the same time.

00:01:35.340 --> 00:01:38.690
Now here's the wide brain coffee e commerce network.

00:01:38.800 --> 00:01:39.420
And again,

00:01:39.550 --> 00:01:43.650
let's see if any of this could be sensibly outsourced and the answer is yes.

00:01:43.760 --> 00:01:47.460
It could be outsourced very easily when the consumer

00:01:47.460 --> 00:01:48.880
is ready to make their payment,

00:01:49.070 --> 00:01:52.020
there could be redirected to a payment page hosted

00:01:52.030 --> 00:01:53.750
by a payment service provider,

00:01:54.240 --> 00:01:57.560
and then the wide brain coffee website doesn't see any Kartal.

00:01:57.560 --> 00:02:01.110
The data and so wide brain will just need to complete the

00:02:01.110 --> 00:02:05.370
requirements contained in S a que a to validate their PC idea says

00:02:05.370 --> 00:02:07.350
compliance for this payment acceptance channel.

00:02:07.840 --> 00:02:10.000
And yes, that's another business change,

00:02:10.000 --> 00:02:12.580
and there will be a cost of using the payment service provider.

00:02:12.800 --> 00:02:16.530
But I can almost guarantee that this cost will be smaller than

00:02:16.530 --> 00:02:20.100
maintaining the website to the level of prescriptive technical

00:02:20.100 --> 00:02:23.450
controls on compliance that PC ideas s requires
