Skip to main content
Ticket transfers let patrons pass individual tickets to someone else by email, for free. The recipient becomes the ticket holder when they claim. Transfers are on by default for each event, including existing events, unless you turn them off. A transfer moves an existing ticket. It doesn’t create another sale or change the ticket price, fees, earnings, or payout.

Turn transfers on or off

1

Open your event's tickets

Click Events in the dashboard sidebar, select your event, then open Tickets.
2

Set your transfer policy

Use Allow ticket transfers to turn transfers on or off. The change saves immediately.
The event owner, committee owner, or someone who owns ticket types on the event can change this setting. Committee membership alone doesn’t grant permission. If you only see Ticket transfers: On or Ticket transfers: Off, the setting is read-only for you. Turning transfers off stops new transfers, including a recipient sending a claimed ticket on again. It doesn’t cancel pending transfers: those recipients can still claim before their deadline.

Understand the ticket’s status

Patrons can transfer only unused tickets before the event ends. Tickets from a payment plan become transferable after the plan completes. A transfer covers one issued ticket, even when the original purchase included several. Recipients claim using the email the ticket was sent to. They can create an account if needed, and can receive a ticket even if they already hold another ticket for the event. No new purchase approval is required to claim a transfer.

Find the current holder and original purchaser

Use the current holder when checking attendance. Use the original purchaser when reconciling payments or discussing a refund.
  • The guest list and scanner show the current holder. Transferred identifies tickets held by someone other than the original purchaser.
  • Guest list search matches the current holder and original purchaser. Select the guest to see Bought by details where shown.
  • In Sales, the Name column leads with the current holder. The Transferred badge shows the original purchaser in its tooltip.
  • Click a sale to see the current holder’s contact details and Original purchaser details.
The name shown in Sales can change after a claim. The original payment still belongs to the purchaser who paid for it.

Export purchaser and attendee records

In Sales, click Export to CSV, then Export. The file keeps the original purchaser in customer and email. Use currentOwner and currentOwnerEmail for the patron attending. transferred indicates whether the ticket is held by someone other than the original purchaser. The web scanner’s guest list export uses the current holder for name and email. It includes boughtBy for the original purchaser of a transferred ticket, plus transferred and status. Use this export for door staff and attendee lists.

View transfer history

Open Sales and click the ticket sale. Look for Transfer history in the details. The timeline shows who sent the ticket, who claimed it, reminders, and dates. It distinguishes transfers cancelled by the sender or Taack, expired unclaimed transfers, and transfers closed because the event ended or the sale was refunded. If the ticket was sent on again, the timeline groups the successive transfers. Transfer history is retained when an order is refunded. A refunded ticket no longer provides admission.

Help patrons at the door

A ticket marked Transfer pending can’t be checked in by scanning or through the guest list. Ask the recipient to finish claiming, or ask the sender to cancel from My Tickets before checking in.
After a claim, ask the recipient to open My Tickets and show their current QR code. Don’t use the sender’s forwarded screenshot or old wallet pass. The recipient’s ticket is the valid copy. If the recipient can’t claim because they’re signed into a different account, ask them to choose Switch account on the claim page. If the email was wrong, the sender must cancel the pending transfer and send it again to the correct address.

Cancellation, reminders, and expiry

Only the sender can cancel or resend a pending transfer from their ticket. You can’t cancel a patron’s transfer from the organizer dashboard. For an urgent issue that needs Taack’s help, contact Taack. Pending transfers expire after 14 days or at the event’s end, whichever comes first. Each resend restarts the 14 days without extending past the event’s end. Senders can resend once an hour, with up to five reminders per transfer. After a claim, the sender can’t take the ticket back. The current holder can transfer it again if your event still allows transfers and the ticket remains eligible.

Custom questions and virtual events

The recipient supplies their own answers to your event’s questions when claiming. Those answers replace the previous holder’s answers for that ticket. For virtual events, access follows the current holder after the claim. A sender who still holds another eligible ticket retains access. The sender’s existing virtual access remains available while a transfer is pending. The recipient’s access follows the event’s normal join window.

Refunds and payouts

Transfers don’t change who receives a refund. For card purchases, any refund returns to the original purchaser’s original card. Taack doesn’t pay the current holder or reimburse any private payment between patrons. Refunds cover the whole order. Refunding an order invalidates its transferred tickets and closes pending transfers. Taack notifies affected current holders or recipients waiting to claim; it doesn’t notify every previous holder in a transfer chain. A transfer doesn’t change the normal refund restrictions. Once you’ve received the payout, the order can’t be refunded through Taack. See Payouts and the Refund Policy.

Share instructions with patrons

Taack emails the recipient when a ticket is sent and emails the sender when it’s sent, claimed, or cancelled. You don’t receive an email for each transfer. Check the guest list, Sales, and Transfer history for visibility. Send patrons the Transfer a ticket guide for sending, claiming, cancelling, and troubleshooting.