Let’s get your guests booked.

SwiftCove gives each experience a public booking page. A guest chooses a date, picks an available time slot, selects their party size, sees the correct price, and pays through O‑Pay. The pending checkout reserves capacity for that slot, and a matched success return or O‑Pay event updates the booking as paid.

It is designed for experiences that have a real operating schedule—sunset sails, excursions, classes, transfers, private charters, and other bookings where the time and number of available places matter.

Start from the SwiftCove sign-in page and choose registration. After you verify your Google account and submit the operator application, SwiftCove reviews and provisions your business. You can then complete setup and a controlled payment test before the booking page is activated.

The 15-day trial starts when your business is deliberately activated, not while the application is waiting for review or setup. After the trial, you can continue for US$35/month if SwiftCove is a fit.

Bring the same information a guest needs before deciding to book: experience names and descriptions, image links, prices, adult or child rates where relevant, duration, time between departures, maximum capacity, and any dates or departures that need to be blocked.

You will also need your logo and colours for the booking page, the domain you want to use if you have one, and an active O‑Pay account before card payments can be turned on.

Yes. Send your current schedule in the format you already use—a website link, a spreadsheet, screenshots, or even a clear list of departures and prices. We use it to set up the experiences, rates, and availability you need rather than asking you to rebuild everything from scratch.

Each experience is configured with its duration, the buffer between departures, and its maximum capacity. SwiftCove derives bookable start times inside the current 9:00 am–3:00 pm operating window. Each generated time is a separate slot, so its seats are counted separately.

Pending and paid bookings hold capacity in the selected slot. Guests see the remaining places before they commit, while you see the booking and its payment status in the dashboard.

Use an availability override when the regular generated slots should not apply. You can close an entire date, block one generated departure, or change capacity for a date or slot without changing the tour's normal duration, buffer, or capacity.

That is useful when a private charter takes the boat, a guide is unavailable, the weather forces a closure, or you want to hold places back for a group. Guests will only be shown the slots you leave available.

Yes. SwiftCove supports shared and private experiences, adult and child pricing, and per-slot capacity. The total is calculated from the guest choices inside the booking flow, so the amount shown at checkout matches the date, time, party type, and party size they selected.

A pending booking holds the selected capacity while the guest checks out. SwiftCove marks it paid after the browser returns with the exact stored O‑Pay session or after a handled paid event arrives from O‑Pay. Only the first paid transition sends the confirmation email.

SwiftCove also sends an automatic email reminder the day before departure, so guests have the details again when they need them.

The SwiftCove cancellation policy is shown as part of the booking experience. To refund a guest, open the booking in SwiftCove and follow the instructions to locate and refund the transaction manually in the O‑Pay Dashboard.

When O‑Pay sends the refund event, SwiftCove records the refund and emails the guest. Refund-event details remain dependent on O‑Pay's webhook behavior.

All card payments on SwiftCove are processed through O‑Pay’s hosted checkout. An active O‑Pay account is therefore required before your booking page can accept cards. SwiftCove does not replace O‑Pay or hold your card funds; it connects the payment result to the right booking and availability slot.

Each business uses its own O‑Pay API credentials, so payments do not fall back to a shared SwiftCove merchant account.

After choosing their date, time, and party details, the guest is taken to O‑Pay’s hosted checkout to enter card details. Card information is entered on O‑Pay’s page, not inside SwiftCove.

A matching success return gives the guest an immediate confirmation experience, while O‑Pay's paid events can confirm or reconcile the provider payment identifiers afterward.

O‑Pay handles settlement under the merchant profile connected to your business. SwiftCove does not receive or store the guest’s card details; it records the booking amount and the payment result.

Available settlement currencies, timing, fees, and bank requirements are controlled by your O‑Pay agreement. Confirm those details directly with O‑Pay before going live.

Point the Book now button on your existing website to your SwiftCove booking-page link. There is no plugin, iframe, or JavaScript snippet to paste into your site. The marketing site stays focused on your story; SwiftCove takes over when a guest is ready to choose a slot and pay.

Yes. Your SwiftCove booking page carries your logo and primary colour and has a SwiftCove booking subdomain. A custom domain can also be configured during setup, so the step between discovering the experience and paying for it feels continuous.

Yes. If you need a proper landing page for your experience business, SwiftCove can build one around your tours and booking page. It is included free for the first six months of a SwiftCove plan—there is no separate web package to buy.

The plan includes unlimited tours and bookings, a branded SwiftCove subdomain or configured custom domain, live slot availability, adult and child pricing, private or shared experiences, O‑Pay card checkout, automatic email reminders, and booking management.

There are no per-booking fees and no add-ons needed for the core booking flow. O‑Pay remains the required payment provider for card transactions.

Dashboard settings let you update the business name, public email and phone, logo URL, primary colour, and O‑Pay credentials. Tour settings cover descriptions, images, prices, duration, buffer, capacity, and whether a tour appears publicly.

Use availability overrides to close a date or slot or change its capacity. Contact SwiftCove when the booking slug or custom domain needs to change; the cancellation policy is maintained centrally and shown on every booking page.

Yes. The trial lets you test SwiftCove with your real schedule before you continue, and the monthly plan can be cancelled at any time. We would rather the system earn its place in your operation than lock you into a contract that does not fit.