Acceptance test plan and checklists for a web service

We are preparing to accept a new version of our web service from a contractor and need an independent QA specialist to build a proper acceptance test plan for it. The service has registration, a user cabinet, a catalogue with filters, an order form and a payment step. We do not want a vague summary; we want a document we can hand to any tester and get repeatable results, and a clear verdict on whether the release can go live.

The deliverable is a test plan plus a set of checklists broken down by area, where each item names the scenario, the exact steps, the expected result and the pass criterion. Critical user paths — sign up, place an order, pay, receive confirmation — must be covered end to end, including negative cases such as wrong input, an expired session and a declined payment. Alongside the checklists we need a defect report: every issue found described with steps to reproduce, severity, and screenshots where they help.

Please run the checklists against the live staging build, not just design them on paper, and mark each item as passed, failed or blocked. We value testers who think about boundary values, mobile layout and accessibility, and who separate a real defect from a matter of taste. The result should let us decide, with evidence, whether to accept the work.