Fandango: evidence from the page to payment completion
A completed purchase does not reveal everything the page executed. Review checkout with accountable owners, recorded artifacts and observable outcomes.
Leer en portuguésBy Pentesty
What the notice establishes
BleepingComputer reported Fandango customer notifications on November 16, 2026. In its original notice, the company describes possible unauthorized access to information from certain checkout transactions between October 8 and 11: card number, CVV, expiration date, billing ZIP and email. On October 30, it determined that recipients could have been affected. It says it resolved the issue and was unaware of resulting fraudulent use.
The document does not disclose the code involved, the page architecture or a nationwide affected count. The report describes a skimmer, but the notice does not provide a technical reconstruction of that mechanism. The assessment below is our proposal for other authorized environments, without assigning undisclosed components to Fandango.
Reconstruct what the browser receives
Choose a representative staging journey covering the product, identification, entry and confirmation steps. Record the application version and the time of each run. Inventory loaded scripts, their owners, origins and approved changes, including resources introduced through marketing, support or tag management integrations where those components actually exist.
Compare the declared inventory with an actual browser capture. Our browser observation analysis helps define what this evidence can establish. A run represents one condition at a particular time; device, region or consent variations need their own samples. State which combinations were examined rather than assuming the sample covers every visitor.
Verify completion at the receiving system
The review of saved card retrieval boundaries complements this work by asking what information may return to the application. For checkout, assign a synthetic identifier to the attempt and follow it through the store and testing processor until it reaches the state the business recognizes as complete.
Include a declined attempt and another interrupted before confirmation. Check how operations identifies pending and repeated requests, without charging customers or using real orders. Connect the displayed message, the received record and the reconciled outcome. A visual success indicator should be supported by an authorized confirmation at its destination.
Document the decision to resume
When an unauthorized change is suspected, preserve available artifacts and records before replacing components. Bring security, development, payment operations and supplier owners together to define containment and recovery. Their choice depends on the observed conditions and acceptable impact for each workflow; the Fandango notice does not provide a universal technical procedure.
Before expanding operations, repeat the approved journeys on the recovered version and compare artifacts with the selected reference. Record exceptions, collection limits, the acceptance owner and conditions for stopping recovery. Pentesty's proposed assessment produces evidence for that decision, keeping a reported correction separate from an independent evaluation of the complete journey.
Frequently asked questions
Does the notice identify the code that caused the incident?
No. It describes possible access to checkout information and the company's response. The complete technical mechanism is not disclosed in that document.
Does an approved test purchase complete the assessment?
It establishes the outcome of that attempt. Scope should also cover loaded resources, destinations, permissions and previously defined failure conditions.
How can testing avoid exposing customer cards?
Use staging, the processor's official testing facilities and synthetic data. Limit collection and access to the records needed to verify outcomes.
What should the recovery decision owner receive?
The examined version, executed journeys, receiver outcomes, approved changes, gaps and accountable exceptions. Acceptance must state the limits of observation.
Sources and references
- BleepingComputer: November 16 report on Fandango customer notifications
- Fandango: original notification published by the California Attorney General
Original Pentesty analysis, published November 16, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.