ONLINE BOOKING CHECKOUT
Online Payments for Activity Bookings
Offer online prepayment through your configured activity-booking checkout. Connect payment attempts and confirmed results with the relevant order, giving staff records to review when a payment is pending, successful or failed.
Online payment requires an enabled gateway, valid credentials and a valid payment amount. Provider and checkout options depend on your setup.
FROM BOOKING TO PAYMENT RESULT
Follow the payment beyond the checkout button
Continue from the booking
The configured activity-booking journey passes the relevant amount into online checkout.
Complete the payment step
Customers use the gateway journey available for the setup. Confirm whether that journey redirects to a hosted page or uses an embedded checkout.
Receive the confirmed result
Payment confirmation can arrive through background processing after the customer leaves checkout. The recorded payment result determines whether collection succeeded.
Submitting an order, selecting a payment button or reaching a return page does not by itself confirm that money has been collected.
PAYMENT RECORDS
Keep pending, successful and failed attempts distinct
Payment attempts are linked to orders so staff can review their recorded status within the available access.
Pending
A pending attempt should not be treated as confirmed collection. Review the recorded result before deciding the next action.
Successful
A successful payment result records collection through the supported process. Check the related order and any remaining balance separately.
Failed
A failed attempt is not a successfully collected payment. Confirm the supported retry or recovery journey rather than assuming the customer can continue from any screen.
BACKGROUND CONFIRMATION
Connect payment results with the booking record
The payment workflow includes background confirmation and reconciliation, with controls to prevent duplicate settlement processing.
Booking confirmation emails can be sent where configured. Confirm when those messages are issued for your payment journey, particularly while a payment result is still pending.
Duplicate-settlement controls do not mean every repeated customer payment attempt is automatically refunded or resolved in the same way.
PAYMENT AMOUNTS AND BALANCES
Confirm the collection process your booking needs
Order-balance functions support part payments, but this does not by itself establish an online deposit calculation or automatic collection of a later balance.
If customers need to pay a deposit, settle a party balance or make instalments, ask to see that complete online journey before offering it. Confirm how the amount is set, how the customer pays and how staff identify any balance remaining.
CANCELLATIONS AND REFUNDS
Treat booking cancellation and payment refund separately
Eligible full or partial refund functions are supported, but cancelling a booking is not the same as completing a refund.
Confirm which staff can initiate a refund, which transactions qualify and how the gateway result is recorded. Do not promise an automatic refund or a particular completion time without confirming the applicable process.
STAFF REVIEW AND RELATED PAYMENT TOOLS
Review payment records within the right workflow
Staff payment views and reports support review of payment activity, subject to scope and permissions. Use them to investigate the recorded result alongside the related order.
Online booking checkout is separate from physical payment terminals and recurring membership billing. QR ordering and kiosk payments also need their own confirmed payment journeys.
QUESTIONS BEFORE YOU CHOOSE
Online booking payment questions
Can customers pay during an activity booking?
Yes, where online prepayment is configured with an enabled gateway, valid credentials and a valid amount. Confirm the provider and checkout journey available for your setup.
Does returning from checkout mean the payment succeeded?
No. A return page alone does not establish successful collection. Payment confirmation can arrive through background processing, and the recorded result needs to be checked.
Can staff see pending or failed payments?
Payment attempts have pending, successful or failed states linked to orders. Staff review depends on the available views, scope and permissions.
Can I collect an online deposit and the balance later?
Part-payment functionality does not by itself establish an online deposit or later balance-collection journey. Ask us to demonstrate the exact process you need before offering it.
Does cancelling a booking automatically refund the customer?
No automatic refund is promised. Cancellation and refund handling are separate, and eligible refunds depend on the transaction, permissions and gateway process.
Are online booking payments the same as kiosk, QR or membership payments?
No. Each journey needs its own configuration and confirmation. This page describes activity-booking checkout; physical terminals and recurring membership billing are separate payment arrangements.
DEMONSTRATE THE COMPLETE CHECKOUT
Walk through payment and its recorded outcome
Tell us how customers should pay for their bookings. We’ll demonstrate the configured checkout, payment-status handling and staff review, and confirm any deposit, balance or refund requirements separately.