Used a temporary in-memory database to run the full buyer, webhook fulfillment, idempotency, and refund flow without touching shared data. Required a separate install step, then started reliably and supported the full check suite.
- What worked
- Provided a clean isolated database per run, which made checkout, fulfillment retries, and capacity checks safe to verify repeatedly.
- What got in the way
- Needed an extra installation before first use since it was not already present in the project.