User guide

Public · no account

Buyers

You do not need an account to buy, find a ticket, request a refund, or make a “I’ll be there” poster.

Buy a ticket

1. Open 237tickets.com and pick an on-sale event, or follow the organizer link (237tickets.com/t/…).
2. Under “Choose your tickets”, set quantities per type.
3. Fill in each attendee: name, email, WhatsApp phone.
4. Pay with MTN, Orange, Wave, or card / PayPal when offered. Confirm on your phone for Mobile Money.
5. If the ticket is 0 XAF, tap “Get my free tickets” — no payment.
6. You land on confirmation, then your QR ticket. Email is sent (WhatsApp too when offered).

A pending order expires after about 10 minutes. Do not double-tap Pay: wait for the confirmation SMS.

View, share, transfer

• Open 237tickets.com/ticket/YOUR-CODE for QR, PDF, print.
• Lost the link: “My tickets” → email or phone used at checkout → 6-digit code.
• Transfer: change the holder name (max 3 times), unless already scanned at the door.
• WhatsApp share or resend email from the ticket page.

Refunds

• Refund page or the button on the ticket: submit a request with the code.
• The organizer contacts you. There is no automatic platform refund.

I’ll be there

1. On the event page, “Make my poster”, or 237tickets.com/je-serai-la.
2. Add your photo (it stays on your phone — not uploaded to our servers).
3. Name + phone, generate, download or share.
4. The ticket link is on the poster so friends buy in the same place.

Sold out / waitlist

If it is sold out, join the waitlist. The organizer can notify you when seats free up.

Approved organizer account

Event owners

Once your account is approved, you create the event, sell, get paid, and run the door. Dashboard: 237tickets.com/login.

Open an account

1. Create an account: name, email, WhatsApp, password.
2. Fill in the unique questionnaire link we email you.
3. 237tickets reviews the account. Login is blocked while status is pending.
4. After approval, sign in → Dashboard.

Put an event on sale

1. New event: title, venue, dates, ticketing slug (e.g. /t/my-show).
2. It starts as a draft — hidden from the public.
3. Add a cover, description, FAQ / lineup if needed.
4. Create ticket types: name, XAF price, stock. Price 0 = free for the buyer.
5. Set status to Live. Share /t/your-slug.
6. Closed = no more sales. Draft = off the homepage.

A free ticket bought on the public checkout (0 XAF) costs the organizer 100 XAF per ticket, owed to 237tickets. Complimentary invitations you send yourself (Growth tools) are not billed that way.

On the day and after

• Check-in: /checkin/your-slug — PIN from the event sheet (skipped if you are logged in as organizer).
• Door scanners: create profiles, copy the token once, give /checkin/scan to staff.
• Guests & tickets, CSV export, scan log, sales stats.
• Ticket designer for the PDF / QR look.
• I’ll-be-there poster: place the photo slot for guests.
• Ticket email template (PDFs are always attached).
• Promos, affiliates (?ref=), invitations, waitlist: Growth tools.
• Payouts: request a withdrawal (minimum 1,000 XAF). Mobile Money fees apply.
• Refunds: handle buyer requests (not automatic).

API and webhooks (partners)

• On the event page, Event API: create a key limited to this event.
• API key and HMAC webhook secret are shown once — copy them immediately.
• Paste the partner HTTPS webhook URL and save.
• order.paid fires only when the buyer paid through the partner checkout link (?partner=…).
• Direct 237tickets.com purchases without that parameter, and complimentary invites, do not notify.
• Technical docs: 237tickets.com/developers.

Team

Invite colleagues (admin, finance, check-in, marketing) from the event or settings. They join via the email link.

Staff · organizer token

Door scanners

Two ways to check people in: the event check-in page (PIN) or the scanner portal (token, including offline).

Mode A — Event check-in

1. Open 237tickets.com/checkin/your-slug (organizer sends the link).
2. Enter the check-in PIN if asked.
3. Scan the QR on the phone / PDF, or type the ticket code.
4. Green = OK. Already scanned = denied. Offline scans queue and sync when the network is back.

Mode B — Scanner portal (best offline)

1. Organizer creates a scanner (Dashboard → Scanners, or the event page).
2. They copy the token once and the /checkin/scan URL.
3. Paste the token, pick the event.
4. Download the guest list (stored on the phone in IndexedDB — then you can go offline).
5. Scan. Sync happens when the network returns.
6. Search a guest by name offline, and open the guest-list PDF.

If the list is stale (new sales), the organizer taps force-reload / sync. A scanned QR cannot be reused. Name transfer is blocked after the first scan.

The ticket QR may open a short /s/CODE link that pre-fills check-in.

role admin

Platform admins

Admins see the whole platform: organizers, events, money, partner APIs. Open Dashboard → Admin (237tickets.com/dashboard/admin).

Organizers

1. Pending queue: This week / Older / Parked.
2. Read the questionnaire, adjust commission % if needed, Approve or Reject.
3. Park hides a request from today’s queue without deciding.
4. You can re-send the questionnaire email if the plan is too vague.

Events

• Force draft / live / closed, suspend (public sale blocked, organizer limited).
• Commission % and per-ticket flat fee, link a contract.
• Buyer export (paid orders, not complimentary invites).

Money

• Billing: takings, organizer share, 237tickets share, admin Tara withdrawals.
• Organizer payout requests: approve, note, pay.
• Contracts: rates, files, attach to events.

Ops

• Partner API (platform keys, webhook URL, rotate key/secret).
• Webhook log (partners, Tara, Stripe).
• Audience: visits, clicks, devices.
• Global search: tickets, orders, users, events.

A webhook secret or API key is shown once. Never paste them in a group email. Partner webhooks do not fan out every sale on an event — only checkouts attributed to that key.