Turn a WordPress page into a complete reserved-seating experience. Buyers can\nexplore the venue, see live availability and prices, choose exact seats, and\ncontinue to checkout without calling, emailing, or guessing where they will sit.<\/p>\n\n
[seatlayer_chart event=\"your-event\"]<\/code> in classic content, builders, or\nshortcode-compatible areas.<\/li>\n- Choose an event from the editor when an optional SeatLayer secret key is\nconfigured, or paste an event key without storing a secret.<\/li>\n
- Load the SeatLayer buyer SDK only on pages that contain a chart.<\/li>\n
- Keep payments in the organizer's connected Stripe or Razorpay account.<\/li>\n
- Manage venue design, event pricing, offers, orders, and ticket delivery from\nthe SeatLayer dashboard<\/a>.<\/li>\n<\/ul>\n\n
Choose the checkout experience<\/h4>\n\n
Hosted checkout \u2014 the safe default<\/strong><\/p>\n\nAfter choosing seats, the buyer continues to the SeatLayer-hosted event page to\npay. SeatLayer completes the Order and ticket-delivery flow through the payment\naccount connected by the organizer.<\/p>\n\n
Checkout from your WordPress page \u2014 optional<\/strong><\/p>\n\nEnable Let buyers pay without leaving this site<\/strong> under Settings \u2192\nSeatLayer<\/strong>. Razorpay opens on the page. Stripe opens its secure checkout and\nreturns the buyer to the WordPress page afterward. This option requires in-page\ncheckout access and the exact WordPress origin to be registered as a SeatLayer\nembed domain; otherwise the plugin safely keeps the hosted-checkout flow.<\/p>\n\nHow it works<\/h4>\n\n\n- Create a SeatLayer account<\/a> and design or select\nyour venue.<\/li>\n
- Create an event, set prices and offers, and connect Stripe or Razorpay.<\/li>\n
- Add the SeatLayer block to a WordPress page and choose the event.<\/li>\n
- Publish the page. Buyers can select seats and purchase through the configured\nSeatLayer checkout.<\/li>\n<\/ol>\n\n
Requirements<\/h4>\n\n
This plugin connects WordPress to an existing SeatLayer account. Venue design,\nevents, pricing, offers, and managed checkout are configured in SeatLayer; the\nplugin is not a standalone seating designer or a WooCommerce checkout extension.<\/p>\n\n
Learn about the WordPress integration<\/a> \u00b7\nChoose the right SeatLayer integration<\/a><\/p>\n\nExternal services<\/h3>\n\n
This plugin is a client for SeatLayer, a hosted seating and ticketing service. It\ndoes not work standalone, and using it means your site and your visitors talk to\nSeatLayer. This section explains each external service, when it is contacted, and\nwhat data is sent.<\/p>\n\n
SeatLayer CDN (cdn.seatlayer.io<\/code>)<\/strong> \u2014 loads the seating-chart renderer.<\/p>\n\n\n- When: only on pages that actually contain a chart. The browser loads\n https:\/\/cdn.seatlayer.io\/seatlayer-js@0\/seatlayer.js.<\/li>\n
- Sent: nothing the plugin adds. As with any script request, the browser sends\nits own IP address, user agent, and referring page.<\/li>\n<\/ul>\n\n
SeatLayer API (api.seatlayer.io<\/code>)<\/strong> \u2014 provides layouts, live\navailability, seat holds, and payment sessions.<\/p>\n\n\n- When (visitor): as soon as a chart renders, to fetch the seating layout and\nlive availability; then when a visitor selects seats, to hold them; then, if\nthey buy, to start a payment.<\/li>\n
- Sent (visitor): the event key, the seats selected, and \u2014 at the payment step\nonly \u2014 the buyer's email address and, if given, their name. A payment is\nstarted with the hold identifier alone: the plugin never sends an amount, and\nthe SeatLayer server recomputes the total from its own records.<\/li>\n
- Also sent for optional in-page checkout: the chart page's public URL, used only\nwhen it matches a pre-declared embed domain so Stripe can return the buyer.<\/li>\n
- When (administrator): only if you save a secret key, and only inside the block\neditor, to list your events in a dropdown. Your server makes this call, not the\nbrowser, and the key is never sent to a browser.<\/li>\n
- Sent (administrator): your secret key. No visitor data.<\/li>\n<\/ul>\n\n
SeatLayer hosted buyer page<\/a><\/strong> \u2014 completes the\ndefault hosted-checkout journey.<\/p>\n\n\n- When: only if a buyer chooses to check out. Their browser is redirected to\n https:\/\/app.seatlayer.io\/e\/EVENT?hold=HOLD_ID.<\/li>\n
- Sent: the event key and the hold identifier, in the URL. No amount, and nothing\nabout the buyer.<\/li>\n<\/ul>\n\n
Stripe or Razorpay<\/strong> \u2014 processes payment through the organizer's connected\ngateway account.<\/p>\n\n\n- When: after a buyer selects seats and presses pay. Razorpay opens its payment\nwindow on the page; Stripe redirects to its secure checkout.<\/li>\n
- Sent by SeatLayer to the gateway: the authoritative amount, currency, and\nbuyer email needed to process payment.<\/li>\n
- Privacy: Stripe Privacy Policy<\/a> \u00b7\nRazorpay Privacy Policy<\/a><\/li>\n<\/ul>\n\n
Card details are handled by Stripe or Razorpay on the account you<\/strong> connected.\nThey never pass through this plugin, your WordPress site, or your database.<\/p>\n\nSeatLayer Terms of Service<\/a> \u00b7\nSeatLayer Privacy Policy<\/a><\/p>\n\n\n