Documentation Index
Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Journey Overview
| Attribute | Value |
|---|---|
| Journey ID | UJ-M-010 |
| Actor | Ticket holder |
| Goal | Transfer ticket ownership to another person |
| Trigger | Member cannot attend and wants to give ticket to someone else |
| Outcome | New recipient has valid ticket for the event |
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
Access My Tickets
Member navigates to My Tickets section:
- View list of upcoming event tickets
- Identify ticket to transfer
- Check transfer eligibility
Check Transfer Eligibility
System validates transfer is allowed:
| Check | Requirement |
|---|---|
| Event allows transfers | Configured by organizer |
| Transfer deadline | Before event or cutoff date |
| Ticket not used | Not checked in |
| Not already transferred | Original holder only |
| Transfer limit | Within allowed number |
Enter Recipient Details
Member provides new ticket holder information:
Validation:
| Field | Required | Notes |
|---|---|---|
| Recipient Email | Yes | New ticket sent here |
| Recipient First Name | Yes | For new ticket |
| Recipient Last Name | Yes | For new ticket |
| Recipient Phone | Configurable | For event communications |
| Personal Message | No | Included in notification |
- Valid email format
- Cannot transfer to self
- Recipient may need to be a member (if member-only event)
Review and Confirm
Transfer summary displayed:Member must acknowledge:
- Transfer is permanent
- Original ticket will be voided
- They will lose access to the event
Process Transfer
System processes transfer:
- Original ticket marked as “Transferred”
- Original QR code invalidated
- New ticket record created for recipient
- New QR code generated
- Audit trail recorded
Transfer Restrictions
Organizations can configure:| Setting | Options |
|---|---|
| Transfers allowed | Yes/No |
| Transfer deadline | X days before event |
| Transfer fee | None, fixed, or percentage |
| Max transfers per ticket | 1, 2, unlimited |
| Recipient must be member | Yes/No |
| Requires approval | Yes/No |
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:- Recipient receives ticket without account
- Can access ticket via emailed link
- Prompted to create account (optional)
- No portal access for ticket management
- Recipient must be existing member, OR
- Recipient must register as member first
- Transfer fails if recipient ineligible
Transfer Fees
If transfer fee configured:Related Entities
Related Journeys
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)