A real-time event callback — from Stripe or the NOWAITN mesh — that keeps state in sync across apps. When something happens (a payment completes, an object changes state), a webhook fires so the right app updates instantly instead of polling for changes.
A real-time event callback — from Stripe or the NOWAITN mesh — that keeps state in sync across apps. When something happens (a payment completes, an object changes state), a webhook fires so the right app updates instantly instead of polling for changes.
See also: Stripe Connect, Notification preference, Token
Continue exploring our knowledge base
Your business account on the platform — the operator entity that runs your queues, events, rides, orders, memberships, and more. One tenant holds one organization, its operators, its customers, and everything you sell, no matter how many modes you switch between.
The person — a user account — who runs a tenant's business day to day: setting up the storefront, working the boards, and serving guests. A tenant can have several operators sharing the one account, each signing in with their own login.
A person using your services — waiting in a line, buying a ticket or pass, booking a ride, or placing an order. Every mode has its own name for a guest in context (a rider, member, registrant, or passenger), but they're all guests tracked in your one Customers book.
The tenant-level record holding your business name, business type, timezone, and legal identity — the "org." It's the top of your account: your operators, storefront, and everything you sell all belong to this one organization.
A CRM record for a person in your value chain, carrying a lifecycle stage that moves lead → qualified → subscriber → churned (a contact can also be marked lost, or reopened back to lead). Customers can self-edit their own details through a hosted profile, so the record stays current without your staff retyping it.