Ticket credentials and check-in records are operational evidence. Check-ins are append-only: a mistake is corrected with a Void input that produces new audit evidence, not by editing or deleting the original scan. Capacity and registration state are validated again during admission.

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 Events → Registrations and confirm the offering, registration number, purchaser, assigned participant, ticket option, occurrence itinerary, seat count, receipt state, requirement completion, and registration status. A receipt-created entitlement can remain unassigned until the post-purchase participant workflow is complete.
  2. A confirmed group registration can hold pending_assignment tickets while seats remain unassigned. pending_assignment is non-admissible and exposes no code or QR. Assign a participant through the authoritative seat/transfer flow; only a participant-bound, unexpired Valid or Used ticket projects an active credential to an authorized viewer. Voided, Transferred, Expired, and pending history remains visible without a credential.
  3. Use Events → Waitlist to review Waiting and Offered demand. Offer next spot calls the server's atomic queue command; use the documented row lifecycle actions for manual cancellation, priority, and acceptance changes.
  4. Offer next is atomic. The service requeues expired offers, evaluates currently available linked capacity, locks eligible rows, and claims one entry by priority and queue position. Concurrent callers cannot offer the same row. Never imitate this behavior with a client-side sort followed by a normal update.
  5. An Offered entry has an expiration and capacity reservation. Accepted points to the resulting registration; Expired, Cancelled, and superseded records remain reportable history. Use the documented waitlist operations for lifecycle changes rather than bypassing another attendee with an unrelated confirmed registration.
  6. Open Events → Check-in and choose the exact offering or occurrence context. Confirm local time, venue, active station, and whether the action is In, Out, or Void. Roster/manual admission sends exact ticket_id plus participant_id and fails closed when a duplicate name, group, or registration search is ambiguous; scanners may alternatively submit one authorized credential.
  7. Submit only the documented check-in input. The atomic admission service locks the registration and ticket, validates participant and occurrence entitlement plus lifecycle state, derives Accepted, Denied, Duplicate, or Voided, and updates accepted ticket and registration state in the same transaction. The caller cannot supply its own result, actor, denial reason, or audit metadata.
  8. Use events:attendance:write for check-in creation and events:attendance:read for attendance records. Keep events:credentials:read/write for scan credentials and events:registrations:read/write for registration lifecycle. A manual override is not an unrestricted success flag; it requires events:attendance:override, an explicit reason, and server-recorded evidence.
  9. For check-out, submit an Out direction. To correct an erroneous attendance action, submit Void with its required operational reason. Never PATCH or DELETE the original evidence; the current API intentionally exposes check-in list, create, and get operations only.
  10. For an offline scanner, persist each attempt locally with the exact offering, registration, ticket and participant context, occurrence_instance_id when applicable, device_id, capture time, and a stable client_scan_id. POST 1–500 attempts to /events/{event_id}/checkins/batch. HTTP 200 is intentionally partial: each item returns an explicit accepted or denied safe checkin result, or an error, and a denied row never rolls back accepted peers. Batch output strips credentials and denial detail.
  11. Reuse the same Idempotency-Key for a retry of the same single-scan or batch request. Within an offline batch, keep the same device_id and client_scan_id for a retry of one physical scan; changing that scan body under the same stable identity conflicts. This protects arrivals after a timeout without suppressing a genuinely separate later action.
  12. After the occurrence, reconcile confirmed seats, issued tickets, accepted entries, unique participants, no-shows, check-outs, denials, duplicates, void corrections, and waitlist conversion. Do not place ticket codes or protected registration answers in routine reports, webhook consumers, or CRM fields.
  13. A single denied or duplicate admission is still committed as append-only evidence and then returns 409 event_admission_not_accepted. The error includes only safe evidence identifiers, direction, result, admitted quantity, and time—never a credential, denial reason, actor, device, or arbitrary metadata.
  14. For a credential-based offline scan, request identity binds a one-way credential digest rather than the raw credential. Retries remain idempotent without putting a reusable ticket secret into request-hash evidence or logs.
  15. Use the camera-first scanner on a registered device. Download its bounded device manifest while online, then scan into the encrypted local queue when connectivity is unavailable. Reconnect and synchronize in batches of at most 500; server admission remains authoritative and the device retires or refreshes its manifest on the documented lifecycle.
  16. PDF tickets are branded on demand. Enable Apple Wallet or Google Wallet only after a manager chooses Check readiness in the tenant’s own isolated data plane. Apple readiness builds and signs a real pass; Google readiness signs with the project-local service account, exchanges an OAuth token, and reads the exact configured event-ticket class from the Google Wallet API. The browser cannot mark a provider Ready and a master-project secret is never accepted as a substitute for tenant-project credentials.
  17. Provision Apple Wallet only through the tenant project secret manager with APPLE_WALLET_PASS_TYPE_IDENTIFIER, APPLE_WALLET_TEAM_IDENTIFIER, APPLE_WALLET_WWDR_PEM, APPLE_WALLET_SIGNER_CERT_PEM, APPLE_WALLET_SIGNER_KEY_PEM, and optional APPLE_WALLET_SIGNER_KEY_PASSPHRASE. Provision Google Wallet with GOOGLE_WALLET_ISSUER_ID, GOOGLE_WALLET_CLIENT_EMAIL, and GOOGLE_WALLET_PRIVATE_KEY_PEM. Never paste any value into the settings screen, documentation, logs, browser storage, or a support ticket.
  18. Enter the full existing Google EventTicketClass ID as issuer ID plus class suffix, such as 3388.event_admission. The class must belong to the configured issuer, be readable by the tenant service account, and have UNDER_REVIEW or APPROVED status. Save-to-Wallet tokens reference that exact verified class and never create a substitute class from an offering ID.
  19. The manager-authenticated readiness broker resolves the exact active tenant data plane and invokes its service-only readiness probe. Recheck after provider identifiers or tenant-plane credentials change; a failed probe stores only safe provider state and diagnostics, never private key or certificate material.

Screen and contract reference

Control or areaWhat it means
Ticket code / QRActive admission credential returned only with events:credentials:read for a participant-bound, unexpired Valid or Used ticket.
Credential omissionRoutine registration-read ticket projections omit ticket_code and mark credential_fields_omitted.
Pending assignment / Valid / Used / Voided / Transferred / ExpiredExact ticket lifecycle. Pending assignment is unassigned and non-admissible; only eligible Valid or Used tickets have an active credential.
Waitlist positionStable queue order evaluated after priority.
Offer nextAtomic expiry cleanup, capacity reservation, and one-row claim; safe under concurrent callers.
Offer expirationDeadline for converting an Offered entry into an accepted registration.
Check-in directionIn, Out, or Void attendance input.
Accepted / Denied / Duplicate / VoidedServer-derived result recorded for an attendance attempt.
events:attendance:readAttendance evidence only; it never grants ticket-code or QR credential access.
events:attendance:writeAtomic check-in creation permission.
Append-onlyOriginal check-in cannot be edited or deleted; correction creates Void evidence.
Offline check-in batchOne to 500 attempts under a device ID; HTTP 200 may contain accepted, denied, and error outcomes independently without credential or denial detail.
client_scan_idStable 8–160 character scanner identity reused with the same device for retries of one physical attempt.
Idempotency-KeyTop-level retry identity that prevents one single-scan or batch request from becoming duplicate writes.
events:credentials:readLists or retrieves an operational event ticket credential.
events:credentials:writeIssues, updates, or revokes a ticket credential; it is not an attendance permission.
event_admission_not_acceptedSafe 409 returned after denied or duplicate evidence is committed; inspect authorized staff evidence separately for operational detail.
Credential digestOne-way value included in offline scanner request identity so retries bind the credential without retaining the raw scan secret.
Camera-first scannerRegistered-device QR capture with an encrypted offline queue and bounded server synchronization.
Check readinessManager-only action that validates wallet signing inside the exact tenant data plane before a provider can be enabled.
Google EventTicketClass IDFull issuer-qualified class ID verified through the Google Wallet API and reused by generated save tokens.
Wallet provider secretsTenant-project-only Apple certificate/key and Google issuer/service-account values; never client-readable or stored in delivery settings.
PDF ticketBranded on-demand document available without an external wallet provider.

Expected result

Valid tickets reach only the authorized participant or household, waitlist offers follow the approved queue and capacity, and every entry, exit, denial, duplicate, or correction is represented by immutable attendance evidence.

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.