In plain English
- Every run stops before the final payment step by default — this cannot be overridden outside a sandbox.
- Card entry uses processor test cards and sandboxes only (e.g. Stripe 4242 4242 4242 4242, Adyen test platform).
- We never ingest real card numbers (PAN).
- Gemini computer use requires a human confirmation at payment steps; we honour it.
1. Why
Payment providers prohibit live-mode testing (for example Stripe’s Services Agreement), and agent vendors require human confirmation for irreversible actions. A test that buys something is not a test.
2. How a checkout cell ends
- Outside sandbox: the agent reaches the payment page, records it, and stops. The cell passes if it got there.
- In sandbox: the agent may submit processor test cards; results are recorded.
- Commit mode (irreversible steps) requires an Approver’s signature on the Test Authorization.
3. Note for your QSA
alt.qa does not inject scripts into payment pages and does not handle cardholder data. Relevant to PCI DSS v4.0 requirements 6.4.3 (payment-page script management) and 11.6.1 (change detection) — our agents interact through a normal browser like any visitor.
This document is provided for transparency. Where a signed order form or master agreement exists, it controls. Previous versions are available on request.