Black Friday
Skip to documentation content

Troubleshooting

Recover a booking or uncertain payment

An interrupted browser, pending payment or missing message can leave a valid saved booking. Locate the authoritative reservation and payment evidence before retrying a charge, creating another booking or recording money manually.

An interrupted browser, pending payment or missing message can leave a valid saved booking. Locate the authoritative reservation and payment evidence before retrying a charge, creating another booking or recording money manually.

Establish the current facts

  1. Record a redacted booking code, time, selected method, currency and expected total.
  2. Find the existing booking in administration. Read its lifecycle state separately from the settled ledger and latest payment attempt.
  3. For Woo payments inspect the linked Woo order; for native providers inspect the verified original transaction and callback/reconciliation state.
  4. Check logs privately for signature, environment, amount, currency or access errors. Remove credentials, tokens, guest contacts and full provider payloads from support evidence.

Choose the matching recovery

Symptom First response
Book Now quote changed Review the refreshed selection/breakdown and submit explicitly again
Booking saved but email missing Inspect mail queue/transport; retain the same reservation
Browser return says success but payment pending Verify callback/provider evidence; query text is advisory
Latest attempt failed after an earlier settled payment Preserve the settled ledger; do not downgrade it from the last attempt
Refund response unknown Reconcile the existing reserved operation; do not create another key
Ledger unavailable Treat amounts as unknown; do not assume zero Paid or zero Balance

Respect action boundaries

Supported same-submission checkout replays can resolve the original booking, but this is not a guarantee across unrelated forms, imports or new attempts. Search first. Payment-return receipts currently expose no general Pay again action. An existing Stripe/Woo account continuation is separately guarded and never created by a read-only account GET.

Cancellation does not automatically refund. The manual refund action records a verified external outcome only; provider-shaped references and active uncertain operations cannot be bypassed by typing a manual amount. See gateway refund recovery.

Verify the repair

Reload the booking and compare status, activity, original amount/currency, settled paid/refunded amounts and any linked order. If a late payment arrives on a cancelled/no-show booking, escalate through the existing staff/refund procedure rather than reopening automatically.

Keep a recoverable backup before data/link repair. Never force a successful state by editing payment status columns or deleting ledger rows.

Was this article helpful?

Your feedback helps us improve the documentation.