Trueline
Prepared for Harbour & Pine Digital
Release audit: Tidewell Bookings v2.4
Customer booking web app, pre-release check before client sign-off.
- Tested
- 10–14 November 2026
- Environment
- staging.tidewell.example
- Browsers
- Chrome 131, Safari 18, Firefox 133
- Viewports
- 1440×900 and 390×844
Summary
Not ready to release. One payment bug can charge customers twice, and a password reset link stays valid after use. Both should be fixed and retested before sign-off.
The rest of the app is in good shape: search, availability and account pages passed on all browsers. Most other findings are Safari or mobile layout issues.
2Critical
3Major
4Minor
2Notes
Fix before release
- TL-01 Double-tapping "Pay now" charges the card twice
- TL-02 Password reset link can be reused
- TL-03 Booking total ignores a removed discount code
Coverage
The 10 flows agreed at kickoff, each run on every browser and viewport above. 146 test cases in total: 131 passed, 15 failed, and those failures make up the 11 findings below.
Out of scope: load testing, penetration testing, the admin back office, and the native mobile apps.
Findings
Severity is judged by impact on your client's customers. Critical: money, data or security. Major: a flow is blocked or wrong for some users. Minor: works but looks or behaves badly. Note: worth knowing, no action needed now.
TL-01CriticalCheckout and paymentSafari 18 on iPhone 15; also Chrome with a slow network
Double-tapping "Pay now" charges the card twice
- Steps
- Add any room to the basket and continue to payment.
- Enter test card 4242 4242 4242 4242.
- Double-tap "Pay now".
- Expected
- One charge and one confirmation.
- Actual
- Two payment intents are created in the Stripe test dashboard, and two confirmation emails arrive. Reproduced 5 out of 5 times.
- Evidence
Screen recording and Stripe log screenshot go here
- Likely cause
- The button stays enabled while
POST /api/payments is pending, and the request carries no idempotency key.
- Suggested fix
- Disable the button on first submit and pass a per-basket idempotency key to Stripe.
- Regression test
test('pay now submits once on double tap', async ({ page }) => {
await checkoutWithTestCard(page);
const calls = [];
page.on('request', r => r.url().includes('/api/payments') && calls.push(r));
await page.getByRole('button', { name: 'Pay now' }).dblclick();
await expect(page.getByText('Booking confirmed')).toBeVisible();
expect(calls).toHaveLength(1);
});
TL-02CriticalPassword resetAll browsers
Password reset link can be reused
- Steps
- Request a password reset and open the link from the email.
- Set a new password.
- Open the same link again.
- Expected
- The link says it has expired.
- Actual
- The form opens and accepts another new password. The link also works after 24 hours.
- Suggested fix
- Mark the token as used on first success and give it a 1-hour expiry.
TL-03MajorBasket and discount codesAll browsers
Booking total ignores a removed discount code
- Steps
- Apply code AUTUMN10 in the basket.
- Remove the code.
- Continue to payment.
- Expected
- The full price is shown and charged.
- Actual
- The basket shows the full price, but payment charges the discounted price. The API response still includes the code.
- Suggested fix
- Recalculate the total on the server when a code is removed, and treat that as the source of truth on the payment page.
TL-04MajorCheckout and paymentFirefox 133
Card declined message never appears in Firefox
- Expected
- Using decline test card 4000 0000 0000 0002 shows "Your card was declined".
- Actual
- The spinner runs indefinitely. The console shows an unhandled promise rejection in
payment-form.js.
- Suggested fix
- Catch the rejected confirm call and show the error state.
TL-05MajorManage and cancel bookingMobile, all browsers
"Cancel booking" button is hidden behind the cookie banner on mobile
- Actual
- At 390px wide, the banner covers the button until cookies are accepted. Users who decline cookies can't cancel.
- Suggested fix
- Add bottom padding to the page equal to the banner height while the banner is shown.
TL-06MinorBookings API
GET /api/bookings/{id} returns 500 for a malformed ID instead of 400
- Suggested fix
- Validate the ID format and return 400 with an error message.
TL-07MinorBasket and discount codes
Discount codes are case-sensitive; "autumn10" is rejected
- Suggested fix
- Normalise codes to upper case before validating.
TL-08MinorRoom detail and gallerySafari 18
Gallery swipe skips every second image in Safari
- Suggested fix
- The touchend handler is registered twice; remove the duplicate listener.
TL-09MinorBooking confirmation email
Check-in date in the email uses US format for UK customers
- Suggested fix
- Format dates with the customer's locale, falling back to the property's country.
TL-10NoteManage and cancel booking
The cancellation confirmation doesn't say when the refund will arrive
- Suggestion
- Add the expected refund time, which is likely to cut support emails.
TL-11NoteBookings API
No rate limit on POST /api/auth/login
- Suggestion
- Outside this audit's scope, but worth a security review before launch.
Recommended next steps
Fix and retestFix TL-01 to TL-03, then send the new build. The retest of these findings is included in the audit price.
Lock it inTurn the 146 cases into a Playwright suite in your CI, so these bugs can't come back unnoticed.
Keep it coveredWith releases every two weeks, a retainer tests each one before your client sees it.
How this audit was done
Flows were mapped from the staging site and the read-only repository. Test cases were drafted with AI assistance, then reviewed, and run with Playwright plus manual exploratory sessions on real devices. Every finding above was reproduced by hand at least twice before it went into this report.