The PCI Security Standards Council moved the expiration date for PTS POI version 5 devices from 30 April 2026 to 30 April 2027 — a one-year extension announced in a bulletin, applying only to devices already approved under the v5 standard.
If a parking operation deferred a pay station refresh on the strength of that news, this is the year the deferral has to end. The extension was granted for reasons that describe the parking equipment market almost exactly, and the same reasons will make the last few months of it crowded.
What the date actually governs
The distinction that matters most, and gets muddled most often: approval expiry is a rule about deploying devices, not a switch that disables installed ones.
After 30 April 2027, all new terminal deployments must be v6-compliant. The extension applies only to already-approved v5 devices and does not reopen the approval process for new ones — no additional device gets a v5 approval between now and then.
What happens to units already in the field is governed by acquirer and card-brand policy rather than by the approval date itself, and those policies vary. That is a question to put to the acquirer in writing now, because the answer determines whether this is a 2027 problem or a multi-year one.
The practical effect for an operator is straightforward: any pay station bought, relocated to a new site, or installed as part of an expansion after that date must be v6. A v5 unit sitting in a storeroom as a spare becomes a spare that cannot be commissioned into a new lane.
Why the extension happened, and why it is a warning
The Council was explicit about the cause. The extension supports deployment continuity against ecosystem-wide constraints: limited technician availability, constrained hardware supply, and complex upgrade timelines — specifically in embedded, unattended, and multi-component environments, naming kiosk-based solutions, ATMs, and self-service payment terminals.
That is a description of parking pay stations. Unattended, embedded, multi-component, installed outdoors on a concrete pad, requiring a technician to attend site.
Read the reasoning rather than the date. The industry was granted an extra year because the sector could not physically execute the replacement in time. Everyone who could not execute it got the same year. Technician availability and hardware supply do not improve because a deadline moved — and demand against both will concentrate as April 2027 approaches.
Building the replacement plan
Inventory by approval version, not by age. A five-year-old terminal may be v5 or v6 depending on when the model was approved, and model families frequently span both. The approval version is the field that matters; chassis age is not a proxy for it.
Separate the estate into three buckets. Units that must be replaced before April 2027 because they will need to be redeployed or because acquirer policy requires it; units that can remain in service under acquirer policy; and units already v6. Only the first bucket is on this deadline, and mixing the three inflates the budget request and undermines its credibility.
Confirm whether the upgrade is a module or a machine. Some pay station platforms allow the payment module to be swapped while the enclosure, printer, and controller remain. Where that path exists it is dramatically cheaper and faster than full replacement, and it consumes far less technician time — which is the genuinely scarce resource here.
Book installation capacity early. The constraint the Council named first was technician availability. Integrators will be scheduling against every operator in the region simultaneously in the first quarter of 2027, and the operators who scheduled in 2026 will be served first.
Check the connectivity and back-office dependencies. A terminal generation change frequently brings changed communication requirements, key injection procedures, and management-platform versions. A replacement plan that budgets hardware and labour but not the back-office work will slip on the integration, not the installation.
What to put in the specification
Anyone specifying new pay stations this year should ensure the v6 approval is stated explicitly against the exact model and firmware being quoted, not against the product family. Approval attaches to specific configurations, and a family-level claim is not verifiable.
It is also worth asking the supplier directly what the expected approval life of the offered v6 device is and how far into its own cycle it already sits. Buying a v6 terminal late in its approval window repeats this exercise sooner than the capital plan assumes — and there is no reason to expect a second extension, since the Council described this one as limited and granted it for circumstances it does not intend to accommodate again.
The extension bought the industry a year of procurement runway. Operations that treat it as a year of planning will replace on schedule; operations that treat it as a year of delay will be competing for the same technicians in the same quarter.
