Platform
Checkout that finishes, orders you can trust.
A payment-intent saga authorizes first and captures only when the seats are yours. Refunds, cancellations, and invoices are ledger entries, not support tickets.
Sound familiar?
Charged, but no seats
Capture-before-inventory takes money for seats that turn out to be gone. We authorize, commit the seats, and only then capture.
Refunds as manual chaos
Spreadsheets and goodwill don't scale. Full and partial refunds run through a ledger with an over-refund guard and per-line accounting.
Money parked elsewhere
Incumbents settle days after the event and hold reserves. Here payments settle to your own provider. Seatmap never holds your funds.
Ledger-grade order management
01Authorize, then captureManual-capture intents mean abandoned carts void with no money moved, and failures after capture auto-refund.
02A saga, not a scriptTemporal workflows hold, freeze, capture, and commit, with compensation defined on every branch.
033DS/SCA built inStripe Payment Element inline, redirect-return handled, and a mock provider for development.
04Refunds with a paper trailFull and partial refunds carry statuses, reasons, and settlement via provider webhooks. Passes revoke automatically.
05Gapless invoice numberingPer-workspace invoice sequences issue at finalize, with minor-unit money columns end to end.
06Orders across devicesBuyers watch their order complete on every tab through a private per-buyer channel.
The purchase saga, step by step
- 01Hold at checkoutSeats freeze as payment-pending. No TTL can expire them mid-payment.
- 02Authorize the intent3DS runs inline; the provider's webhook signals the workflow to continue.
- 03Capture & commitCapture succeeds, seats commit as sold, and the invoice number issues.
- 04Refund with a ledgerFull or partial refunds settle asynchronously, tracked per line, never over the paid amount.
Run a test checkout
Authorize, capture, refund, the whole saga in the demo.