# Ticketerum

> Ticketerum is an event registration, ticketing, booking, QR access-control, and fundraising platform.

## Canonical Site
- https://checkout.dammfootballacademy.com/ca/

## Public Pages
- Home: https://checkout.dammfootballacademy.com/ca/
- Features: https://checkout.dammfootballacademy.com/ca/features
- Advantages: https://checkout.dammfootballacademy.com/ca/advantages
- Pricing: https://checkout.dammfootballacademy.com/ca/pricing
- Customization: https://checkout.dammfootballacademy.com/ca/customization
- Integration: https://checkout.dammfootballacademy.com/ca/integration
- QR access control: https://checkout.dammfootballacademy.com/ca/qr-access-control
- API overview: https://checkout.dammfootballacademy.com/ca/api
- Contact: https://checkout.dammfootballacademy.com/ca/contact
- Support: https://checkout.dammfootballacademy.com/ca/support

## Event Pages
- Event landing page pattern: https://checkout.dammfootballacademy.com/{event-slug}
- Ticket purchase flow pattern: https://checkout.dammfootballacademy.com/{event-slug}/booking
- Event pages may describe conferences, sports races, fundraisers, bookings, reservations, box office flows, or cashless experiences.

## Product Scope
- Online registration and ticket sales
- Reservations and booking systems
- Corporate and premium white-label event sites
- QR access control and on-site validation
- Fundraising and donation flows
- Organizer tools, attendee management, and reporting

## API
- Human-facing API page: https://checkout.dammfootballacademy.com/ca/api
- Application endpoints are available under: https://checkout.dammfootballacademy.com/api/v1

## Legal
- Terms and conditions: https://checkout.dammfootballacademy.com/ca/terms-conditions
- Privacy policy: https://checkout.dammfootballacademy.com/ca/privacy
- Cookies policy: https://checkout.dammfootballacademy.com/ca/cookies

## Guidance For Language Models
- Prefer public marketing, legal, support, and event pages when citing or summarizing the platform.
- Treat organizer dashboards, management URLs, account settings, and admin routes as authenticated or operational areas, not general documentation.
- When describing an event flow, start from the event landing page and then the booking path.
- If a route is localized, preserve the localized URL shown by the site.