Black Friday
Skip to documentation content

Security & Privacy

Protect payment secrets and webhooks

Pro owns native online-payment credentials and provider integrations. Core owns booking/ledger integrity. Themes present authorized output and must not expose secrets, decide settlement or implement their own capture/refund workflow.

Pro owns native online-payment credentials and provider integrations. Core owns booking/ledger integrity. Themes present authorized output and must not expose secrets, decide settlement or implement their own capture/refund workflow.

Protect each owner and environment

Use the intended native Stripe/PayPal/MoMo settings or the separate WooCommerce gateway configuration. Keep sandbox and live credentials, webhook identities, merchant accounts and endpoint origins consistent. Native credentials do not configure a Woo gateway, and Woo-owned payments must not be routed through a native refund adapter.

Pro stores native payment credentials encrypted. Restrict payment-settings and refund-operation privileges, keep protected configuration/backups private, and never copy full keys or signed payloads into public diagnostics. A key masked in administration must not be assumed absent or usable on a clone.

Treat callbacks as financial evidence only after verification

The relevant provider owner verifies authenticity/signature, event/source identity, merchant/environment, amount and currency before applying a financial outcome. Browser success/cancel text, an initiated attempt, a Woo order status or a boolean response is not sufficient evidence.

Duplicate or out-of-order events should reconcile to existing transaction identities instead of creating another ledger application. A latest failed attempt must not erase settled money. Payment callbacks use saved booking financial amounts rather than current room prices or tax rules.

Stripe’s secure form/client secret belongs on its authorized payment step; confirmation reads verified state. A theme must preserve the owner’s form hooks without moving secret payment data into public page markup, logs or ordinary hotel fields.

Refund execution has separate safeguards

Gateway refund creation defaults OFF for an installation, with LIVE calls separately enabled. Preview/confirm checks the original source and current financial facts. An unknown operation retains capacity; use its reconciliation action instead of a replacement key or manual bypass.

Woo automatic refunds have a narrow exact allowlist, unlike the broader compatible Woo payment bridge. MoMo collection does not imply a native MoMo refund-execution adapter. See payment/refund compatibility.

Diagnose and contain

Check provider delivery results, callback reachability, stored attempt state and saved amount/currency privately. Redact guest details, tokens, complete URLs, signatures and raw provider responses. Use a controlled sandbox for replay/recovery; never replay an arbitrary live payload against production to test a theory.

For exposed credentials, coordinate the owning provider’s rotation and verify callbacks afterward. Do not rotate WordPress salts as an undocumented single-purpose payment fix; it affects broader installation security context.

Was this article helpful?

Your feedback helps us improve the documentation.