#shimmyshadow
1 messages · Page 1 of 1 (latest)
For A. I don't see any reason that wouldn't work. That should be totally fine.
As for #2: this sounds exactly like Separate Charges and Transfers https://stripe.com/docs/connect/charges-transfers
You can accept charges as the platform account, then create a Transfer from your platform's balance to any number of other Connect accounts that your platform controls
ok, a follow up question, the transfer will be to the users of the websites, and it will be a fixed amount (let's say 5 USD), do we need the strong authentication of the user, b efore we send them those 5 bucks?
They will need to have a fully verified Connect account, which includes adding a lot of sensitive details and other KYC information before they can pay out to their bank
ok so basically, every user, who wants to receive the 5 dollars per transaction payment will need to go through the full verification and KYC information flow, otherwise, we can;t send them any money
Correct
in other words, every customer of the website, will need to have a flow in their account to verify their account with stripe
and only after that they will be eligible to receive funds
am I correct?
(Also apologies for many questions, I'm the scrum master / client liaison and I am looking at it from user perspective rather than the dev one)
Correct. The onboarding is a slightly different flow for each of the 3 Connect types (express, custom, and standard), but the information they would need to provide would be the same
ok, fair enough, either way it is additional flow with document upload, and hence a bit difficult for the user. nonetheless might be necessary
Are there any outstanding questions?