BYD and Parkopedia announced yesterday a deal that turns the dashboard of every BYD vehicle in Europe into a parking payment terminal — no phone, no app-switching, no typing. The service, called ParkPay, uses Android Automotive OS's persistent location layer to detect when a driver is parking in a supported zone and surfaces a payment prompt automatically. It is scheduled to go live in production vehicles early next year, and existing BYD owners will receive it via an over-the-air update. What European drivers considering or already owning a BYD vehicle need to understand is that this convenience is delivered through a connected-vehicle architecture subject to Chinese national law — and those legal obligations cannot be waived by any European data storage commitment.

How BYD ParkPay Works: The AAOS Architecture Behind Geo-Triggered Payments

ParkPay is built on Android Automotive OS (AAOS), a full embedded operating system that runs directly on the vehicle's hardware — distinct from Android Auto, which merely mirrors a smartphone's screen. BYD's European models run AAOS with Google built-in (Google Automotive Services, or GAS), which means Google Maps, the Google Play Store, and Google Assistant are native to the infotainment system alongside BYD's own apps.

The technical mechanism behind ParkPay's contactless-style experience is geofencing: a virtual perimeter drawn around every parking zone in Parkopedia's database of more than 90 million spaces across 90 countries. The AAOS location layer — operating through the Vehicle Hardware Abstraction Layer, which bridges the car's GPS receiver and other sensors to the software stack — continuously monitors the vehicle's position. When the car crosses into a registered parking zone, the Car Services layer triggers a notification on the infotainment display. The ParkPay app opens with the relevant zone pre-selected. A few taps later, the parking session is underway.

In the UK, payments are processed through RingGo; across Europe, EasyPark handles the payment rail. Both are market-leading mobile parking payment networks already embedded in parking infrastructure across hundreds of cities. Their integration into AAOS converts two existing app ecosystems into a single dashboard-native experience.

This architecture is materially different from a phone-mirroring approach. Because AAOS runs persistently on the vehicle's own hardware, ParkPay can operate without the driver's phone being present, unlocked, or connected. The vehicle's built-in SIM card handles cellular communication. The geofencing trigger is always listening.

Which BYD Models Get ParkPay, and When

ParkPay will arrive pre-installed on two upcoming BYD models: the Denza Z9 GT, the brand's flagship luxury electric shooting brake, and the BYD Atto 3 Evo, the refreshed version of BYD's best-selling compact SUV in Europe. The production rollout is targeted for early 2027, with a public showcase planned before then.

Owners of existing BYD vehicles will receive the feature through a software over-the-air (OTA) update delivered via the car's built-in cellular connection — a delta update that transfers only the changed code, not a full firmware reinstall. OTA delivery is how BYD intends to add subsequent capabilities as well: EV charging payments, toll payments, and parking reservations are all planned for future iterations of the ParkPay service within the broader BYD mobility app.

What AAOS as a Commerce Platform Means for the Connected Car Race

ParkPay is not BYD's product in isolation. It is a demonstration of what Android Automotive OS enables that phone-projection systems do not. Because AAOS runs as a full operating system with its own persistent processes, third-party developers can build location-aware applications that respond to what the vehicle is doing in real time — without requiring the driver to launch an app or even look at a screen until a relevant event occurs.

The commercial architecture underlying ParkPay — vehicle telemetry feeding a geofenced trigger, which surfaces a contextual payment interface at the precise moment the driver needs it — is the same pattern that could eventually power drive-through ordering, fuel payment, and toll collection in AAOS-equipped vehicles generally. BYD is among the first major brands to deploy this pattern at production scale for a recurring daily use case. Duncan Licence, Head of Automotive and Data at Arrive (Parkopedia's parent company), described the deployment as groundwork that "will unlock greater connectivity capabilities for BYD vehicles in urban areas, supporting integration with infrastructure as cities continue to improve their smart capabilities."

Stella Li, Executive Vice President of BYD, tied ParkPay to the company's broader software strategy: alongside FLASH Charging technology and the second-generation Blade Battery, seamless in-car payments are positioned as infrastructure for removing the friction points that slow EV adoption in Europe.

What BYD Drivers in Europe Need to Know About Data and Chinese Law

The ParkPay service collects precise, real-time location data and payment transaction data on an ongoing basis. That data flows through BYD's connected-vehicle architecture — which also collects GPS location history, driving behavior, infotainment usage, and smartphone data mirrored through the cabin system. Understanding who can legally access that data requires looking beyond BYD Europe's privacy policy.

China's National Intelligence Law (2017), in Article 7, requires: "All organizations and citizens shall support, assist, and cooperate with national intelligence efforts in accordance with law." China's Cybersecurity Law (2017) and Data Security Law (2021) add data localization requirements and government-access provisions. These laws apply to BYD as a Chinese company headquartered in Shenzhen, regardless of where its European vehicles operate, where their data is physically stored, or what privacy certifications the company holds.

BYD Europe's published privacy position states that data is stored in the European Economic Area or the UK and processed in compliance with GDPR. BYD holds R155 (Cybersecurity Management System) and R156 (Software Update Management System) certifications from independent auditors. BYD has publicly denied that Chinese government agencies have unauthorized access to vehicle data. These commitments are genuine statements of BYD's own practices — but they do not and cannot override a legal obligation imposed by Chinese national legislation.

In October 2025, security researchers at PlaxidityX demonstrated that personal data — including GPS location history, contacts, healthcare information, and app preferences — could be extracted from the infotainment unit of a 2023 BYD Atto 3 without any active network intrusion, because data was stored unencrypted and consent prompts had not triggered after a factory reset. BYD has not published a public response to those findings or an independent security audit confirming remediation. The Atto 3 Evo named in the ParkPay announcement is the direct successor to that vehicle.

On the regulatory front, the U.S. Commerce Department's Connected Vehicle Rule is already pushing Chinese-linked vehicles out of the American market — Polestar lost its 2027 model-year authorization today under the same Chinese-ownership-nexus standard that would apply to BYD. European regulatory frameworks addressing Chinese EV data practices remain under development.

No technical mitigation fully resolves the structural legal risk created by Chinese intelligence law. Network segmentation at home (placing the vehicle on an isolated IoT network) limits exposure from that connection point but does not affect the vehicle's always-on cellular data link. Readers evaluating a BYD vehicle should treat the China data-law framework as a fixed condition of the product, not a risk that GDPR compliance or European data-storage addresses.

Is BYD's Connected Car Strategy Worth the Tradeoff?

BYD's ParkPay launch encapsulates the decision facing European EV buyers in 2026. The AAOS-based commerce layer it is building is technically sophisticated, genuinely useful, and architecturally ahead of most Western competitors in its integration depth. The geofencing-to-payment pipeline is not a phone workaround — it is a purpose-built vehicle intelligence system. The 90-million-space Parkopedia database and the RingGo and EasyPark payment integrations give it real-world coverage from day one.

The data obligations attached to that system are not speculative. They are statutory requirements of Chinese law that BYD cannot contractually waive for its European customers. A European driver using ParkPay in 2027 will be interacting with a commerce layer built on AAOS — meaning data flowing through BYD's vehicle architecture, Google's GAS infrastructure, and Parkopedia's parking database simultaneously. The convenience is real. The legal framework governing who can access BYD's share of that data is also real, and it is not European.

Frequently Asked Questions

How does BYD ParkPay know when to prompt me to pay for parking?

ParkPay uses geofencing — a virtual boundary drawn around every parking zone in Parkopedia's database — combined with Android Automotive OS's persistent location layer. The vehicle's GPS and cellular hardware continuously cross-references the car's position against that database. When the car enters a registered zone, the AAOS Car Services layer triggers an on-screen notification without requiring the driver to open an app.

Which BYD vehicles in Europe will get ParkPay and when?

The Denza Z9 GT and the BYD Atto 3 Evo will have ParkPay pre-installed when they reach production in early 2027. Owners of existing BYD vehicles will receive the feature through an over-the-air software update delivered via the car's built-in SIM card connection.

Does China's National Intelligence Law apply to data collected through a BYD car in Europe?

Yes. China's National Intelligence Law (2017), Article 7, requires BYD — as a Chinese company — to cooperate with Chinese government intelligence requests. This obligation applies regardless of where the vehicle is driven, where the data is physically stored, or whether the company complies with European GDPR requirements. BYD's European data-storage commitments address its own practices and comply with EU law; they do not extinguish the legal obligation imposed by Chinese national legislation.

What connected car payment features are planned beyond parking?

Parkopedia and BYD have confirmed plans to add EV charging payments, toll payments, and parking reservations to the ParkPay service in future updates. These will be delivered over the air to the same vehicles receiving the initial parking payment feature.