Where the market actually is
The National Electric Vehicle Policy 2025–2030 sets a target of 30% of new vehicle sales being new energy vehicles by 2030, rising further toward mid-century, backed by purchase subsidies weighted heavily toward electric motorcycles and rickshaws. That is a deliberate choice: two- and three-wheelers are where Pakistani adoption is real.
On infrastructure, the policy outlines roughly 3,000 charging stations nationwide by 2030, starting with fast chargers at strategic sites along the motorway network and the N-5. Licensing runs through NEECA, which has been issuing permits for EV charging infrastructure and battery swapping stations since its 2024 regulations, with a one-window approval route intended to shorten the path from decision to energised site.
The tariff is the business model
Everything in charging economics sits between two numbers: what you pay for a unit of electricity and what you can charge a driver for it. NEPRA’s approved discounted EV charging tariff — materially below commercial rates — is what makes the gap wide enough to operate in, alongside relaxed rules around a second meter for charging load.
That gap is not enormous, which has two consequences most first-time operators underestimate. Utilisation matters more than headline capacity: a 60 kW DC unit doing four sessions a day is a liability, not an asset. And every cost that scales with revenue — including your payment processing rate — comes directly out of the same thin margin.
Which site types work in Pakistan
| Site type | What it serves | The real constraint |
|---|---|---|
| Motorway / N-5 fast charging | Inter-city car travel, range anxiety | Utilisation — traffic is bursty and overnight demand is thin |
| Mall & retail destination | Dwell-time AC charging while people shop | The bay is worth more as parking unless charging is paid |
| Two- & three-wheeler swap stations | Riders, delivery fleets — the volume segment | Battery inventory cost, not charger cost |
| Fleet & ride-hailing depots | Overnight depot charging | Grid connection and load management |
| Housing societies & apartments | Residential top-up charging | Billing individual residents fairly |
| Hotels, offices & workplaces | Guest and employee charging | Recovering the tariff instead of absorbing it |
Getting paid is the part that breaks first
Almost every pilot site in Pakistan starts the same way: an attendant takes cash, or the driver transfers to a wallet number belonging to a staff member. Both work at one site with one person watching. Both fall apart the moment you have three sites, no attendant at 2am, and an investor asking for audited revenue by location.
The defining constraint of charging payments is that nobody is standing there. There is no cashier, no terminal to hand over, and no way to chase a driver who has already left. The payment has to complete before the electrons move, on the driver’s own phone, in under twenty seconds.
The four models that work
- Scan and charge. A QR on the charger opens a checkout with the session amount. The driver pays by Raast, card or wallet; your CMS unlocks the connector on the webhook. Best for public and highway sites.
- Prepaid app wallet. Drivers load a balance and you debit each session against it. One payment, instant sessions afterwards — the model that produces repeat use.
- Post-paid fleet accounts. Ride-hailing and delivery fleets charge all month and settle on a recurring invoice instead of per session.
- SoftPOS at attended sites. Where staff are present anyway, an Android phone becomes a tap-to-pay terminal — no separate POS rental.
Where the payment layer sits
A common point of confusion: a charging management system and a payment gateway are not competitors. Your CMS handles OCPP, the hardware, session metering and connector control. The gateway moves the money under State Bank regulation and settles it into your company account. The CMS calls the gateway’s API to create a payment and listens for a signed webhook before energising the connector.
That keeps the integration small — most CMS teams finish it in a day — and it means you can change either side later without ripping out the other. See the webhooks guide for how the confirmation leg works in practice.
A checklist before you energise site one
- Is the merchant account in the operating company’s name, not an individual’s?
- Can a driver pay with no app download and no account — Raast QR from their own bank app?
- Does every transaction carry your site and connector reference, so revenue lands attributed?
- Can you refund a failed or interrupted session without a phone call?
- Does reporting split by site, charger and time of day — the data that tells you which site to build next?
- If you operate on a host’s land, can revenue share be paid out automatically via a payout API rather than a monthly manual transfer?
- What is the MDR, and have you modelled it against your per-kWh margin rather than your revenue?
Build the payment layer while the network is small
Retrofitting payments across fifty live sites is a project. Wiring it into site one is an afternoon. If you are planning charging or battery-swap infrastructure in Pakistan, see how session payments work on Rapid Gateway, or talk to the team with your site count and CMS and we will send the integration path and rates.