Where does your agent checkout break?
A checkout PASS needs observed behavior and recovery evidence. The free self-check records your merchant evidence for each case; the €29 test kit adds an offline shop fixture with seven transaction cases.
For merchant staging and sandbox checkouts. Production observation stops before purchase.
Use your staging checkout UI. Capture visible cart, account and challenge steps. Record the browser and agent build. Production observation stops before purchase.
Entries stay in this browser tab. Export to keep them before closing or reloading.
Record a case. Keep its evidence.
PASS needs observed behavior and recovery. Leave incomplete cases as NOT TESTED.
Merchant and environment details
Capture visible availability before and after the stock change.
Use your merchant evidence. This form does not visit your store.
Stale stock
This case is NOT TESTED.
Your route report
All cases start as NOT TESTED. Record your observations above.
| Case | Verdict | Evidence |
|---|---|---|
| Stale stock | NOT TESTED | Awaiting merchant evidence |
| Repricing | NOT TESTED | Awaiting merchant evidence |
| Expired session | NOT TESTED | Awaiting merchant evidence |
| Repeated submission | NOT TESTED | Awaiting merchant evidence |
| Payment decline | NOT TESTED | Awaiting merchant evidence |
| Shipping / tax change | NOT TESTED | Awaiting merchant evidence |
| Human handoff | NOT TESTED | Awaiting merchant evidence |
| Forced account | NOT TESTED | Awaiting merchant evidence |
| Challenge | NOT TESTED | Awaiting merchant evidence |
| Human approval | NOT TESTED | Awaiting merchant evidence |
| Recovery | NOT TESTED | Awaiting merchant evidence |
Export includes the selected route and its merchant records. Other routes keep separate case records in this tab.
A checkout failure is only half the test.
The kit’s synthetic shop deliberately breaks seven transaction cases. Each has a fixed mode with a recovery path.
I ran every case in both modes over local HTTP. All seven unsafe behaviors were detected. All seven fixed cases passed recovery or safe retry.
The runner passed 92 assertions. These results cover the original fixture. Merchant stores, browser execution and ACP/UCP integrations were outside that run.
| Case | Broken | Fixed |
|---|---|---|
| Stale stock | FAIL | PASS |
| Repricing | FAIL | PASS |
| Expired session | FAIL | PASS |
| Repeated submission | FAIL | PASS |
| Payment decline | FAIL | PASS |
| Shipping / tax change | FAIL | PASS |
| Human handoff | FAIL | PASS |
FAIL means unsafe behavior was observed. The ZIP includes the runner, HTTP traces and completed report.
Paste this into your agent
Fetch https://lab.anonyfox.com/agent-checkout-check/index.md and checks.json; ask me for my checkout route and staging evidence, then record PASS / FAIL / NOT TESTED for each case.Agent checkout test kit
Rehearse the failures locally. Then use the same evidence record in your staging checkout.
- README.md, kit/procedure.md and kit/procedure-a4.pdf
- Evidence schemas and blank CSV/JSON records (kit/evidence-*.json, kit/evidence-template.*)
- kit/merchant-prompts.md for browser and protocol paths
- Offline Node shop (kit/fixture/shop.mjs) with seven broken and fixed cases
- expected-results.md, example reports, and the recorded fixture traces in tests/
Run the fixture with Node.js 18 or newer. It has no npm dependencies and runs offline. Includes browser and protocol procedures, screenshot instructions and a manually released source matrix.
€29
One-time payment.
- README.md, kit/procedure.md and kit/procedure-a4.pdf
- Evidence schemas and blank CSV/JSON records (kit/evidence-*.json, kit/evidence-template.*)
- kit/merchant-prompts.md for browser and protocol paths
- Offline Node shop (kit/fixture/shop.mjs) with seven broken and fixed cases
- expected-results.md, example reports, and the recorded fixture traces in tests/
The ZIP agent-checkout-check-v1.0.zip is attached to the confirmation email after payment. Start with README.md.
Digital content: § 356 Abs. 6 BGB; details in Withdrawal and Terms.
Buy the kit · €29No VAT is charged under § 19 UStG (German small business regulation).
You run the cases in your own environment and retain the evidence.
Keep the route attached to the result.
Shopify’s cart and checkout guide describes cart, checkout and human continuation. Use the actual negotiated version and record your platform access.
For custom implementations, use the UCP checkout specification or ACP seller guide for your route. The fixture rehearses state changes through original endpoints.
Stripe’s agentic commerce guide separates builder and seller routes; availability varies by integration. Record observed challenges alongside merchant settings using Cloudflare’s detection guidance.
Before you run the cases
What does PASS mean?
Your recorded observation and recovery match the expected behavior for that case, route and environment. Each PASS needs evidence. Unrun or incomplete cases stay NOT TESTED.
Does the fixture implement ACP or UCP?
The fixture uses original HTTP routes to rehearse transaction state and recovery. For a protocol run, use your merchant implementation and record the negotiated version and platform eligibility.
Can I use this on production?
Observe production only up to the purchase boundary. Run failure injection, payment attempts and completion in your staging checkout or sandbox.
How do I receive the paid kit?
The ZIP arrives by email within 24 hours after payment at the address used at checkout. Stripe sends the receipt separately.
Merchant checkout evidence report
A product page must be reachable before an agent can evaluate its checkout path. Run the AI crawler access check first, then inspect readable product facts through the AI visibility audit workflow. If an agent will modify the purchase integration, use the coding agent security review to check its permissions and secret handling. The agent-ready site prompt helps turn these findings into a focused implementation task.