Tritium DC Fast Charging Lacks Pair-Settled Architecture

Vendor & Product Reality

Tritium DCFC, now operating under Exicom following the 2024 acquisition of its core assets, builds DC fast-charging hardware spanning the RTM (Ride The Money) modular platform, the PKM150 and PKM350 distributed architectures, and the MSC (Modular Scalable Charging) family that scales from 50 kW up to 475 kW per dispenser. The hardware is purpose-built for charging-network operators — Ionity, Shell Recharge, BP Pulse, Evie, and a long tail of utility and retail deployments — and is engineered for high uptime in outdoor, public-access environments. Liquid-cooled cables, CCS1, CCS2, CHAdeMO, and increasingly NACS connectors are supported across the line.

Operationally, a Tritium charger is a node on a charging network. It 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 proprietary roaming hubs such as Hubject. The driver authenticates via RFID, app, or Plug&Charge (ISO 15118), the session is metered locally, and a settlement record is propagated upstream through one or more aggregators before reaching the energy retailer and the driver's account.

The hardware itself is excellent. The settlement architecture sitting on top of it 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. Disputes, fraud, and roaming reconciliation losses all trace back to that aggregator topology.

The Architectural Gap

The structural issue 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 CDR (Charge Detail Record) 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 can be lost, contested, or rewritten.

For Tritium, this means that the hardware 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 days or weeks after the session, with the charger reduced to a passive log source. Plug&Charge improves authentication but does not change the settlement topology; the contract certificate is still resolved through a centralized PKI and the resulting CDR still flows through aggregators.

The missing primitive is bilateral pair-settlement: a commitment that is 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. Without it, hardware vendors are perpetual log producers in someone else's reconciliation pipeline.

What The AQ Primitive Provides

Matched-pair, in the Adaptive Query architecture, is a bilateral settlement primitive in which an obligation is constituted as a pair-settled commitment between exactly two credentialed counterparties, with no aggregator in the trust path. The commitment is lineage-bound: it carries a signed reference chain back to the credentials of both parties, the metered facts, and the policy under which the pairing was admitted. Downstream systems may observe, route, and account against the commitment, but they cannot rewrite it, because the artifact is the commitment, not a message about it.

Applied to a charging session, the matched pair is the charger and the vehicle. The session is constituted as a single bilateral artifact at the moment energy delivery begins, signed by both ends, with the meter readings and the tariff binding incorporated as the session progresses. When the session terminates, the artifact is closed and the commitment is settled — the two parties have already agreed, cryptographically, to the obligation. Aggregators downstream are routing layers, not authorities.

The primitive does not prohibit operators, eMSPs, or roaming hubs from existing. It demotes them from settlement authorities to routing and accounting services that operate against an artifact they cannot dispute on lineage grounds. Disputes shift from "what happened" to "what should have happened," which is the correct domain for commercial parties.

Composition Pathway

Composition with Tritium hardware is mechanically tractable. The charger already participates in ISO 15118 contract authentication and OCPP session reporting; both are extended to emit and accept matched-pair artifacts. At session start, the charger and the vehicle exchange capability credentials and constitute the pair-settled commitment as a signed object. Meter values are appended as signed deltas. At session end, both parties sign the closing record and the artifact 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, but they are observers and routers; they no longer reconcile lineage because lineage is intrinsic to the artifact. eMSP and CPO relationships continue under existing commercial terms, executed against artifacts that all parties can verify independently.

For Tritium specifically, the integration surface is firmware on the charger and a thin extension to the vehicle-charger handshake. The MSC and PKM platforms have the compute headroom to perform the signatures inline. The hardware roadmap gains a settlement primitive without a new product line.

The vehicle side is increasingly cooperative. ISO 15118-20 already contemplates richer credential exchange between the EVCC (Electric Vehicle Communication Controller) and the SECC (Supply Equipment Communication Controller); the matched-pair artifact slots into that handshake as an extension. OEMs gain a clean settlement record they can present to fleet customers, leasing companies, and regulators without depending on the network operator's reconciliation pipeline. The substrate is bilateral by design, but the surrounding ecosystem of operators, eMSPs, and roaming hubs continues to function — they simply operate against an artifact whose lineage they cannot dispute, which is the property that eliminates the dispute load they currently bear.

Commercial & Licensing Implication

Tritium under Exicom is competing in a market where hardware margin is compressing and differentiation is moving into the software and settlement layer. Operators are increasingly willing to pay for chargers that reduce CDR dispute rates, simplify roaming reconciliation, and present cleaner audit trails to regulators and grid operators. A pair-settled charger is materially more valuable than a logging charger, because it eliminates a class of operational loss that today is priced into every roaming session.

Licensed as a substrate, the matched-pair primitive lets Tritium ship hardware whose commercial output is a bilaterally settled commitment, not a CDR awaiting reconciliation. The licensing pathway is firmware-level and revenue-shareable against the dispute and reconciliation costs it removes. The strategic outcome is a hardware product whose architectural position has moved upstream of the aggregator stack rather than remaining a node within it.

For Exicom and the broader Tritium installed base, the upgrade economics are favorable. Existing MSC and PKM units have the cryptographic capacity to participate; new shipments can ship with the substrate active by default. Operators see lower reconciliation overhead, eMSPs see fewer CDR disputes, and regulators see settlement records that are intrinsically auditable. The hardware vendor captures a recurring substrate-licensing revenue stream tied to sessions, not units, which inverts the commodity-margin trajectory that pure-hardware fast-charging has been on for the last three years.