DEMO ← Use cases

Digital key & contactless pickup

The digital key comes from the vehicle’s OEM — Tesla Fleet API, Ford Pro, GM OnStar — and Hertz’s fleet account provisions a temporary, revocable key for the rental. TransactionTree binds that key to the signed e-RA, captures consent, and delivers it to the customer’s wallet: “your car is in stall 34, unlock here.” TT is the agreement + consent + delivery layer — not the key issuer.
HertzReady
How the pickup flows
Where the key actually comes from
“Digital key” means two different things. Only one is built for renting a car to a stranger for two days — and TT sits around it, never holding the OEM’s keys.
Consumer phone-as-keynot the rental path

Apple Wallet / Google / CCC Digital Key. Provisioned by the OEM and bound to the owner’s account. Great for the person who owns the car; not designed for a third party to mint a fresh key per rental at scale.

Fleet remote-unlock APIthe rental path ✓

The OEM’s connected-car API grants time-boxed, revocable access. Tesla’s Fleet API is productized for this today (virtual keys, expiring invites, revoke); GM OnStar/Envolve and Ford Pro expose remote lock/unlock for approved fleet accounts.

1 →
OEM connected-car API
Tesla Fleet API · Ford Pro · GM OnStar — the OEM is the only party that can issue the key.
2 →
Hertz fleet account
Hertz (the vehicle owner) provisions a temporary key scoped to this rental & renter.
3 →
TT · Lynxs
Binds the key to the signed e-RA + captures consent. TT never holds OEM credentials.
4 →
Renter’s wallet
Key + agreement delivered together; stall shown; one-tap unlock.
5 ✓
Unlock → TTDR
Pickup + telematics start event logged as the system of record.
Reality check: this is a growing subset of the fleet, led by Tesla — every Tesla Hertz rents already supports app access today. GM, Ford, Hyundai/Kia and Volvo expose the APIs but need per-OEM enablement + Hertz’s fleet authorization. The vehicle’s counter/rental system (DASH) has no key capability — the key always comes from the OEM layer; TT orchestrates, binds to the agreement, captures consent, and delivers.
Demonstration only — renters, stalls and keys are synthetic. The wallet agreement is delivered & signed via Lynxs; the pickup flow runs in Digivize; unlock/telematics events log to TTDR.
Pairs with Pre-arrival check-in — verified renter goes straight to the stall.