> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# How do ticket transfers work?

> Understand how ticket transfers differ from forwarding a PDF, resale and name changes.

**A ticket transfer reassigns an admission entitlement from one holder to another.** In a controlled transfer, the ticketing system records the new holder and determines whether the original credential must be revoked or replaced. Simply forwarding a PDF or screenshot may leave both parties with a copy of the same scannable code.

## What happens in a controlled transfer?

A typical process is: (1) an authorised holder chooses an eligible ticket; (2) the platform checks restrictions and deadline; (3) an invitation or claim link is issued; (4) the recipient accepts, where required; (5) the system updates entitlement ownership and credential validity; and (6) both parties receive a clear status update. Some platforms support transfer at checkout as well as after purchase.

| State                | Operational question                                 |
| -------------------- | ---------------------------------------------------- |
| **Transfer offered** | Can the sender revoke the invitation?                |
| **Pending claim**    | Who can still enter while transfer is pending?       |
| **Accepted**         | Is the old barcode invalidated immediately?          |
| **Reversed**         | Can the system restore the original holder securely? |
| **Already scanned**  | Should further transfer be blocked?                  |

These answers depend on event rules. They should be explicit, not inferred from an email stating 'ticket sent'.

## What restrictions are common?

Restrictions might include transfer cut-off times, named-ticket verification, minimum age, accessible seating, hospitality packages, payment-plan status or orders undergoing dispute. Identity checks should be proportionate to the legitimate access requirement, rather than applied to every event by default.

Transfers need a clear record of **buyer, original holder, current holder and ticket history**, because customer service and access-control teams may need different information. Privacy controls should determine which personal details are visible to each person.

## How is transfer different from resale?

Transfer normally reassigns a valid ticket without creating a new commercial sale. Resale involves a new transaction and may trigger price caps, refunds to the seller, fees and a replacement ticket. An organiser may permit gifting but prohibit resale, or allow both through different channels. These differences matter for accounting and the official admission list.

## What should operators test?

Test a transferred ticket at an online scanner and an offline device, then try the previous barcode. Also test transfer reversal, duplicate invitations, a late transfer close to doors and a ticket already checked in. The **source of truth for validity** must remain consistent when devices reconnect.

## Related explanations

#### [What is official ticket resale?](/distribution-access/what-is-official-ticket-resale)

Distribution & Access · Transfers and resale

#### [What happens to ticket validity after a transfer or resale?](/distribution-access/what-happens-to-ticket-validity-after-a-transfer-or-resale)

Distribution & Access · Transfers and resale

#### [How do offline ticket scanners work?](/distribution-access/how-do-offline-ticket-scanners-work)

Distribution & Access · Entry and access control

[More in Distribution & Access →](/distribution-access)