01
Scan
A location-specific QR code opens the correct branded charger page in the phone's default browser. Nothing is installed.
Scan, charge, pay — no download
A web-based EV charging app drivers open with one scan
Drivers point a phone camera at the QR code on your charger, pick a connector, start the session, and pay in the browser. No app store, no signup, no account to remember.
The browser journey runs on the same CSMS records your operators use, so charger status, tariffs, meter values, receipts, and payment outcomes stay consistent on both sides. You connect your own payment gateway, so funds settle straight into your merchant account.
Who it is for
Built for teams accountable for live charging.
- Public and destination charging networks
- Hotels, malls, and retail hosts serving guests
- Parking operators adding charging to existing sites
- New CPOs reducing launch friction
- Networks serving occasional or roaming drivers
Problems it solves
Replace operational blind spots with one system.
- Drivers abandoning the charger at the app store
- Signup and wallet top-up 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
Choose
The driver sees live connector availability and the exact tariff before committing to a session.
03
Charge
One tap sends the start command through the CSMS over OCPP. Energy, time, and running cost update live on screen.
04
Pay
Payment is authorised up front and captured against the real session. The receipt appears on screen and by email — no account required.
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
- Guest charging with no signup required
- Optional driver accounts, RFID, and fleet billing
- Live session progress and remote stop
- Your own payment gateway, connected directly
- Tariff, tax, and idle-fee 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.1HTTPSStripeRazorpayPayment 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
Connect your Stripe, Razorpay, or other gateway 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
White-label apps · Local payment gateway
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. Payment processing costs stay between you and your gateway; 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 an app?+
No. The primary journey runs in a modern mobile browser and opens directly from the QR code on the charger. Nothing is installed at any point.
Do drivers need to sign up or create an account?+
No. Guest charging works with no signup — scan, charge, pay. Accounts are available for drivers who want saved payment methods, session history, or fleet billing, but they are never required to start a charge.
Can we use our own payment gateway?+
Yes. Stripe and Razorpay are supported, and other gateways with a documented payments API can be integrated. Funds settle directly into your merchant account, so you keep your negotiated processing rates.
Can the web app use our domain and branding?+
Yes. The white-label setup supports your logo, colours, naming, support information, receipts, and custom domain.
Does the page show live charging progress?+
Yes. It shows session state and meter-derived energy, time, and running cost received through the connected charger and CSMS, and the driver can stop the session from their phone.
Does it work with our existing chargers?+
If they are OCPP 1.6J or OCPP 2.0.1 compliant, yes. No hardware replacement is required.
How long does launch take?+
Most branded web deployments go live within a week. Larger programmes that add native iOS and Android apps take longer — the Viafast rollout ran to two months end to end.
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