Supported providers
A tenant connects provider accounts for Stripe, PayPal, 2Checkout, or Authorize.Net. The tenant's default provider is used for checkout unless a specific provider is requested. Manual payment recording (cash, card-on-site) is also supported through the payment status flow. Provider choice is a tenant setting, not a platform mandate.
The checkout flow
When a booking requires payment, QUE creates a hosted checkout session through the tenant's connected provider account and returns a checkout URL. The customer completes payment on the provider's hosted surface; on return, the booking's payment status is pending with the provider's session reference stored on the booking. The inbound Stripe webhook then updates payment_status as the provider reports settlement — paid, failed, or otherwise — so the booking record always reflects what the provider actually returned.
Webhook verification
The inbound Stripe endpoint verifies the stripe-signature header against the tenant's webhook secret before applying any update, refuses requests without a signature, and reports an unavailable state if the webhook secret is not configured. Unsigned or unverifiable payloads are never applied to booking state.
Provider boundaries
QUE describes the application boundary and configured integration behavior. It cannot promise provider uptime, payment settlement, or account approval — those are the provider's domain. If settlement is disputed, reconcile from the booking's stored provider reference, not from the dashboard summary.