#khadim_code
haughty sequoiaBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1389973713390272544
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
opal bay
Ah thats very bad, okay question then.
If a user want to buy something a payment flow is initiated from directly over the connected account. If a user now adds a payment method, this method is added to the connected accounts customer. If the customer now buys from a different connected account, he has no access to his payment methods.
How could this be solved in a great ux way ?
So basically:
- User buys from connected account A, adds credit card
- User buys again from connected account A, reuses credit card
- User buys from connected account B, no credit card, he has to reenter his payment details.
untold lark
There's a few ways you can handle.
- You can tokenize payment method on platform account always and then copy to the respective connect accounts when necessary via: https://docs.stripe.com/connect/direct-charges-multiple-accounts
- You can use org payment method sharing: https://docs.stripe.com/get-started/account/orgs/sharing/customers-payment-methods
- You can do destination charges instead where payment method details and payment are always on platform account and funds are just transferred to the connect account: https://docs.stripe.com/connect/destination-charges
opal bay
Awesome thanks for this !!!
For the second option, is it a problem if conencte accounts are not associated with the same company. So basically if they belong to different companies than the platform account ?
untold lark
You mean if a connect account is a different legal entity from its platform account?
opal bay
yyes
untold lark
Connect accounts usually have different legal entities from the platform
That's the most common connect scenario
But that shouldn't impact anything
opal bay
Okay there is one more issue, in our privacy texts we state that only conencted accounts can see custiomers that really buy from them. With that solution "After one account in the sharing group creates a customer," every connected account sees every customer right ?
untold lark
Correct
opal bay
Okay super valuable feedback thanks so much for your quick support! Appreciated alot!
untold lark
No problem
opal bay
If we would use the first option with tokenization on the platform account. Can we prevent users to input new payment methods in the payment flow ?
untold lark
You would have to build this logic yourself
To not surface the payment element conditionally