problem: merchants can disconnect xiome from their stripe account, and link another. xiome's store schema doesn't account for this, and isn't able to track customers/subscriptions/etc for the different accounts -- so currently, everything explodes.
solution: xiome needs a more sophisticated connect aparatus.
[x] all store schema is namespaced to a specific connected stripe account.
[x] the active stripe store is whichever was most recently connected. i suppose merchants need a big old disconnect button?
[x] ❔ use stripe-connect webhooks to track changes to the stripe accounts in our own database (cut down on requests)
[x] looks like we need a way to recover the disconnected stripe accounts.
the problem, is that every connected stripe account is always a new stripe account. if your account has a bunch of customers, subscriptions, etc -- we need a way to reconnect that existing stripe account?
it's possible it doesn't quite work that way -- it's possible that the stripe connect popup actually allows people to reconnect an existing account?
testing is needed to determine how stripe handles this
looks like stripe doesn't want us to authorize multiple users for the stripe account
instead they want us to use Teams in the dashboard via email
this means, in some future case, we may need to introduce an emergency switch-stripe-account feature
which means we'll probably keep the stripe account namespacing, just in case (otherwise it would make abandoning/switching stripe accounts impossible in the future)
problem: merchants can disconnect xiome from their stripe account, and link another. xiome's store schema doesn't account for this, and isn't able to track customers/subscriptions/etc for the different accounts -- so currently, everything explodes.
solution: xiome needs a more sophisticated connect aparatus.