Fandango Checkout Breach: What E-commerce Teams Should Check

A payment card over a cinema ticket illustrates the Fandango checkout breach.
5/5 - (1 vote)

Last Updated on November 17, 2026 by Narendra Sahoo

The Fandango checkout breach put payment card data from some ticket purchases at risk from October 8 to 11, 2026. In its breach notice filed with the California Attorney General, Fandango lists card numbers, CVVs, expiration dates, billing ZIP codes and email addresses as potentially exposed. The company says it resolved the issue.

The notice leaves the attack method unspecified. On November 16, 2026, BleepingComputer reported that a skimmer planted on the checkout page captured card details during that period. The number of customers affected and Fandango’s PCI DSS status remain unconfirmed in those accounts.

Start with one question

If you had to show, by tomorrow, what runs in a shopper’s browser at checkout, what could you provide?How do you detect tampering, and what proof could your team show?

PCI DSS payment page security checklist

In e-skimming, malicious code in a shopper’s browser copies card details entered on a payment page. Where they apply, PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1 have been mandatory since March 31, 2025.

Requirement 6.4.3 calls for a way to confirm each payment page script is approved. It also requires a way to verify each script’s integrity. It also requires an inventory that explains why each script is needed.

Requirement 11.6.1 calls for monitoring scripts and security-impacting HTTP headers received by the shopper’s browser. It also requires alerts for unauthorized changes. Run the checks at least once every seven days or at the frequency set by your targeted risk analysis.

1. Check script inventory and approvals

Ask for a current script inventory with a justification and approver for each script.

Suggested owner   E-commerce engineering lead

2. Verify script integrity

Ask for the integrity check method and its latest result, such as a hash check against an approved script version.

Suggested owner   Application security lead

3. Test payment page tamper alerts

Ask for a dated test record showing what changed, what alert it triggered and who received it.

Suggested owner   Security operations lead

See VISTA InfoSec’s guide to PCI DSS Requirement 11 for testing examples.

SAQ A for embedded payment forms and redirects

The January 2025 SAQ A revision removed Requirements 6.4.3, 11.6.1 and 12.3.1 from the questionnaire and added a script-security eligibility criterion.

PCI SSC FAQ 1588 says this criterion applies when the merchant embeds a payment provider’s form, such as an iframe. The merchant can use controls like those in 6.4.3 and 11.6.1 or get confirmation from its PCI DSS-compliant provider that the solution protects the payment page from script attacks when implemented as instructed.

Redirects to a provider-hosted payment page fall outside this specific criterion. Confirm which SAQ applies with your acquirer.

How VISTA InfoSec can help

VISTA InfoSec’s Qualified Security Assessors can map your checkout flow. They can identify the PCI DSS requirements that apply. They can also review evidence from your payment pages. A PCI DSS gap assessment helps prioritize fixes before validation.

Conclusion

Walk through one checkout flow with engineering and security operations. Compare the scripts a browser actually loads with the approved inventory. Give each gap an owner and a retest date.

Bring your checkout flow and payment provider details to a scoping discussion with VISTA InfoSec.

Request a PCI DSS gap assessment