Black Friday
Skip to documentation content

Pricing, Payments & Tax

Configure native PayPal Checkout

Pro's native PayPal method uses its own payment owner and callbacks. It is separate from choosing a PayPal gateway inside WooCommerce Checkout, which remains WooCommerce-owned.

Pro’s native PayPal method uses its own payment owner and callbacks. It is separate from choosing a PayPal gateway inside WooCommerce Checkout, which remains WooCommerce-owned.

Configure the intended environment

With compatible Free and entitled Pro, open Hotel Booking Payment Settings. Select PayPal, choose Sandbox first and save the matching Client ID, Client Secret and Webhook ID. The webhook ID identifies the configured destination; it is not the client ID or secret.

Use the exact callback/webhook URL supplied by the current installation. Ensure the provider can reach it over the site’s intended public HTTPS origin and that cache/security middleware does not replace its response. Keep sandbox and live credentials and webhook identities separate. The supported currency also depends on the configured adapter and merchant account; verify an actual sandbox quote rather than assuming all currencies work.

Test the booking journey

  1. Create a synthetic reservation and choose native PayPal.
  2. Review the final quoted amount, currency, services, discount and taxes.
  3. Complete PayPal approval/payment and return to the hotel site.
  4. Verify the authoritative transaction and settled booking ledger, plus webhook delivery separately.
  5. Test a browser cancellation, pending response and delayed callback without creating a replacement reservation immediately.

An approved browser return or success parameter is not payment evidence. A browser cancellation is advisory and can leave an attempt pending. Supported receipt layouts can use bounded refresh for an in-flight PayPal attempt, but current payment-return output supplies no general Retry/Pay again action. Account detail also introduces no new PayPal continuation.

Refunds and recovery

Native capture-owned PayPal payments can enter the separate staff-approved gateway refund workflow after account, environment, balance and original-source readback. Cancellation itself does not dispatch it. A WooCommerce-owned PayPal payment must never be passed to this native adapter.

If a response is uncertain, reconcile the existing operation/attempt and inspect verified provider evidence. Do not use a pasted provider ID as manual financial proof or mint a second refund to replace a timeout. Protect guest access links, complete payloads and merchant credentials in every support report.

Was this article helpful?

Your feedback helps us improve the documentation.