Confirm the contract
Turn the instruction into explicit constraints. Review the size, quantity and delivered-total limit before the run.
Customer intentConfirmed constraints
COMRDY means Commerce Ready
Test the purchase.
Before the capture.
A successful payment can still be the wrong purchase. Test your AI checkout against the buyer’s instructions, then follow every decision back to the evidence.
Controlled merchant · Simulation or PayPal Sandbox
No real-money payments
COMRDY / TEST BENCHIllustrative workflow
Follow the transaction.
From customer intent to inspectable proof.
- 01INPUT
Confirmed contract
Human-reviewed purchase constraints
- 02EXECUTE
Controlled shopper
Agent actions + merchant observations
- 03CHECK
Verification gate
Every hard constraint must pass
- 04INSPECT
Evidence record
Contract, observations and decision
One contract. A traceable decision.
Workflow illustration. No live agent or payment activity.
THE CHECK BETWEEN AUTHORIZATION AND CAPTUREFollow the transaction
The verification path
One promise.
Every checkpoint.
A completed flow is only part of the story. Inspect what the shopper was allowed to buy and what the merchant actually offered.
Inside the evidence modelIntroduce a known failure
Change the variant or shipping cost in a controlled store. Follow versioned observations through the transaction.
CheckoutFinal merchant state
Inspect the decision
Compare the final state with the original contract. A missing hard constraint cannot become a pass.
Deterministic checkAllow / review / deny
Payment boundary
Authorization is a step.
Capture needs evidence.
The Sandbox path rechecks the confirmed contract before capture. Inspect the test verdict, authorization, capture and merchant order as separate facts.
Read the payment contract01Buyer approvalPayPal authorization
02COMRDY checkAll hard constraints must pass
03Capture or stopPreserve the outcome and evidence
Local simulation makes no PayPal API calls. Each run displays its environment.
An executable readiness bench
Go beyond
the happy path.
A changed quantity. A missing total. A stale authorization. Run the real verification engine against a bounded suite, inspect every failed rule, and export a reproducible report.
Run the constraint suite Deterministic synthetic cases. No payment or AI calls.01Purchase intent
Item · size · quantity · subscriptions
02Delivered cost
Budget boundary · shipping · currency
03Evidence & bindings
Inspect the evidence workbenchMissing facts · stale state · authorization
Start with a controlled failure
Find the first divergence.
One controlled store. A reproducible suite. An inspectable decision.