NZD $149 payment-flow smoke test
Public Stripe payment-path evidence memo for small teams.
A scoped public-only check for one checkout, donation, booking, subscription, portal, or payment-link path. I inspect visible payment states, stale public URLs, buyer next-step copy, and obvious date/price drift, then return a concise evidence memo your owner or developer can act on.
What is included
- One public checkout, donation, booking, subscription, portal, or payment-link path.
- Visible payment-state checks: test-mode wording, missing payment item, stale URL, and 404 risk.
- Success, retry, and buyer next-step copy review where visible without private access.
- Stale indexed checkout, event-registration, and public product URL checks where relevant.
- A short memo with URLs, screenshots, observed issues, and handoff questions within two working days.
Input rules
Send a public URL and short product/page context. For an event, course, booking, donor, or subscription flow, include the current page plus any old public product URLs you want checked. Do not send secret keys, dashboard credentials, customer payment details, private customer data, or bank details.
Synthetic sample memo
| Check | Observation | Action |
|---|---|---|
| Checkout start | Product name, price, and buyer-facing scope are visible before payment. | Pass. Keep wording specific so the buyer knows what they are buying. |
| Return path | Success page works, but the buyer is not told what to send next. | Add a short next-step block with reply address and required inputs. |
| Stale public URLs | Old event-registration product URLs are still discoverable, but now return 404 before the buyer sees the current registration path. | Redirect retired product URLs to the current registration page or a clear closed-registration page. |
| Date and price drift | A public registration page mixes current event context with older schedule, ticket, or tax wording. | Check visible date, price, GST, and group-ticket labels against the current offer before buyers pay. |
| Public payment state | A donor, booking, portal, or subscription page visibly shows test-mode or missing-payment-item wording. | Capture the URL, screenshot, and exact buyer-facing wording so the owner or developer can confirm the Stripe/plugin state. |
| Recovery | Failed-payment retry is possible, but the page does not explain the retry state. | Add a retry note and support email. |
Boundaries
This is a public evidence memo only. It is not a fix, remediation project, security audit, PCI review, tax or accounting advice, chargeback review, legal advice, or production certification.