---
title: "Verify guest checkout sends a matching receipt without creating surprise access"
description: "Complete guest checkout with a controlled inbox and compare receipt details, order lookup behavior, and any account creation against the product guest policy."
canonical_url: "https://vostride.com/agent-library/checkout-payments/guest-order-email-consistency.md"
md_url: "https://vostride.com/agent-library/checkout-payments/guest-order-email-consistency.md"
content_kind: "recipe"
topic: "checkout-payments"
---

# Verify guest checkout sends a matching receipt without creating surprise access

Complete guest checkout with a controlled inbox and compare receipt details, order lookup behavior, and any account creation against the product guest policy.

## Risk

Guest checkout spans an unauthenticated browser, an order record, and email delivery. A receipt may have the wrong amount or expose an order lookup link beyond its documented access scope, while an implicit account can alter the promised guest experience.

## Fixtures

- A controlled guest email address with no registered account and a dedicated test inbox.
- A sandbox cart and payment fixture with a known itemized total.
- A documented guest-order lookup and account-creation policy plus order and account inspection hooks.

## Steps

1. Choose guest checkout and verify the application does not require an account password unless its declared flow explicitly creates an account.
2. Enter the controlled email, complete sandbox payment, and verify the order confirmation identifier and itemized total.
3. Retrieve the run-specific receipt and compare its order identifier, items, total, currency, and recipient with the persisted order fixture.
4. Follow the receipt order-lookup route and verify the documented email verification or link-based access behavior, including absence of unrelated orders.
5. Inspect account state and verify guest checkout created or did not create an account exactly as disclosed by the product policy.

## Expected results

- The receipt matches the completed guest order and reaches only the intended test inbox.
- Order lookup exposes the intended order under the documented guest access contract.
- Account creation behavior matches what checkout disclosed.

## False-pass traps

- A delivered email with the correct subject can still contain the wrong order details.
- An order lookup page listing all orders for an email would exceed a single-order link contract.

## Cleanup

- Cancel or refund the guest sandbox order, delete run-specific mail, and remove any disclosed fixture account.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa auth state](/docs/agent-qa/guides/auth-state.md)

- [Checkout and payment QA recipes](/agent-library/checkout-payments.md)
- [Software factory QA library](/agent-library.md)