Verify. Qualify. Reward. Record.
Four steps turn a charging session into a program result, underneath the apps and programs drivers already use.
The infrastructure behind every program.
Every program, whether it’s a merchant offer, a parking validation or a loyalty reward, runs the same four steps in order.
1Verify
Confirm the session happened, using data the driver or network has authorized: connected-vehicle data (Live) or charging-network session evidence, weighed by its source. Not every source carries the same authority, and unverified candidates are kept separate.
2Qualify
Check the session against the program’s terms: location, time window, duration, frequency, eligibility and remaining budget.
3Reward
Credit a Nerava wallet, or send the qualifying event to your system so you fulfil the benefit there (points, validation and so on). Partner fulfilment depends on the integration.
4Record
Store the result against the original session, such as redemptions and partner-reported outcomes. A partner-reported outcome is recorded as reported; an accepted API request is not, by itself, independent proof that it happened. With Square Loyalty, a loyalty event can be associated with the same driver’s recent session.
One event model for every charging source.
Sessions arrive from different places with different levels of evidence. Nerava normalizes them into one session record, keeps track of where each came from and how much it can be trusted, and runs programs on that record. Programs run when a session is processed, not necessarily the instant charging starts.
- Tesla vehiclesTesla Fleet API, authorized by the driver through OAuth.Live
- Other EVsSmartcar, authorized by the driver. Coverage depends on the vehicle.Live
- Charging networks and appsSessions sent through the Partner API, weighed by the evidence they carry.
Clear data boundaries.
- Drivers authorize vehicle access and can disconnect it.
- Each partner’s workspace shows only that partner’s own programs and results.
- Aggregate reporting applies minimum group sizes.
- More detail is on the security page.
Availability and integrations.
We confirm your site’s setup in the walkthrough. Each connection depends on the systems and permissions in a program.
- Charging
- Tesla and other EVs through connections the driver authorizes, and charging networks through the Partner API.
- Point of sale and loyalty
- Supported connections are confirmed for each site. Other systems can be scoped as implementation work.
- Benefit delivery
- At payment or as a rebate, depending on what the charging provider supports.
- Driver consent
- Drivers authorize any vehicle or account access themselves and can disconnect it. They may see Nerava’s name on that consent screen.
- What a result shows
- A redemption shows a benefit was used. On its own, it does not show the benefit caused the visit.
Commercial details.
What counts as billable activity?
Activity where the agreed checks and the required fulfillment confirmation have completed. Observation alone, duplicate messages and failed deliveries are not billed as successful activity. Any usage-based platform work is described separately in the agreement.
How is a benefit delivered?
At payment, the customer pays $20 and the business covers $5, so the charging provider receives $25. As a rebate, the customer pays $25 and gets $5 back once the qualifying activity is confirmed. Illustrative amounts, before taxes, refunds and processing fees.
Is the customer benefit Nerava’s revenue?
No. Benefit funding reaches customers and is separate from Nerava’s service fee. The business funding benefits and the one paying for the service can be different organizations.
What does the proposal define?
Who pays, the billable event, any minimums and the benefit budget. Ordinary charging and unrelated store purchases are outside the program.
Does every merchant pay a Nerava fee?
Not necessarily. An operator or property can fund the Nerava service for a program. A merchant-led program can have its own agreed fees. Benefit contributions and third-party processing costs are separate.
Does connecting a POS mean a subscription?
No. Standard supported connections are different from custom integration work, dedicated operations or contracted platform services. The proposal spells out the scope.