---
title: "Verify successful checkout creates one matching paid order"
description: "Complete a sandbox purchase and reconcile the confirmation page, order history, payment record, and reserved inventory for one uniquely identified order."
canonical_url: "https://vostride.com/agent-library/checkout-payments/successful-order-reconciliation.md"
md_url: "https://vostride.com/agent-library/checkout-payments/successful-order-reconciliation.md"
content_kind: "recipe"
topic: "checkout-payments"
---

# Verify successful checkout creates one matching paid order

Complete a sandbox purchase and reconcile the confirmation page, order history, payment record, and reserved inventory for one uniquely identified order.

## Risk

A checkout confirmation can be optimistic, duplicated, or detached from the payment actually collected. Matching stable identifiers and independent monetary values prevents a persuasive success page from concealing an unpaid or wrongly scoped order.

## Fixtures

- A test-owned customer and a sandbox product with known price, tax rule, shipping rate, and sufficient inventory.
- A provider-supported successful test payment method and an independently calculated expected total.
- Hooks reading order, payment, and inventory reservation records for the unique run marker.

## Steps

1. Add the fixture product and open checkout; verify item identifier, quantity, unit price, shipping option, tax, currency, and grand total against the fixture expectation.
2. Enter the test-owned shipping and billing details and verify the final review reflects the intended address and delivery method.
3. Complete payment once with the sandbox success method and verify the confirmation shows a stable order identifier and paid or documented processing status.
4. Open order history and reload its detail page; verify the same order, items, amount, and address persist.
5. Run reconciliation hooks and verify one order, one successful payment for its exact total, and the expected inventory reservation.

## Expected results

- The order identity is consistent across confirmation and account history.
- The sandbox payment amount and currency match the independent expected order total.
- Inventory is reserved once for the purchased quantity.

## False-pass traps

- A thank-you heading alone does not prove settlement or durable order creation.
- Counting all sandbox payments rather than filtering by the run-owned order can match an unrelated transaction.

## Cleanup

- Cancel or refund the sandbox order through the fixture workflow and release its inventory reservation.

## 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)