| 开发者 | navincse |
|---|---|
| 更新时间 | 2026年9月5日 16:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
[seatlayer_chart event="your-event" height="720" max_selection="6"]
Set the event, height, maximum seat selection, locale and currency.
The block supports wide/full alignment where your theme provides it. Currency
is a display fallback; the event's configured prices remain authoritative.
Enter an event key or use an optional server-side secret key for an event
dropdown. Scripts and styles load only on pages containing a chart.
See the WordPress seat map setup guide
for block settings and shortcode options.
Accept payments through Stripe or Razorpay
Hosted checkout: buyers continue from seat selection to SeatLayer's hosted
event page and pay through your connected account.
Checkout from your WordPress page: enable Let buyers pay without leaving
this site under Settings → SeatLayer. Razorpay opens on the page; Stripe
opens its secure checkout and returns the buyer to the WordPress page.
This needs in-page checkout access and a registered embed domain. Hosted
checkout remains the fallback.
Manage venue layouts, events, ticket prices, offers, orders and ticket delivery
in the SeatLayer dashboard.
Account requirements and service pricing
You need an approved SeatLayer Managed Ticketing account, a published
reserved-seat chart, a Managed event and a connected payment account.
Request Managed access before opening sales.
The WordPress plugin is free to install. SeatLayer's hosted service has usage
charges, and your payment provider has its own fees. See
Managed Ticketing pricing for current rates.
[seatlayer_chart] shortcode
to a WordPress page and enter your event key.Create and edit venues in the seating chart designer, then embed the published chart on WordPress. The plugin provides the buyer picker and display settings.
Yes, within a published chart alongside reserved seats. A pure-GA event without a chart uses a different ticketing flow.
The plugin uses SeatLayer's shared buyer renderer. Try the public 53,018-seat stadium demo and read the large-chart renderer measurements. These measure the shared renderer; also evaluate your own chart, WordPress theme and target devices before opening sales.
It can run on a site that also uses WooCommerce. SeatLayer ticket purchases use your connected Stripe or Razorpay account and do not create WooCommerce cart line items or orders.
Only one active hold can own a seat; expired holds release inventory for sale. If payment completes after a hold expires and booking fails, SeatLayer refunds the buyer automatically and flags the order.
In your WordPress database, used server-side and never sent to visitors. Database administrators can read it. Leave it blank and enter event keys directly if you do not want to store it.
Developers who need their own buyer controls, cart or payment flow can use the JavaScript seat map SDK and SeatLayer seat booking API. The plugin provides the Managed Ticketing flow described above.