This site uses cookies for analytics and to improve your experience. By clicking Accept, you consent to our use of cookies. Learn more in our privacy policy.

You are on HappenBoard documentation. Go back to main site

Selling tickets on the event page

Available in:Pro

The Ticket Picker block shows an event’s tickets on its page. Visitors choose how many they want, enter their details, then pay on Stripe’s secure page. Free tickets are booked straight away.

The Ticket Picker needs HappenBoard Pro. See what Pro adds.

Where the Ticket Picker appears

You do not have to place it. On an event with at least one ticket type, free or paid, the RSVP form of the single event template is replaced by the Ticket Picker. The RSVP form also stops taking sign-ups for that event.

To choose where the tickets appear, add the Ticket Picker block yourself, in the event’s content or in the single event template. Building a single event page shows both ways. The RSVP form then shows a short line instead: “This is a ticketed event: book a ticket to attend.” Tickets are never offered twice.

In the editor, the block previews the event’s real tickets. In the Site Editor’s template, where there is no event yet, it shows a placeholder.

The block has colour, spacing and typography settings. Its button uses your theme’s button style, so it looks like the other buttons on your site.

What buyers see

The form shows, from top to bottom:

  1. On a recurring event, a Date list of the upcoming dates. A full date is marked sold out and cannot be chosen. The seats left update when the buyer changes the date.
  2. One row per ticket on sale: its name, its description, its price (or Free), the seats left when the ticket has a capacity, and a quantity box. A buyer can take up to 20 of each ticket at once.
  3. Your details: Your name and Email, both required.
  4. The event’s registration questions, if you created any. These are the custom fields set to Attendee registration, the same ones the RSVP form asks. Required questions must be answered.
  5. A Continue to checkout button, or Get tickets when every ticket listed is free.

Tickets outside their sale dates are not shown. A sold-out ticket stays in the list, marked Sold out, without a quantity box.

When free tickets are offered and your site uses Cloudflare Turnstile, a captcha appears above the button. See protecting your forms from spam.

How a buyer pays

  1. The buyer clicks Continue to checkout. Your site checks that each ticket is still on sale and has enough seats. If not, the buyer sees how many seats are left and nothing is charged.
  2. The seats are held for the buyer for about 30 minutes.
  3. The buyer pays by card on Stripe’s page. Card details are typed on Stripe, never on your site.
  4. Stripe sends the buyer back to the event page, on the same date for a recurring event. The block says the booking is being processed and that a confirmation email is on its way.
  5. A few seconds later, Stripe confirms the payment to your site. The buyer is added to your attendee list and receives the confirmation email, with the ticket’s QR code and a PDF e-ticket.

If the buyer cancels on Stripe’s page, the block says no charge was made and shows the form again.

A buyer books one date per checkout, in one currency. One visitor can start up to 10 paid checkouts and hold up to 60 seats per hour, so nobody can block a show without paying. Setting up Stripe explains these limits.

Free tickets

A selection that costs nothing never goes to Stripe. The tickets are booked at once, the form says so, and the confirmation email follows. Free tickets go through the same spam checks as the RSVP form, and one booking can take up to 20 of them.

In search results

HappenBoard adds Event schema to each event page: event details written for Google. It lists each ticket on sale with its price, its currency and whether it is sold out. Paid tickets are listed only once Stripe (or WooCommerce) can take the payment. Search engines see your real prices, and a paid event is never described as free.

If something goes wrong

  • The block says online checkout is not configured: no Stripe publishable key is saved. Paid tickets are hidden until you add it, and free tickets are still offered.
  • The block says no tickets are available: the event has no ticket type, or none is on sale right now. Check the sale dates of your ticket types.
  • Buyers pay but do not appear in your attendee list or in the Orders screen: Stripe’s webhook is not reaching your site. Check it in the Stripe tab.
  • The tickets appear twice on the page: your Ticket Picker sits inside a template part. Move it into the template itself or into the event’s content.
  • A buyer was refunded without you doing anything: Stripe confirmed their payment so late that the held seats had already been sold to someone else. That ticket line is refunded automatically and no confirmation email is sent.

Next steps

On this page