RFID payments refer to charging sessions where a driver uses RFID authentication (a tap card or key fob) and the cost of that session is then paid through a linked payment method or billing arrangement. The RFID card itself usually does not process the card transaction like a bank card—rather, it identifies the user’s account so the charging platform can apply the correct tariff and collect payment via invoice, wallet, subscription, or a stored payment method.
In public networks, RFID payments are common for repeat users and roaming customers who want “tap-and-charge” convenience without opening an app.
Why RFID Payments Matter
RFID payments enable:
– Fast user experience for frequent charging (tap, plug, and go)
– Reliable account-based billing for fleets, employees, and residents
– Clear session attribution for revenue reporting and customer support
– Compatibility with roaming ecosystems where users carry one card across networks
– Reduced friction at sites with poor mobile signal or restricted app use (depots, underground parking)
How RFID Payments Typically Work
A standard RFID payment flow looks like this:
– Driver taps RFID card on the charger’s RFID reader
– Charger sends an authorization request via OCPP to the backend
– Backend identifies the customer account linked to that RFID token
– Charging starts and the tariff is applied (per kWh, per minute, session fee, idle fee)
– A charge detail record (CDR) is generated with energy, time, and cost
– Payment is collected using the configured billing method:
– Postpaid invoice
– Prepaid wallet balance
– Subscription plan
– Stored payment method (card-on-file) via a payment gateway
– Roaming settlement via OCPI
Common RFID Payment Models
RFID payments can be structured in several ways:
– Postpaid invoicing
– Sessions are accumulated and billed periodically (monthly/bi-weekly)
– Common for fleets, workplaces, and residents
– Prepaid wallet
– The customer tops up balance; sessions deduct funds automatically
– Useful where credit checks or invoicing is not desired
– Subscription / membership
– RFID card is linked to a plan with discounted tariffs or bundled kWh
– Common for public networks with regular users
– Card-on-file (automatic charging)
– RFID identifies the account; the backend charges a stored payment method
– Often used for consumer accounts with frictionless repeat charging
– Roaming payment
– User taps an eMSP-issued RFID card; billing is handled by the eMSP and settled between parties
– Requires reliable token handling and CDR reconciliation via OCPI
Key Requirements for Accurate RFID Payments
– Correct mapping of RFID token to the right customer account and tariff
– Reliable session and metering data to calculate costs (kWh/time accuracy)
– Clear handling of VAT/taxes, receipts, and invoicing rules
– Strong reconciliation between sessions, billed amounts, and collected payments
– Controls for lost/stolen cards (blocking, re-issuing, audit trails)
Common Problems and How They Show Up
– Session starts but payment fails (authorization OK, capture/invoicing fails)
– Offline authorization starts sessions, but CDRs sync late or incompletely
– Wrong tariff applied after pricing updates or account changes
– Roaming CDR rejection leading to missing settlement revenue
– Refund disputes due to failed stops, connector lock issues, or idle fee confusion
These issues are a frequent source of revenue leakage and customer support load.
RFID Payments vs Contactless Bank Card Payments
RFID payments are not the same as tapping a bank card:
– RFID identifies a charging account; payment happens through that account’s billing method
– Bank card payments use EMV/contactless terminals and charge the card directly at the point of sale (or via tokenized flows)
Many public charging sites support both to cover both ad-hoc and repeat users.
Related Glossary Terms
RFID authentication
RFID charging cards
RFID billing
Payment gateway integration
Charge detail records (CDRs)
OCPI
OCPP
Roaming
Revenue leakage detection
kWh-based billing