Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a228baa09db4f43c

Jump to content

Talk:PAX Technology

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia

Request to add PAX Technology Appointed to PCI Security Standards Council 2025–2027 Board of Advisors

[edit]

I am affiliated with PAX Technology and would like to suggest an update to the article to reflect recent developments. The current information is outdated and may misrepresent our role in the PCI SSC. Suggested update:

"PAX Technology was reappointed to the Board of Advisors for the PCI Security Standards Council (PCI SSC) for the 2025–2027 term. The company is represented by LeAnn Hostetler, Chief Security Compliance Officer for PAX North America, and Aileen Liu, Global Director of Payment Technology.

The PCI SSC Board of Advisors consists of representatives from Participating Organizations across the payments industry. The Board provides input and guidance on the development and implementation of PCI security standards, which are designed to enhance payment data security globally.

Members of the Board began their term on June 1, 2025, and participate in Council initiatives, including having voting rights on proposed standards before they are publicly released."

This reflects recent developments and maintains a neutral tone.

Sources: PCI Security Standards Council Announces 2025-2027 Advisory Board - PCI Security Standards Council

PCI Security Standards Council – Protect Payment Data with Industry-driven Security Standards, Training, and Programs

PCI Security Standards Council – Protect Payment Data with Industry-driven Security Standards, Training, and Programs Sgrove357 (talk) 20:11, 11 September 2025 (UTC)Reply

Request to Add Context to FBI Raid Section

[edit]

I am affiliated with PAX Technology and would like to suggest a balanced update to the section discussing the FBI raid. The current content does not reflect follow-up reporting that clarified the outcome of the investigation. Suggested addition:

"In October 2021, Worldpay, Inc., a subsidiary of FIS, began removing PAX point of sale products due to cybersecurity concerns.[1]

On October 26, 2021, it was reported that agents from the U.S. Federal Bureau of Investigation, Department of Homeland Security, and other federal officials raided the Jacksonville, Florida offices of PAX Technology. KrebsOnSecurity reported the raid was tied to reports that PAX's systems may have been involved in cyberattacks on U.S. and E.U. organizations.[1] Following the raid, a senior executive in charge of PAX Technology's security resigned.

In December 2021, following the FBI raid and initial cybersecurity concerns, Seeking Alpha reported that no evidence was found to confirm that PAX Technology had been hacked or that its devices were involved in cyberattacks on U.S. and E.U. organizations. The report highlighted that security firms analyzing PAX terminals did not identify any malicious activity, and the company denied any wrongdoing, stating that its products remained secure and compliant with industry standards. Despite the initial allegations, PAX Technology continued operations and maintained its position as a global provider of point-of-sale solutions."

This reflects recent developments and maintains a neutral tone.

Sources:PAX Global Has Not Been Hacked After All (NASDAQ:PANW) | Seeking Alpha Sgrove357 (talk) 20:16, 11 September 2025 (UTC)Reply

Seeking Alpha is not a WP:RS. You would need WP:RS to substantiate any factual claims. - Amigao (talk) 23:31, 11 September 2025 (UTC)Reply
  1. 1 2 Cite error: The named reference :0 was invoked but never defined (see the help page).