# Reserved seating, added to WordPress like any other block. The SeatLayer plugin puts a real seating chart on a page or post. Visitors see live availability, pick the seats they want, and pay — with the money going straight into your own Stripe or Razorpay account. ### Opening Night Friday · 7:30 PM · The Lantern Theatre The dropdown is filled by your server, not the browser — the key that lists these events never leaves WordPress. ## A wrapper around the parts that are easy to get wrong. You can already paste a SeatLayer embed into a Custom HTML block, and it will work. The plugin exists because three things are awkward that way, and each of them is a way to leak a credential or lose a buyer. ### The secret key stays on the server Listing your events needs a key that can also create and modify them. The plugin makes that call from WordPress itself, through an admin-only route, so the key is never written into a page a visitor can read. ### Editors pick an event from a dropdown Whoever writes the page chooses the event by name in the block sidebar. No copying identifiers between two browser tabs, and no silently-wrong chart because a character was dropped. ### Buyers come back to the page they bought from With in-page checkout on, a card payment that leaves for the gateway returns to the exact page holding the chart, read in the browser at load so a cached page cannot send a buyer to the wrong address. What it is not: the plugin is a safe, no-code wrapper around the buyer-facing chart — not a second copy of SeatLayer. Designing venues, creating events, connecting gateways, refunds, and check-in all live in your SeatLayer dashboard, and the plugin deliberately does not try to reproduce them inside wp-admin. ## Set the event up once. Drop the block wherever it belongs. The chart needs an event key and nothing else. The optional secret key only buys you the dropdown, so a site that would rather not store one simply does not. ### It runs on an ordinary WordPress site. No build step, no bundled dependency tree, and no server extensions. Requests go through WordPress's own HTTP layer, so site proxies and host timeouts apply as they do for every other plugin. - WordPress6.3+ - PHP7.4+ - EditorBLOCK OR CLASSIC - LicenceMIT - AccountSEATLAYER ## Your site, your gateway, your customers. SeatLayer is not a payment processor and never holds your money. It is the seating and ticketing layer beneath a sale that stays yours end to end. ### The page and the commercial relationship - The event page, its story, imagery and policies - Ticket prices, on-sale timing and buyer support - The Stripe or Razorpay account the money lands in - Refunds, issued from your own payment dashboard ### Seats, holds, tickets and entry - Published seating, live availability and temporary holds - Checkout against your connected gateway, and the order record - Seat-specific tickets, QR codes, printable PDFs and confirmation email - Releasing seats back on sale when it sees a refund The current standard rule uses one credit when a seat is first confirmed sold. Payment-provider fees, taxes, enterprise terms and entitlements can still apply. ## The plugin is a client for a hosted service. Here is what leaves your site. It does not work standalone, so installing it means your pages and your visitors talk to SeatLayer. The same disclosure ships inside the plugin's own readme, and it is the whole list. ### Visitors On a page that contains a chart — and only on such a page — the browser loads the chart renderer and asks SeatLayer for the seating layout and live availability. Selecting seats places a hold; buying starts a payment. ### Administrators Only if you saved a secret key, and only inside the block editor: your server asks SeatLayer for your event list to fill the dropdown. That request carries the key and no visitor data, and the response is projected down to the four fields the dropdown shows. Deleting the plugin removes its settings, including any saved key. Deactivating deliberately leaves everything alone. ## Answered plainly, including the parts that are not finished. If your site needs to run its own checkout, react to seat selection in code, or sell through an existing cart, the plugin is the wrong tool and the SDK is the right one. ### Do I need a secret key to show a seating chart? No. The chart renders from the event key alone, which is not a secret. Saving a secret key only makes the editor nicer, by listing your events in a dropdown instead of you pasting keys by hand. ### Where does the secret key go if I do save one? Into your WordPress database, like any other plugin setting, and it is used only in server-side requests. It is never sent to a browser. Anyone with administrator or database access to the site can read it, so if that is not acceptable, leave it blank and type event keys by hand. ### Where does the ticket money go? To the Stripe or Razorpay account you connected. SeatLayer is not a payment processor and never holds the money. Refunds happen in your own payment dashboard, and SeatLayer releases the seats back on sale when it sees one. ### Does the plugin work with WooCommerce? Not today. Buyers pay through SeatLayer checkout using your own connected gateway. A WooCommerce integration, with seats as cart line items paid through your existing Woo gateway, is a separate piece of work. ### Will it slow the rest of my site down? The chart's code is enqueued only on pages that actually contain a chart, so pages without one load nothing extra. ### Can two people buy the same seat? No. A seat is held on SeatLayer's servers the moment a buyer selects it, and only one hold can exist per seat. If they do not pay in time the hold expires and the seat returns to sale. ## Keep the WordPress site you have. Give it the seat map it is missing. Design the venue, create an event, connect your gateway, and drop the block on the page you already send people to. --- _Machine-readable site index: [/llms.txt](https://seatlayer.io/llms.txt) · full corpus: [/llms-full.txt](https://seatlayer.io/llms-full.txt)_ _Source page: [https://seatlayer.io/integrations/wordpress/](https://seatlayer.io/integrations/wordpress/) · Questions: [Contact SeatLayer](https://seatlayer.io/contact/) · hello@seatlayer.io_