Many drivers arrive at a charger with no app installed and no RFID card from your network. QR code payment gives them a fast way in: scan the code on the charger, pay in the phone's browser and start charging. No download, no account and no extra hardware on the charger. For AC chargers and smaller sites, it is often the most cost-effective ad-hoc payment method.
- QR payment opens a web page where the driver selects a connector, sees the price and pays by card or mobile wallet.
- The CSMS then starts charging remotely via OCPP and charges the final amount after the session.
- Under AFIR, an online payment solution such as QR is accepted for new public chargers below 50 kW.
- QR stickers can be faked, so use tamper-evident labels, a recognisable domain and clear instructions.
How QR code payment works
- Scan: the driver scans a QR code on the charger. The code contains a URL that identifies the charger or the specific connector, usually through its EVSE ID.
- Web page: a mobile page shows the location, the connector status and the full price, including any idle fees.
- Payment: the driver pays by card, Apple Pay or Google Pay. Usually an amount is pre-authorised.
- Remote start: the CSMS sends a RemoteStartTransaction (OCPP 1.6J) or RequestStartTransaction (OCPP 2.0.1) to the charger.
- Live status: the page shows kWh and cost during charging, and lets the driver stop the session.
- Settlement: after charging, the final price is captured and a receipt is sent by email or shown on the page.
QR payment and AFIR
AFIR requires ad-hoc payment at all new publicly accessible chargers. For chargers below 50 kW, operators may use a secure online payment solution, for example a QR code linking to a web payment page. For chargers of 50 kW and above, a card reader or contactless device is required, and QR can only be an additional option. Our AFIR guide and our article on payment terminals cover these thresholds.
Pros and cons
| Advantages | Limitations |
|---|---|
| No extra hardware on the charger | Driver needs a phone with mobile data |
| Works on existing chargers that support remote start | Underground car parks may have poor reception |
| Supports mobile wallets and many card types | Not sufficient alone for new chargers of 50 kW and above under AFIR |
| Easy to update prices and languages centrally | Stickers can be damaged or replaced by fraudsters |
| Low cost per site | Payment fees still apply to small sessions |
Preventing QR code fraud
Fake QR stickers that send people to phishing pages are a known problem in parking and charging. Protect your drivers:
- Use tamper-evident or engraved labels that are hard to cover with a new sticker.
- Print your domain name next to the QR code and show it again on the payment page.
- Use your own HTTPS domain rather than a link shortener.
- Inspect sites regularly and ask drivers to report suspicious labels.
- Where the charger has a screen, show a dynamic QR code generated by the charger or CSMS.
Designing a good QR payment page
- Speed: the page should load quickly on a weak connection. Avoid heavy scripts.
- Price first: show the full price per kWh, any session fee and idle fee before payment. See idle fees.
- Language: detect the phone language and offer a switch.
- Connector clarity: one QR code per connector avoids starting the wrong socket.
- No forced account: ad-hoc means no registration; offer it only as an option.
- Clear status: tell the driver to plug in, then confirm when charging has started.
- Receipt: provide a downloadable receipt or invoice with VAT details.
Technical requirements
- Chargers that support remote start and stop through OCPP and report status reliably.
- A payment provider that supports pre-authorisation and partial capture.
- CSMS logic that cancels the pre-authorisation if the session does not start.
- Mapping of every QR code to the right charger and connector, maintained when hardware changes.
When QR payment is the right choice
QR payment fits best at AC destination sites such as hotels, retail parks, offices and residential car parks, where sessions are long, power is moderate and adding a card reader to every charger would be expensive. It also works well as a second option at DC sites, for drivers whose card is not accepted by the terminal or who prefer a mobile wallet. Track how many sessions start through QR, how many payments fail and how often drivers abandon the page, and use those numbers to improve the flow.
Frequently asked questions
Do I need a separate app for QR payment?
No. QR payment uses a web page in the phone browser, so no app is required.
Can QR payment replace card readers on DC chargers?
Not for new public chargers of 50 kW and above in the EU, which need a card reader or contactless device. QR can be offered as an additional option.
What if the driver loses mobile signal during charging?
The session continues because it is controlled by the CSMS and the charger. The driver receives the receipt once they are back online.
Üreticy provides ad-hoc QR code payment with remote start, live session status and automatic receipts. See payment features or contact us.