In Revenue Cat Web billing, we're seeing single Revenue Cat customers generate multiple stripe customerIds.
After messaging support, it seems that might be a known issue? If so my feature request would be to capture stripe customer IDs in the RC Web Billing flow (i.e., purchases-js Web SDK?) and pass that through to stripe to prevent multiple stripe customers from being created.
This isn’t a problem if you’re using Stripe as the payment processor. Nor is it a problem if you’re using subscriptions. But if you have multiple products (e.g., consumables) then a few issues arise from the current behavior: (1) stripe customers proliferate and can’t be merged (2) vendor lock-in since RC is then the only source of truth that consolidates customer accounts and (3) there’s no possibility to store and reuse customer CC information adding friction to the user UX.
To be clear, what I’m proposing is something like:
```
const ret = await purchases.purchase({
rcPackage: pkg,
stripeCustomerId: xxx
});
```
