Guides
Multifamily EV charging payments: who bills, who pays and who handles disputes
An activity matrix of multifamily EV payment roles: owner, charging network, payment processor, utility and card issuer, with fee ranges, PCI DSS, NIST Handbook 44, dispute rights and a 2027 renewal check.
Multifamily EV payment work becomes confusing when job titles stand in for actual authority. A property manager may own resident communications but not a network account. A network may collect the money but not own the electricity bill. A board may set the price but not answer a same-day payment question.
What to take away
- Five parties touch a resident's charging paymentthe property owner, the charging network, the payment processor, the utility and the resident's card issuer.
- The property owner usually sets the price. In site-owned systems the owner also pays all operating costs, including electricity.
- Networks may charge 3% to 15% per transaction or a flat $0.25 to $0.50, per the US Department of Energy's multifamily guide published by PNNL.
- Card data falls under PCI DSS, and card billing errors fall under the Fair Credit Billing Act.
- Give each activity one accountable owner and a named escalation path.
Use an activity matrix
| Activity | Named role | Boundary sentence | Source to check |
|---|---|---|---|
| Set the price and who pays | Property owner or board | May choose per-kWh, session, time or subscription pricing, and free or paid access for residents and guests; may not change what the utility charges. | Ownership decision record |
| Collect payment | Charging network operator | May take card, RFID or app payments under the owner's rates and keep its fee; may not change site parking rules. | Network service agreement |
| Protect card data | Payment processor and network | Must meet PCI DSS where they store, process or transmit card data; property staff should not handle card numbers. | Vendor compliance statement |
| Measure energy sold | Charger or meter supplier | May report kWh from a certified commercial device; may not adjust a reading for a resident. | Device certificate and NIST Handbook 44 checklist |
| Pay the electricity bill | Account holder named on the utility bill | Pays kWh and any demand charges at the utility's tariff; may not bill residents through the utility. | Utility tariff |
| Refund or dispute | Network support first, then the card issuer | May open a ticket and correct a session; may not promise a refund the owner has not approved. | Network terms and issuer dispute process |
| Reconcile payouts | Property manager | May compare network payouts with the utility bill; may not edit a resident charge. | Monthly billing summary |
NIST explains that EV charging measurement and field inspection sit in NIST Handbook 44, which shows why the person who sees a charge should not be assumed to own the technical transaction record.
Activity Ownership and Authority
Likely operating owner
- Resident support request
- Assigned support route
- Parking message
- Property operations
- Account setting
- Account holder or provider
- Equipment condition
- Maintenance or service party
- Payment question
- Provider channel or reviewer
Authority to confirm
- Resident support request
- Current service instruction
- Parking message
- Approved property material
- Account setting
- Account authorization record
- Equipment condition
- Current maintenance route
- Payment question
- Current terms and issue process
Who sets the price and who receives the money
PNNL's guide says common pricing bases are kWh, session, time or subscription. Session and time pricing are common where a non-utility cannot sell electricity by the kWh. Owners may set different prices for different users, for example free for residents and paid for guests.
Revenue follows the ownership model. Under site-owned systems the owner sets rates and keeps the revenue, but carries all operating and maintenance costs, including electricity. Under leased systems the vendor may take a share. Charging-as-a-service can split revenue after ongoing fees.
Networks such as ChargePoint, Blink and EV Connect sell these arrangements. Compare them with the questions in what to ask before buying multifamily EV charging.
How residents are billed
Networked chargers collect payment by RFID fob, credit card or smartphone app, according to PNNL. The network's software applies the owner's rate and records each session. Ask for the processor's name and fee schedule in the contract, because both change what the owner nets from each charge.
In most buildings the utility bills the account holder, not the resident. Utility metering falls under the authority of entities such as the local utility commission, as NIST notes. A per-kWh charge to a resident is a separate sale, measured by a device the matrix lists.
Card data, measurement and disputes
Three rules apply to the payment itself:
- PCI DSS applies to entities that store, process or transmit cardholder data, including merchants, processors and service providers. The PCI Security Standards Council publishes it. Ask each vendor which party holds the compliance obligation.
- NIST Handbook 44 now carries the method of sale and tolerances for commercial EV charging devices, after a national work group finished that work in July 2024. The NCWM Publication 14 checklist cites Sections 1.10, 3.40 and 5.55.
- The Fair Credit Billing Act governs credit card billing errors. The FTC says a dispute letter must reach the issuer within 60 days after the first bill with the error. The issuer must acknowledge in 30 days and resolve within 90.
Debit-card disputes follow different rules, so check the Consumer Financial Protection Bureau before writing a refund policy. Decide who answers first: the network support line, then the property manager, with the card issuer as the last step.
What to check at a 2027 renewal
The 2027 date is a contract calendar, not a legal deadline. Any network or processor agreement that renews in 2027 resets the account holder and the escalation route. Find the term, auto-renewal clause, notice period, fee schedule and price escalator in each agreement.
Budget dates decide when the work happens. Draft the review before the owner or board votes, so a January 2027 renewal is decided in the preceding autumn. The matrix should be re-dated at that point.
Build the matrix in 5 steps
- List every routine activity residents touch, from a support request to a billing question.
- Name the job title that owns each one, not a department.
- Attach the source that settles the duty.
- Mark the approval step and the escalation route.
- Date the review so the next reader knows which version is current.
Write a boundary for each role
For every role, record what it may do, what it may tell a resident, what it must escalate, and the source that gives it that boundary. A short boundary is useful: "May confirm that a payment posted and open a ticket; may not promise a refund."
Review roles whenever management, the account owner, provider, equipment or resident instructions change. A current matrix is more useful than a detailed org chart that does not name the actual handoff.
Do not merge data access with decision authority
Someone may need a limited report to perform an operational task without having authority to change a payment setting or approve a resident commitment. Give people only the payment-related information their task requires.
The Federal Trade Commission's business guide, Protecting Personal Information: A Guide for Business, asks firms to identify sensitive data and limit who can reach it, including card transaction vendors.
Retest the matrix after a change
A role matrix goes stale after a provider transition, equipment change or management turnover. Test a real handoff: each named role locates its source, states its boundary and names its escalation route. Record gaps without blaming the finder.
A strong matrix gives staff a simple answer to routine questions and a clear way to escalate everything else. For the cost side of who pays, see apartment EV charging budget models.
Common questions
Can one person hold several roles?
Yes, but document the separate boundaries. Combining roles in practice should not hide which authority supports each action.
Who should approve a resident notice?
The role named in current property records, not simply the staff member who drafted or sent the message.
When should the matrix change?
Update it with any account, provider, management, equipment or policy change that affects a handoff.
