GridMagik publishes tenant-branded availability, creates capacity-safe reservations, tracks guests, and moves bookings into venue operations. Stripe checkout, explicit per-product deposits, multi-tender collection, connected-account refunds, and operator-issued gift vouchers are implemented in controlled beta.
A venue can publish products and availability, capture the primary guest and party details, create a reservation, and manage that record through calendar, transaction, and arrival workflows. Database locks and regression tests protect capacity and hold transitions under competing demand.
The payment foundation creates direct charges on a venue's connected Stripe account, supports server-driven Stripe Terminal, records multiple immutable tenders, and initiates provider-confirmed Stripe refunds. Live activation still requires venue-specific sandbox approval and operational review.
Staff can issue paid or explicitly comped vouchers, deliver a secure bearer link, download a one-page PDF, track liability, reissue or void access, and redeem part or all of a balance into a reservation. Products can also require a server-calculated fixed or percentage deposit and collect the remaining balance later. Consumer gift purchasing, scheduled delivery, automatic balance charging, dunning, and voucher refund reinstatement are not released.
Available means implemented in the application; beta and planned items are not sold as finished features.
Products, availability, holds, reservations, customers, guests, calendar, and check-in foundations.
Connected-account hosted checkout exists in sandbox while payment safety work is completed.
Permissioned partial refunds use connected-account Stripe, durable idempotency, and webhook-confirmed settlement.
Immutable cash, external, gift, and provider attempts derive one reservation balance with replay protection.
Secure staff issuance, delivery links, printable PDFs, partial redemption, balance carry-forward, expiry, and liability reporting.
Explicit fixed or percentage product rules snapshot the due-now amount and preserve later balance collection and refund history.
Tender and refund balances are derived from immutable rows; disputes, payouts, and settlement reporting remain planned.
Catalog extras are repriced on the server, locked after capture, and stored as tenant-bound transaction lines.
Yes. The public booking and reservation workflow is implemented with capacity locks and tenant-bound access tokens. Paid rollout still requires venue setup and payment-provider approval.
Both are in controlled beta. A venue can configure an explicit fixed or percentage product deposit, collect only the amount currently due through Stripe, and let the guest return for the balance or use pay on arrival when allowed. Gift vouchers and approved manual tenders can also contribute to the same immutable balance. Automatic balance charging and dunning are not included.
Operator-issued gift vouchers are in controlled beta with secure tokens, balances, partial redemption, delivery links, PDFs, expiry, and liability reporting. A consumer storefront for buying and scheduling gifts is not released.
Authorized staff can initiate an idempotent partial Stripe Connect refund and GridMagik waits for provider-confirmed success before changing settled totals. Square and gift-value reinstatement refunds are not available.
30-minute walkthrough. Your pricing, your calendar, your receipts — running live in a sandbox on your data. No slides.
