How to set fair ticket transfer rules for buyers

Set fair ticket transfer rules by letting eligible buyers give their ticket to someone else through one official process, with the deadline, cost and entry requirements visible before purchase. Keep changes to the person attending separate from paid resale and refunds, and make sure your team follows the same rules at the door.

Someone bought a ticket to your event. Now they can't come, but their friend can. You have already sold the place. The buyer wants a reasonable way to use what they paid for, and you want the right person arriving with a valid ticket. That's the problem your policy needs to solve.

The trouble starts when "tickets are transferable" is the whole explanation. Does sending the email count? Does the new person need an account? Can a student ticket go to anyone? Who gets the refund if you cancel? Your buyers will discover those gaps, usually when your team has other things to do.

This guide walks you through eligibility, identity, deadlines, fees, the transfer process and arrival. You'll also get sample wording and practical cases to test before tickets go on sale. The aim is a policy buyers understand and your team can actually run.

Start with a gift or change of attendee

For this guide, a transfer means an approved change to the person entitled to attend, without an organizer-managed sale between the old and new holder. A parent gives a ticket to their child. A colleague takes a place someone can no longer use. The admission remains attached to the same event.

Resale involves selling the ticket again. A refund returns money under your policy or applicable rights. Buyers sometimes use "transfer" for all of these, so your instructions need to separate them. Otherwise someone may expect payment because they sent a ticket to a friend, or assume a transfer creates a refund request.

Ask one plain question when deciding your default. If the replacement attendee meets the entry requirements, what would prevent them from using this paid place? For ordinary general admission, allowing a genuine gift is usually the more practical choice. You avoid making a customer negotiate a favour to change a name.

There are legitimate exceptions. A professional course might require a named qualification. A ticket might include something already prepared for a specific person. Explain that reason alongside the restriction. "Non-transferable" on its own tells buyers the answer without helping them understand the event they are purchasing.

Don't promise that a transfer resolves a private payment dispute. If friends arrange money between themselves, your holder-change process doesn't automatically check the payment or guarantee it. Give buyers the official resale route where one exists, and explain what your transfer process covers before anyone relies on it.

Decide eligibility for every ticket type

Start with the admission ticket most people buy. Then check every exception against the actual offer. A reserved seat, a student rate, a group bundle and an admission package may all be sold on the same page, but the conditions attached to them can differ.

An early booking price doesn't automatically need an eligibility test. If the discount simply rewarded buying earlier, transferring that ticket doesn't change why the original buyer qualified. A membership or student discount is different. Decide whether the replacement must qualify, how that is checked, and what happens if they don't.

Keep those decisions specific. "Discounted tickets cannot be transferred" catches buyers whose only difference was buying during the first release. If your concern is a benefit reserved for current members, say that. Buyers can follow a condition they recognise. A broad ban creates arguments about tickets you never intended to restrict.

For packages, list what travels with the admission. The seat might stay the same while a personalized item cannot change. A meal selection may have a separate supplier deadline. A workshop place may require the replacement to meet a prerequisite. Resolve these details before saying the entire booking can move.

If the ticket is part of an order containing several admissions, explain whether buyers can transfer one ticket or must move the whole package. Test the actual process. Don't describe individual transfers simply because the order contains individual names, and don't require a whole group to change when the system supports one person.

Separate the purchaser from the attendee

The person who pays isn't always the person who comes. Businesses buy places for staff. Friends buy together. Parents purchase gifts. If your policy assumes every ticket holder used their own card, ordinary customers will look like exceptions before anything has gone wrong.

Decide which details identify the order and which identify the attendee. The purchase record helps your team answer payment questions. The current ticket holder helps them answer entry questions. Those jobs may involve different people, and changing the attendee should not silently rewrite the history of who made the purchase.

Name checks also need a purpose. An age-restricted event needs the attendee to meet the age requirement regardless of who bought the ticket. A professional qualification belongs to the attendee. Checking the purchaser's identity wouldn't answer either question. Match the check to the rule you are trying to enforce.

For an ordinary ticket without a named-person condition, don't introduce an identity check just because a name appears on a confirmation email. Decide how your event handles gifted admission, then make the ticket instructions agree. Your door staff should not be inventing a lead-purchaser rule because the buyer happens to be absent.

Our ticket management guide covers the wider relationship between orders, attendees and entry. Here, the useful distinction is simple. Keep the payment record understandable, keep the attending person's details current where required, and tell buyers whose identity your team will check.

Make the official process do the work

Use the supported transfer process wherever your ticketing service provides one. Sending a screenshot, editing a PDF or forwarding the purchase receipt may share information, but none tells your team whether the authorized holder has changed. Your policy should direct buyers to an action the service actually records.

Loopyah's ticket transfer instructions explain that the organizer must enable transfers. The holder opens My Tickets, selects the ticket and chooses Transfer. They can find an existing Loopyah user or enter the recipient's name and email address to send an invitation.

For an email transfer, the recipient receives a link, signs in and accepts. The ticket transfers once they accept. A pending transfer can be recalled through My Ticket Transfers before acceptance. These are useful details for your buyer instructions because sending an invitation and completing a transfer are different moments.

That official route gives buyers a defined way to pass admission to someone else. Don't make each ordinary transfer an email negotiation with your team when the enabled process already handles it. Save support for cases such as a wrong address, a missing invitation or a restriction the buyer needs explained.

Before announcing transfers, run the process with your event setup. Check which ticket types offer it, what the sender sees and what the recipient must do. Make sure your instructions describe the screens buyers will actually reach. A general help page doesn't settle every condition attached to your event.

Pick a deadline your operation needs

A fair deadline leaves buyers enough time to act while respecting work that must happen before arrival. Start with the task that requires a cutoff. Is it finalizing a named guest list, preparing badges, confirming meals or handing a specific attendance record to the venue?

If you can't name the task, reconsider an early deadline. Closing transfers well before the event may simply push later changes into your support inbox. You haven't removed the work. You've moved it into a less convenient process while making buyers explain why their plans changed.

Use an exact date, time and time zone. "Before the event" can mean before doors open, before the first performance or before the calendar day begins. Buyers travelling across time zones need the same answer as local customers. Put that answer in the event information and the transfer instructions.

Also say what must happen before the cutoff. Is sending the invitation enough, or must the recipient accept? Where acceptance completes the transfer, requiring completion by the deadline gives you a clearer admission record. Don't count an invitation as completed merely because it arrived before your chosen time.

Here is a hypothetical example. Doors open on Saturday at 7 pm. You set a transfer completion deadline of Saturday at noon, in the venue's local time, because the named list must be finalized that afternoon. An invitation sent at 11:50 am and accepted at 12:10 pm misses that stated deadline.

Treat fees as a real buyer decision

For a straightforward gift of ordinary admission, my starting recommendation is to make the transfer free where your costs and service terms allow it. You have already sold the ticket. Charging someone again to let a friend use it needs a better reason than "other events do it."

If there is an unavoidable service charge or genuine additional work, make the fee clear before the buyer purchases. State the amount or how it is calculated, who pays it, when payment happens and whether a failed or recalled request incurs a charge. Don't leave the recipient to discover a surprise bill.

Avoid using a transfer fee to recover a ticket-price difference unless that is an openly stated, lawful condition for an eligibility change. A member ticket becoming a standard ticket is a different decision from giving an ordinary ticket to a friend. Explain any permitted upgrade separately and check that your service supports it.

For US events within its scope, the FTC's guidance on deceptive fees explains total-price disclosure and truthful fee descriptions for live-event tickets. It distinguishes mandatory charges from optional services and discusses some charges incurred after purchase. That doesn't establish how every transfer fee should be classified.

Check the applicable rules for your transaction, then write the buyer-facing explanation in plain language. Even where a fee can be charged, hiding it creates an avoidable complaint. Your decision should account for the support it causes and the effect on customers who were willing to pay for your event.

Collect only the information you need

A transfer may require the recipient's name and email address. That doesn't mean you need their home address, employer, identification scan and a story about why the original holder cannot attend. Decide what information is necessary for the specific event and use the supported process to collect it.

In the UK, the ICO's data minimisation guidance says personal data must be adequate, relevant and limited to what is necessary for its purpose. If you operate under UK GDPR, that principle applies to information you collect for transfers too. It isn't a licence to gather details just in case.

Avoid asking buyers to email a passport or card photograph as your standard transfer step. If a particular issue requires identity verification, use an appropriate process and limit access to those handling it. A routine gift shouldn't create a folder of sensitive documents your event team doesn't need.

Make the recipient's communication needs clear as well. They need admission details and event updates relevant to their ticket. That doesn't mean accepting a gifted ticket should silently subscribe them to unrelated marketing. Check the privacy and marketing requirements that apply, and keep your explanation consistent with your actual settings.

Tell support staff where to check transfer status rather than copying personal details into scattered chats. If they need to record an exception, record the decision and necessary ticket reference. Keep payment information with the appropriate order process. Your door team needs enough to admit the right person, without seeing everyone's purchasing history.

Handle accessible tickets without unfair restrictions

Accessible admission deserves careful handling because a casual rule can remove someone's ability to give their ticket away. Start with the laws applicable to your venue and event. Don't assume that a condition you use for a membership discount can also be imposed on accessible seating.

For covered US assigned-seat events, the Department of Justice's ticket sales guidance says that if venues allow patrons to give or sell tickets, that right must extend to patrons with disabilities holding accessible-seat tickets. It says an accessible-seat holder with a disability may transfer the ticket to anyone, including someone without a disability.

So a blanket instruction that accessible tickets may only go to another disabled person would conflict with that guidance in its stated scope. Check your own obligations and train the team. Don't send buyers through extra informal approval simply because their ticket is for an accessible seat.

Separately, explain how attendees can contact you about access needs. A change in holder may change the assistance someone needs, even when the admission itself remains valid. Keep that conversation focused on arrangements you can provide. Don't make the person disclose unnecessary medical history to complete a normal ticket transfer.

Companion tickets and access arrangements need the same attention. Check the terms and legal requirements attached to the specific offer. Where a companion arrangement must change with the main ticket, explain the process together. Two disconnected support replies can leave a buyer with valid admission but no usable plan for arriving.

Say what changes and what stays attached

A transfer should have a clear result. The replacement receives the eligible admission you have approved. The event date, ticket type, seat and included benefits should remain as described unless your policy explicitly permits a separate change. A holder change isn't a quiet upgrade to a different package.

Tell buyers whether any personalized extras need separate action. Perhaps the admission can transfer but a printed badge cannot be replaced after production closes. Perhaps the meal choice stays with the booking. These are event-specific decisions, so only publish conditions you can fulfil and explain them before they become a surprise.

Also explain what the original holder should do after completion. They should stop sharing or trying to use the transferred admission. The recipient should use their current ticket through the official route. Avoid telling either person to rely on an old screenshot when your service provides a current ticket.

Our QR ticketing guide explains the wider entry process. For your transfer policy, verify the particular service's behavior rather than assuming every barcode works the same way. Check what happens to the original ticket, what the recipient receives and how the door team confirms the current status.

This is especially useful for a buyer transferring one place from a group order. Their other tickets should remain understandable and usable under the event's rules. Confirm that the process moves the selected admission and explain how the rest of the group accesses their tickets. Nobody should have to guess which attachment to keep.

Keep cancellation and refunds clear

A buyer changing their plans and an organizer cancelling an event are different situations. Your transfer policy may offer an option for the first. It shouldn't imply that finding another attendee is the only remedy for the second, or that accepting a transfer removes rights that otherwise apply.

For Australian events, the ACCC's ticket selling guidance explains that cancellation or significant changes can create refund rights, depending on the circumstances. It distinguishes organizer decisions from some changes caused by third parties. Apply the relevant rules to the actual situation before giving buyers an answer.

Decide who receives operational messages after a transfer and who handles the payment inquiry. The recipient needs to know if the event moves or is cancelled. The purchaser may need the refund information connected to their original payment. Make sure neither person assumes the other will receive every update.

Explain the refund route your service actually uses. Don't promise the recipient a refund to their own card if they never paid through that service. Equally, don't invent a universal rule that every transferred ticket must always refund to the original purchaser. Verify the payment arrangement and relevant rights before writing that sentence.

If friends exchanged money privately, tell them that arrangement is separate from your event's payment records. You can explain what your team can confirm and where a refund request belongs. You cannot settle an unseen private payment simply by changing the name on the attendance list.

Give the door team clear authority

Your policy isn't finished until the person scanning tickets can apply it. Give staff the current entry rules, where to check a ticket and who handles disputes. A buyer shouldn't get one answer from your email team and a different answer after travelling to the venue.

On Loopyah, our ticketing page describes QR scanning in the app and check-in access for door staff. That gives the team a defined entry tool without sharing the organizer's login. Agree how the team checks any transfer problem using the current ticket information and the event's policy.

Give ordinary scanning staff a narrow job. They admit valid tickets under the stated entry conditions and send unresolved issues to a named supervisor. They shouldn't approve a disputed holder change because someone has a convincing message thread, or reject a valid gift simply because the purchaser isn't standing beside the recipient.

A supervisor needs an actual decision process. Check the current ticket status, the transfer record available to the team and the published conditions. If two people claim the same place, move the discussion away from the scanning queue. Don't treat the person who shouts louder as having better evidence.

Record any decision that changes admission so another entrance doesn't unknowingly reverse it. Never admit both people against one ticket while the dispute remains unresolved. At the same time, don't label a worried attendee a fraudster because their email invitation failed. Investigate the ticket issue and explain the next step calmly.

Write a policy buyers can read

Put the short explanation beside the ticket information before purchase. Then include the process in confirmation messages and your event FAQ. Buyers should be able to answer whether transfers are allowed, which tickets qualify, when completion is due, what it costs and what the recipient must do.

Keep the wording direct. "You may give an eligible ticket to another person through our official transfer process" tells the buyer what action is allowed. Follow it with the actual instructions and restrictions. A page of legal language followed by a buried contact address doesn't make a routine holder change easy.

For UK consumer contracts, the CMA's unfair contract terms guidance explains the need for fair and transparent terms and notices. Clear wording is part of the work, but wording alone doesn't make an unfair restriction acceptable. Have relevant conditions checked in the jurisdiction where you operate.

Here is sample wording for the hypothetical Saturday event described earlier. "Eligible general admission tickets may be given to another person at no transfer charge. Complete the official transfer by Saturday at noon, venue local time. The recipient must accept before that deadline. Sending the invitation alone does not complete the transfer."

Add the event-specific entry conditions and support route immediately after it. For example, explain any age requirement, whether the recipient needs an account and how to report a missing invitation. Use this as a starting point after confirming your setup, rather than publishing a deadline or free transfer promise your event cannot support.

Make a group booking easy to untangle

Imagine this hypothetical booking. One person buys four general admission tickets for a paid evening event. A friend drops out, and another friend takes that place. The purchaser is still attending, the other two tickets are unchanged, and nobody is asking for money back.

The useful outcome is one replacement attendee with one valid admission. Send the buyer to the official transfer process for the selected ticket if your setup supports it. Explain how the purchaser retains the remaining tickets. Don't tell the entire group to cancel and rebook because one person changed.

Now change the example. The purchaser bought the tickets as gifts and isn't coming at all. Does your policy still work? If your door team expects the paying customer to accompany everyone, those gifts become a problem. Either support the gifts through your chosen process or disclose that named-purchaser restriction before purchase.

A third version involves a business buying conference places for employees. An employee changes jobs before the event. Decide whether the company can substitute another eligible attendee, who can authorize the request and whether personalized extras have closed. The accounts contact and the person attending may need different information.

These cases are worth discussing because buyers don't organize their lives around your order structure. Your rules should handle ordinary purchases without treating them as suspicious. Where a booking really does need special handling, explain the reason and give the buyer a route that reaches the person who can resolve it.

Give support a useful reply

A buyer writes, "I transferred my ticket, but my friend can't see it." Start by checking whether the transfer is pending or accepted. Those states lead to different instructions. Asking the recipient to wait without checking anything may leave them waiting for an action they still need to take.

For a pending email invitation, your reply can explain that the recipient must use the acceptance link and sign in. Ask the sender to check the address through the supported transfer process. Tell them where to recall a pending request if the address is wrong, without promising changes after acceptance.

For a completed transfer, direct the recipient to their current ticket access and investigate the missing ticket through the appropriate support route. Keep the buyer's question attached to the selected admission. Someone who transferred one ticket shouldn't have to explain their whole order each time a different colleague replies.

A late request needs a different answer. State the published deadline and whether your event offers a supported exception. If no exception is available, say so clearly. If a supervisor can consider it, tell the buyer what information is needed and when to expect an answer. Don't imply approval while you investigate.

Use reply templates to cover those common questions, then let staff adapt them to the facts. The person asking wants their friend to get in. Give them the relevant next action rather than repeating the entire policy, without making them chase colleagues.

Test the awkward cases before selling

Run a normal gift first. Have a buyer transfer one eligible ticket, have the recipient accept, and check the result the door team will use. Then check a pending invitation. Your team should understand the difference without needing the buyer to explain the entire sequence.

Next, test a wrong email address before acceptance. Verify how the sender recalls or corrects the pending request through the supported process. Then ask what happens after acceptance. Don't promise a recall after completion when your verified instructions only describe recalling a pending transfer.

Try the ticket types with conditions. Does the replacement qualify for the member rate? Can one ticket leave a group booking? Do a seat and its included extras stay together? Check an accessible-ticket case against the applicable rules. Each answer should agree with the buyer's policy and the event setup.

Finally, rehearse a late request and a cancellation. Who answers the recipient? Who can verify the payment? Where does the door supervisor find the current rule? These cases expose handoffs that an ordinary successful transfer won't show. Fix those gaps before your first real buyer depends on the process.

Improve the rule without moving the goalposts

After the event, review transfer complaints alongside the policy buyers actually saw. Separate missing invitations, missed deadlines, eligibility misunderstandings and entry disputes. A vague total for "transfer issues" won't tell you which condition needs changing. Read the actual requests and identify where people got stuck.

If many ordinary gifts require manual help, first check whether your instructions match the enabled transfer flow. If recipients miss acceptance, make that step clearer. If your cutoff creates avoidable last-minute requests, reconsider the operational reason for it before the next event goes on sale.

Respect the conditions attached to tickets already sold. Don't quietly tighten transfer eligibility because an awkward case annoyed the team. If a genuine problem requires a change, check your obligations, communicate it directly and provide the relevant options. A revised FAQ shouldn't be the first place a buyer discovers their purchase changed.

Fair ticket transfer rules give eligible buyers a workable way to pass admission on. Decide the exceptions, publish the deadline and cost, use the official process, and prepare the door team. Then follow the same policy when the buyer who needs it turns up.