← All insights

Technology Education · Connected Mobility

Insight

Who Is This Car? The Identity Layer Connected Payments Still Need

November 2026 · By Raheel Anwar, CTO, AuthenCore AI

Toll agencies have a polite word for money they never collect: leakage. An internal Pennsylvania Turnpike report found that nearly 11 million of about 170 million trips in the year ending May 2021 generated no revenue. In 1.8 million of those trips, the agency could not identify the license plate at all (AP via Inquirer; Washington Examiner).

Cameras get blamed for numbers like these, but the deeper issue is older. For decades we have identified vehicles by what is attached to them, a plate or a sticker, and hoped the label is readable, current and on the right car.

I have spent most of my career in enterprise security. In that world, nothing joins a network because of the label on its case. A laptop, a server or a badge reader has to prove what it is, cryptographically, before it is trusted. Vehicles are moving toward the same rule. The in-vehicle toll pilot covered in a recent In-Vehicle Evolution article is one early sign of it.

This article looks at the layer underneath that pilot: how a car proves who it is, why that question reaches far beyond tolls, and what my company, AuthenCore AI, is building to answer it.

Labels versus proof

A car can be identified in five common ways today. Four of them identify something attached to the car or near it.

MethodWhat it actually identifiesWhere it falls short
License plateA registration recordChanges when the car is sold or re-registered; can be misread, obscured or cloned
VINThe physical vehicleVisible through the windshield, so anyone can copy it into a form
Toll transponderAn account tied to a tagRead only by participating networks; the tag can be moved to another car
Phone appThe driverEach operator asks for its own app, account and card on file
Digital certificateA private key held by the vehicleHard to forge, but today each one is accepted by a single ecosystem

Only the last row is proof. With a certificate, the private key stays inside the vehicle. The car answers a challenge using that key, and the other party checks the answer. Nothing reusable is handed over, so there is nothing for an attacker to copy from the transaction itself.

This is the same principle behind chip cards and passkeys. Applying it to vehicles is not new. Making it work everywhere a vehicle goes is the unfinished part.

Credentials cars already carry

Many vehicles already hold digital credentials. Each was built for one job.

DomainStandard or methodWhat it establishes
EV chargingISO 15118 Plug & ChargeThe car and charger exchange certificates, so a session can start without an app, RFID card or bank card. ISO 15118-20 adds a certificate unique to each vehicle.
Road safety messagesIEEE 1609.2A safety broadcast came from a legitimate vehicle or roadside unit
In-car paymentsPayment tokenizationA protected stand-in for the card number, linked to vehicle details such as the VIN and plate in North Carolina's in-vehicle toll pilot
Vehicle cybersecurityISO/SAE 21434Security risk is managed across the vehicle's engineering lifecycle
Portable identityW3C Decentralized IdentifiersAn identifier the holder controls, not tied to a single company's registry

The roadside is being prepared as well. In November 2024 the FCC adopted final rules for cellular V2X in the upper 30 MHz of the 5.9 GHz band. A U.S. Department of Transportation deployment plan released in August 2024 set targets of V2X on 20% of the National Highway System by 2028 and 50% by 2031, with nationwide coverage by 2036. Those targets are aspirational: the plan imposes no mandate and dedicates no federal funding, and future money depends on Congress's next surface transportation bill (Nossaman).

Even within one domain, getting these credentials to work is hard. Plug & Charge needs the charger, the charging network's back end, the certificate authority, the mobility provider and the driver's contract to be integrated before a single session can start.

Every operator is its own island

The certificate that starts a charging session cannot open a parking gate. A toll account cannot pay at a car wash. Each system knows the car only inside its own walls.

That fragmentation has costs that rarely show up in product demos. Drivers enroll again with every new brand. Operators each build and maintain their own sign-up flow, fraud controls and payment integrations. Automakers that want to offer in-car payments end up negotiating with merchants one at a time.

One point is often missed in this debate. The credentials a car uses for road safety should not be reused for buying things. V2X safety messages are signed with certificates built to protect drivers from being tracked, and mixing them with payment identity would undo that protection. A vehicle needs a safety identity and a separate commerce identity.

Card payments faced a version of this problem long ago. A corner shop does not need a relationship with your bank, because it trusts the card network and the network vouches for the card. Vehicles do not yet have an equivalent for identity.

What AuthenCore is building

AuthenCore AI is building that missing identity layer for vehicles. We call the outcome V-Commerce: a car that can be recognized and trusted at a fuel pump, parking gate, charger or drive-through without the driver re-enrolling at each one.

The approach has three parts.

  1. A-Pulse is AuthenCore's vehicle identity technology. It gives an enrolled vehicle a credential that can be verified but not copied, and it is designed to be manufacturer-neutral rather than tied to one brand or model year.
  2. The AuthenCore network is the trust layer. An operator asks one question, whether this vehicle is genuine and its owner enrolled, and gets an answer it can rely on.
  3. Operator solutions connect fuel, parking, EV charging, car washes, tolling and retail to the network. Each operator keeps its own pricing, loyalty programs and customer relationships.

One car identity, recognized at every stop

A-Pulse®: the car's verifiable identity

Gives each enrolled vehicle a credential that can be verified but not copied, across makes

AuthenCore network: the trust layer

Operators ask once: is this car genuine, and is its owner enrolled?

Operator solutions: each keeps its own pricing, rules and customers

FuelParkingEV chargingCar washesTollsRetail

V-Commerce™: the car pays as a trusted participant, card and ticket as fallback

V-Commerce in three layers: the vehicle proves itself once, the network vouches for it, and every operator on top can rely on that answer.

AuthenCore is a software company. The work builds on the standards above instead of replacing them: certificate-based identity, tokenized payments, and security engineering aligned with ISO/SAE 21434.

The same errand, with a verified car

Picture a driver who stops for fuel, parks downtown and charges on the way home. With a shared identity layer, the day looks like this:

  1. Enroll once. The owner links the vehicle and a payment method, and chooses what each type of operator may see.
  2. Arrive. The pump, gate or charger asks the vehicle to identify itself, and the vehicle responds with proof instead of a label.
  3. Verify. The operator checks that proof against the network and applies its own price, membership discount or time limit.
  4. Pay. The payment settles over existing card rails using tokens, so the operator never handles raw card numbers.
  5. Keep a record. Every stop appears in one history the driver can review in the car or on a phone.

If any step fails, the familiar options remain: tap a card, take a ticket, pay at the window. The North Carolina pilot followed the same principle by keeping license-plate billing as the fallback, and any serious system in this space should do the same.

What has to be true for drivers to trust it

A car that can prove its identity could also become a car that is easy to follow. Any vehicle identity system has to be judged on how it handles that risk, along with a few others.

Privacy. A transaction should reveal only what it needs. A parking operator needs to know the vehicle is enrolled and can pay. It does not need the VIN, the driver's name or where the car was an hour ago. Each operator relationship should be opt-in, and commerce identity should stay separate from safety identity.

Theft and compromise. Keys should live in protected storage, and credentials must be revocable so a stolen vehicle or compromised account can be cut off quickly.

Change of ownership. The vehicle's identity and the owner's account are different things. When a car is sold, the previous owner's payment link is removed and the new owner enrolls separately.

Control. Identity should not be locked inside one automaker or platform. Owners should be able to use it across operators, which is the problem open identity standards are designed to address.

Fallback. Existing payment options stay in place while the new system earns trust.

Where this goes next

The earliest gains are likely where stops are frequent and lines are costly: parking, fueling, EV charging and car washes. Drivers already stay in the vehicle at these places, and a few seconds saved per visit adds up across millions of visits.

Tolling may follow as agencies look for ways to reduce leakage without adding equipment to every windshield. Roadside V2X deployment, as it expands, gives infrastructure another way to recognize vehicles it can trust.

The longer-term driver is software acting for the driver. In-car assistants are starting to handle tasks such as finding a charger or reserving parking. Once software begins spending money on someone's behalf, every merchant will need to know which vehicle is asking and what its owner has authorized. Vehicle identity, with limits set by the owner, is what makes that safe.

The industry has spent years teaching vehicles to communicate. Making them trustworthy counterparts for the businesses they deal with is the next problem to solve, and it is the one AuthenCore is focused on.

Frequently asked questions

What is vehicle identity?

It is the ability of a vehicle to prove that it is the specific vehicle it claims to be, using cryptography rather than a printed number or a sticker.

Is this the same as V2X?

No. V2X covers how vehicles and roadside equipment exchange messages. Vehicle identity for commerce is about whether a business can trust which vehicle it is dealing with. V2X safety messages use their own privacy-protecting credentials, which should stay separate from payments.

How is this different from in-vehicle toll payments?

In-vehicle tolling is one application. A shared identity layer is meant to let the same verified vehicle transact with tolling, parking, fueling, charging and retail operators without a separate enrollment for each.

Will my car need new equipment?

AuthenCore is designed to work across manufacturers, including vehicles already on the road. What a specific vehicle needs depends on its make and model.

Who can see my information?

Only the operators you choose, and only what a given transaction requires.

What happens when I sell my car?

Your account and payment link are removed. The next owner enrolls under their own account.

Sources

Disclosure: The author is the CTO of AuthenCore AI, the company discussed in this article. A-Pulse is a registered trademark of AuthenCore AI.

Want to see A-Pulse® in action?