A narrow window, sensitive payment fields

Fandango says an unauthorized party could access payment-card information associated with certain ticketing checkout transactions from 8 through 11 October 2026. The notice lists card number, CVV, expiration date, billing ZIP code and email address as potentially involved. It says names, government identification, Social Security numbers and other account information were not involved.

Fandango says it resolved the issue and is not currently aware of fraudulent use resulting from the incident. The notice does not state how access was gained, how many transactions were involved, or whether the exposure came from a browser script. Those points need confirmation before they become part of the incident account.

Do not infer the mechanism

A checkout exposure is enough to warrant response. Calling it a skimmer, supply-chain compromise or site intrusion goes beyond the technical detail in Fandango's own notice.

Preserve the transaction window and the page evidence

  1. 1

    Reconcile the period. Match affected transactions and payment flows to the 8–11 October window. Keep precise timestamps, page versions and payment-provider boundaries.

  2. 2

    Preserve what the browser loaded. Retain checkout script inventories, response captures and change records so investigators can test possible entry paths without assuming one.

  3. 3

    Help affected customers. Notify people within the confirmed scope and give them a direct route to their card issuer for suspicious charges. Fandango's notice advises checking financial accounts and reporting unauthorized transactions.

Payment data changes the urgency

Card number, expiry and CVV make this more immediately actionable than an email-only exposure. Payment teams should coordinate with their processor and card brands under their incident procedures while the security team establishes how the checkout data became accessible. Keep the public account tied to confirmed findings as the investigation develops.