Checkout Release QA Bench
Checkout Release QA Checklist for Digital Downloads
Before a release, trace a test checkout through signed payment evidence, the correct variant and a buyer download. Reload and retry scenarios should preserve one paid order and one intended delivery effect.
Worked example
| Synthetic case | Expected evidence | Decision |
|---|---|---|
| One paid order and two page loads | One order and one delivery effect | Pass |
| Declined payment | No paid order or file delivery | Pass |
| Paid receipt but wrong file revision | Download differs from release manifest | Hold |
Hold release until the exact variant delivers the expected file revision. Repeat the checkout in a fresh browser and verify the attachment.
How to run the check
- Record the provider environment, test order, variant ID and expected file revision.
- Run paid, declined and repeat-delivery fixtures using provider test mode.
- Open the buyer receipt and download the file. Compare it with the release manifest before signing off.
A sandbox checkout does not prove live settlement, real receipt delivery or a live merchant account. Keep test records separate.
Can the thank-you page clear the release gate?
Reconcile the signed order event and inspect the actual file delivered to a buyer. The page is only one observation.
Reference: Lemon Squeezy test mode documentation