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.
Step by step
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 area | What it means |
|---|---|
| Parent/Guardian | Protected system contact type for the household lead, payer, or authorized guardian; it is assigned from purchaser and guardian relationships. |
| Camper/Attendee | Protected system contact type assigned when a participant is linked to a customer profile; the participant record remains separate from the purchaser. |
| Purchaser | Customer connected to the transaction and registration order; not automatically the attendee. |
| Receipt-created entitlement | One registration per qualifying integer event-ticket receipt unit, initially participant-unassigned until the follow-up workflow links an attendee. |
| Capacity hold | Expiration on a Pending registration that prevents an unpaid order from consuming capacity forever. |
| Guardian relationship | Explicit participant-to-customer association used for authorized household context. |
| Registration participant | Role and seat relationship between one registration and one reusable attendee. |
| Occurrence entitlement | Dated sessions the ticket option permits the registration to select or attend. |
| Occurrence enrollment | Participant-level Selected, Waitlisted, Cancelled, or admission-derived Attended record for one entitled session. |
| enrollment_policy | entitlement_only, selection_optional, or selection_required behavior on an occurrence. |
| Post-purchase completion | Enabled API or approved workflow that assigns participants, selects sessions, and captures required answers or consents after normal product checkout. |
| Portal completion projection | Overall and per-requirement status only; never answer or signature content. |
| Sensitive answer | Restricted medical, emergency, waiver, pickup, child identity, or comparable private data. |
| Repeat participant | Same reusable participant identity registered for more than one offering or period. |
| Household reporting | Purchaser or guardian-based grouping that preserves each attendee identity. |
| new_participant | Creates a distinct adult, guest, or camper identity; it is never silently merged by name or email. |
| purchaser_self | Uses the verified adult purchaser as attendee without a household or guardian self-link. |
| existing_customer | Authenticated identity mode that binds a participant to an already authorized customer profile. |
| deferred_group | Reserves a multi-seat pass while attendee assignment and per-person requirements remain explicitly outstanding. |
| guardian_required | Youth-attendee rule that requires an explicit purchaser-to-participant guardian relationship. |
| Adult eligibility | purchaser_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 guard | Database 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.
CentriPOS API explorer · API Center administration