For Platform and SDK integrations, SeatLayer uses a prepaid credit wallet. One credit is consumed when one guest place is first booked; rendering, holds, releases, and organizer blocking do not consume credits.
Purchased credits remain in the organization wallet until used. They do not expire at the end of a month or contract period. If no guest places are sold, no sold-seat credits are consumed.
No card is required to create charts and test the integration. Promotional credits are not part of the standard published pricing contract unless a specific active offer states its eligibility and expiry terms.
Prepaid packs
| Pack | Price | Effective price |
|---|---|---|
| 500 credits | $50 | 10.0¢ per credit |
| 1,000 credits | $90 | 9.0¢ per credit |
| 5,000 credits | $400 | 8.0¢ per credit |
| 25,000 credits | $1,500 | 6.0¢ per credit |
| 50,000 credits | $2,500 | 5.0¢ per credit |
| 100,000 credits | $5,000 | 5.0¢ per credit |
Pack prices are in USD. The server catalog—not a browser-submitted amount—is authoritative for checkout. This v2 catalog applies to new checkouts; completed purchases, existing balances, and already-created checkout sessions keep the price and credits recorded when they were created.
Every organization also receives 100 free credits each month. The allowance renews on the first of the month and is not a trial — it does not run out after a starter period. Beyond it you can buy a smaller pack for a quiet season, keep unused purchased credits indefinitely, and top up again only when your sold-seat volume requires it.
Managed Ticketing
Managed Ticketing is enabled only for approved organizer and venue accounts;
request access and confirm that Hosted Checkout (hosted_checkout) is enabled
before planning a live managed event.
It uses a separate Hosted Ticket wallet. The first 200 confirmed Hosted Tickets are free once per organization. After that allowance, each confirmed Hosted Ticket costs $0.50 for an organization on the USD catalog or ₹25 for an organization on the INR catalog. The dashboard and server catalog determine which account currency applies.
Hosted Ticket credits and Platform/SDK seat credits are separate and cannot be exchanged. The organizer’s connected payment provider controls processing fees, applicable taxes, and payout timing; those amounts are separate from the Hosted Ticket price.
What consumes a credit
| Operation | Credits |
|---|---|
| Render a chart or picker | 0 |
| Create, replace, extend, release, or expire a hold | 0 |
| Best-available hold | 0 |
| Block or unblock inventory | 0 |
| First successful booking of guest capacity | 1 per newly sold place |
| Idempotent booking replay | 0 additional |
| Cancellation | No refund of the original credit |
| New ordinary booking after cancellation/unbook of already-metered inventory | 0 additional |
| Test-mode booking | 0 |
Grouped objects and variable occupancy are guest-weighted. A five-person table booked for five guests consumes five credits, not one object credit.
Features and add-ons
Core Designer, buyer SDK, Server API, webhooks, workspaces, and embed surfaces use the same usage wallet. Some account capabilities can still require an entitlement—for example, removing “Powered by SeatLayer” is enforced as a white-label add-on at buyer-serve time. Do not treat a theme flag as proof of entitlement.
For committed volume, SSO/SAML, an SLA, a DPA, integration support, or custom venue design, contact hello@seatlayer.io.
Buy and retrieve invoices
Admins purchase packs in the dashboard. SeatLayer creates a provider-hosted
checkout from a server-authoritative packId, credits the wallet exactly once
after a verified completion, and sends a purchase confirmation.
Where the payment provider supports invoices, a completed purchase can expose a
hosted invoice or PDF. A just-completed purchase can briefly return
invoice_not_ready; retry the invoice action rather than starting a second
checkout.
Plan for production
- Estimate peak sold guest capacity, not chart renders or holds.
- Keep a buffer before a high-volume on-sale.
- Monitor the organization balance, not individual workspace balances.
- Use test-mode events for integration and load validation.
- Treat public pack values as product pricing that can change; read the dashboard/server catalog before building an internal purchase UI.
- Confirm white-label and enterprise entitlements separately.
See the credit model and test-mode authentication.