內容簡介
SeatLayer Seating Charts 外掛可將 WordPress 頁面轉換為完整的預訂座位體驗，讓使用者能在網站上選擇座位並購票。買家可即時查看場地、可用性和價格，並輕鬆完成結帳，無需聯繫第三方售票網站。
【主要功能】
• 互動式場地地圖，顯示各種座位區域
• 實時更新的可用性資訊
• 清晰的座位詳情與價格顯示
• 支援多種票務層級與活動優惠
• 移動裝置友好的選擇控制
• 成功付款後發送電子郵件確認
外掛標籤
開發者團隊
原文外掛簡介
Turn a WordPress page into a complete reserved-seating experience and sell
tickets with seat selection on your own site. Buyers can explore the venue, see
live availability and prices, choose exact seats, and continue to checkout
without calling, emailing, or guessing where they will sit. Payment goes to the
Stripe or Razorpay account you connect, not to a third-party ticketing site.
A better seating experience for buyers
Interactive venue maps for rows, tables, booths, general-admission areas,
accessible seating, and multiple floors.
Live availability that updates while buyers are viewing the event.
Clear seat details and prices before a buyer makes a selection.
Ticket tiers and active event offers shown through the SeatLayer buyer
experience when configured for the event.
Temporary seat holds during checkout, with automatic release when a buyer
does not finish.
Mobile-ready controls with touch selection, pinch-to-zoom, responsive
summaries, and a layout designed for smaller screens.
Best-available assistance when buyers want SeatLayer to find seats
together.
Email confirmation with the seats purchased after successful payment.
Built for WordPress organizers
Add the SeatLayer seating chart block in the Gutenberg editor.
Use [seatlayer_chart event="your-event"] in classic content, builders, or
shortcode-compatible areas.
Choose an event from the editor when an optional SeatLayer secret key is
configured, or paste an event key without storing a secret.
Load the SeatLayer buyer SDK only on pages that contain a chart.
Keep payments in the organizer’s connected Stripe or Razorpay account.
Manage venue design, event pricing, offers, orders, and ticket delivery from
the SeatLayer dashboard.
Choose the checkout experience
Hosted checkout — the safe default
After choosing seats, the buyer continues to the SeatLayer-hosted event page to
pay. SeatLayer completes the Order and ticket-delivery flow through the payment
account connected by the organizer.
Checkout from your WordPress page — optional
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 afterward. This option requires in-page
checkout access and the exact WordPress origin to be registered as a SeatLayer
embed domain; otherwise the plugin safely keeps the hosted-checkout flow.
How it works
Create a SeatLayer account and design or select
your venue.
Create an event, set prices and offers, and connect Stripe or Razorpay.
Add the SeatLayer block to a WordPress page and choose the event.
Publish the page. Buyers can select seats and purchase through the configured
SeatLayer checkout.
Requirements
This plugin connects WordPress to an existing SeatLayer account. Venue design,
events, pricing, offers, and managed checkout are configured in SeatLayer; the
plugin is not a standalone seating designer or a WooCommerce checkout extension.
Learn about the WordPress integration ·
Choose the right SeatLayer integration
External services
This plugin is a client for SeatLayer, a hosted seating and ticketing service. It
does not work standalone, and using it means your site and your visitors talk to
SeatLayer. This section explains each external service, when it is contacted, and
what data is sent.
SeatLayer CDN (cdn.seatlayer.io) — loads the seating-chart renderer.
When: only on pages that actually contain a chart. The browser loads
https://cdn.seatlayer.io/seatlayer-js@0/seatlayer.js.
Sent: nothing the plugin adds. As with any script request, the browser sends
its own IP address, user agent, and referring page.
SeatLayer API (api.seatlayer.io) — provides layouts, live
availability, seat holds, and payment sessions.
When (visitor): as soon as a chart renders, to fetch the seating layout and
live availability; then when a visitor selects seats, to hold them; then, if
they buy, to start a payment.
Sent (visitor): the event key, the seats selected, and — at the payment step
only — the buyer’s email address and, if given, their name. A payment is
started with the hold identifier alone: the plugin never sends an amount, and
the SeatLayer server recomputes the total from its own records.
Also sent for optional in-page checkout: the chart page’s public URL, used only
when it matches a pre-declared embed domain so Stripe can return the buyer.
When (administrator): only if you save a secret key, and only inside the block
editor, to list your events in a dropdown. Your server makes this call, not the
browser, and the key is never sent to a browser.
Sent (administrator): your secret key. No visitor data.
SeatLayer hosted buyer page — completes the
default hosted-checkout journey.
When: only if a buyer chooses to check out. Their browser is redirected to
https://app.seatlayer.io/e/EVENT?hold=HOLD_ID.
Sent: the event key and the hold identifier, in the URL. No amount, and nothing
about the buyer.
Stripe or Razorpay — processes payment through the organizer’s connected
gateway account.
When: after a buyer selects seats and presses pay. Razorpay opens its payment
window on the page; Stripe redirects to its secure checkout.
Sent by SeatLayer to the gateway: the authoritative amount, currency, and
buyer email needed to process payment.
Privacy: Stripe Privacy Policy ·
Razorpay Privacy Policy
Card details are handled by Stripe or Razorpay on the account you connected.
They never pass through this plugin, your WordPress site, or your database.
SeatLayer Terms of Service ·
SeatLayer Privacy Policy
