Testing TDC (Tickets.com) loaded tickets takes coordination between Fanmaker, TDC, and your POS provider. Start early — TDC event files are the long pole.
Before you start, make sure:
Your TDC integration is active with Fanmaker.
Your POS integration (Xenial, Shift4, Retail Cloud, etc.) is configured.
You have access to a POS terminal for physical scanning.
Go to Point of Sale > Loaded Tickets and click Add Loaded Ticket Type.
Name — anything you'll recognize in reporting, e.g. "Test Loaded Ticket". Required.
Buyer Type — must match your TDC buyer type exactly, and be unique for your program. Enter the Buyer Type itself, not the Buyer Type Description.
Amount — e.g. 10.00. Required. TDC does not pass a dollar value with the barcode, so this field is where the value comes from.
Leave Enabled ticked and click Create Loaded Ticket Type.
You can narrow how and where the value is used:
Restrict to POS System — limit the type to one or more specific systems, e.g. Xenial only. Leave it empty for no restriction.
Redemption Restrictions — choose SKU to reveal Allow SKUs (only barcodes matching these SKUs are accepted — a meal deal, say) and Block SKUs (barcodes matching these SKUs are rejected — no alcohol). Choose Location to reveal Allow Locations and Block Locations for specific concession stands or retail spots.
Allow multiple redemptions per seat: this one is TDC-only — it isn't shown on Ticketmaster, TicketReturn, or SeatGeek programs.
Off (default): the value is tied to the seat, identified by event, section, row, and seat number. Only the first barcode for that seat is funded; any other barcode with the same seat details is treated as already funded.
On: the value is tied to each individual barcode instead, so every barcode is funded in its own right even when they share seat details. Turn this on only for general admission events, or programs where every ticket carries identical seat information (Section: GA, Row: GA, Seat: 0). Without it, one GA fan spends the credit meant for everyone.
Work with your TDC team to create a test event.
Warning: TDC typically sends event files only once or twice a day. Get the configuration done 48 hours before your test date so the file has time to land.
Scan window: make sure the scan start and end times in TDC are active for the whole duration of your test.
1. Purchase: in TDC, create a test order using the matching buyer type, and note the barcode numbers.
2. Wait for sync: Fanmaker checks the TDC feed about once a minute, but nothing can appear until TDC has actually delivered the event file. That delivery, not the polling, is what you're waiting on.
1. Dashboard check: go back to Point of Sale > Loaded Tickets, set the Date picker to your event date, and confirm your barcodes appear under the right type with the right value. Use Action > View Barcodes on your test type to see them individually, and Search by Account Number to find a specific one.
2. POS scan: at the integrated POS terminal, add items to a transaction and scan the test barcode.
3. Verify:
The value applies correctly to the balance.
Any SKU or location restrictions behave as intended.
The transaction shows up in the Transactions chart on the Loaded Tickets page, and in Point of Sale > Transactions.
Barcode missing from the dashboard
Sync window: TDC transmits event files once or twice a day. Barcodes won't appear until the file arrives.
Buyer type mismatch: if the code doesn't match your loaded ticket type exactly — including a stray space — it won't match.
Wrong date: check the Date picker is on the event date. The page always opens on today.
Check the Unmatched row: if a red-tinted Unmatched Loaded Ticket row appears at the bottom of the types table, barcodes are arriving with no matching type behind them. View Barcodes on that row will show you exactly what came through.
Ticket rejected at the POS
Scan window inactive: verify the scan start and end dates in TDC are currently active.
Type disabled: a type that's switched off shows a disabled pill next to its name in the table.
Restrictions: check the type for POS, SKU, or Location restrictions that would block the sale.
Need support?
Email [email protected] with the barcode number, event date, and buyer type code.
