Which connector?:
Stripe

Additional details:
We would like Fivetran’s Stripe connector to support Sync Connected Accounts / Stripe Connect for all Stripe tables, ideally with parity to what is available when using separate Stripe connectors per account.

Current situation:
We manage multiple Stripe accounts/entities (for example UK, US, DE, FR) and are evaluating whether we can use Stripe Connect plus Fivetran’s Sync Connected Accounts feature so we can maintain a single Stripe connector instead of multiple separate ones.

Current limitation:
From the Stripe connector documentation and our discussion with your team, it appears that Sync Connected Accounts currently supports only a subset of Stripe objects/endpoints. Some important objects we rely on, such as customers, are not available through this setup.

Why this matters:
We use most of the Stripe tables in Fivetran. If Sync Connected Accounts supported all tables, it would let us:
- manage one Stripe connector instead of many
- reduce connector maintenance and operational overhead
- simplify modeling and downstream transformations
- avoid additional dbt logic purely to union and normalize data from multiple Stripe connectors
- keep costs and implementation complexity lower

Requested improvement:
Please extend Stripe Connect / Sync Connected Accounts support to all Stripe tables, or as close to full parity with the standard Stripe connector as possible.

Priority objects:
Ideally all Stripe tables/endpoints should be supported, since we use most of them. If full rollout needs to be phased, customers is one clear example of an important table that should be included.

Expected outcome:
A single Stripe connector using Sync Connected Accounts should be able to replicate the same core Stripe data coverage that customers get when setting up multiple standalone Stripe connectors.