01
Present
Show the driver the applicable tariff and collect the payment method through the approved gateway flow.
Charging and payment in one operational record
EV charging payment gateway integration tied to every session
Sock8 connects a network's charging journey to the chosen payment gateway so authorization, session progress, final energy, tariffs, capture, receipts, and exceptions can be reconciled against the same charging record.
Payment design varies by country, gateway, currency, tax, and customer journey. The integration is therefore scoped around the operator's merchant account and required flow rather than routing revenue through a one-size-fits-all gateway.
Who it is for
Built for teams accountable for live charging.
- Public CPOs accepting digital payments
- Networks entering a new payment market
- Operators bringing their own merchant account
- Finance teams reconciling energy and gateway records
Problems it solves
Replace operational blind spots with one system.
- Payment success disconnected from charger state
- Final session value differs from the initial estimate
- Manual reconciliation across gateway and CSMS
- Failure and refund paths not tested end to end
How it works
A clear path from connection to daily operation.
02
Authorize
Complete the required gateway step before asking the CSMS to start charging.
03
Finalize
Use the completed session and tariff rules to determine the final amount and payment action.
04
Reconcile
Match gateway references, session identifiers, receipts, failures, refunds, and settlement reports.
Product view
See the operating detail behind the promise.
Tariff rules and payment outcomes stay connected to the charging plan, connector, and completed session.
Representative Sock8 product interface
Features
Capabilities included in the product scope.
- Bring-your-own gateway integration
- Pre-authorization or market-specific flow
- Session-linked payment references
- Tariffs, idle fees, and final amount calculation
- Receipts and payment status
- Failure, retry, refund, and reconciliation handling
Protocols and interfaces
Designed to connect the charging stack.
Gateway REST APIsSigned webhooksHTTPSOCPP 1.6JOCPP 2.0.1CSMS APIs
Implementation or migration
Move from technical discovery to a controlled launch.
- 1
Commercial flow
Define merchant ownership, countries, currencies, taxes, tariffs, receipts, refunds, and settlement responsibilities.
- 2
Gateway review
Confirm API access, test credentials, webhook security, supported payment methods, and production onboarding.
- 3
End-to-end build
Connect driver, gateway, and CSMS states with stable identifiers and failure handling.
- 4
Financial acceptance
Test successful, declined, abandoned, interrupted, adjusted, refunded, and reconciled scenarios before launch.
Customer evidence
Local payment gateway integrated
2 mo to launch · iOS+Android published
Viafast · UAE
The network launched its branded driver experience with market-specific payment handling as part of the production rollout.
Evidence shown is limited to the named deployment facts currently approved for this site.
Deployment
Choose the operating boundary.
Payment integrations can support the branded web journey and optional native apps in managed or customer-hosted deployments.
Pricing information
Scope the commercial model.
Gateway integration is scoped by provider, market, payment methods, merchant onboarding, tax and receipt requirements, and the required exception workflows.
View platform pricingBuyer FAQs
Questions technical and commercial teams ask.
Can we use our own payment gateway?+
Yes, subject to suitable APIs, webhooks, merchant onboarding, test access, and a validated market-specific flow.
Does Sock8 hold our charging revenue?+
The preferred design uses the operator's payment-gateway and merchant relationship; exact fund flow and responsibilities are confirmed during discovery.
How is the final charge amount calculated?+
The final amount is based on the completed session data and configured tariff rules, then passed through the agreed gateway flow.
Are refunds supported?+
Refund and adjustment paths are included when the selected gateway exposes them and the operator defines the required process.
How are payments reconciled?+
Stable session and gateway references connect CSMS records, webhook outcomes, receipts, and settlement or finance reports.
Which gateways are supported?+
Availability depends on country and provider. Sock8 reviews the required gateway during technical discovery instead of publishing an unqualified universal list.
Next step