What is vehicle commerce?

Vehicle commerceis a category, not a vertical. It is the set of transactions in which the vehicle is a load-bearing part of the experience — either because the driver never gets out of the car, or because the vehicle's identity is the thing being paid for.

In the US, this category covers most of a 270-million-vehicle fleet's daily activity: roughly $400B at the fuel pump, $116B in the drive-thru, $26B in parking, $15B at the wash, plus fast-growing slices in valet, EV charging, tolling, and on-demand fleet services. By any reasonable accounting, vehicle commerce is a $500B+ annual flow — larger than streaming, ride-share, and food-delivery combined.

Despite the size, it has never had its own payments infrastructure. The category has been served by patchwork — every operator running their own app, their own loyalty card, their own pay-at-pump terminal, their own gate, their own kiosk — and the driver carrying the integration cost in friction.

Vehicle commerce, addressable as a payments category today, lives in five verticals. Each has scale; each has incumbent operators with their own stacks; each has been waiting for the network effect that a neutral rail unlocks.

The categories adjacent — EV charging, tolling, fleet maintenance, drive-up retail, in-cabin commerce — are vehicle commerce too, and they sit naturally on the same rail. paived.io is building the five today and designing the rail to absorb the rest.

Vehicle commerce is not just retail with a car parked outside. Three things make the category structurally different — and structurally interesting:

• The vehicle is the identity, not the card. In retail, the buyer is identified by what they present at the terminal. In vehicle commerce, the buyer is identified by what they arrive in. The plate is a stable, network-recognizable credential the customer is carrying anyway, by law. No retail category has that.
• Transactions are repetitive. The same driver washes the same car, fills up the same car, parks the same car, drives through the same drive-thru. Repetition makes subscription, membership, and account-based pricing the dominant business model — which makes identity matching economically central, not a nice-to-have.
• Time matters more than choice.Retail customers often choose to stop and engage. Vehicle commerce customers are mid-journey; every second of friction is a percentage chance they leave. The price of payment friction is not abandoned cart — it's revenue the operator never sees in the first place.

For decades, vehicle commerce was solved one vertical at a time — and one operator at a time within each vertical. The driver paid the integration cost: a different account, app, card, or kiosk code for every wash they used, every drive-thru they frequented, every lot they parked in.

A typical commuting US driver in 2026 carries five to ten of these accounts. A loyalty card at one gas brand. A subscription app at one wash chain. A drive-thru loyalty app at one QSR. A parking app for the lots near their office. A second parking app for the lots near their home. None of these systems talk to each other. None of them know each other's driver is the same person.

The recent “solution” from the largest player in the space has been vertical integration: build the sites, own the payment stack, run a closed system across the sites you own. It works at scale — at $5B in valuation and $1.6B raised — but it requires owning the dirt. It also forecloses every operator that doesn't want to be acquired into a competitor's network, which is the majority of operators.

The category needed the pattern every other payments category eventually adopted: an open, operator-neutral network running above the existing stack — not replacing it.

Every functioning payments category in history has the same shape. There is an identity layer. There is a settlement rail. There is a merchant connectivity API. There is a consumer-facing credential the buyer carries with them. The category names vary — Visa, Mastercard, PayPal, Stripe — but the infrastructure shape repeats.

Vehicle commerce needs an infrastructure layer the way retail needed Visa — not a competitor that owns the merchants.

Vehicle commerce has been missing the same shape. There has been no neutral identity layer — every operator runs their own customer registry. There has been no shared settlement rail — every operator runs their own processor relationship. There has been no common merchant API — every operator integrates one-off with whatever camera or POS partner they happen to use.

For the category to grow, that pattern needs to be inverted. The identity layer should be shared across operators. The rail should be neutral about which operator collects which transaction. The API should accept every vertical's integration shape from a single endpoint. The driver should carry one enrollment that works everywhere.

That is the infrastructure shape paived.io is building.

paived.io is the operator-neutral payments rail for vehicle commerce. The network owns the identity layer (every Driver, every Vehicle, every consent). The rail owns the settlement contract (one merchant API, every vertical). Merchants keep their own processor, their own cameras, their own POS, their own customers.

Concretely, this means three guarantees written into every operator agreement:

• Neutrality. paived.io will not run a lot, a wash, or a restaurant. The rail does not compete with the merchants on it.
• Transparency. Pricing is published. Every charge is shown before it lands. Refunds are self-serve, with published SLAs.
• Consent. Every enrollment is opt-in. Every charge requires prior consent. Per-merchant data isolation is enforced at the database layer, not on a promise.

Level Parkingis paived.io's lighthouse merchant — proving the rail's parking surface against a working operator's sites and a working operator's economics. The wash, drive-thru, and fuel surfaces follow.

Three trends are converging in the same five-year window:

• Plate recognition got real. Snapshot-cloud services and edge LPR boxes have driven plate-read accuracy past the threshold where it can be the primary identity signal in a payments flow — not a backup to a card scan.
• OEM in-cabin payments arrived. Major automakers — BMW, Mercedes, Tesla, GM — now ship in-cabin commerce features. Each is a walled garden today; they will standardize, and when they do, the rail that already speaks the language wins the integration.
• Operators have learned what walled gardens cost. A decade of being squeezed by closed loyalty programs, closed POS ecosystems, and closed delivery platforms has taught franchisees and independents to read the architecture before they sign. The market is now actively allergic to closed systems.

Vehicle commerce is large enough, structured enough, and ready enough to have its own neutral rail. The first one that ships with the right shape — operator-neutral, consent-first, multi-vertical from day one — is the one the network coheres around.

For the mechanism inside the rail, read Lane payments, explained. For the technical shape of the integration, see paived.io for developers.