#.iameugene
boreal vigilBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- eugene-connect-accountproperties, 1 day ago, 13 messages
- .iameugene, 1 day ago, 4 messages
- .iameugene, 1 day ago, 5 messages
- iameugene-destination-charge, 3 days ago, 13 messages
sterile otter
If you're using express/custom, you likely want to create an account for users that have standalone stripe accounts already anyways, using existing standard accounts would be a fairly different experience/flow.
The legacy oauth flow for standard accounts does this, yes, but thats not recommended and you wouldn't be able to automatically route from that to your express/custom pattern.
What are you trying to achieve, exactly?
flat shale
In our flow, we publish digital products ourselves (as a platform), and sellers only receive compensation (via transfer_group). We also cover all transaction fees. Let's consider a scenario where a seller is already publishing similar digital products elsewhere (like Patreon/Gumroad) and wants to connect their existing account to our platform to receive commissions from selling their products on our marketplace. We can create a new account for them and request verification during the payout stage. However, I'm confident that users in such a situation would wonder: why do they need another account and go through verification again if they already have a different Stripe account connected to another platform that pays them? Such users would prefer to have all their earnings in one account...