Account type
Omnibooking creates a Stripe Standard account through Stripe Connect.
Stripe Connect lets Omnibooking require card payment before a selected booking is confirmed. This guide follows the current backend flow: connect Stripe, wait for verification, turn on payment for fixed-price services, then test the booking page.
When you connect Stripe from Omnibooking, the backend creates a Stripe Standard connected account if your Omnibooking account does not already have one. If an account ID already exists, Omnibooking reuses it and sends you back through Stripe onboarding.
Omnibooking creates a Stripe Standard account through Stripe Connect.
The app sends you to Stripe account onboarding, then returns you to integration settings.
The Stripe webhook marks your Omnibooking account connected after Stripe reports that details were submitted.
The payment toggle is tied to service setup. It appears after Stripe is verified and is intended for fixed-price services.
For paid bookings, the backend calculates an Omnibooking application fee from the booking amount in cents.
ceil(amount_cents * 0.039 + 40)
The client is charged the service price. Omnibooking passes the connected Stripe account as the payment destination and sets the application fee on the payment. Stripe processing fees are handled by Stripe and are separate from the Omnibooking application fee shown here.
Paid booking PaymentIntents are created in USD.
The paid booking endpoint restricts payment methods to card payments.
The payment request includes the connected Stripe account ID as the destination for the charge transfer.
The paid event is created inside the same backend flow that creates and confirms the PaymentIntent. If Stripe does not return a succeeded payment, the booking returns an error instead of completing normally.
Give clients a clean way to choose services, times, and confirmations without the back-and-forth.
Get feature updates, product notes, and occasional Omnibooking news.