[00:00:00.205]

Hi, I’m Steven from Littlepay

[00:00:02.405]

and today I’ll be going through

[00:00:04.085]

how littlepay supports multi operator capping.

[00:00:06.715]

Multi operator. Capping or mock is where two

[00:00:10.165]

or more transport operators with their own

[00:00:13.185]

separate open loop systems collaborate

[00:00:15.925]

to offer passengers a payment cap when they travel

[00:00:18.445]

across focus operators.

[00:00:20.675]

There are a few points to note though your existing system

[00:00:25.005]

doesn’t have to change.

[00:00:26.715]

You do have to have data sharing agreements

[00:00:28.535]

of all members of the mock scheme.

[00:00:29.915]

But don’t worry, we already have tried

[00:00:32.175]

and tested templates for this

[00:00:33.795]

for your data protection officers.

[00:00:35.635]

In terms of PCI exposure, there is no exposure

[00:00:39.555]

of the sensitive EMV card data

[00:00:41.275]

to any system other than little paste level one

[00:00:44.415]

P-C-I-D-S-S certified PSP.

[00:00:47.195]

So you should have no additional PCI concerns when it comes

[00:00:50.875]

to calculating revenue.

[00:00:51.935]

Apportionment Littlepay provides a full suite of reports

[00:00:54.995]

to allow apportionment and reconciliation between operators

[00:00:58.195]

for sales refunds or debts.

[00:00:59.965]

Finally, if you’re an existing Littlepay customer,

[00:01:03.205]

this functionality is available to you at no extra cost.

[00:01:07.645]

This solution is both a broker and device agnostic.

[00:01:11.555]

You can even bring your own PSP.

[00:01:13.795]

An integration that might be required is a very light touch.

[00:01:17.795]

Now, in truth, this is all

[00:01:20.235]

so much better explained with an example.

[00:01:23.355]

So here it goes. Here we have four different operators

[00:01:27.255]

and to keep things simple, let’s say each has a single fare

[00:01:30.835]

of one pound 80 for a single journey.

[00:01:34.435]

Uh, but there’s a daily multi operator cap of four pounds.

[00:01:38.435]

What’s the user experience

[00:01:39.955]

and who gets paid what at the end of the day

[00:01:42.965]

when the passeng initially travels on the green bus,

[00:01:45.715]

the standard single fare of one point 80 is sent to

[00:01:48.295]

Littlepay for multi operator aggregation

[00:01:51.645]

when the partial van travels on the blue bus.

[00:01:54.155]

And number 180 sent a little pay

[00:01:55.775]

to pay aggregated when the passeng van travels on the pink

[00:01:58.845]

tram and therefore one point 80 Fair sent a little pay.

[00:02:01.755]

But now the daily mock cap of four pound has been reached.

[00:02:05.115]

So the fares adjusted to only 40 pence.

[00:02:07.835]

And when the travels on the red train,

[00:02:10.355]

the standard single fares again sent a littlepay.

[00:02:12.675]

But the more cap has already been reached

[00:02:14.715]

and the fares adjusted to zero.

[00:02:16.555]

And on the left hand pan in here, you can see what is sent

[00:02:19.855]

to each relevant operator’s acquirer to be settled.

[00:02:23.635]

Now this settlement

[00:02:26.035]

and a portionment model is based on a

[00:02:28.655]

where it lies approach,

[00:02:30.635]

but there are other models, for example,

[00:02:32.535]

where the lead operator collects all the revenue.

[00:02:35.075]

The point is that with a little pay solution,

[00:02:38.155]

you get all the reports necessary

[00:02:39.855]

to facilitate whatever model works

[00:02:41.635]

for your multi operator agreement.

[00:02:44.195]

So how does this all look to the transit provider?

[00:02:47.285]

Well, basically each operator maintains their own

[00:02:51.175]

separate processing rules.

[00:02:52.595]

And it is only when a passenger uses multiple operators

[00:02:55.635]

within the moc scheme.

[00:02:57.315]

But data is shared in A

[00:02:58.775]

PCI and GDP are compliant manner so

[00:03:01.485]

that the operator can see the relevant trip

[00:03:03.345]

and the cap has been applied.

[00:03:05.545]

The multi operator broker service takes care

[00:03:08.125]

of generating the reports you need for revenue,

[00:03:10.285]

apportionment, and reconciliation at the

[00:03:12.405]

cadence you require.

[00:03:13.945]

And the passenger can use the multi operator traveler

[00:03:16.485]

portal, see all their trips across the schemes,

[00:03:20.005]

participating transit providers.

[00:03:22.065]

Now you may say,

[00:03:24.035]

this all sounds very good, but is it proven?

[00:03:27.025]

And the answer is a very firm yes.

[00:03:30.505]

If we ask you now, go

[00:03:31.685]

and take a look at some of the case studies

[00:03:33.205]

where we’ve deployed this.

[00:03:34.945]

You’ll see what I mean.

[00:03:36.835]

Leicester was the first to go live in March, 2022

[00:03:40.435]

with three operators,

[00:03:41.865]

and Cornwall has been live since July, 2022

[00:03:46.795]

with five participating operators.

[00:03:49.305]

In the last case here, north Wales has 27

[00:03:53.405]

operators across more than 200 routes,

[00:03:56.345]

and they have been live since February, 2023.

[00:03:59.985]

So this is not just theory

[00:04:01.625]

and slideware, this is a real solution delivering benefits

[00:04:05.785]

to those operators today.

[00:04:08.145]

And in truth, there’s another half dozen

[00:04:09.645]

or so deployments live at this moment with more yet to come.

[00:04:13.585]

So let’s wrap us up with summary of some

[00:04:16.245]

of the key features I’ve mentioned here.

[00:04:18.675]

It’s available now at no extra cost

[00:04:21.625]

for existing littlepay customers.

[00:04:23.615]

There are no changes required to your devices

[00:04:26.785]

if you’re not a little pay customer.

[00:04:28.665]

It is still possible to participate

[00:04:30.565]

with a light touch integration to our broker service,

[00:04:33.305]

and there’s no exposure to the sensitive EMV card data.

[00:04:37.545]

So no additional PCI burden on you.

[00:04:40.745]

And the data sharing parameters are entirely configurable

[00:04:43.605]

to best suit your moc schemes needs.

[00:04:47.925]

If you want to know more,

[00:04:49.725]

please visit the littlepay website

[00:04:52.045]

or contact us to speak to a representative.

[00:04:54.795]

Thank you.