Pro can execute staff-approved refunds for supported payment owners. This workflow is separate from the ledger-only manual refund action and does not automatically run when a booking is cancelled or marked no-show.
Check readiness and ownership
Use payment-management permission, a verified cancellation/refundable entitlement and the original settled payment. Check payment versus refund compatibility before proceeding. Native PayPal and native Stripe use their owner adapters. WooCommerce-owned payments use only the WooCommerce owner and its exact refund allowlist; OTA-owned payments have no Hotel Booking gateway operation.
Open Hotel Booking → Gateway Refund Operations. New operation creation defaults OFF. A settings manager must explicitly enable it for this installation; LIVE provider calls have a separate opt-in. Enablement is bound to home URL, site URL, environment and blog ID. A copied database requires new authorization rather than inheriting permission to refund.
Preview, then confirm
- Inspect the booking’s saved decision, settled ledger, previous refunds and active operations.
- Select Preview refund via gateway. Preview reads provider evidence but does not dispatch a refund; it saves a ten-minute approval snapshot bound to the staff actor.
- Review the exact source payment, amount, currency, account and environment.
- Use Confirm refund … — MODE only for the intended result. Expired or changed evidence requires a fresh preview.
Confirm rechecks the complete snapshot. A durable operation, reserved amount and idempotency key are saved before dispatch. Duplicate confirmation resolves the same submission identity instead of inventing a second operation.
Recover an uncertain result
If the provider times out or the result is unknown/requires action, retain the existing operation and reserved refund capacity. Use its explicit refresh/reconcile action to read the outcome; refresh does not create a replacement key or a new refund request. Do not bypass the reservation with Record external/manual refund.
Only verified provider outcomes affect settled financial history. Manual recording remains for completed external events and is guarded against active operations, duplicate references and unverified provider IDs. A response failure is not proof that the provider sent no money.
Turning new-operation creation off stops new commands, but existing reconciliation and correction notifications remain active. Review queued corrections or reversals with the ledger. Customers receive semantic progress labels rather than provider/account identifiers.
Run the full preview/confirm/reconcile procedure on disposable sandbox data before live use. Credentials, real provider delivery and bank settlement require separate evidence; source or offline tests cannot establish them.
