Skip to main content

Journey Overview

Preconditions

  • Member has a valid ticket for an upcoming event
  • Event allows ticket transfers (configurable)
  • Transfer deadline has not passed
  • Ticket has not been used (checked in)

Journey Flow

Detailed Steps

1

Access My Tickets

Member navigates to My Tickets section:
  • View list of upcoming event tickets
  • Identify ticket to transfer
  • Check transfer eligibility
2

Check Transfer Eligibility

System validates transfer is allowed:
3

Enter Recipient Details

Member provides new ticket holder information:Validation:
  • Valid email format
  • Cannot transfer to self
  • Recipient may need to be a member (if member-only event)
4

Review and Confirm

Transfer summary displayed:
Member must acknowledge:
  • Transfer is permanent
  • Original ticket will be voided
  • They will lose access to the event
5

Process Transfer

System processes transfer:
  1. Original ticket marked as “Transferred”
  2. Original QR code invalidated
  3. New ticket record created for recipient
  4. New QR code generated
  5. Audit trail recorded
6

Notifications Sent

To Original Holder:
  • Confirmation of transfer
  • Receipt for records
  • Note that they can no longer attend
To Recipient:
  • Welcome message with event details
  • New ticket with QR code
  • Registration instructions (if account needed)
  • Calendar invite

Transfer Restrictions

Organizations can configure:

Transfer Types

Standard Transfer

  • Ownership changes completely
  • Original holder loses all access
  • Recipient becomes new owner

Name Change Only

  • Original holder remains owner
  • Attendee name updated for check-in
  • May have different approval process

Gift Ticket

  • Same as transfer but framed as gift
  • Personal message option
  • Gift-themed notification

Non-Member Recipients

If event allows non-member recipients:
  1. Recipient receives ticket without account
  2. Can access ticket via emailed link
  3. Prompted to create account (optional)
  4. No portal access for ticket management
If event requires membership:
  1. Recipient must be existing member, OR
  2. Recipient must register as member first
  3. Transfer fails if recipient ineligible

Transfer Fees

If transfer fee configured:

Acceptance Criteria

Frontend

  • Transfer button on eligible tickets
  • Recipient details form
  • Transfer confirmation modal
  • Disabled state for ineligible tickets
  • Error messages for validation failures
  • Success confirmation page
  • Transfer history visible

Backend

  • POST /api/tickets/{id}/transfer - Initiate transfer
  • GET /api/tickets/{id}/transfer-eligibility - Check eligibility
  • Original ticket invalidation
  • New ticket generation
  • Email notifications (both parties)

Permissions

  • Only ticket owner can transfer
  • Admin can transfer on behalf (support)

Business Rules

  • Transfer deadline enforced
  • Transfer limits tracked
  • Fee charged if configured
  • Audit trail maintained
  • Member-only events validate recipient

Error Handling

  • Clear message if transfers not allowed
  • Deadline passed notification
  • Recipient validation errors
  • Payment failure handling (if fee)