Black Friday
Skip to documentation content

Pricing, Payments & Tax

Understand payment, refund and reconciliation ownership

Payment collection and refund execution have different compatibility boundaries. A method that can collect booking money does not automatically support a staff-initiated refund, and a booking cancellation does not automatically send funds.

Payment collection and refund execution have different compatibility boundaries. A method that can collect booking money does not automatically support a staff-initiated refund, and a booking cancellation does not automatically send funds.

Payment versus refund compatibility

Payment source Booking payment path Refund execution from Hotel Booking
Pay at hotel Free offline reservation; record actual receipt No provider execution; record verified external return
Native PayPal Pro native Checkout/capture Staff-approved native PayPal owner after source/account/environment readback
Native Stripe Pro payment step Staff-approved native Stripe owner after PaymentIntent/Charge readback
Native MoMo Pro VND redirect/IPN No native MoMo refund-execution adapter in this baseline
WooCommerce Checkout Pro bridge to an installed compatible Woo gateway Woo owner only; exact allowlist below, never a native adapter bypass
OTA/external payment External platform owns payment No Hotel Booking gateway operation

All provider operations require their actual feature, source, entitlement and operational checks. The installation-local new-operation switch defaults OFF; LIVE calls need separate opt-in. Neither installation nor a sandbox test authorizes live refunds.

Exact WooCommerce automatic refund allowlist

The current bridge accepts WooCommerce 11.1.1, WooCommerce PayPal Payments 4.1.3, gateway ppcp-gateway, PayPal sandbox, USD, and HPOS. It also requires an exactly linked Hotel Booking order/settled Woo transaction, one PayPal order, one purchase unit and one captured payment, with matching amount and currency and the expected order shape.

Other versions, live mode, currencies, legacy order storage, mixed orders, multiple captures and other gateways are outside this automatic refund path. A gateway’s generic “supports refunds” flag is insufficient. This narrow allowlist limits refund execution, not every booking-payment use of WooCommerce Checkout.

Reconcile evidence, not labels

Verified callbacks and provider readback can settle or correct ledger facts. A browser return, Woo status change, boolean success, unknown response or accepted request alone is not proof of returned money. Webhook duplicates and out-of-order events must converge on the existing payment/refund identity rather than create duplicate entries.

Unknown/requires-action operations retain reserved capacity. Use the existing operation’s reconcile-only refresh; do not create a new key or bypass it with a manual refund. Record external/manual refund is ledger-only and subject to guards. Provider-shaped IDs need verified reconciliation.

If a refund is corrected or reversed, review its ledger application and the queued admin alert. Turning new-operation creation OFF does not disable existing recovery/notification handling. Actual sandbox dispatch, callback delivery and bank settlement need integration evidence separate from offline tests.

See gateway refund operations for the preview/confirm procedure.

Was this article helpful?

Your feedback helps us improve the documentation.