EV Charging Software FAQs

Our platform is built on native OCPP 1.6J (JSON) and OCPP 2.0.1 architectures.

• OCPP 1.6J: A proven standard for mainstream commercial and residential charging scenarios.
• OCPP 2.0.1: Supports stronger security, granular device management, ISO 15118 Plug & Charge workflows and advanced smart-charging profiles.

A decoupled protocol abstraction layer enables operators to manage mixed-version hardware fleets from one CSMS dashboard.

Real-world OCPP implementations often include vendor-specific behaviors. TrendPower validates interoperability through:

• An onboarding test matrix covering authorization, remote start/stop, MeterValues, firmware updates and diagnostics.
• A gateway-layer message sanitizer that handles protocol edge cases and normalizes variations before they reach the core business logic.

Yes. We support OCPI 2.2.1 for EV charging roaming, including locations, tariffs, sessions and Charge Detail Records.

Operators can connect to roaming hubs such as Hubject or Gireve, or establish direct peer-to-peer integrations with eMSPs and other CPOs.

The turnkey solution can include four main modules:

• CSMS / CPMS: Charger management, tariffs, real-time health monitoring, remote diagnostics and financial reporting.
• Driver App: White-label iOS, Android or WebApp for charger discovery, QR/NFC authorization, live sessions, payment and history.
• Site Host Portal: Utilization, energy consumption and revenue-split visibility for landlords and property partners.
• Embedded Gateway or Firmware: Optional edge software for smart controllers or Linux-based chargers.

TrendPower supports two primary load-management strategies designed to protect site capacity and reduce unnecessary electrical upgrades:

• Static or scheduled DLM: Sets maximum site power by defined time windows, such as peak and off-peak periods.
• Dynamic DLM: Connects to real-time energy meters through Modbus or REST APIs, then adjusts charger output through OCPP charging profiles.

Allocation logic can be configured for equal share, first-come-first-served or State-of-Charge priorities.

The platform supports a multi-path payment architecture:

• In-app payment: Project integrations may include Stripe, Adyen, PayPal, Apple Pay and Google Pay, including pre-authorization and automated billing workflows.
• App-free guest checkout: Drivers scan a QR code and pay through a lightweight mobile web page without downloading an app.
• Payment terminal integration: POS hardware such as Nayax or Payter can be integrated where required.

Yes. The tariff engine supports granular commercial models, including:

• Energy-based pricing per kWh, including peak and off-peak rates.
• Time-based pricing per minute or hour.
• Grace-period-based idle or overstay fees.
• Subscriptions, promo codes, member tiers and custom fleet rates.

Privacy and security controls are built into the solution architecture:

• Privacy workflows: Data anonymization, consent management and deletion processes for applicable GDPR and CCPA requirements.
• Regional hosting: Customer data can be isolated and hosted in the selected deployment region.
• OCPP security: TLS encryption and mutual authentication using X.509 certificates can be implemented according to project scope.
• Payment security: Payment data is tokenized through compliant payment providers, so raw card data does not need to enter the TrendPower application database.

For German and Austrian market projects, the CSMS can parse, store and forward cryptographically signed meter-value data.

The platform can also support transparency invoice workflows so end users can verify charging-session data with compatible verification tools.

TrendPower offers flexible deployment models for different ownership and governance needs:

• Managed SaaS: Multi-tenant or dedicated cloud deployment operated by TrendPower.
• White-label or on-premise: Deployment into a customer-managed AWS, Azure or GCP environment using containerized infrastructure such as Docker or Kubernetes.

Enterprise scope can include API access, technical handover and source-code licensing options.

Supported offline workflows can include:

• Local caching: The charger stores transaction logs and meter values during a network outage.
• Offline authorization: Approved RFID credentials can remain available on the charger for local session initiation.
• Data resynchronization: Queued transactions are uploaded to the CSMS after connectivity returns for billing and accounting reconciliation.

Yes. The fleet-management module can support:

• Driver and vehicle pairing: RFID or app-based authorization with configurable energy quotas.
• Home-charging reimbursement: Track eligible fleet-vehicle energy use and generate reimbursement reports for employees.
• Departure-based smart charging: Prioritize vehicles according to scheduled departure times and lower-cost charging windows.