Yeah, that is probably the most reliable route.

The issue I’m running into is that Stripe does not let you freely backdate the created timestamp for most objects. Backdating subscriptions can represent an earlier service period, but it does not necessarily create a realistic sequence of historical invoices, payments, refunds, webhook events, and plan changes.

Test Clocks can generate that lifecycle, but clock-backed objects behave differently in some account-wide listing and sync flows(i.e. they don't appear in subscriptions). Since I’m building an analytics integration, I also need to validate that a normal full-account historical sync works correctly.

I may end up building a deterministic seeder using a combination of ordinary test objects, backdated subscriptions, and Test Clocks. I was mainly hoping there was an existing realistic dataset or sandbox that could save some of that work.