Skip to main content

Payments architecture

Reliable payment routing.
Honest provider readiness.

Booking Bible has a production-grade Stripe Connect rail for venue payments. Any additional provider connection is treated as a separate commercial, technical and operational rollout.
Discuss payment requirementsReview platform pricing
  • Stripe Connect live
  • Provider capabilities modelled
  • Account-local refunds

Available payment rail

One production path, stated clearly

Stripe Connect is the supported venue payment processor today. A provider name is added here only after its complete transaction, checkout, reconciliation, certification and support path is accepted.

Production rail

Stripe Connect

The complete Booking Bible payment path today: online and recurring payments, saved cards, refunds, venue-aware routing, country-aware transaction fees and Stripe Terminal where configured.

The durable layer

Payment behavior is centralized, not scattered

The strongest part of a payments platform is not a logo grid. It is what happens when accounts change, retries arrive, refunds race and webhooks are delivered twice.

Venue-aware money movement

Stripe charges resolve through the shared charge model instead of one-off payment builders. The platform records the connected account used for the transaction.

Refunds follow the original rail

Refund logic uses the account stored with the payment, not a venue’s current configuration, and reverses applicable transaction fees through the canonical refund path.

Capability checks before promises

Provider features are represented as capabilities—recurring, saved cards, terminal, refunds and off-session charging—so unsupported behavior can fail closed.

Scoped credentials and attribution

Connection records, provider-specific webhook routing and organization scope keep integration credentials and event ownership separated by venue.

For payment and integration partners

A credible provider project starts with the hard questions

We scope the commercial, technical and operational contract together—before presenting a provider as available.

Account modelWho owns the merchant, customer, mandate and settlement account?
Payment lifecycleWhich checkout, recurring, retry, refund and dispute primitives are authoritative?
Event contractHow are signatures, retries, ordering, deduplication and reconciliation handled?
Regional scopeWhich currencies, payment methods, legal entities and certifications apply?
RolloutHow do sandbox validation, canaries, observability and rollback work?

Payment questions

What venues and partners usually ask

Availability always depends on the venue, market, plan, account configuration and active rollout.

Which payment processor can a venue use in production today?
Stripe Connect is the complete production payment rail today. Other provider-aware code paths are not live venue offerings and are not advertised as supported processors.
Can an existing processor account be moved automatically?
Not automatically. Credential ownership, customer identifiers, saved-card locality, subscription contracts and provider transfer rules must be assessed for the source and destination accounts. Booking Bible treats card migration as a scoped, PCI-conscious project.
Does every payment feature work on every provider?
No. Terminals, saved-card setup, recurring billing, off-session retry, refunds and marketplace fee collection vary by provider. Booking Bible models these capabilities explicitly and only exposes a flow when the underlying rail supports it and the rollout is enabled.
Can a payment provider or enterprise partner integrate with Booking Bible?
Yes. A serious integration starts with the provider’s account model, checkout and recurring primitives, webhook contract, reconciliation data, regional requirements and certification path. Contact the integrations team to scope the work against the public API and the internal payment abstraction.

Next step

Bring us the payment constraint

If you are evaluating Booking Bible for a venue group—or represent a processor that wants to integrate—send the account model, markets and use cases. We will answer with a concrete scope.

Contact integrationsExplore the developer platform