---
title: Checkout and 3D Secure on your domain
description: When your site takes payment with Stripe, the entire booking flow runs on your own domain. Search, the quote, the checkout form, the payment itself, and…
url: "https://homerunner.io/docs/does-the-booking-flow-stay-on-my-own-domain-including-the-3d-secure-step/"
updated: "2026-10-26"
category: Booking engine and checkout
---

# Checkout and 3D Secure on your domain

When your site takes payment with Stripe, the entire booking flow runs on your own domain. Search, the quote, the checkout form, the payment itself, and the booking confirmation page are all served by your website.

**How payment works with Stripe.** Your guest enters and confirms their card on the checkout page. When a card requires a 3D Secure challenge, the challenge appears in a secure Stripe window on the same page, so the guest is not sent to another site. After payment succeeds, the guest goes to the confirmation page on your domain. That is where booking-completion events fire.

**When guests leave your domain.** Two setups send the guest off-domain. If your account is configured for a hosted checkout, the guest is handed off to the payment provider's own page to finish paying. This hosted checkout is the fallback for gateways other than Stripe. Guests paying through GuestyPay are sent to a separate authentication page when 3D Secure is required.

**If you track completed bookings.** If tracking completed bookings matters to your strategy, ask your HomeRunner contact to confirm that your account uses Stripe with the hosted-checkout fallback switched off.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.
