Black Friday
Skip to documentation content

Pricing, Payments & Tax

Configure native Stripe payments

Pro's native Stripe method places the secure payment step between Book Now and booking confirmation. Creating a reservation or initializing a PaymentIntent does not by itself mean the booking is Paid or Confirmed.

Pro’s native Stripe method places the secure payment step between Book Now and booking confirmation. Creating a reservation or initializing a PaymentIntent does not by itself mean the booking is Paid or Confirmed.

Configure credentials and callbacks

With compatible Free and entitled Pro, open Hotel Booking Payment Settings and select Stripe. Choose Test mode first and save matching Publishable Key, Secret Key and Webhook Signing Secret. Test keys and live keys must match the selected mode; the endpoint signing secret belongs to the configured webhook destination.

Use the webhook URL and event instructions supplied by the current installation. The destination must be publicly reachable at its intended HTTPS origin. A dashboard destination marked Active is not proof that WordPress credentials were saved or that a booking event was processed. Do not paste secret keys into public page content, screenshots or logs.

Verify the payment journey

  1. Search a synthetic stay, choose Stripe on Book Now and review all final charge lines.
  2. Submit the form. If the coordinated quote changed, review the refreshed amount and click again.
  3. Complete the secure Stripe payment step, including additional authentication when requested.
  4. Inspect the returned result and compare its payment state with the authoritative stored transaction/ledger.
  5. Verify callback delivery separately; test an unsuccessful attempt, cancellation and delayed result as well as success.

The theme must preserve the secure form’s required integration hooks. An empty or permanently loading form can indicate blocked assets, configuration or incompatible markup; it is not a reason to collect card details in an ordinary hotel form.

Continue and refund boundaries

Current payment-return receipts do not expose a general Retry/Pay again action. An owned account detail can show an existing Stripe continuation only when stored booking, balance, amount/currency and attempt checks allow it. Loading that account page does not initialize or reconcile a new payment.

Native Stripe-owned payments can use the separate staff-approved gateway refund operation. Refund-related webhooks and reconciliation require verified source identity; cancellation alone does not execute a refund. WooCommerce Stripe payments remain Woo-owned and are outside the current Woo automatic refund allowlist.

If payment is uncertain, preserve the booking and attempt, inspect verified evidence and use supported recovery before requesting another charge. Browser success text is never the settlement authority.

Was this article helpful?

Your feedback helps us improve the documentation.