Version 2.3.0
October 30, 2025
New Feature
Improvement
Cross-pool Certificate Creation (eMSP)
CrossCharge eMSP users can now create contract certificates for OEMs that belong to external pools
PCP Integration with Ecosystem Pools
Valid ecosystem pool providers can issue contract certificates for PCIDs managed by CrossCharge PCP
Cross-pool Certificate Deletion (eMSP)
eMSPs can delete contract certificates they own, even if hosted by another pool
Delegated Deletion (Pool Providers)
Ecosystem pool providers are now capable of deleting contract certificates on behalf of their eMSP clients
Cross-pool Certificate Requests (CPO)
CPOs connected to CrossCharge can request certificates for vehicles registered under different pools
Bugs & Enhancements
October 30, 2025
Bug Fix
EST Interface - CPO EVSE Leaf Certificate Response
Updated to return just the base64 encoded certificate instead of a string with Certificate header and footer. This matches the format specified by Hubject in their OPCP documentation
Known Issues
⚠️ CPO: Vector Charger Controller TLS Connection Issue
There is a global issue affecting all vehicles using Vector's Charger Controller. The controller fails to establish TLS 1.2 connections with charging stations when the EVSE Leaf Certificate and its certificate chains (CA1 + CA2) have start and end dates falling on the last day of the month (e.g., March 31, April 30, etc.).
⚠️ eMSP: Inconsistent API Response Format
With the recent integration with External Pool Partners, there are slight differences in the return value for the "v1/cps/generate/signedContractData" API. In some instances the certificate bundle is returned, while in others only "ok" is returned. Relying on HTTP return codes can help avoid confusion for now.