Does SeatLayer replace my checkout system?
You choose. In an SDK integration, your application keeps buyer identity, checkout, payment, tax, refunds, orders, and ticket delivery. For hosted reserved-seating events, SeatLayer can provide the event page and checkout while payment runs through the organizer's own connected payment gateway. That provider controls processing fees, applicable taxes, and payout timing. SeatLayer bills Hosted Ticket charges separately. Hosted Ticketing is self-serve and supports Stripe, PayPal, Square, Braintree, Authorize.Net, Checkout.com, Mollie, Razorpay, Tap, Mercado Pago, Xendit, Flutterwave, Paystack and iyzico.
Does optional 3D replace the 2D seat map?
No. The complete 2D Map remains available. Optional 3D uses the same published chart and selection state, loads only after a visitor asks for it, and is offered when WebGL2 and the evaluated browser context support it.
How does SeatLayer handle two buyers asking for the same seat?
Every seat request for an event goes through one server-side state authority, in order, so one buyer gets the seat and the conflicting request receives a conflict response. Nothing is ever sold twice.
Can a buyer use an AI assistant to find seats?
Yes, when an integrator opts in to buyer WebMCP in a compatible browser. The assistant can read the event, find candidates, select seats, and inspect the current selection. Placing a temporary hold is a separate optional permission. There is no checkout or payment tool. Buyer WebMCP is separate from Designer MCP for authorised chart edits and the public knowledge MCP.
Which integration paths does SeatLayer support?
Transactional embedded buyer flows use the JavaScript, React, Vue, Angular, React Native, Flutter, iOS, or Android SDK. Native mobile SDKs currently support Event pickers, not Seasons. The Designer uses a short-lived, origin-scoped session inside an organizer CMS. Hosted reserved-seating event pages are a separate path for organisers who want SeatLayer to provide the buyer site and checkout. Hosted Ticketing is self-serve and supports Stripe, PayPal, Square, Braintree, Authorize.Net, Checkout.com, Mollie, Razorpay, Tap, Mercado Pago, Xendit, Flutterwave, Paystack and iyzico.
Which SDKs and languages are published?
Web: JavaScript and TypeScript, React, Vue 3, and Angular 17+. Mobile Event pickers: React Native, Flutter, Swift on iOS, and Kotlin on Android. Server: Node.js, Python, PHP, Java, Go, Ruby, and .NET. Any other backend can use the REST API and its OpenAPI reference directly.
Where are Fixed Renewable Seasons supported?
Fixed Renewable Seasons are released through browser SDKs, the REST API, and server SDK integrations. Organizer-dashboard rollout remains controlled by account, and native mobile SDKs do not support Seasons.
How is Hosted Ticketing priced?
$0.50 per confirmed ticket, and every new organization gets its first 25 tickets free. There is no subscription. Buyers pay into your own gateway: Stripe, PayPal, Square, Braintree, Authorize.Net, Checkout.com, Mollie, Razorpay, Tap, Mercado Pago, Xendit, Flutterwave, Paystack or iyzico.
Can an agent or MCP client work on my chart?
Designer MCP lets a compatible MCP client work through one authorised chart scope. The agent can read the chart and prepare changes as a revision; publishing stays a human action. The docs are also published as LLM-readable Markdown for the coding agent integrating the SDK.
Can a venue reuse one chart for multiple events?
Yes. A venue chart can be published as a reusable version, while each event adds its own pricing and seat inventory. That separates stable venue geometry from the open, held, sold, and blocked state of a particular event.
Can I try it before paying?
Yes. Test mode is free, with no time limit and no card. Platform/SDK organizations also receive 100 free credits each month. Hosted Ticketing is self-serve and supports Stripe, PayPal, Square, Braintree, Authorize.Net, Checkout.com, Mollie, Razorpay, Tap, Mercado Pago, Xendit, Flutterwave, Paystack and iyzico.