How to set the maximum depth for chained transfers
Cap how many times one ticket can be passed between different people.
The same ticket can be transferred several times over — buyer to friend to cousin to acquaintance. A tier's maxTransferDepth sets how many hops are allowed before check-in. Once the limit is reached, further transfers are blocked and the ticket is "pinned" to its current holder.
How depth works
Depth = the number of times the ticket has already changed hands.
- Depth 0: the ticket is still with the original buyer
- Depth 1: one transfer accepted
- Depth 2: two transfers accepted
- ...
With maxTransferDepth = 2, the ticket can go from John to Mary (depth 1) to Peter (depth 2), and Peter cannot transfer it to anybody else.
Step by step
- In the dashboard, open the event → the Lots section → click the tier to edit it
- In the tier's form, find the Transfer limit field (
maxTransferDepth) - Type the number of hops allowed. Leave it blank for unlimited — the smallest value accepted is
1. To block transfers entirely, untick Allow transfer rather than touching this field - Click Save
When to use it
| Scenario | Recommended value |
|---|---|
| A tier with no control | null (unlimited) |
| Light prevention of chained resale | 3 |
| Strong prevention | 1 (a single transfer only) |
Why cap the chain
Scalpers buy tickets, resell them, and the secondary buyer sometimes resells again — one purchase can pass through 4 or 5 hands before the event. That:
- Makes tracking harder if there is fraud
- Raises the risk of confusion at check-in
- Makes the attendance list less predictable
Capping the depth (at 1 or 2, say) makes sure the ticket goes through at most one legitimate "swap" (a friend who can no longer make it passing it to somebody else) and shuts down speculative chained resale.
Where to check the limit
In the Lots section, every tier with a limit shows a Max Nx badge (for example, Max 2x) with the value you configured. In the Transfers section, you follow the event's transfers, with sender, recipient, tier, status, and date.