Detect tampered and deepfake Event Ticket or Program

What a genuine event ticket or programme contains

A ticket carries the event name and organiser, the venue with its address, the date and start time, the seat, block or category, the ticket or order number, the price and the purchaser, and a barcode or QR code encoding the order. A programme or letter of participation carries something else entirely: the organiser's letterhead, the participant's name and role - speaker, delegate, exhibitor, competitor - the session or stand assigned to them, a registration number, the dates of the event, and a statement of which costs the organiser is covering.

For a visa file the role is the decisive field, because it is what makes the trip purposeful and it is the field with the least support behind it. A delegate pass, a free registration and a speaking invitation are three different things, and only one of them was earned. The registration number should retrieve the same person from the organiser's system, the event dates should bracket the travel dates rather than sit loosely near them, and any cost undertaking should agree with the financial evidence filed alongside it.

How event ticket or programme forgeries are made

• Name inserted into a published programme

  The organiser's programme PDF is downloaded and the applicant's name and role added to a session list. The inserted line is rendered in a substituted font, and its spacing and leading rarely match the entries directly above and below it in the same table.

• Free registration dressed as a paid delegate pass

  A confirmation for an open or waitlisted registration is edited to read as confirmed paid attendance, with a fee line and a status added. The order number stays the one the free registration issued, so the document points back at the record that contradicts it.

• Barcode and payload mismatch

  The visible ticket detail is edited while the code beneath still encodes the original order, seat and date. Scanning returns the record the ticket was issued against, which is how an altered ticket fails at a desk and a resold duplicate fails at a turnstile.

• Duplicated tickets sold repeatedly

  One genuine ticket is photographed and sold many times. Every copy is an authentic document and only the first scanned is admitted, so the forensic question is not whether the ticket was edited but whether the image has been re-encoded and passed around.

• Organiser letterhead on an invented invitation

  A participation letter is built on a header lifted from the organiser's website and signed with a name taken from the same pages. The logo carries the compression profile of a web image while the text around it was rendered locally, at a different quality entirely.

• Events that exist only to issue documents

  A conference with a name, a venue, a programme and a registration system, created to produce invitation paperwork. Nothing in the documents contradicts anything else, so the assessment falls back to whether the event has any presence beyond the files it generates.

What TamperCheck checks on an event ticket or programme

TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.

• Date and validity consistency

  Issue, expiry, and period dates are checked against one another and against the file's own creation metadata, which catches backdating and validity extension.

• Reference and document number checks

  Document, account, and reference numbers are checked for issuer format conformance and against every other place the same value appears on the page.

• Field-level forensics

  Every text region is analysed in its own right rather than as part of one whole-page image. This catches the smoothed and feathered edits that whole-image Error Level Analysis misses entirely.

• And many more checks

  The three above are the layers that carry the most weight on an event ticket or programme. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Who verifies an event ticket or programme, and why

Consulates and event organisers confirming participation. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.

How to verify an event ticket or programme in 4 steps

1. 1

   Check the fields against each other

   Read event dates, attendee name, and barcode or QR payload together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.

2. 2

   Inspect the file metadata

   Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.

3. 3

   Ask for a second document

   Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.

4. 4

   Run a forensic check

   Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 200+ forensic checks on an event ticket or programme and returns a risk score from 0 to 100 in about a minute, at $0.50 per document.

Frequently asked questions