01Features · Commerce
Take money the way Indian drivers actually pay
Charging is an awkward payment problem: you have to collect before you know the amount, and settle after. zevOS handles the whole shape — hold, charge, adjust, refund — across the gateways Indian operators actually use, and keeps a ledger that reconciles.
Payments & billing
UPI, cards, net banking, wallets
Methods
Razorpay, PayU
Gateways
Never stored by zevOS
Card data
Capabilities
What this gives you
Pay before, settle after
A driver authorises an amount before the session starts. The final charge is computed from the energy actually delivered, and the difference is refunded automatically — no manual adjustments, no support ticket.
- Pre-authorisation sized from the tariff and expected session
- Automatic capture of the true amount at session end
- Automatic refund of the unused balance
- Failed-capture handling with retry and reporting
Wallets and prepaid balances
Drivers can top up a wallet and charge against it, which removes a payment round-trip from every session. Balances, top-ups and deductions are individually ledgered.
Multiple gateways, one interface
Gateway adapters are pluggable. Credentials are held per tenant, so each operator collects into their own merchant account rather than through a platform pool.
- Razorpay and PayU adapters in production
- Per-tenant gateway credentials, encrypted at rest
- Normalised webhooks so gateway differences stay in the adapter
A ledger that reconciles
Every payment, refund, wallet movement and settlement posts to a transaction ledger with the session it belongs to. Month-end reconciliation is a report, not an investigation.
Specifications
The technical detail
The things a procurement team or an integration partner will ask for, stated plainly.
- Gateways
- Razorpay, PayU (adapter interface for others)
- Flows
- Pre-auth + capture, direct charge, wallet debit
- Refunds
- Automatic partial, manual full
- Webhooks
- Signature-verified, idempotent, normalised
- Card storage
- None — handled entirely by the aggregator
Questions
What operators ask about this
Whose merchant account collects the money?
Yours. Each operator configures their own gateway credentials, so driver payments land in the operator’s account and the descriptor on the driver’s statement is the operator’s.
What happens if a session fails after payment?
If no energy was delivered, the authorisation is released or the payment refunded in full. If a partial session completed, the driver is charged for the energy delivered and the remainder returned.
Does zevOS store card details?
No. Card data is handled entirely by the RBI-authorised payment aggregator. zevOS stores only the gateway’s payment reference and status.
Related
Works closely with
Tariffs & pricing plans
Per-kWh, per-minute, flat-fee and time-of-day pricing, with idle fees, driver-group rates and tariff groups across sites.
Settlements & payouts
Automated revenue sharing with site owners and partners, with statements, payout runs and a reconcilable ledger.
GST invoicing
GST-compliant invoices and receipts for drivers, fleets and partners, with HSN/SAC codes, tax splits and sequential numbering.
See payments & billing working
A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.