Trust centre

Your bookings and payments, clearly explained.

Booking software sits close to your customers and your revenue. Here is how GetItBooked handles payments, payouts, refunds, account access, and the services used to run the platform.

Stripe Connect

What happens when a customer pays

GetItBooked uses separate charges and transfers: the customer payment is processed on the platform first, then the operator’s share is transferred to their connected Stripe account according to the payout schedule.

01

Connect your Stripe account

Operators complete Stripe-hosted onboarding. Identity and bank details are submitted directly to Stripe, not entered into GetItBooked.

02

The customer pays securely

Stripe processes the card payment at checkout. GetItBooked stores Stripe references and payment status, never full card numbers.

03

The booking is confirmed

A verified payment confirmation from Stripe finalises the booking. The customer receives confirmation and the operator can see the payment status.

04

Your payout is released

GetItBooked deducts the published platform fee, then transfers the operator share to the connected Stripe account when the payout becomes due.

What “connected” means: your Stripe account remains the destination for operator funds and gives Stripe the information it needs to make payouts. GetItBooked initiates the transfer and shows its status in the dashboard; Stripe handles the underlying payment and banking rails.

Refunds keep both sides of the payment in step

A refund should not leave the customer refunded while the operator still holds the same payout. GetItBooked coordinates the payment and transfer as one workflow.

Before the payout is released

The customer payment is refunded or cancelled through Stripe, and the booking is updated accordingly.

After the payout is released

GetItBooked first attempts to reverse the operator transfer, then refunds the customer from the original payment. If the transfer cannot be reversed, the customer refund is not issued automatically and the operator is shown that the reversal failed.

Safeguards around the booking flow

Practical controls protect payment events, customer card data, and access to each operator’s workspace.

Verified payment events

Stripe webhook signatures are checked before payment events are acted on. A browser redirect alone cannot confirm a paid booking.

Card data stays with Stripe

Stripe’s secure payment interface collects card details. GetItBooked never stores complete card numbers or security codes.

Scoped business data

Authenticated operator and team access is scoped to the relevant business account, with role checks around administrative actions.

Operational notifications

Booking confirmations, cancellations, reschedules, refunds, and relevant operator notifications are sent through the platform’s email provider.

Infrastructure and data handling

GetItBooked runs on established specialist services rather than operating every part of the stack itself. Cloudflare provides application delivery, Stripe processes payments and payouts, and Resend delivers transactional email.

We store the booking and account information needed to operate the service, along with Stripe identifiers and payment status. Our Privacy Policy explains what is collected, why it is used, retention periods, subprocessors, and your data-protection rights.

Still have a question?

Trust is easier when you can ask a real person. Contact us about payments, data handling, or anything else you need to understand before using GetItBooked.

Contact us