Mobile wallet charging is EV charging that is authenticated and/or paid for using a mobile wallet on a smartphone—most commonly Apple Pay, Google Pay, or other regional wallets. It typically enables fast checkout with tokenized card credentials, reducing friction compared to manual card entry or full app registration.
How mobile wallet charging works
Mobile wallet charging is usually delivered through one of these flows:
– In-app wallet payment: the driver starts a session in a charging app and selects Apple Pay / Google Pay at checkout
– Web-based / QR payment: the driver scans a QR code on the charger, opens a payment page, and pays via the mobile wallet
– Terminal-based contactless: the driver taps their phone on an on-charger contactless payment terminal (phone acts like a card)
In all cases, the payment is processed through a payment service provider (PSP) and linked to a specific charging session in the operator’s CPMS.
Where mobile wallet charging is used
Mobile wallets are most common where operators want fast, user-friendly payment without heavy onboarding:
– Public destination charging (retail, leisure, city parking)
– Hospitality sites (hotels, resorts)
– Ad-hoc public charging where users may not have an account
– High-traffic sites where reducing payment time improves turnover
Benefits of mobile wallet charging
– Faster checkout and fewer drop-offs compared to manual card entry
– No need to carry a physical card; phone tap or quick confirmation
– Tokenization improves security and reduces exposure of card details
– Improves conversion for casual users who do not want to register
– Works well with ad-hoc payment requirements when implemented via QR/web or terminals
Operational and technical considerations
To implement mobile wallet charging reliably, operators typically need:
– PSP support for Apple Pay / Google Pay and compliant checkout flows
– Clear pricing display before payment (per kWh, per minute, fees)
– Session linking logic between payment authorization and charger start via OCPP
– Connectivity reliability (charger ↔ CPMS) to prevent paid-but-not-started sessions
– Refund and support workflows for failed starts or early stops
Limitations and common issues
– Not all PSPs or regions support the same wallets
– Wallet availability can depend on device type, OS settings, and bank eligibility
– QR/web flows depend on mobile connectivity at the site
– Terminal-based wallets require additional hardware and maintenance (card readers, certifications)
– Roaming payments via third-party apps may display different tariffs than the operator app
Related glossary terms
Contactless payment
Ad-hoc payment
Mobile app payments
Payment service provider (PSP)
CPMS
OCPP
QR code payment
Tariffs and pricing models
RFID authentication
Roaming