A customer buys a ticket six months before an event. Then something changes. They cannot attend, but a friend can. Or a colleague. Or someone who was waiting for a ticket to become available. For the customer, the solution seems obvious: send the ticket to someone else. For the organiser, it is more complicated.
Who is now attending? Is the original ticket still valid? Has the ticket actually been transferred, or has someone simply forwarded a screenshot? What happens if the original buyer requests a refund? What will the scanner show at the entrance?
A good transfer system makes changing the attendee easy without losing control of the ticket.
Decide What a Transfer Actually Means
The first step is to define what changes when a ticket is transferred. The attendee may change while the original purchase remains exactly the same.
For example, Sarah buys a £60 ticket and later transfers it to James. James becomes the person attending, but that does not automatically mean that Sarah's original transaction disappears or that James needs to purchase another ticket. This distinction is important because a ticket, an order and an attendee are different pieces of information.
The order records the transaction. The ticket represents the entitlement to attend. The attendee is the person who will use that entitlement. A well-structured system keeps these relationships separate.
Changing who attends should not automatically mean changing what was purchased.
Keep the Transfer Inside the Ticketing System
The easiest way to lose control is to let customers manage transfers entirely through screenshots, forwarded emails or private messages.
The organiser may never know that the ticket changed hands. The original customer might still appear as the attendee. The new customer might arrive with an outdated ticket. Two people might even present the same ticket.
A controlled transfer process avoids these problems by keeping the change attached to the ticket record.
The customer requests the transfer. The recipient receives an invitation. The transfer is accepted. The system updates the ticket information or issues a new credential, depending on how the platform works.
The exact technical method can vary. The important thing is that the organiser's system remains the source of truth. This also gives the organiser a reliable history of what happened to the ticket.
Make Sure the Original Ticket Cannot Be Used Twice
This is one of the most important security considerations.
If a ticket is successfully transferred, the original holder should not retain a separate, independently valid version of the same entitlement.
Depending on the ticketing system, this might mean invalidating the original ticket and issuing a new one, or updating the existing ticket record so that only the current credential is valid. The technical implementation is different across platforms.
The principle is the same: One ticket should not become two valid admissions simply because someone changed hands.
This is also why screenshots are a poor substitute for controlled transfers. An image can be copied indefinitely. A properly managed ticket record cannot legitimately represent multiple admissions at the same time.
Set Transfer Rules That Match the Event
Not every ticket needs to be transferable in the same way.
A general-admission event may allow straightforward transfers. A personalised event may require the attendee's details to be updated. A premium ticket may include benefits that are restricted to the original purchaser.
Some events may prohibit transfers altogether under their terms. Others may allow transfers only until a certain point before the event. There is no universal rule.
The correct policy depends on the event, ticket type, venue requirements, security considerations and applicable terms and law.
Whatever rules you choose, tell customers before they buy.
For example, a 2026 event policy published by Active Travel England allows transfers within the same organisation but requires attendee details, including access and dietary information, to be updated before the event.
A transfer policy should reflect the operational reality of the event, not simply what the ticketing software happens to allow.
Do Not Confuse Transfers With Resale
These processes can look similar but have different purposes.
A transfer changes who will use the ticket. A resale involves selling the ticket to another customer. The distinction matters financially and operationally.
If Sarah gives her ticket to James, there may be no new sale. If Sarah sells her ticket to James through an authorised resale process, there may be a new transaction, different payment arrangements and potentially different rules around pricing and fees.
In the UK, secondary ticketing is subject to specific consumer-protection requirements, including rules concerning information that must be provided when tickets are resold.
Organisers should therefore avoid treating every transfer as a resale, or every resale as a simple transfer. The person using the ticket can change without the money changing hands, and the money can change hands without the underlying ticket becoming a completely new entitlement.
Keep the Entrance in Sync
A transfer is not operationally complete if the entrance team still sees yesterday's information.
Suppose a ticket was transferred successfully, but the scanning system has not received the update. The new attendee arrives. Their ticket fails. The customer now has a problem that was created by the organiser's systems rather than by the customer. That is why ticket transfers need to flow through to every system involved in admission.
If the event checks names, the relevant attendee information needs to be current. If entry is based entirely on ticket validation, the current ticket status needs to be available to the scanner. If additional access rights are attached to the ticket, those should update as well. The transfer is only finished when every part of the event system recognises the new state of the ticket.
Keep the Financial Record Separate
A transfer does not automatically create a refund. This is an important distinction.
If a customer transfers a ticket to a friend, the original purchase may remain intact. If the organiser operates a resale marketplace, the original ticket may instead be cancelled or adjusted and a new transaction created. These are different financial events and should be recorded separately.
This separation also makes reporting much more accurate. You can see how many tickets were transferred without incorrectly treating every transfer as a new sale or refund.
The cleanest systems separate who bought the ticket, who holds it now and how the money moved.
Protect Customers From Transfer Scams
Official transfer systems do more than help organisers. They also make it harder for customers to be deceived.
Ticket scams often exploit situations where customers are desperate to obtain tickets, particularly for high-demand events. UK government guidance continues to advise consumers to use official ticketing channels and warns against moving payments away from recognised platforms.
That means organisers should make the legitimate transfer process obvious. Tell customers where transfers are completed. Explain whether official resale is available. Make it clear whether payment is involved. Do not force customers to arrange transfers through private messages when the system can provide a controlled alternative.
A clear official process protects both the organiser and the customer.
Frequently Asked Questions
Q: Should every event allow ticket transfers?
A: No. Transferability should depend on the event, ticket type, security requirements, venue arrangements and applicable terms. Some events may need personalised or restricted tickets.
Q: Does transferring a ticket mean the original buyer should receive a refund?
A: Not necessarily. A transfer can change the attendee while leaving the original purchase intact. Refunds and transfers should be treated as separate processes unless the organiser's terms specify otherwise.
Q: Is sending a screenshot an acceptable way to transfer a ticket?
A: It is difficult to control securely because screenshots can be copied and forwarded. A transfer managed through the ticketing system gives the organiser much better visibility over who is authorised to use the ticket.
Q: Should the ticket number change after a transfer?
A: There is no universal technical requirement. Some systems issue a new credential, while others update the existing ticket record. What matters is that the system does not leave two independently valid versions of the same admission entitlement.
Q: How late should customers be allowed to transfer tickets?
A: There is no single correct deadline. The cutoff should reflect your operational needs, such as identity checks, access-control systems and the time required for changes to reach the entrance system. Whatever deadline you choose should be communicated clearly before purchase.
If you need additional advice or support, the TicketCRM team is always ready to help with your questions!