Mobile app charging payments are payments for EV charging sessions initiated and settled through a smartphone application. The app typically identifies the driver, authorizes the charger, records session data, and processes payment using a payment service provider (PSP)—often without requiring a physical RFID card or on-site terminal.
How mobile app payments work
A typical app-based payment flow includes:
– Driver selects a charger in the app (map, location code, QR code, or NFC tap)
– The app sends an authorization request to the operator’s CPMS (back office)
– The CPMS starts the session via OCPP and logs energy, time, and status events
– Pricing is displayed (per kWh, per minute, flat rate, or hybrid tariff)
– Payment is captured at the end of the session (or pre-authorized upfront)
– The driver receives a receipt and session summary in the app
Payment methods supported in apps
Mobile apps usually support one or more of these payment rails:
– Card payments (credit/debit) via tokenized checkout (e.g., stored card)
– Digital wallets (Apple Pay / Google Pay) depending on region and PSP support
– In-app balance or prepaid wallet (common for fleets or frequent users)
– Subscriptions and membership plans with discounted tariffs
– Promo codes and vouchers (retail, hospitality, partnerships)
App payments vs other charging payment options
Mobile app payments are one piece of a broader payment ecosystem:
– Apps are convenient for casual users but require connectivity and onboarding
– RFID is fast for repeat users and fleets, especially where phones are restricted
– Contactless card terminals enable true ad-hoc access without registration (important for public charging compliance in many markets)
– Plug & Charge can automate authorization and billing without app interaction when supported
Key benefits for operators and site owners
Mobile app payments can improve commercialization and user experience:
– Lower hardware complexity compared to installing payment terminals on every charger
– Dynamic tariffs, time-of-use pricing, and automated idle fees
– Better customer communication (notifications, receipts, support tickets)
– Rich session data for analytics, utilization tracking, and revenue reporting
– Easier integration with loyalty programs and destination partners (retail, hospitality)
Operational and technical considerations
To deliver reliable app payments, operators typically need:
– Stable charger-to-back-office communication (Ethernet/LTE) and high uptime
– Clear tariff logic and transparency (what is billed: kWh, time, parking, fees)
– Secure payment handling (tokenization, PCI-aligned PSP integration)
– Fraud controls (pre-authorization, velocity limits, blocked accounts)
– Customer support workflows for failed starts, refunds, and disputed sessions
– Roaming strategy if users should pay via third-party apps through OCPI or roaming hubs
Common issues and limitations
– Poor cellular coverage at sites can prevent session start or confirmation
– Registration friction can reduce conversion for first-time users
– Pricing confusion if tariffs are not displayed consistently across app and signage
– Session “stuck” states if communication drops between charger and CPMS
– Refund and dispute handling complexity across PSPs, operators, and roaming partners
Related glossary terms
CPMS
OCPP
Ad-hoc payment
Contactless payment
RFID authentication
OCPI
Roaming
Idle fees
Plug & Charge
Tariffs and pricing models