Add New Revenue Streams: How EV Charging Becomes a Passive Transactional Layer for Platforms with Users

The conclusion first: the most efficient way to add new revenue streams to a platform with users is rarely to build a new product. It is to find a high-frequency transaction already happening on the user base — one the platform is currently watching from the outside — and to position itself inside the financial flow of that transaction. EV charging is the cleanest example in mobility today. Every EV-driving user in the platform's base is generating multiple charging sessions a week, indefinitely. The platform either earns on those sessions or it does not. NetworkCore makes the capture completely passive: one integration, transparent commercial mechanics, no operational footprint after deployment, and a recurring revenue layer that compounds with the platform's user base. This is what it actually looks like to add new revenue streams the right way.

Why the cleanest new revenue is the revenue already happening

Most efforts to add new revenue streams start with product invention — new features, new tiers, new bundled services. These efforts are necessary but slow. They require user research, product investment, go-to-market planning, and a long maturation period before the revenue line is meaningful. Some of them work. Many do not.

The category of new revenue that is consistently underestimated is the kind that does not require invention at all. The user is already performing the transaction. The transaction is already monetised by someone. The platform's question is simply whether to be the layer the user transacts through, or to remain outside it.

EV charging is the textbook case. The platform's EV-driving users are charging multiple times a week. They are paying for it. Someone is earning from it — currently the public charging app the user defaulted to, the bank whose card was used at the terminal, and the various intermediaries embedded in the financial flow. The platform that wants to add new revenue streams has, in this category, a structural opportunity that requires no product invention: route the existing transactions through its own integration and earn a defined share of each session. The user behaviour does not change. The economics simply re-route through a layer that includes the platform.

This is the cleanest version of the play. The transaction was always going to happen. The question is whether the platform participates in it.

What "transactional revenue" means as a category

The reason EV charging is unusually well-suited as a way to add new revenue streams comes down to the structure of the underlying transaction.

It is high-frequency. EV drivers charge multiple times a week, every week, for the lifetime of their vehicle. There are very few categories of recurring user behaviour that match this density and durability.

It is bounded and well-defined. Every charging session is a discrete event with a clear start, a clear end, a measurable energy quantity, and a clean financial value. Settlement at the per-event level is mechanically straightforward.

It is universal across the platform's user base. The platform does not need a new feature, a new sign-up flow, or a new behaviour to be created. The behaviour already exists in any user who drives an EV. The integration simply lets that existing behaviour run through the platform's product instead of through someone else's.

It is geographically broad. Public charging exists across every market the platform's users drive in. The transactional revenue is available wherever the user is, not only where the platform has built infrastructure.

It is independent of the platform's other revenue lines. Charging revenue does not cannibalise the platform's primary product. It is purely additive — a new transactional layer running alongside whatever the platform is already monetising on its user base.

When the goal is to add new revenue streams without distorting the platform's core product, transactional layers with these characteristics are the most efficient available. EV charging is the most fully-formed of them in 2026.

What "completely passive" looks like in this context

The phrase "passive revenue" is over-used in marketing and earned in a small number of categories. EV charging through a real platform is one of them. The test is whether anyone on the platform's team has to do operational work, on a continuing basis, after the integration goes live.

The answer, in the model NetworkCore is built for, is no.

There is no reconciliation. Sessions are matched to users, transactions, and revenue allocations automatically. The platform's finance team receives consolidated reporting in their own preferred format, on their own preferred cycle, without manually tying anything together.

There is no bilateral CPO management. The platform does not negotiate, contract with, or manage individual Charge Point Operators. The network grows beneath the integration as the platform onboards new operators. The platform's Demand Partner gains access to that growth automatically.

There is no compliance team to staff. VAT calculations, jurisdiction-specific invoicing, audit-ready records, AML and KYC obligations — all of this is absorbed by the infrastructure beneath the integration. The platform does not build compliance logic for charging.

There is no operational team to run. There is no escalation queue, no monthly close process specific to charging, no human-in-the-loop for routine sessions. The integration runs.

What happens, on a continuing basis, is that the platform's EV-driving users charge through the integration, sessions settle on a short cycle, and the platform's defined revenue share lands in its account. Reporting arrives. Nothing else happens.

This is what "add new revenue streams completely passively" actually means as an operational profile. The revenue accrues. The team continues working on the platform's primary product. The new revenue stream is genuinely a layer rather than a project.

Trust and transparency as commercial requirements

The other dimension of getting this right that platforms underestimate is the trust posture of the integration itself.

A platform that introduces a new transactional layer in front of its users needs the layer to be commercially clean, operationally trustworthy, and transparent about its mechanics. If the layer extracts margin from users in ways the user will eventually notice, the platform's brand absorbs the consequences. If the pricing seen at the point of consumption differs from the pricing on the user's invoice, the platform — not the underlying provider — loses trust with its base.

NetworkCore is built so the platform does not face this risk. Drivers charging through the integration pay the Charge Point Operator's transparent public tariff — the price that any other driver in the market would see at the same charger. There is no markup inserted between the charger and the user. The platform's revenue share is earned through the platform's transparent commercial arrangement with NetworkCore, not extracted from the driver. The financial relationship is clean from end to end.

This matters because add new revenue streams efforts that introduce opacity into a previously transparent user experience tend to underperform commercially even when they look good on a quarterly slide. The model that compounds is the one in which the user gets a better experience, not a worse one, because of the integration. The platform offers consolidated charging, in-product convenience, native experience, and access to every public network the user might ever need. The user trusts the integration. The volume compounds. The revenue layer scales with the user base rather than against it.

This is why the trust and transparency posture of the underlying platform matters as much as the commercial mechanics. Add new revenue streams in a way that the user would feel positively about if they understood every detail of the financial flow, and the revenue layer becomes durable. Add new revenue streams in a way the user would feel taken advantage of by, and the layer is structurally fragile from the day it ships.

NetworkCore: the layer that makes this work

NetworkCore is the platform that turns the question of how to add new revenue streams through EV charging into a deployment decision rather than a strategic project. The infrastructure connects platforms with EV-driving users to the existing public charging network, captures the financial flow of every session that runs through the integration, settles all parties on a short cycle, handles compliance across markets, and pays the platform a defined revenue share per session — with no operational footprint required after deployment.

The integration paths are flexible. Platforms with strong UX preferences can build their own charging interface on the API. Platforms that want to ship faster can use NetworkCore's drop-in iframe. The financial flow can stay inside the platform's existing PSP and ecosystem or run autonomously on NetworkCore's infrastructure — the platform picks the configuration that fits its operational reality.

The companion guides worth pairing with this post: EV Charging as a Revenue Stream covers the underlying economics in more depth; Transaction-Based Revenue Models explains the broader category of usage-based revenue layers; New Revenue Streams for Fintechs addresses the specific case of financial platforms; and How to Offer EV Charging in an App is the operational guide for shipping the integration.

For platforms looking to add new revenue streams that are structurally clean, completely passive, transparent in mechanics, and proportional to the user base they already hold, EV charging through NetworkCore is the most efficient available position in mobility right now. The transactions are happening. The integration takes weeks. The revenue layer runs.

Reach the team at networkcore.org to discuss what it would look like for your platform.