Resources · Payments
What if the charger goes offline right after payment?
Pay-first, charge-later breaks when sessions interrupt. Hold and capture keeps payment aligned with energy actually delivered.
Imagine a customer scans a QR, pays ₹1,000, and starts charging. A minute later the charger goes offline. They want to stop. Payment already completed. Now the system must decide: energy used, amount due, refund timing, and what happens if the charger returns later.
Hold, then capture what was used
Instead of capturing the full amount immediately, a hold-and-capture flow authorizes an amount, starts the session, then captures only what the session consumed and releases the rest.
- ₹1,000 → hold
- Session runs; meter values and OCPP events update progress
- If usage is ₹320 → capture ₹320, release ₹680
If the charger drops or the user stops early, you only capture what was actually used.
Why this is a product problem
EV charging is not always plug → charge → unplug. Chargers go offline, networks fail, and sessions end early. Payment has to follow the session lifecycle: OCPP events, meter values, status, authorization, capture, and release.
That is part of how Voltatic thinks about payments on the same platform as your CSMS—not as a disconnected checkout page.
Want this running on your network? Book a Voltatic demo — commercial terms for India are shared before you commit.