01
Scan
A location-specific QR code opens the correct branded charger or connector page.
No-download driver charging
A web-based EV charging app drivers can open from a QR code
Sock8 lets drivers scan a charger QR code, open a branded web experience, authorize a connector, start charging, follow the session, and pay without installing an app first.
The browser journey is connected to the same CSMS records used by operators, so charger status, tariffs, sessions, meter values, receipts, and payment outcomes remain consistent on both sides.
Who it is for
Built for teams accountable for live charging.
- Public and destination charging networks
- Hospitality, retail, and parking operators
- New CPOs reducing launch friction
- Networks serving occasional or roaming drivers
Problems it solves
Replace operational blind spots with one system.
- App-store friction before a first charge
- Drivers choosing the wrong connector
- Unclear tariffs and session status
- Disconnected payment and charging records
How it works
A clear path from connection to daily operation.
02
Review
The driver sees availability, tariff information, and the required identification or payment step.
03
Charge
The web app requests the session through the CSMS and shows live progress based on charger messages.
04
Complete
The driver stops charging, receives the final amount or receipt, and can return to their session history.
Product view
See the operating detail behind the promise.
Driver actions and live meter data resolve into the same session record used by network operators.
Representative Sock8 product interface
Features
Capabilities included in the product scope.
- Branded responsive web experience
- QR-to-connector deep links
- Live session progress
- Tariff and payment presentation
- Driver session history and receipts
- Custom domain and brand settings
Protocols and interfaces
Designed to connect the charging stack.
OCPP 1.6JOCPP 2.0.1HTTPSPayment gateway APIsCSMS APIsWebhooks
Implementation or migration
Move from technical discovery to a controlled launch.
- 1
Journey mapping
Define guest, registered, RFID, and payment flows for each operating market.
- 2
Brand and domain
Apply the network identity, support details, languages, and custom web address.
- 3
Gateway connection
Configure the chosen payment flow and verify authorization, failure, capture, and refund paths.
- 4
Field launch
Publish QR codes, test them against installed connectors, and monitor first sessions before full rollout.
Customer evidence
Branded network and apps launched
2 mo to launch · iOS+Android published
Viafast · UAE
Viafast launched a branded charging experience with a local payment gateway and published iOS and Android options over a two-month programme.
Evidence shown is limited to the named deployment facts currently approved for this site.
Deployment
Choose the operating boundary.
The driver web app is included with Sock8 white-label cloud and can use a custom domain. Native apps remain an optional extension.
Pricing information
Scope the commercial model.
Web-app scope follows the white-label platform offer; gateway work, localisation, and optional native apps are scoped separately when required.
View platform pricingBuyer FAQs
Questions technical and commercial teams ask.
Do drivers need to install anything?+
No. The primary journey runs in a modern mobile browser and can open directly from a charger QR code.
Can the web app use our domain and branding?+
Yes. The white-label setup supports your logo, colours, naming, support information, and custom domain.
Can drivers pay in the browser?+
Yes, when the selected payment gateway and market flow have been integrated and validated.
Does the page show live charging progress?+
It can show session state and meter-derived information received through the connected charger and CSMS.
Can we add native apps later?+
Yes. Native iOS and Android apps are optional add-ons and can be introduced after the web journey is live.
Next step