A registration is the paid or reserved entitlement; a participant is the person attending; and the purchaser is the customer who owns the transaction. Adult self-registration, another adult attendee, a youth camper with an authorized guardian, an existing verified customer, and a deferred group pass are distinct identity modes and must never be collapsed by matching only a typed name or email.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. Open Contacts and search for the household lead before creating a duplicate. CentriPOS provisions the protected Parent/Guardian and Camper/Attendee contact types. Household authority, participant identity, and purchaser ownership remain separate even when one person fills several roles.
  2. From a published event feed, choose an option whose checkout_status is ready. The branded storefront revalidates the event_ticket product, sale window, remaining capacity, form and waiver definitions, session choices, add-ons, and ticket quantity before it creates a quote.
  3. For each one-seat ticket unit, choose Another attendee or This ticket is for me. Another attendee creates a distinct adult, guest, or camper profile. This ticket is for me binds the attendee to the verified purchaser customer and never creates a self-guardian link. When the offering has an age policy, birth date is required; when supplied in any case, the purchaser must be at least 216 months old on the first scheduled eligibility date.
  4. For a minor, enter the attendee birth date and purchaser relationship. Checkout records an explicit authorized guardian association so the purchaser can manage that camper registration. It does not infer guardianship from a shared surname, email, address, or payment method.
  5. Anonymous checkout never searches or exposes customer records. Reusing an existing participant_customer_id is restricted to an authenticated, tenant-authorized staff, portal, or API workflow that can prove access to that customer; integrations must not merge adults by email or name alone.
  6. A multi-seat option must use deferred_allowed. Checkout creates a deferred group entitlement and reserves the documented seat count without fabricating participant profiles. The organizer later assigns every attendee and completes required questions, waivers, add-ons, and session selections by the assignment deadline.
  7. Complete every required purchaser-, registration-, and participant-scoped question. Standard answers with an approved report_key can become report dimensions. Medical, accessibility, emergency, pickup, birth-date, signature, and similarly protected values remain sensitive and require dedicated authorization.
  8. Accept each assigned versioned waiver using the displayed content hash and signer name. The immutable acceptance preserves which version was shown; it is not copied into general CRM fields, public feeds, normal reports, or event webhooks.
  9. Choose participant sessions only from the ticket option’s entitled concrete agenda. Selection groups enforce their minimum, maximum, and overlap policy; recurring choices retain occurrence_instance_id so a class date cannot drift to another occurrence.
  10. Choose participant add-ons by product, variant, and quantity. Checkout adds the aggregate products to the sale and retains participant-level assignments so shirts, take-home robots, kits, lunches, parking, or other items reconcile to receipt units and returns.
  11. The quote stores short-lived, tamper-evident registration intents. Final checkout atomically binds the purchaser, receipt line and unit, registration, participant or deferred identity, answers, waiver evidence, session selections, add-on assignments, capacity, and ticket lifecycle. A mismatched or expired intent fails closed.
  12. Pending or partially paid sales hold capacity only until capacity_hold_expires_at and do not expose an active credential. Completed paid/closed sales confirm and issue tickets. Returns, voids, refunds, quantity reductions, cancellations, and expired holds reverse only their matching entitlements.
  13. Use the authorized customer portal and staff roster to review purchaser, guardian, participant, repeat-attendee, requirement-completion, schedule, asset, receipt, and ticket state. Use separate report dimensions for siblings, repeat campers, adult self-attendees, group passes, and purchasers.
  14. Treat receipt-backed purchaser ownership, ticket entitlement, sale and line identity, seat count, amount, and currency as guarded snapshots. Change them only through the source receipt or authoritative registration workflow; the database rejects a generic registration update that could detach financial or entitlement history.

Screen and contract reference

Control or areaWhat it means
Parent/GuardianProtected system contact type for the household lead, payer, or authorized guardian; it is assigned from purchaser and guardian relationships.
Camper/AttendeeProtected system contact type assigned when a participant is linked to a customer profile; the participant record remains separate from the purchaser.
PurchaserCustomer connected to the transaction and registration order; not automatically the attendee.
Receipt-created entitlementOne registration per qualifying integer event-ticket receipt unit, initially participant-unassigned until the follow-up workflow links an attendee.
Capacity holdExpiration on a Pending registration that prevents an unpaid order from consuming capacity forever.
Guardian relationshipExplicit participant-to-customer association used for authorized household context.
Registration participantRole and seat relationship between one registration and one reusable attendee.
Occurrence entitlementDated sessions the ticket option permits the registration to select or attend.
Occurrence enrollmentParticipant-level Selected, Waitlisted, Cancelled, or admission-derived Attended record for one entitled session.
enrollment_policyentitlement_only, selection_optional, or selection_required behavior on an occurrence.
Post-purchase completionEnabled API or approved workflow that assigns participants, selects sessions, and captures required answers or consents after normal product checkout.
Portal completion projectionOverall and per-requirement status only; never answer or signature content.
Sensitive answerRestricted medical, emergency, waiver, pickup, child identity, or comparable private data.
Repeat participantSame reusable participant identity registered for more than one offering or period.
Household reportingPurchaser or guardian-based grouping that preserves each attendee identity.
new_participantCreates a distinct adult, guest, or camper identity; it is never silently merged by name or email.
purchaser_selfUses the verified adult purchaser as attendee without a household or guardian self-link.
existing_customerAuthenticated identity mode that binds a participant to an already authorized customer profile.
deferred_groupReserves a multi-seat pass while attendee assignment and per-person requirements remain explicitly outstanding.
guardian_requiredYouth-attendee rule that requires an explicit purchaser-to-participant guardian relationship.
Adult eligibilitypurchaser_self must be at least 216 months old at the first scheduled eligibility date when a birth date is supplied; an offering age policy makes birth date required.
Receipt-backed guardDatabase protection against generic rewrites of purchaser, entitlement, receipt identity, seats, amount, or currency.

Expected result

Each receipt-backed registration is attached to the correct purchaser, reusable participant, guardian relationship, ticket option, seat count, answers, and lifecycle state, so repeat-attendee and household reporting works without exposing protected data.

Troubleshooting

  • Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
  • Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
  • Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.