Performing a test for TDC (Tickets.com) Loaded Tickets requires coordination between Fanmaker, TDC, and your POS provider. Please note the critical 48-hour lead time for TDC event files.
Before starting, ensure:
TDC integration is active with Fanmaker.
POS integration (Xenial, Shift4, Retail Cloud, etc.) is configured.
You have access to a POS terminal for physical scanning.
Navigate to Point of Sale > Loaded Tickets > TDC and click Add Loaded Ticket Type.
Field | Value | Notes |
Name | Test Loaded Ticket | Internal name for reporting. |
Buyer Type | [Match TDC Code] | Critical: Must match TDC buyer type exactly (case, spaces, dashes). |
Amount | e.g., $10.00 | TDC does not pass dollar values; you must set this here. |
You can further refine how and where these tickets are used.
POS System Restriction: Limit this ticket type to a specific system (e.g., Xenial only).
SKU Restrictions: Use "Allow" to whitelist items (e.g., only hot dogs or certain beverages for a meal deal) or "Block" to blacklist items (e.g., no alcohol).
Location Restrictions: Limit redemption to specific concession stands or retail locations.
Allow Multiple Redemptions Per Seat:
OFF (Default): The value is tied to a specific ticket barcode. If a ticket for Section 101, Row A, Seat 5 is transferred, the value moves with that specific barcode. Only the first barcode scanned for that unique seat location can use the value.
ON: The value is tied to the Seat Location (Section + Row + Seat Number) rather than a specific barcode. Turn this ON only for General Admission (GA) events or programs where every ticket is issued with identical seat info (e.g., Section: GA, Row: GA, Seat: 0). This ensures that every fan with a GA ticket can access the $5 credit, even though they technically share the same "seat" in the data.
Work with your TDC team to create a test event.
Warning: TDC typically sends event files only 1-2 times per day. Configuration should be completed 48 hours before your testing date.
Scan Window: Ensure the scan start and end times in TDC are active for the duration of your test.
Purchase: In TDC, create a test order using the matching buyer type and note the barcode numbers.
Wait for Sync: Fanmaker cannot sync barcodes until the TDC event file is received.
Non-event days: Sync occurs every 15 minutes after file receipt.
Event days: Sync occurs every 2 minutes after file receipt.
Dashboard Check: Navigate to Point of Sale > Loaded Tickets > TDC. Select the event date in the calendar and verify your barcodes appear with the correct value.
POS Scan: Go to the integrated POS terminal, add items to a transaction, and scan the test barcode.
Verify:
Value applies correctly to the balance.
Any SKU or location restrictions work as intended.
The transaction appears in the Fanmaker dashboard..
Symptom | Potential Causes & Resolutions |
Barcode missing from dashboard | 1. Sync Window: TDC transmits files 1-2x daily. Barcodes won't sync until the event file is received. 2. Buyer Type Mismatch: If the code doesn't match your Loaded Ticket type exactly (case-sensitive), it won't show. 3. Incorrect Date: Verify you are viewing the correct event date in the calendar. |
Ticket rejected at POS | 1. Scan window inactive: Verify the scan start/end dates in TDC are currently active. 2. Restrictions: Check the Loaded Ticket Type for POS, SKU, or Location restrictions blocking the sale. |
Need Support?
If issues persist, email help@fanmaker.com with the Barcode Number, Event Date, and Buyer Type code.
