Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

SeatLayer Seating Charts Wordpress Plugin - Rating, Reviews, Demo & Download

SeatLayer Seating Charts Wordpress Plugin - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

Add a real seating chart to any page or post. Visitors see live availability, pick
the seats they want, and pay — with the money going straight into your own payment
account.

How it works

  1. Design your venue and create an event in your SeatLayer dashboard.
  2. Connect your Stripe or Razorpay account there, under Payments.
  3. Drop the SeatLayer block on a page, or use [seatlayer_chart event="your-event"].

What you get

  • Live availability — seats update as other people buy, without a page refresh.
  • Real venue layouts: rows, tables, booths, general-admission areas, multiple floors.
  • Works on phones. Pinch to zoom, tap to select.
  • Seats are held while a buyer checks out, then released automatically if they
    don’t finish — so two people cannot buy the same seat.
  • Buyers get an emailed confirmation listing their seats.

About payments

SeatLayer is not a payment processor and never holds your money. You connect your
own Stripe or Razorpay account, and buyers pay you directly. Refunds happen in your
own payment dashboard; SeatLayer notices them and puts the seats back on sale.

Requirements

A SeatLayer account. The plugin embeds charts from an existing account — it is not
a standalone seating designer.

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. Exactly what is sent, and when:

cdn.seatlayer.io — 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.

api.seatlayer.io — seat 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, only when Checkout is set to “Let buyers pay without leaving this
    site”: the web address of the page the chart is on, so a buyer returning from
    Stripe lands back on it. It is the page’s own public URL and nothing else — no
    visitor data. SeatLayer uses it only if it matches an embed domain you declared
    in advance, and otherwise ignores it.
  • 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.

app.seatlayer.io — the hosted buyer page, used in the default handoff mode.

  • 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.

checkout.stripe.com / checkout.razorpay.com — the payment step, and only if
you switch Checkout to “Let buyers pay without leaving this site”.

  • When: only after a buyer has selected seats and pressed pay. Razorpay’s script
    is loaded into your page to open its payment window; Stripe redirects the
    buyer to its own page.
  • Sent: what the gateway needs to charge — the amount and currency, which
    SeatLayer computed, plus the buyer’s email. Your site does not send this; the
    payment window and the redirect are set up by SeatLayer and your own gateway
    account.
  • Stripe: https://stripe.com/privacy — Razorpay: https://razorpay.com/privacy

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.

Service terms: https://seatlayer.io/terms
Privacy policy: https://seatlayer.io/privacy

Screenshots

No screenshots provided


Reviews & Comments