Vendor and product reality
Tritium's DC fast-charging business was acquired by Exicom Tele-Systems in 2024 (the acquisition, announced in August 2024 with a definitive-agreement value reported at up to roughly 29.6 million dollars, though some outlets cited higher figures) and now operates as a Tritium-branded business within Exicom. The product line spans the RTM modular charger, the PKM150 and PKM350 distributed architectures, and the Modular Scalable Charging (MSC) hardware platform that shares interchangeable liquid-cooled power modules across models. The hardware is purpose-built for charging-network operators, including deployments associated with Ionity, Shell Recharge, and BP Pulse alongside a long tail of utility and retail sites, and is engineered for high uptime in outdoor, public-access environments. Liquid-cooled cables and CCS, CHAdeMO, and NACS connector options are supported across the line. On the reported record of an estimated 13,000 chargers sold across 47 countries, this is serious, field-proven hardware.
Operationally, a Tritium charger is a node on a charging network. It commonly speaks OCPP (Open Charge Point Protocol) northbound to a Charge Point Management System (CPMS), which in turn brokers authorization, pricing, and settlement with eMobility Service Providers (eMSPs) via OCPI (Open Charge Point Interface) or roaming hubs such as Hubject. The driver authenticates by RFID, app, or Plug and Charge (ISO 15118), the session is metered locally, and a charge detail record is propagated upstream through one or more intermediaries before reaching the energy retailer and the driver's account.
The hardware itself is excellent. The point of comparison is narrow and architectural: the settlement layer sitting on top of the hardware is a multi-hop aggregator stack in which the bilateral fact (this vehicle drew this energy from this charger over this interval) is repackaged, re-signed, and reconciled across parties that were not present at the event. Roaming reconciliation and dispute handling are structural properties of that intermediary topology, not defects of the charger.
The Architectural Gap
The structural point is that the commercial commitment of a charge session is not represented as a bilateral artifact between the charger and the vehicle. It is represented as a chain of messages: a session record from the charger to the CPMS, an authorization token from the eMSP, a charge detail record (CDR) propagated through OCPI, a clearing entry at the roaming hub, and a final billing event at the retailer. Each hop is a place where the lineage of the original event is re-serialized, and reconciliation exists precisely because those re-serializations must be brought back into agreement.
For a hardware vendor, this means the equipment that physically performed the transfer is not the system of record for the commitment that arose from it. CDR disputes are resolved by the operator and the eMSP, often after the session, with the charger acting as a passive log source. Plug and Charge improves authentication but does not change the settlement topology: the contract certificate is resolved through a centralized PKI and the resulting CDR still flows through intermediaries.
The architectural element the category lacks is bilateral pair settlement: a commitment constituted at the moment of the session, between the charger and the vehicle, with cryptographic lineage that survives the trip through any number of downstream systems. Absent that primitive, hardware vendors remain log producers inside someone else's reconciliation pipeline.
What the matched pair provides
Matched-pair settlement, as disclosed in the provisional, is a first-class architectural primitive for governance-chain-preserving bilateral settlement of a physical-world exchange. Two authority-credentialed parties emit paired governed observations within a governance-policy-defined spatial and temporal window: a first observation representing an offer, tender, claim, demand, or commitment, and a second observation representing acceptance, counter-tender, acknowledgment, or fulfillment. A spatial-proximity evaluator confirms the parties are co-located within the policy-defined window, a temporal-proximity evaluator confirms the observations fall within the policy-defined interval, a per-party authority evaluator checks each credential, and a cryptographic binding mechanism produces a cryptographically bound settlement artifact supporting non-repudiation. The result is a persistent settlement record admissible by downstream consumers without third-party intermediary, without centralized consensus, and without pre-negotiated session state. Every step (each observation, the pairing determination, the binding, any negotiation or escrow, any failure or dispute, and each downstream consumption) is written to the governance-chain lineage field.
The specification enumerates energy transfer as an explicit domain instance: for vehicle-to-grid, vehicle-to-building, and peer-to-peer energy exchange, the first observation is the energy-receiver's demand directive and the second observation is the energy-source's delivered-energy observation. Mapped to public EV charging, the receiver is the vehicle and the source is the charger. The session is constituted as a single bilateral artifact when energy delivery begins, bound by both credentialed ends, with delivered-energy observations incorporated as the session progresses. On termination the pair is closed and the artifact is the settled commitment, because the two parties have already produced mutually attested, lineage-recorded observations of the exchange.
The primitive does not prohibit operators, eMSPs, or roaming hubs from existing. Consistent with the specification's downstream-consumer routing, it repositions them: settlement follows from credentialed proof of the interaction rather than from a trusted central operator, and downstream systems observe, route, and account against an artifact whose lineage they cannot rewrite. Disputes shift from reconstructing what happened toward the commercial question of what the parties owe, which is the correct domain for a dispute-resolution authority. The specification also provides counter-offer negotiation, escrow and chained settlement, rollback on timeout or non-fulfillment, and cross-unit exchange as parts of the same governance-chain-preserving mechanism.
Composition pathway
A skilled implementer can compose the matched-pair primitive onto existing charging hardware without a new product line. The natural integration surface is the vehicle-to-charger communication handshake and the charger firmware. ISO 15118 already establishes a credentialed channel between the vehicle communication controller and the supply-equipment communication controller, and OCPP already carries session reporting northbound; both are candidate transports for emitting and accepting matched-pair observations. At session start the charger and the vehicle exchange credentials and constitute the pair-settled commitment as a cryptographically bound artifact per the binding mechanism above. Delivered-energy observations are appended as signed increments as the session progresses. At session end both credentialed parties attest the closing observation and the pair is final.
Northbound, the OCPP CDR becomes a transport for the matched-pair artifact rather than the artifact itself. CPMS, OCPI, and roaming hubs continue to operate as downstream consumers and routers; they no longer reconcile lineage, because lineage is intrinsic to the artifact and recorded in its governance chain. eMSP and CPO relationships continue under existing commercial terms, now executed against artifacts every party can verify independently.
Enablement is not exotic. The primitive is signaling-mechanism-agnostic: the spatial and temporal proximity windows can be satisfied by mesh reachability, radius-from-point, or credentialed-venue extent, and the cryptographic binding admits a plurality of non-repudiation patterns disclosed in the specification (simple-signature, threshold-signature, zero-knowledge, anonymous-credential, ring-signature, hash-commit-reveal, and timelocked-release). Embodiments span more than public DC fast charging: the same energy-transfer instance covers vehicle-to-grid and vehicle-to-building exchange, peer-to-peer transfer between vehicles, depot and fleet charging, and stationary-storage dispatch, and the broader primitive generalizes across tolling, point-of-sale commerce, capacity reservation, and chain-of-custody handoff. On the vehicle side, richer credential exchange contemplated by ISO 15118-20 gives OEMs a clean settlement record to present to fleet customers, leasing companies, and regulators without depending on any single operator's reconciliation pipeline. The surrounding ecosystem of operators, eMSPs, and roaming hubs continues to function; it simply operates against an artifact whose lineage it cannot rewrite.
Commercial and licensing implication
Differentiation in EV charging increasingly moves from raw hardware into the software and settlement layer. Operators have a standing interest in chargers that reduce dispute handling, simplify roaming reconciliation, and present cleaner audit trails to regulators and grid operators. A charger whose output is a bilaterally settled commitment is architecturally distinct from one whose output is a CDR awaiting reconciliation, because the commitment is settled at the source rather than reconstructed downstream.
Licensed as a substrate, the matched-pair primitive lets a hardware vendor ship equipment whose commercial output is a bilaterally settled artifact rather than a record awaiting reconciliation. The integration is firmware-level, so an installed base with sufficient cryptographic capacity can participate through a software update and new shipments can enable the substrate by default. The strategic effect is to move the vendor's architectural position upstream of the aggregator stack rather than leaving it a node within it, with a licensing model that can be tied to settled sessions rather than only to units shipped.
For Exicom and the broader Tritium installed base, the practical draw is that operators see lower reconciliation overhead, eMSPs see fewer disputes to resolve, and regulators see settlement records that are auditable by construction because the lineage is intrinsic to each artifact.
Disclosure scope
This article is a public technical disclosure of subject matter rooted in the Matched Pair inventive step, disclosed in U.S. Provisional Application No. 64/049,409. The claims made here about the invention (the matched-pair settlement primitive, its paired governed observations, spatial and temporal proximity windows, per-party authority evaluation, cryptographic non-repudiation binding, downstream-consumer routing, governance-chain lineage recording, and the enumerated domain instances including energy transfer) trace to that specification. References to Tritium, Exicom, Ionity, Shell Recharge, BP Pulse, Hubject, OCPP, OCPI, and ISO 15118, and to market and product facts about them, are external context provided for accurate positioning and are not claims of the filing. Product names and marks belong to their respective owners. The competitive framing describes an architectural axis (bilateral, pair-settled, mutually attested settlement with no central operator in the trust path) and is not an assertion of any defect in the named products, which are capable, widely deployed systems within their own architecture.
