Bookings & customer payments

Turn a trusted handover into a booked appointment.

RelayLocal Bookings keeps service setup, availability, customer policy acceptance, appointment status and direct Stripe payment evidence in the same business workspace. The service business remains the provider and merchant; RelayLocal facilitates the workflow.

Fewer platform jumps after a customer says yes

A local service business can move from enquiry or referral to a controlled booking flow without asking the customer to switch to an unrelated scheduling or payment product.

Bookable services

Publish the service, duration, price, deposit or full-payment requirement and practical booking limits.

Real availability

Offer server-generated times from weekly hours while slot locks protect against concurrent double booking.

Clear terms before confirmation

Show the current cancellation, reschedule, no-show and additional terms and save the exact accepted policy version with the booking.

Real workflow

From service choice to payment evidence

  1. 01

    Choose a service

    The customer selects one of the business's active services.

  2. 02

    Choose a live slot

    RelayLocal generates valid times from the business schedule and service rules.

  3. 03

    Review terms

    The customer sees the current booking and cancellation policy before accepting it.

  4. 04

    Lock the time

    The server re-checks the selected time and creates unique occupancy locks so competing requests cannot silently take the same slot.

  5. 05

    Pay the business

    Where payment is required, Stripe-hosted Checkout processes a deposit or full payment as a direct connected-account charge.

  6. 06

    Confirm from Stripe evidence

    Payment confirmation comes from verified Stripe events rather than trusting the browser return page.

  7. 07

    Manage privately

    The customer receives a private booking-management link for supported cancellation, rescheduling and refund status.

  8. 08

    Keep business records together

    Authorised staff can review bookings, payment status and payouts without mixing them with RelayLocal subscription billing.

Customer payments are separate from your RelayLocal subscription

The Stripe Customer Portal used for a business's RelayLocal subscription remains separate. Customer booking payments use the business's own connected Stripe merchant account, so RelayLocal does not operate an internal wallet or escrow balance.

Policies are versioned, not overwritten

Publishing a new booking policy creates a new version. Existing bookings retain the exact policy snapshot and hash accepted by that customer, so later edits do not rewrite historical terms.

Payment security uses Stripe-hosted card entry

RelayLocal does not intentionally store full card numbers or card security codes. Card entry and payment processing are handled by Stripe; RelayLocal stores limited booking/payment identifiers needed to reconcile the workflow.

Refund rules stay bounded by law

Businesses can configure cancellation and deposit rules, but a saved policy does not make an unfair or unlawful term enforceable. Statutory rights, Stripe disputes and card-network rights can still apply.

Clear boundaries

Bookings & payments are not…

  • RelayLocal acting as the service provider
  • A RelayLocal customer wallet or escrow account
  • A guarantee that a customer attends or a service is completed
  • A guarantee of payout timing or dispute outcome
  • Permission to keep every deposit in every circumstance
  • A claim of certified banking-level security

Bookings & customer payments questions

For supported paid bookings, the connected service business receives the direct Stripe payment. RelayLocal facilitates the booking workflow.

Cookies on RelayLocal

Essential cookies keep RelayLocal working. Analytics run only if you allow them. Cookie Policy