Adding EV charging to a parking facility is rarely just an electrical project. The billing layer — how drivers are charged for energy, how that charge is combined with parking fees, and how the data reconciles across systems — is where most integration projects either succeed or stall. Operators who treat charging as a separate silo end up with two revenue streams, two reconciliation processes, and two support escalation paths.

The Three Billing Models

Separate billing. The charging network (ChargePoint, EVgo, Electrify America, Blink, etc.) handles payment through its own app or RFID card. Parking fees are billed separately by the parking operator. Simple to deploy, painful for drivers and operators: two receipts, two disputes, two reconciliation reports.

Bundled billing through the parking system. The parking pay station or LPR-based system charges a single combined fee covering time and kWh consumed. The charging hardware reports session data (energy delivered, duration) to the parking management system, which calculates and bills the total. This is the cleanest driver experience but requires integration work.

Bundled billing through the charging network. The charging network’s app handles payment for both energy and parking time, with a revenue share flowing back to the operator. Common at destination parking (retail, hotels) where the charging network has an existing payment relationship with drivers.

Integration Protocols

The Open Charge Point Protocol (OCPP) is the dominant open standard for communication between chargers and charging network management software. OCPP 1.6 is widely deployed; OCPP 2.0.1 is the current specification and adds features relevant to parking integration including ISO 15118 plug-and-charge support.

For parking integration specifically, most operators use:

  • OCPP backend integration. The parking system subscribes to charging session data from the CSMS (charging station management system).
  • Direct hardware integration. For installations where the charger and pay station share a controller, direct serial or IP integration bypasses OCPP.
  • API integration with the charging network. Cleanest for brownfield sites where chargers are already deployed on a managed network.

Payment Rail Considerations

When the parking pay station bills for combined parking + charging, the combined transaction flows through the parking operator’s acquirer. This has implications:

  • MCC selection. Parking operators typically process under MCC 7523 (parking lots and garages). Adding a significant EV energy component may or may not be compatible with that MCC depending on acquirer policy. Some acquirers prefer a split or a separate MCC for energy.
  • Interchange treatment. Energy and fuel historically route through different interchange categories. Pure parking interchange rates should be verified with the acquirer when EV volume becomes material.
  • Tax handling. Energy sales and parking services are taxed differently in most jurisdictions. The billing system must itemize cleanly for sales tax reporting.

Reconciliation Across Two Data Sources

Every charging session produces data from the charger (energy delivered, start/stop timestamps, session ID). Every parking transaction produces data from the pay station or LPR system. Reconciliation requires tying these together.

A typical reconciliation flow:

  1. Charger reports session start to the parking management system.
  2. Parking system associates the session with a vehicle (via LPR, RFID, or ticket).
  3. Charger reports session end with total kWh.
  4. Parking system calculates combined fee at exit, processes payment.
  5. End-of-day, parking system reconciles: every charging session should tie to a paid transaction.

Orphan sessions — where energy was delivered but no payment was collected — are the most common exception and usually indicate a timeout, LPR miss, or gate failure.

Pricing Strategy

Pricing models range from:

  • Flat per-session fee. Simple but poorly calibrated to actual energy cost.
  • Per-kWh pricing. Common at destination charging. Requires accurate kWh metering (submeter-grade).
  • Per-minute while plugged in. Discourages hogging after charging completes. Some jurisdictions regulate this as an energy sale even though it’s billed by time.
  • Time-of-use tiered pricing. Aligns driver cost with underlying utility rate structure.

Federal Reserve research on payment economics does not yet publish specific EV charging payment data, but utility regulators in several states have opined on when per-minute charging constitutes an energy sale versus a service fee — a distinction that affects weights-and-measures compliance.

Practical Integration Checklist

  • Confirm OCPP version compatibility between chargers and the parking management system.
  • Clarify which system is the billing system of record.
  • Verify MCC and interchange treatment with the acquirer.
  • Define reconciliation tolerance (e.g., charger kWh must match billed kWh within 0.5%).
  • Define orphan-session handling procedure.

FAQ

Can a parking pay station handle EV charging payment without OCPP integration?

Yes, but it requires either direct hardware integration with the charger or a manual entry flow. Neither scales well. For any deployment above a handful of ports, OCPP-based integration is the norm.

Who is the merchant of record on a combined parking + EV charging transaction?

Whichever entity’s acquirer processes the transaction. If the parking operator bills the combined fee, the operator is merchant of record for the entire amount and is responsible for PCI scope, chargebacks, and tax reporting.

Does EV charging change a parking operator’s PCI scope?

Not directly, provided cardholder data handling remains unchanged. Adding a charger that has its own independent payment terminal would add that terminal to the cardholder data environment.

Are there interoperability standards beyond OCPP?

Yes. OCPI (Open Charge Point Interface) governs roaming between charging networks. ISO 15118 governs communication between the vehicle and the charger, including plug-and-charge authentication. EMVCo has published contactless payment specifications that some newer chargers implement for direct card-present payment.