Verified person, verified vehicle, verified location

ANPR payments verified to the person, not just the plate

VeriLinq has developed a patented method that links a recognised vehicle to an authorised user and their mobile device at the point of service. Payments for parking, tolls, fuel, EV charging and other vehicle-based services can be triggered automatically and charged to the right person. This is more accurate, more reliable and easier to defend than payment by plate alone.

The problem with paying by number plate alone

ANPR has made it possible to charge for parking, fuel and other vehicle-based services automatically, using the number plate as the trigger. VeriLinq builds and operates ANPR software today, so we see the strengths of that model first-hand, and its limits. A number plate only ever identifies the vehicle. It cannot tell you who is driving, who should pay, or whether anyone authorised the payment at all. That gap shows up in familiar, expensive ways:

The wrong person gets charged

Shared cars, pool cars, hire and lease vehicles, and plates still registered to a previous keeper all mean the account billed is not always the person who used the service. Every mismatch is a refund, a complaint or a lost customer.

Missed reads mean missed revenue

When a plate is dirty, damaged, obscured or only partially captured, there is often no charge at all. The service is delivered and nobody pays.

Misreads become wrong charges

Every ANPR system sometimes reads a plate as a similar one belonging to someone else. Without a second check, a misread becomes a wrong charge or a wrongly issued parking charge, followed by appeals, refunds and reputational damage.

A plate is not authorisation

Number plates are visible to everyone and can be cloned. Taking a payment on a plate read alone is like taking a payment on a name alone. There is no second factor confirming the customer is really there.

Disputes are hard to defend

When a customer disputes a plate-triggered charge, the operator has to show that the account holder was actually present. A camera image of a vehicle is often not enough.

No personalisation

A plate cannot tell you which of several account holders is in the car, so loyalty, pre-orders and personal service stall at the window or the barrier.

What verified presence adds

The patented method checks whether an authorised user's device is present at the location alongside the recognised vehicle. That one extra fact changes each of these problems:

  • The right account is charged. The payment follows the person who is actually there, not just the plate. Where several people drive the same vehicle, each can be charged as themselves, and the same person is recognised whichever vehicle they arrive in.
  • Missed and partial reads can be recovered. Because the match works in both directions, an incomplete or uncertain plate read can still be confirmed against the registered customers present at that location, turning lost transactions into completed ones.
  • Payments gain a second factor. Vehicle plus verified device rather than plate alone: closer to chip-and-PIN than to a signature.
  • Disputes and enforcement gain evidence. A record that the account holder's device was present at the time and place of the charge.
  • Service becomes personal. Knowing which customer has arrived enables loyalty, pre-orders and tailored service.

These problems appear, in different forms, in every sector below. The use cases show what solving them could look like in each.

What the technology does

The patented method brings together elements that are usually handled separately: a user account, a mobile device, a vehicle registration, a defined service location, and a payment or service event.

Verified account

A registered user account, with a mobile device and a vehicle registration linked to it.

Verified vehicle

The registered vehicle, recognised by its number plate.

The VeriLinq mark: three connected points representing account, vehicle and presence

Verified presence

The account holder's device is confirmed present at the defined service location.

Each element can be checked on its own. The patented method links all three at the same moment, so a payment or service can follow with confidence.

In plain terms, it works like this:

  1. Register

    A user registers an account, a mobile device and their vehicle registration.

  2. Arrive

    The vehicle arrives at a participating location, such as a car park, forecourt or collection point.

  3. Verify

    The business system recognises the vehicle registration and checks whether an associated authorised user or device is present.

  4. Serve

    A payment, service, permission or customer journey can then be triggered automatically, at the right place and time.

Why it is different

Location technologies typically answer one question at a time. The patented method is designed to answer several together, and to make the result usable within a payment or service.

Standard geofencing

Knows that a mobile device has entered or left a defined area.

ANPR (number-plate recognition)

Knows that a recognised vehicle has arrived.

The patented method

Can associate the recognised vehicle with an authorised user or mobile device in the relevant location, and use that association within a payment or service.

Use cases

Choose a sector below to see how the patented method could be applied there.

Payments, charging and permits

Beyond payments

The same verified link between vehicle, user and location also has applications where the trigger is a service or a permission rather than a payment.

Discuss a use case

If you can see a potential application of the technology in your sector, we would like to hear from you. Please share a short outline and a preferred next step.

Does your organisation have internal development capability?

Prefer email? Contact us directly at info@veri-linq.com.