PRIVATE / NOINDEX — HOSTINGER TEST PAYMENT BOOKING TEST

End-to-end booking test, no real charge.

This page exercises the real estimate-save, real availability and real Hostinger hosted-checkout paths using a clearly-marked TEST estimate. It uses Hostinger’s built-in Test payment method(enabled by the owner in the store dashboard) — not Stripe test mode. The Test payment method completes the hosted checkout without a real card and without a real charge. It does notopen public live bookings — those stay paused. This is a platform test payment only; it is notproof that Stripe or any live card processor works.

Public live reservations: PAUSED · Hostinger Test payment only · 0 passed · 0 failed · 12 untested

Automated test attempt — 2026-10-25

An automated test was run against the live Hostinger store API (real GET/POST calls, not a simulation) using the Hostinger Test payment path. It verified the estimate-to-checkout plumbing up to the hosted checkout URL. Completing the Test payment and verifying the appointment, Google Calendar sync and email delivery could not be completed in this environment — those need a human browser on the hosted checkout page and store-dashboard/inbox access the automated test does not have. This is aHostinger Test payment attempt only; it is not proof that Stripe works.

Verified by the automated test (real evidence)

  • 4 booking products exist in the store, all purchasable, each priced at $75 (7500 cents), each carrying its own booking event/calendar (2-Mover, 3-Mover, 4-Mover, 4 Movers + 2 Trucks).
  • Live availability returned 59 available days in America/Chicago; first available day 2026-10-26 with 5 time slots (sample 2026-10-26T08:30:00 America/Chicago).
  • Real Hostinger hosted checkout URL generated (HTTP 200) at checkout.hostinger.com, carrying the selected slot, the America/Chicago time zone, and the $75 2-Mover Crew variant at quantity 1.

Blocked — not completable in this environment

  • Completing the Test payment on the hosted checkout page — Hostinger’s hosted checkout is browser-driven and there is no API to complete a checkout session with the Test payment method. Requires a human browser.
  • Confirming exactly one Hostinger appointment is created and linked to the saved estimate — requires a completed payment plus store-dashboard inspection; there is no public appointment-list API.
  • Google Calendar sync with the correct America/Chicago date, time and 2-hour duration — a store-dashboard setting the public API cannot read.
  • Customer and business confirmation email delivery — requires a completed payment plus inbox access the automated test does not have.

To finish the test, run Steps 1–4 below in this browser: create a test estimate, pick a real window, generate the checkout URL, then open it and complete the order with the built-in Test payment method. Record what you observe in Step 5. Public live bookings and payments stay paused.

Step 1 — Create a test estimate

Creates a real moving_estimates record (name prefixed “TEST —”) with a private access key. This is the same save path the live booking flow uses, and it fires the PocketBase hook that sends the customer estimate email. Use your own email so you can confirm delivery.

Step 2 — Pick a real arrival window

These dates and times come from the live store availability API for the selected crew’s booking event, in America/Chicago. This is real availability, not sample data. Pick a window to use for the test checkout.

04 / YOUR TIME, YOUR MOVE

Find your moving window.

Preferred date: . The windows below are an availability preview while online reservations are paused.

The two-hour appointment is a scheduling placeholder — it reserves your crew and arrival window, not your total moving time. Your crew stays for the full job and the balance is settled on actual time worked. The time below is your arrival-window start; allow 30 minutes for arrival.

Choose your date

No available dates in the next 60 days. Save your estimate below and call (832) 779-2681 to arrange a window.

Choose your arrival window

No daytime moving windows are available on this date. Choose another day, refresh, or call (832) 779-2681. The Houston crew calendar may still be getting set up.

All dates and times are shown in Houston time (America/Chicago). Only 7 AM–19 PM arrival starts are offered.

Step 3 — Generate the test checkout URL

Calls the real initializeCheckout with the selected slot and the Labor-Only — 3 Movers variant. The returned URL is a real Hostinger hosted-checkout page. On that page, choose the built-in Test payment method to complete the order without a real card or charge. No Stripe test-mode confirmation is required for this test.

Choose an arrival window in Step 2 first.

Step 4 — Run the test on the hosted checkout

Open the checkout URL from Step 3. On the hosted checkout page, select the built-in Test payment method (enabled in the store dashboard) and complete the order. Do not enter a real card. No Stripe test card is used here — this is the Hostinger platform Test payment method, not Stripe test mode.

  1. Open the test checkout URL from Step 3.
  2. On the hosted checkout page, choose the Test payment method as the payment option.
  3. Complete the order. You should be redirected to /checkout/success with no real charge.
  4. Check the store dashboard: exactly one appointment exists for the test slot, on the selected crew’s calendar, with the correct America/Chicago date/time and 2-hour duration.
  5. Check the connected Google Calendar: the appointment appears with the same date/time/duration.
  6. Confirm the store receipt (booking confirmation email) reached the customer inbox.
  7. Repeat the checkout for the same slot from a fresh URL and deliberately double-click reserve: confirm only one order and one appointment result.
  8. Generate a new checkout URL for a different slot and abandon the hosted checkout (do not complete payment): confirm no appointment is created, no confirmation email is sent, and the slot stays available.

Step 5 — Record the observed results

Mark each check based on what you actually observed. “Code-verified” items are guaranteed by the site code (already inspected on /booking-verify); confirm them with the live test anyway. “Live” items can only be confirmed by running the test. “Dashboard” items are store settings the public API cannot read. Every result below reflects the Hostinger Test payment method only — it is not evidence that Stripe works.

  • Test estimate saved to PocketBase. A moving_estimates record was created with a TEST marker and a private access key. Verifies the estimate-save path the real booking flow uses.Live test
  • Customer estimate email delivered. The PocketBase after-create hook sends an estimate email to the customer address on the record. Use your own email so you can confirm receipt.Live test
  • Business notification email delivered. Only sent when BUSINESS_NOTIFICATION_EMAIL is set in the PocketBase environment. If unset, this stays untested until the owner configures it.Live test
  • Hosted checkout URL generated. initializeCheckout returned a real Hostinger hosted-checkout URL carrying the selected time_slot and America/Chicago time zone. The Test payment method appears on that hosted page as a payment option.Live test
  • Checkout completed using the Hostinger Test payment method (no real charge). On the hosted checkout page, select the built-in Test payment method and complete the order. No real card and no real charge should occur. Confirm you are redirected to /checkout/success. This is a platform test payment only — it does not exercise Stripe.Live test
  • Exactly one $75 deposit line on the order. Checkout sends one item at quantity 1. Confirm the order/receipt shows a single $75 line, not two. (Code sends quantity:1; the charge itself is owner-verified.)Live test
  • One Hostinger appointment created and linked to the estimate. A successful booking payment creates exactly one appointment on the crew calendar. Confirm in the store dashboard that one (not zero, not two) appointment exists for the test slot, and that it references the test estimate (via the ref passed in the success URL).Live test
  • Appointment appears in Google Calendar with correct America/Chicago date, time and duration. Google Calendar sync is a store dashboard setting. Confirm the test appointment appears with the right date, time and the 2-hour event length in the connected Google Calendar.Requires dashboard
  • Booking confirmation email/receipt delivered. The store receipt is the booking confirmation. Confirm it reaches the customer after a successful Test payment. This site does not self-confirm from the success URL.Live test
  • Repeated clicks produce no duplicate appointment or charge. The reserve button is disabled while a submission is in flight, and re-submitting updates the existing estimate record rather than creating a new one. Confirm only one order and one appointment result after deliberate double-clicking.Code-verified
  • Abandoned/cancelled checkout produces no confirmed booking. Cancel out of the hosted checkout (or do not complete payment). Confirm no appointment is created, no confirmation email is sent, and the slot remains available. The /checkout/cancelled page leaves the estimate intact and charges nothing.Code-verified
  • Hostinger built-in Test payment method is enabled in the store dashboard. A store dashboard setting the public API cannot read. The owner has enabled it. Confirm it still appears as a payment option on the hosted checkout page before relying on this test.Requires dashboard

What this test can and cannot prove

Real and verifiable here: the estimate-save path, the estimate email hook, the live availability API, and the real hosted-checkout URL generation. These exercise the actual PocketBase and Hostinger store plumbing — not a simulation.

Hostinger Test payment only — not Stripe proof. The Test payment method is a platform test payment that completes an order without a real card or charge. It proves the estimate-to-appointment checkout plumbing works end to end. It does not prove Stripe is connected, approved, or able to process a real card payment. Stripe live payments remain unverified until Stripe is separately connected, switched to live mode, and tested with a real card. Do not enable live payments based on this test alone.

Owner-verified only: the actual appointment creation, Google Calendar sync, and confirmation-email delivery. These only happen on a completed checkout, and whether the Test payment method is available on the hosted checkout page depends on the store dashboard setting the public API cannot read. If the Test payment method does not appear on the hosted checkout page, this test cannot complete — confirm it is enabled in the store dashboard and re-run.

Emails: the estimate email is sent by the PocketBase hook on record create — verifiable from Step 1. The booking confirmation email is the store receipt, sent by the platform after a completed checkout — verifiable only from Step 4. The business notification email requires BUSINESS_NOTIFICATION_EMAIL to be set in the PocketBase environment.

Public live bookings and payments remain paused. Do not set liveReservations,livePayments or paymentProviderConnected to true until the Hostinger Test payment test above passes AND a separate Stripe live test is run. Call (832) 779-2681 with questions.

Call (832) 779-2681Get an estimate